is there any way to explicitly specify where module dependency jars will
be stored in the resulting .ear file when project is published to the
server?
The problem i have is that there couple of jar files that should be
available (i.e. shared) to all modules in the ear file. The target
platform is Jboss which means that they have to be in lib directory
inside the .ear file. Application is 1.3 compliant hence there is no way
to use J2EE 5 methods of customizing location of the EAR libraries. But
when WTP publishing project (for internal run or debuging) to JBoss all
files appear in the root of the .ear file which makes them unavailable
to the EAR deployer classloader.
So, the question (as above) is can i explicitly specify where publisher
should put the jar files? I am digging into this problem for past couple
of weeks and seems like there is no easy way of doing this.
In case i am right and there is no easy way of doing this is there any
possible workaround for this. I can use ant build in order to do this
deployment to the externally configured server but it is confusing for
some developers in the team so it would be nice to have the easier
solution from the user's perspective.