In the most recent jboss 3.2.1 ebuild, the code that copies the client jars to /usr/share... is commented out. Unfortunately, this also means that neither a classpath.env nor a package.env is created. java-config depends on one of those being there in order to manage classpaths. While I am fine with leaving the client jars in the /opt/jboss tree, there should be a package.env that points a classpath fragment at them. Maybe a re-factoring of java-pkg_dojar to allow finer grained control is in order. Pos- sibly some way to declare that certain jars should be in the package classpath but without forcing them to be in the /usr/share tree. Reproducible: Always Steps to Reproduce: 1. remove any old jboss artifacts 2. ebuild /usr/portage/net-www/jboss/jboss-3.2.1.ebuild 3. try starting and stopping the service 4. try java-config --list-available packages Actual Results: In step 3: Both the start and stop commands issue a warning that the package is not installed. (this comes from the use of config-java inside the conf.d/jboss script). In step 4: jboss is not listed Expected Results: step 3: no issued a warning step 4: jboss should be listed
please check that jboss-3.2.1-r1 corrects this bug
fixed
