search

jsuereth / scala-mojo-support

Helper to create maven mojo projects in the Scala languages
BSD 3-Clause "New" or "Revised" License
20 stars 10 forks source link

Docs #12

Closed rossabaker closed 11 years ago

rossabaker commented 11 years ago

Documents the cross build in the README and the mvn site.

rossabaker commented 11 years ago

7cfa96b fixes mvn:site, but integration tests are broken.

Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find org.scala-tools:scala-mojo-support:jar:0.5-SNAPSHOT in http://scala-tools.org/repo-releases was cached in the local repository, resolution will not be reattempted until the update interval of scala-tools.org has elapsed or updates are forced
rossabaker commented 11 years ago

Install on master (5d70901f2c) is broken, too. This is the problem worked around in 7cfa96b.

[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.1.0:doc-jar (attach-javadocs) on project scala-mojo-support_2.9: Execution attach-javadocs of goal net.alchim31.maven:scala-maven-plugin:3.1.0:doc-jar failed: Failed to build parent project for com.jsuereth:scala-mojo-support_2.9:jar:0.5-SNAPSHOT: Some problems were encountered while processing the POMs:
[ERROR] [ERROR] 'dependencies.dependency.version' for org.scala-lang:scala-library:jar must be a valid version but is '${scala.version}'. @ line 73, column 16
[ERROR] [ERROR] 'dependencies.dependency.version' for org.scala-lang:scala-compiler:jar must be a valid version but is '${scala.version}'. @ line 78, column 16: 2 problems were encountered while building the effective model for com.jsuereth:scala-mojo-support:0.5-SNAPSHOT
[ERROR] [ERROR] 'dependencies.dependency.version' for org.scala-lang:scala-library:jar must be a valid version but is '${scala.version}'. @ line 73, column 16
[ERROR] [ERROR] 'dependencies.dependency.version' for org.scala-lang:scala-compiler:jar must be a valid version but is '${scala.version}'. @ line 78, column 16
[ERROR] -> [Help 1]

Seems to me this "abstract" scala.version is causing multiple problems: the parent pom mentioned in your code comment, plugins complaining about it not being defined in the parent at various stages, etc. I'm leaning toward git-branch-per-bincompat being a better strategy here. As a bonus, I could clean up the SIP-18 warnings in Scala 2.10.

rossabaker commented 11 years ago

scala-2.10.0-RC2 commited to my fork's scala-2.10.x. Can submit as a separate pull request if this is the desired approach.

jsuereth commented 11 years ago

Yeah, let's do separate git branches.

jsuereth commented 11 years ago

Cool, this LGTM now. Thanks much for the work!