Created attachment 366982 [details] jdom-2.0.5.ebuild Here is an initial version bump ebuild for jdom 2.0.5. Its a but crude could be cleaned up and still a few things to be done. Also I believe jdom-jaxen also needs to be updated based on the same sources, but its its own ebuild/package. Not sure if this one still depends on that or not. Again its very initial and crude, but does compile and install. Just needs to be dialed in, cleaned up, etc. Like I had to do 3 lines of sed, because I could not get sed or grep to match/ingore patterns at same time. Remove all test classes when test use flag is not set, but need to keep PerfTest.java class for Performance test. Though that class and the other classes in the perf folder are not necessary to jdom function, but performance tests. I guess that could be built under test but its added complexity.
*** Bug 517826 has been marked as a duplicate of this bug. ***
Created attachment 399324 [details] jdom-2.0.6.ebuild
Updated ebuild for 2.0.6. This is slotted to 2, for jdom v2. It does not need minor/revision slots. That is left over stuff from before. Nothing uses this at the moment. It should be safe to add as is. This ebuild should be good to go for the most part. But review for any errors, etc before commit to tree.
Hi William If I comment out parts that call on javadoc documentation, the ebuild works fine. Lines that cause problems: - in src_compile(): 55: use doc && \ 56: javadoc -d "${S}"/docs -cp ${cp} "@${T}"/src.list \ 57: -Xdoclint:none -quiet || die "javadoc failed" - in src_install(): 67: use doc && java-pkg_dojavadoc docs Otherwise, the rest looks good and works as expected. Thanks.
Looks to be that -cp for javadoc is non-standard, or not implemented in all jdks. That needs to be changed to -classpath for javadoc only. However it also looks like icedtea does not support -Xdoclint:none, which seems to be required for jdk >=1.8. I think due to increased strictness on javadocs. I will have to revise the ebuild to do some things differently for jdk 1.8. I will submit a revised ebuild.
Rather than fixing this ebuild. I think something needs to be done in an eclass to detect if the jdk is >= 1.8, and if so set the -Xdoclint:none parameter for javadoc. Otherwise I bet many packages will have issues with that. At the same time if the jdk is <1.8, it will not recognize that option as its new. That would be the best approach, rather than doing this within each ebuild.
Created attachment 399436 [details] jdom-2.0.6.ebuild
Updated ebuild that uses ejavadoc which has a check for the version and sets appropriate flag if the compiler is >=1.8. Requires ejavadoc to be added to java-utils-2.eclass.
+*jdom-2.0.6 (04 Apr 2015) + + 04 Apr 2015; Patrice Clement <monsieurp@gentoo.org> +jdom-2.0.6.ebuild: + Version bump courtesy of William L. Thomson Jr. <wlt@obsidian-studios.com>. + Fix bug 496986. + I have commented out the doc USE flag as well as ejavadoc. We need to get this new function in if we want to use it in ebuilds.
I was going to get ejavadoc committed today anyway but was busy with family. Will do it now.