Jar for Scala 2.9 and 2.10 #49

Closed
dnadolny opened this Issue May 6, 2013 · 5 comments

Comments

Projects
None yet
2 participants
@dnadolny
Contributor

dnadolny commented May 6, 2013

Right now, scalagen is only compiled for Scala 2.9. I'm working on a Scala IDE plugin backed by scalagen, but in order to have it available for both Scala IDE targets I need a version of the scalagen jar compiled for Scala 2.10 (as well as 2.9).

It would be ideal if scalagen was published to a maven repository for both versions, using the sbt naming convention. To do it manually, in the pom.xml you would change the scala.version property to 2.10.1 and change the artifactId to scalagen_2.10.1 and publish that, and again for 2.9.3 (or 2.9.1 if there's a reason to stick with that). See http://mvnrepository.com/artifact/com.typesafe.akka for an example of this.

@timowest

This comment has been minimized.

Show comment Hide comment
@timowest

timowest May 7, 2013

Owner

Is it possible to do this easily in Maven? Using classifiers seems easier. Manual cross deployment is not an option.

Owner

timowest commented May 7, 2013

Is it possible to do this easily in Maven? Using classifiers seems easier. Manual cross deployment is not an option.

@dnadolny

This comment has been minimized.

Show comment Hide comment
@dnadolny

dnadolny May 7, 2013

Contributor

It seems possible to do it with classifiers, where the classifier name is the scala versions (combined with specifying the scala.version property on the command line or via profile).

Contributor

dnadolny commented May 7, 2013

It seems possible to do it with classifiers, where the classifier name is the scala versions (combined with specifying the scala.version property on the command line or via profile).

@timowest

This comment has been minimized.

Show comment Hide comment
@timowest

timowest May 7, 2013

Owner

Feel free to patch it. A classifier based solution is ok for me.

Owner

timowest commented May 7, 2013

Feel free to patch it. A classifier based solution is ok for me.

@dnadolny

This comment has been minimized.

Show comment Hide comment
@dnadolny

dnadolny May 7, 2013

Contributor

One note: this doesn't exactly match the convention since classifiers are separated from the artifactId by a hyphen rather than an underscore, which means that it will be harder to add scalagen as a dependency for sbt users that want to cross compile. Maybe there's a way to change that, I'll look in to it. Being separated by a hyphen works for what I need though, so maybe that's good enough

Contributor

dnadolny commented May 7, 2013

One note: this doesn't exactly match the convention since classifiers are separated from the artifactId by a hyphen rather than an underscore, which means that it will be harder to add scalagen as a dependency for sbt users that want to cross compile. Maybe there's a way to change that, I'll look in to it. Being separated by a hyphen works for what I need though, so maybe that's good enough

@timowest

This comment has been minimized.

Show comment Hide comment
@timowest

timowest May 9, 2013

Owner

Implemented here mysema#50

Owner

timowest commented May 9, 2013

Implemented here mysema#50

@timowest timowest closed this May 9, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment