*maven-bin-2.2.1 (11 Sep 2009) 11 Sep 2009; Miroslav Šulc <fordfrog@gentoo.org> +maven-bin-2.2.1.ebuild: Version bump. maven-2.2.1 contains jdk 1.5 jar so it needs >=virtual/jdk-1.5 *maven-bin-2.1.0 (12 May 2009) *maven-bin-2.0.10-r1 (12 May 2009) 12 May 2009; Alistair Bush <ali_bush@gentoo.org> +maven-bin-2.0.10-r1.ebuild, +maven-bin-2.1.0.ebuild: Add support for eselect-maven. Required as mvn have made possible incompatiable changes to 2.1.
Created attachment 225977 [details] ebuild for maven-2.2.1 Just some slight changes to the existing maven-bin-2.0.11.ebuild and it's possible to emerge maven 2.2.1. It looks like it's working but I'm just a gentoo user.
dev-java/maven-bin-2.0.11 is ready
(In reply to comment #1) > Created an attachment (id=225977) [details] > ebuild for maven-2.2.1 > > Just some slight changes to the existing maven-bin-2.0.11.ebuild and it's > possible to emerge maven 2.2.1. > It looks like it's working but I'm just a gentoo user. > I don't understand this patch. maven 2.2.1 is already in the tree. If you have a build failure you should open a new bug.
Petteri Räty: I failed to notice that the ebuild was already in the portage tree (probably a sleepless nigh or something of the kind). Kindly disregard the attachment. What about changing the but status to prevent dorks such as me to input more noise.
(In reply to comment #4) > > What about changing the but status to prevent dorks such as me to input more > noise. > There's nothing wrong with the status. This is about changing keywords from testing to stable.
x86 stable
amd64 stable
Created attachment 251539 [details] 3.0 version 3.0 version released.
(In reply to comment #8) > Created an attachment (id=251539) [details] > 3.0 version > > 3.0 version released. > Please do not hijack a stabilization bug and file a new bug for version bump. By the way Jesse Farinacci committed 3.0 ebuild to java-experimental overlay. That can probably be added to tree (I don't know how to test it so I pass)
Latest PPC stable 2.0 slot directly symlinks as mvn as opposed to mvn-${SLOT}. This scheme is not supported anymore and this bug blocks the removal. Please proceed ASAP.
(In reply to comment #10) > Latest PPC stable 2.0 slot directly symlinks as mvn as opposed to mvn-${SLOT}. > This scheme is not supported anymore and this bug blocks the removal. > > Please proceed ASAP. Hi Serkan, I've tried to reproduce the error you mentioned, but was not able to. My installation worked as expected for 2.0 slot (specifically maven-bin-2.0.11 ebuild). I've used: "sudo emerge maven-bin:2.0" It created the symlink /usr/bin/mvn-2.0. Isn't this the expected behavior? I'm willing to have a look. Please let me know the exact procedure to reproduce the bug you mentioned.
(In reply to comment #11) > Isn't this the expected behavior? I'm willing to have a look. Please let me > know the exact procedure to reproduce the bug you mentioned. Try with exactly 2.0.10.
(In reply to comment #12) > (In reply to comment #11) > > Isn't this the expected behavior? I'm willing to have a look. Please let me > > know the exact procedure to reproduce the bug you mentioned. > Try with exactly 2.0.10. Yes, I was able to reproduce it. I've updated the patch for maven-bin-2.0.10 for the bug 355507 with relevant changes. The patch can be found at: http://bugs.gentoo.org/attachment.cgi?id=270869&action=edit
ppc stable, last arch closing
