Doug,
We are using the following as a key for artifact matching:
a.getGroupId() + ":" + a.getArtifactId() + ":" + a.getVersion() + ":" +
a.getClassifier();
while back type used to be included instead of classifier but it been
changed at some point.
The best would be to create JIRA issue and attach project that would
allow to reproduce issue and which we could also use for our test suite.
Also see the following page for some hints at the following document.
http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues
Thanks
Eugene
Doug Bateman wrote:
I'm having problems using the M2 plugin (both the latest and prior
versions) when my pom has reference to both the jar and the test-jar
for an artifact. e.g.
<project>
...
<dependencies>
<dependency>
<groupId>com.thecompany</groupId>
<artifactId>my-project</artifactId>
<version>2.0</version>
</dependency>
<dependency>
<groupId>com.thecompany</groupId>
<artifactId>my-project</artifactId>
<version>2.0</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
</dependencies>
...
</project>
Maven itself behaves just fine. But the plugin only includes one of
the two plugins, because it's checking that the artifactId and groupId
are the same, but ignoring the fact that the type is different. This
occurs both on the latest plugin as well as in prior versions. Is
anyone else having this problem? I haven't checked Jira yet (but
will), but before I submit any issues on it, I want to confirm this
exists for others too.
Thanks,
Doug
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
