Xavier Hanin wrote:
Damned, is it yet another trick in maven 2? The problem here is not much the
use of profiles, but that in the profile a plugin is configured to publish
an artifact with a specific classifier:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<configuration>
<classifier>jdk15</classifier>
</configuration>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
I don't even know if depending on this module with no classifier works in
maven based on the profile information, but we support maven classifiers in
Ivy trunk version, at least when they are expressed in the pom:
https://issues.apache.org/jira/browse/IVY-418
ok, I will have a look
But here we could know testng is publishing a classifier artifact based on
the maven-jar-plugin details. But I don't know if it's something maven does
or not, and if it's standard or not. So for the moment if you want to
declare a dependency on testng I would do something similar to what is
internally generated by Ivy when converting a pom with a dependency like:
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>5.7</version>
<classifier>jdk15</classifier>
</dependency>
that's all I need! Is there going to be a beta soon, or do I need to
build everything myself ?
which should be something like:
<dependency org="org.testng" name="testng" rev="5.7">
<artifact name="testng" type="jar" ext="jar" classifier="jdk15" />
</dependency>
If you have time to give maven 2 a test to see if it works without the
classifier in the dependency declaration, I'd be interested to know.
ahh, something else to install.
