Re: JPackage 6.0: maven22 requires maven-plugin-testing-harness which doesn't exist
David Walluck <[email protected]>
| Newsgroups | gmane.linux.jpackage.general |
|---|---|
| Message-ID | <[email protected]> |
On 04/05/2012 10:19 AM, Michel Jouvin wrote: > I'm trying to install maven22 from JPackage 6.0. Unfortunatly is has a RPM > dependency on maven-plugin-testing-harness but only > maven-shared-plugin-testing-harness can be found. According to a private > exchange with David Walluck (Maven packager), they are not the same. Any > chance to see the missing piece showing up in the short term? I uploaded maven-plugin-testing-1.2-10.jpp6. Give it a try. I have not had time to test maven22 much, so you're likely the first one who is trying to test this. I changed the Epoch in maven-plugin-testing from 0 to 1, so be warned. I am thinking that the 1 epoch will help with removing maven-shared-plugin-testing-harness automatically in order to avoid conflict between the old and new versions of this package There is an issue with having both maven versions installed at once. This will not work because what happens is that there is a shared map in /etc/maven/fragments that makes it impossible to have more than one version of a an artifact with the same maven groupId:artifactId. In this case, we can only deal with one version of the maven core at a time for now until we fix that issue with our resolver. It turns out that the plugins can generally be shared between maven 2.0 and maven 2.2 (or maven 3), so most of the plugins do not have this issue. I also have work on maven 3.0.4 in progress, but no estimate on when this work will be completed.