Comments (6)
I'm happy to type my Sonatype password in if we can get to that stage! What needs to be done?
By the way, thanks for putting this into an issue - it's the only way I won't forget...
from contextual.
I'll need to double check, but according to our gitter conversation on the subjet a while ago, what remains is typing your sonatype password :)
from contextual.
Ok, I just worked out the issue. The macros are not compatible, and I'll need to have different source. Scala 2.10 doesn't recognise TermName
.
from contextual.
Ok, @nrinaudo: It was a three-character fix to the source which breaks it for Scala 2.11+, so I just made the change locally, sbt publishSigned
it, then discarded the change, and 1.0.1 is now published for Scala 2.10, but don't tell anyone this is how I did it.
from contextual.
But.. but does it mean you're going to have to do this for every new version?
(Also, how did you publish 1.0.0 then??)
from contextual.
Yep, I know. ;)
I may have done the same for 2.10, and forgotten, as I wish to do about this time. Maybe this delayed-release process should be a way of weaning people off 2.10...?
from contextual.
Related Issues (20)
- How does type embedding work? HOT 1
- Don't depend on scala-compiler
- Scala 2.13 release HOT 4
- Error macro has not been expanded in Scala 2.13.0 HOT 2
- 'scala.reflect.macros.whitebox.Context' is missing from the classpath
- Outdated docs
- The latest Fury layer doesn't contain classes from the data module
- Check version 2.0.0 works correctly HOT 1
- Embedding custom types not working with version 2.0.0 HOT 7
- contextual version 3.0.0 prints interpolated text during compile HOT 4
- Represent substitution types with an `enum` HOT 1
- Offer type refinements on return types HOT 2
- Use `Text` instead of `String` in the Contextual API
- Check if there is a reason why `Interpolator` methods cannot be `protected`
- Provide a simpler `Verifier` type for interpolations without substitutions
- Obviate need to specify companion object twice
- Offer better error message when failing to substitute `Nothing`
- Make it easier to refine the return type
- Make `PositionalError` a top-level class
- Consider using `boundary`/`break` to avoid throwing
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from contextual.