Attached find what I refer to as jboss-3.2.5-r1.ebuild. The jboss-3.2.5.ebuild currently in portage makes some assumptions about classpath settings and jar file availabilities, but there is nothing within the ebuild that says "Hey, add these to your classpath before you emerge jboss". The attached ebuild file tries (for the most part) to stick with java-config to pull in the required classpath stuff to get jboss 3.2.5 to compile. The exception is the necessary j2ee.jar file... Without a better source, I added sun-j2ee as a dependency to pull it in (perhaps there's better choices, but I'll leave that up to the maintainers to decide).
Created attachment 70825 [details] jboss-3.2.5-r1.ebuild
In the future, please submit patches against existing ebuilds instead of attaching the whole ebuild. This makes it easier to see what was changed/deleted/removed. Could you please include the logs of the errors you get when trying to build? I suspect that something else may be skewed, but it is hard to say without logs. The way you're tweaking the CLASSPATH seems a bit misguided to me: * First of all, you would need to DEPEND/RDEPEND on the packages you will be calling java-config -p on, to make sure they are available. * Second, there are helper functions in java-pkg to handle this instead of directly calling java-config: java-pkg_getjars is what you want in this case. * Thirdly, you should not need to include j2ee.jar from sun-j2ee.... JBoss builds its own copy of j2ee.jar.
