The package log4j and possibly others that depend on the sun-jmx package pull in a package that needs to be downloaded from sun servers due to restrictions in the license. However, in the URL that I pasted for this bug report it mentions that java platforms 5 and 6 contain JMX so this package is useless now. It can be eliminated and replaced with a virtual or something else. If a person uses any java version less than 5 then they need the JMX package, but I don't see any reason to use less than version 5 except for really old software. Please fix this so programs do not need to depend on a fetch restricted file. Sun changed the license so that java can be downloaded without a manual fetch and it contains jmx, so this just needs to be changed. I know log4j is one program depending on this via use flag and I think that use flag is there only because of the fetch restriction, but now if version 5 or better of java is detected, then there is no need for a use flag and jmx can be enabled automatically because jmx will already be available. At least to me it makes sense. Thanks. Reproducible: Always Steps to Reproduce:
By some TV magic... There will be a new release of java-config-2 that does just this. we are planning on having a java-virtuals/jmx to allow for this.
is there a way to emerge hibernate without messing with sun-jmx? hibernate depends on =dev-java/swarmcache-1* dev-java/swarmcache-1.0_pre20050106-r1 depends on >=dev-java/jgroups-2.2.7 dev-java/jgroups-2.4.1_p1-r1 depends on dev-java/sun-jmx should i keep a modified jgroups ebuild in a local tree?
I will attempt to update the hibernate ebuilds this weekend to close this bug. Especially seeing that java-config-2.1.4 is being stabilised
There is now a java-virtuals/jmx in the tree.
