Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 261307

Summary: [java-experimental] dev-java/jaranalyzer-1.2
Product: Gentoo Linux Reporter: Ralph Sennhauser (RETIRED) <sera>
Component: [OLD] JavaAssignee: Java team <java>
Status: RESOLVED OBSOLETE    
Severity: enhancement Keywords: InOverlay
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://www.kirkk.com/main/Main/JarAnalyzer/
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 259027    
Attachments: The ebuild
The patch mentioned in the ebuild
more invasive patch
The new ebuild
release candidate
The patch exceeded the size of the build.xml
added default filters and two launch scripts

Description Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-05 13:05:57 UTC
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:
Comment 1 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-05 13:07:17 UTC
Created attachment 184006 [details]
The ebuild
Comment 2 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-05 13:08:00 UTC
Created attachment 184007 [details, diff]
The patch mentioned in the ebuild
Comment 3 Serkan Kaba (RETIRED) gentoo-dev 2009-03-05 13:44:12 UTC
(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.
Comment 4 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-05 15:24:31 UTC
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.
Comment 5 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-05 15:25:10 UTC
Created attachment 184025 [details]
The new ebuild
Comment 6 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-06 23:12:54 UTC
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.
Comment 7 Serkan Kaba (RETIRED) gentoo-dev 2009-03-07 02:19:59 UTC
(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

Comment 8 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-07 20:11:27 UTC
Created attachment 184266 [details]
release candidate

This ebuild contains a lot of improvements, thanks for clearing my questions.
Comment 9 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-07 20:13:37 UTC
Created attachment 184267 [details]
The patch exceeded the size of the build.xml
Comment 10 Ralph Sennhauser (RETIRED) gentoo-dev 2009-03-19 18:23:18 UTC
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.
Comment 11 Ralph Sennhauser (RETIRED) gentoo-dev 2009-04-08 10:44:21 UTC
An new version with lots of improvements can now be found here: http://overlays.gentoo.org/proj/java/browser/java-experimental/dev-java/jaranalyzer
Comment 12 Patrice Clement (RETIRED) gentoo-dev 2015-09-30 19:48:34 UTC
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