It looks like Maven 2.0.9 is refusing to resolve the JRuby 1.0 dependencies
due to a self referential property in its POM:
[WARNING] POM for 'org.jruby:jruby:pom:1.0:test' is invalid. It will be
ignored for artifact resolution. Reason: The POM expression:
${java.specification.version} could not be evaluated. Reason: Expression
value '${java.specification.version}' references itself in
'org.jruby:jruby:jar:1.0'. for project org.jruby:jruby at Artifact
[org.jruby:jruby:pom:1.0:test]
Obviously the ${java.specification.version} property should be resolved via
system properties, so I am wondering if there is a change in property
resolution order or something similar that has caused this to start failing
where it was working with 2.0.8.
The property entry:
<java.specification.version>${java.specification.version}</java.specification.version>
I would think that this should resolve to the system property first and not
cause the failure to resolve, but I wanted to pass this along here before
filing a bug. Thoughts?
Chris
