I have a couple of projects that each reference to a "common" project. This
common project itself has a number of external jars it uses that are placed in
the lib dir of this project. These jars are only needed for the common
classfiles, not the other projects.
When I reference the project from my main project, only the jar with the
common classfiles is created, not including the classfiles of the external
My solution so far is to redefine the pre-jar target of the common project, in
which I unjar the external libs in the build dir, which means they will be
incorporated into the common jar. The drawback of this is when I have selected
the option "build projects on classpath" in my main project, it will unjar the
external libs of the common project, each time I build the project. This makes
me select/unselect the option when I'm working/not working on the common
project, which is a bit cumbersome.
It would be great if there would be an option to include the classfiles of the
external jars in a project jar, which can then be referenced by other projects
as a single working entity, without further hassle of dealing with the
dependencies of the "common" project.
A solution would be to add an option "include classfiles of libraries in jar"
in the libraries tab.
At the same time, this would remove the need for people who want to
redistribute a project with external jars as a single jar, to include the
unjar in the pre-jar in the build.xml.
Please help me if I'm missing some option that can resolve this issue in other
Probably duplicate of something filed; also a FAQ entry in the wiki somewhere, I
Yes, it is a duplicate of #70077
*** This issue has been marked as a duplicate of 70077 ***