ScalaNLP checkout broken?
Steven Bethard
and see what it looks like these days. But a straightforward checkout
seems to be broken, as a "mvn compile" from the top level gives:
[ERROR] Failed to execute goal on project scalanlp-data_2.8.1.RC2:
Could not resolve dependencies for project
org.scalanlp:scalanlp-data_2.8.1.RC2:jar:0.3.2-SNAPSHOT: Failure to
find org.scalanlp:scalala_2.8.1.RC2:jar:0.4.2-SNAPSHOT in
http://scala-tools.org/repo-releases
The problem appears to be that only
org.scalanlp:scalala_2.8.0:jar:0.4.2-SNAPSHOT is in the repo, not the
2.8.1.RC2 version. Changing the scala-version property in
scalanlp-data to 2.8.0 fixes the dependency problem but then the code
doesn't compile:
scala.tools.nsc.FatalError: package <empty> does not have a member object
at scala.tools.nsc.symtab.Definitions$definitions$.getMember(Definitions.scala:492)
Hard coding the version 2.8.0 in the dependency declaration gets rid
of the dependency problem and allows compilation with maven on the
command line, but causes Eclipse to hemorrhage because of the multiple
versions of the scala compiler and libraries.
Is there a current workaround for this? I assume the longer term plan
is to use scalala 1.0, but in the meantime...
Steve
P.S. Some other things maven doesn't like in the current poms:
[WARNING] Some problems were encountered while building the effective
model for org.scalanlp:scalanlp-data_2.8.1.RC2:jar:0.3.2-SNAPSHOT
[WARNING] 'artifactId' contains an expression but should be a
constant. @ org.scalanlp:scalanlp-data_${scala.version}:0.3.2-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/data/pom.xml, line 16, column 15
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-eclipse-plugin is missing. @
org.scalanlp:scalanlp-data_${scala.version}:0.3.2-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/data/pom.xml, line 153, column
15
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.scalanlp:scalanlp-learn_2.8.1.RC2:jar:0.3.2-SNAPSHOT
[WARNING] 'artifactId' contains an expression but should be a
constant. @ org.scalanlp:scalanlp-learn_${scala.version}:0.3.2-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/learn/pom.xml, line 10, column
15
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:cobertura-maven-plugin is missing. @
org.scalanlp:scalanlp-learn_${scala.version}:0.3.2-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/learn/pom.xml, line 99, column
15
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-eclipse-plugin is missing. @
org.scalanlp:scalanlp-learn_${scala.version}:0.3.2-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/learn/pom.xml, line 135, column
15
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.scalanlp:scalanlp-graphs_2.8.1.RC2:jar:0.1-SNAPSHOT
[WARNING] 'artifactId' contains an expression but should be a
constant. @ org.scalanlp:scalanlp-graphs_${scala.version}:0.1-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/graphs/pom.xml, line 10, column
15
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:cobertura-maven-plugin is missing. @
org.scalanlp:scalanlp-graphs_${scala.version}:0.1-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/graphs/pom.xml, line 68, column
15
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-eclipse-plugin is missing. @
org.scalanlp:scalanlp-graphs_${scala.version}:0.1-SNAPSHOT,
/Users/bethard/Projects/scalanlp-core/graphs/pom.xml, line 104, column
15
--
Where did you get that preposterous hypothesis?
Did Steve tell you that?
--- The Hiphopopotamus
David Hall
I think there's starting to be some amount of divergence between my
fork of Scalala (https://github.com/dlwh/Scalala branch oldstyle) and
Dan's, especially as Dan preps 1.0. I've been so overwhelmed with
school (I made pushes for 4 deadlines in the last 3 months), that I
haven't really had a chance to be a good Open Source Developer.
Don't worry about the warnings. It seems to be standard Scala practice
to use ${scala.version} in artifact names.
-- David
> --
> You received this message because you are subscribed to the Google Groups "ScalaNLP" group.
> To post to this group, send email to scal...@googlegroups.com.
> To unsubscribe from this group, send email to scalanlp+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/scalanlp?hl=en.
>
>
Steven Bethard
> I think there's starting to be some amount of divergence between my
> fork of Scalala (https://github.com/dlwh/Scalala branch oldstyle) and
> Dan's, especially as Dan preps 1.0. I've been so overwhelmed with
> school (I made pushes for 4 deadlines in the last 3 months), that I
> haven't really had a chance to be a good Open Source Developer.
No worries - it wasn't like I had an immediate use case for anything.
Just thought I should let someone know. ;-)
Good luck with your papers!
> Don't worry about the warnings. It seems to be standard Scala practice
> to use ${scala.version} in artifact names.
Yeah, the recommended solution to this is to use classifiers:
http://comments.gmane.org/gmane.comp.jakarta.turbine.maven.user/110613
But I guess if all the cool Scala kids are doing it the "wrong" way... ;-)
Steve