Shane Isbell wrote:
Another problem is that some poms in the repo contain uninterpolated
${mavenVersion} values. If we specify the runtime version of say Maven 3.0,
when the artifact provider compiled with Maven 2.0, then we could get all
sorts of nasty class cast exceptions. Outside of cleaning up the repo
metadata, I don't see how to solve this problem.
It cannot be solved outside of cleaning metadata: I came across a lot of
examples like that that either require specific code in the plugins or a
system property: http://jira.codehaus.org/browse/MNG-3856
For instance:
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.4/pom.xml
has a dependency:
<dependency>
<groupId>org.apache.maven.doxia</groupId>
<artifactId>doxia-sink-api</artifactId>
<version>${doxiaVersion}</version>
</dependency>
and no definition for ${doxiaVersion} in itself nor it's parents. So
it's either supplied by -D or ...
Maybe somebody has an insight on where those came from and how they are
interpolated by Maven 2 ?
Thanks,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
