This is an ebuild for jaranalyzer-1.2, a dependency of mockrunner. Should in such a case the doc flag be moved from JAVA_PKG_IUSE to IUSE instead so javadoc doesn't get called twice? Reproducible: Always Steps to Reproduce:
Created attachment 184006 [details] The ebuild
Created attachment 184007 [details, diff] The patch mentioned in the ebuild
(In reply to comment #0) > This is an ebuild for jaranalyzer-1.2, a dependency of mockrunner. > > Should in such a case the doc flag be moved from JAVA_PKG_IUSE to IUSE instead > so javadoc doesn't get called twice? > > Reproducible: Always > > Steps to Reproduce: > It's better if you pacth out clean dependency in doc target.
Created attachment 184024 [details, diff] more invasive patch removed dependency of target javadoc on clean removed dependency of target dist on javadoc so we call javadoc only if needed.
Created attachment 184025 [details] The new ebuild
jakarta-regexp isn't needed so I drop this one too. Slipped somehow through. As it doesn't matter witch junit would the following code be prefered over fixing it to a slot? has_version dev-java/junit:4 && java-pkg_jar-from junit-4 has_version dev-java/junit:4 || java-pkg_jar-from junit Also is there a possibility to do the same for the tasks ant-junit and ant-junit4? Should the test be patched out as well and only be built and executed if FEATURES test is enabled? Help is always appreciated.
(In reply to comment #6) > jakarta-regexp isn't needed so I drop this one too. Slipped somehow through. > > As it doesn't matter witch junit would the following code be prefered over > fixing it to a slot? > has_version dev-java/junit:4 && java-pkg_jar-from junit-4 > has_version dev-java/junit:4 || java-pkg_jar-from junit > That shouldn't be possible unless they wrote 2 set of tests for each since junit4 breaks api. Also that will cause runtime failures if the build time junit slot gets unmerged in favor of the other. > Also is there a possibility to do the same for the tasks ant-junit and > ant-junit4? > > Should the test be patched out as well and only be built and executed if > FEATURES test is enabled? Yes > > Help is always appreciated. > We (Java Devs) are @ #gentoo-java on FreeNode
Created attachment 184266 [details] release candidate This ebuild contains a lot of improvements, thanks for clearing my questions.
Created attachment 184267 [details] The patch exceeded the size of the build.xml
Created attachment 185552 [details] added default filters and two launch scripts This version contains the default Filter.properties file in jaranalyzer.jar. If the need for someone arises to alter this file, please leave a comment in this bug, so a more appropriate location can be found for it. Also there are now two lunch scripts namely jaranalyzer-run-xml and jaranalyzer-run-dot to conveniently make use of the two standalone Use Cases. The usage is simple: there are no parameters for both.
An new version with lots of improvements can now be found here: http://overlays.gentoo.org/proj/java/browser/java-experimental/dev-java/jaranalyzer
commit b69dcfc (HEAD, master) Author: Patrice Clement <monsieurp@gentoo.org> Date: Wed Sep 30 19:46:51 2015 +0000 dev-java/jaranalyser: Upstream dead. Cleaning it up. Fixes bug 261307. Signed-off-by: Patrice Clement <monsieurp@gentoo.org> delete mode 100644 dev-java/jaranalyzer/ChangeLog delete mode 100644 dev-java/jaranalyzer/Manifest delete mode 100644 dev-java/jaranalyzer/files/build.xml delete mode 100644 dev-java/jaranalyzer/jaranalyzer-1.2.ebuild delete mode 100644 dev-java/jaranalyzer/metadata.xml
