From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041228 Firefox/1.0 Fedora/1.0-8 Description of problem: Currently build-classpath requires you to specify the transitive closer of jars required by a given program. The calculation of dependency jars should be done automatically instead. We've considered two sources for the dependency information used by the script: 1) the RPM database and 2) autogenerated dependency data files installed by each package. Such a script would be useful both on the command line, but also in RPM spec files and possibly even within Eclipse (e.g. we could add an "autogenerate classpath" button to Eclipse's "Add Jars" dialog). A further improvement to the script could be the ability to point it at a java source tree and have it caculate the required build classpath. Likewise for a jar file (though I'm not sure how doable that is). The ultimate step would be to build this classpath generation into the java command itself, and so eliminate classpath munging altogether (again, I'm not sure this is possible in the general case). For now though, we should focus on extending build-classpath so that only the direct dependencies of a given program must be specified, and indirect dependencies will be auto-resolved. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. try building a complex classpath Additional info:
Is this bug still relevant?
Adding patrickm to the cc list as the manager of the disabled user fitzsim who reported this bug
This bug has stayed opened for far too long and I don't see it happenning. Not to mention the technical difficulties to properly calculate the classpath with reflections and etc. Once there is a proper java modules system this will be achievable. Closing as wontfix.