Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross build for Scala 2.9 and 2.10 #11

Merged
merged 4 commits into from
Nov 12, 2012
Merged

Cross build for Scala 2.9 and 2.10 #11

merged 4 commits into from
Nov 12, 2012

Conversation

rossabaker
Copy link
Contributor

Use a separate POM for each minor version of Scala, and add it to the artifactId. Could do a _2.9.1, _2.9.2, etc., like SBT convention, but this won't be used by SBT anyway, so this is the minimum that supports binary compatibility.

Alternatively, 0.5 could just be the Scala 2.10.x release, but it's trivial to support both in case anybody enhances this.

I'll move the 2.10.0-RC2 pom to a simple _2.10 once it's final. Mainly want to get a Scalate port up and running, and this is one of our blockers.

* scala.StaticAnnotation went away in 2.10.x.
* Use 2.9.0 so it works for all 2.9.x.
* Adds _2.9 or _2.10.0-RC2 to artifact id.  When 2.10.0-final is
  released, will change artifact id to _2.10.

* To build, use mvn -f pom-${scala_version}.xml.  We could keep one
  POM with a variable in the artifactId, but this makes Maven sad.

* Cleans up compiler warnings introduced in 2.10.  Did not fuss about
  feature warnings in order to keep a unified source tree.
@jsuereth
Copy link
Owner

LGTM. If I was feeling fun, I'd set up an sbt build to do the cross-versioning and auto generate the poems.

jsuereth added a commit that referenced this pull request Nov 12, 2012
Cross build for Scala 2.9 and 2.10
@jsuereth jsuereth merged commit 5d70901 into jsuereth:master Nov 12, 2012
@jsuereth
Copy link
Owner

Oh, as an aside, can you update a READMe file about the cross build?

@rossabaker
Copy link
Contributor Author

Yes, I was going to circle back to the docs if the approach was ruled Not Crazy. Thanks for the merge.

I thought about the sbt generator too, and then I looked at my scar from building an sbt plugin in maven. That hurt mostly due to getting sbt libs in a maven repo, so this direction might be easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants