Bug 225659 – java-pkg_jarfrom --virtual virtual-name jarname.jar fails with JVM providers.

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Serkan Kaba (RETIRED) 2008-06-09 20:05:13 UTC]

This construct fails not finding the specific jar if compiled with a JVM provider.

Reproducible: Always

Actual Results:  
emerge dies with "Failed to find stax-api.jar in stax-virtual" message in the attached ebuild.

Expected Results:  
Possibly should skip creating a symlink if the MERGE_VM is the provider of the virtual.

dev-java/java-config: 1.3.7, 2.1.6

[Comment 1 Serkan Kaba (RETIRED) 2008-06-09 20:06:22 UTC]

Created attachment 156117 [details]
dom4j-1.6.1-r4.ebuild

Example ebuild to reproduce issue with stax-virtual in java-experimental overlay.

[Comment 2 Alistair Bush (RETIRED) 2008-06-10 06:55:27 UTC]

I don't see an issue with this,  your asking for a jar that it can't provide.

[Comment 3 Serkan Kaba (RETIRED) 2008-06-10 19:42:39 UTC]

(In reply to comment #2)
> I don't see an issue with this,  your asking for a jar that it can't provide.
> 

silently ignoring for jvm providers will work like a non-virtual package (the old way) for non-jvm providers and provide the needed classes from jvm's bootclasspath for jvm providers.