Requesting testing and stabilization of both dev-java/jdom-1.1.3 & dev-java/jdom-2.0.6. This is a slot change for jdom 1.1.3 from 1.0 slot to :0. jdom 2.0.6 is in slot :2. Nothing is using jdom 2 yet. Packages that are presently using jdom:1.0 need to have their slot updated per bug 543958. However deps can't be updated till 1.1.3 is stabilized. If we are going to test and stabilize 1.1.3, might as well do it to 2.0.6. I use both of these extensively in my own custom business applications. 1.x has just had bug and security fixes. No regressions or anything that should or would cause issue for any apps with jdom:1.0 dependency. jdom 2.0.6 has a different package path, org.jdom2 vs org.jdom. Thus unless something uses that, which I do not believe anything in tree presently does. Not really any means to test that. I have switched most all my applications that used jdom 1.x over to jdom 2.x without any issue. No regressions etc. So most packages can likely just be updated from org.jdom to org.jdom2 without issue. But that is a task for upstreams. Either way there should be no reason to not stabilize both. There should not be any bugs from upstream, and the ebuilds themselves should be good to go. This would allow updating the jdom slot of other packages, and cleanup, as jdom has many older versions. Please do not remove jdom-1.0-r4.ebuild, as that is the current stable one. But anything older than that can go, including all beta ebuilds from long ago.
Arch teams please proceed. TIA.
amd64 stable
x86 stable
+ 16 Jun 2015; Patrice Clement <monsieurp@gentoo.org> jdom-1.1.3.ebuild, + jdom-2.0.6.ebuild: + Stable for ppc+ppc64 via ALLARCHES. Fix bug 548062 and bug 548062. +
