akhikhl
Compiling Scala with new 0.0.13-SNAPSHOT fails
Hi Andrey,
I'm compiling Scala in my of my projects. In 0.0.12 version it's just fine, but when trying to move up to the new snapshot version, I get the following: "Could not find any version that matches eclipse-luna-sr1:org.scala-lang.scala-library:+"
So I'm thinking the new version somehow changes my scala dependencies. Could you take a look?
Thanks!
Could you, please, provide simplest project, allowing to reproduce a problem?
I'm afraid I was unable to reproduce using a simple project (as you can imagine, the build project I'm working on is very, very, complicated).
I was however able to solve the issue by adding the following to my configurations{ all*.exclude group:'eclipse-luna-sr1', module: 'org.scala-lang.scala-library' }
I used "all" as looking at the "dependency" output, the dependency seems to be present in multiple configurations.
The original dependency is org.scala-lang:scala-library, so I guess for some reason the new wuff version "parses" that dependency in a way that adds the mavenGroup as the group and not the actual one, and creates the module as a concatenation of the original group and module. That's just an educated guess, can't find support for that in the code though.
Just a few more details - I'm building a multi-project setup, and this issue seem to be happening for other dependencies as well.
The other dependencies are project dependencies - they are set as plugin dependencies in the original manifest.mf file.
A short update - it caused the same issue with Xtend compilation - this time, it the "bad" dependency is the compiler itself: org.antlr.runtime became eclipse-luna-sr1:org.antlr.runtime:+ (the correct dependency is 'org.antlr:antlr-runtime'). The thing is, in this case, removing this dependency from the configurations causes the Xtend compiler to stop working (even when the correct dependency is added). This one is a real blocker, so I'm afraid I'll have to stick with version 12 until this problem is fixed (if ever).