[MECLIPSE-184] Ear utility-jar are put in WEB-INF/lib of the wtp ear

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Auto Closed
• Affects Version/s: 2.3
• Component/s: WTP support
• Environment: Tested on Windows XP and Linux Ubuntu Dapper Drake
• Assignee: Unassigned
• Reporter: Elid OR
• Created: 02/Nov/06 02:07
• Updated: 06/Sep/15 20:44
• Resolved: 06/Sep/15 20:44

Description

It seems that the maven eclipse plugin add ear jar dependencies in the
WEB-INF/lib directory.

I've used the following command : mvn eclipse:clean
eclipse:eclipse -Dwtpversion=1.0 (I've also tried 1.5 with the snapshot
version)

And when deploy the ear project through WTP in a J2EE Server I see the
following structure :

my-ear
  |---- my-ejb.jar
  |---- my-webapp.war
  |---- META-INF/
                |---- application.xml
                |---- MANIFEST.MF
  |
  |----- WEB-INF/
                |---- lib
                        |---- dependency-1.jar
                        |---- dependency-2.jar

But I don't expect these dependencies to be here, I expect something like
this :

my-ear
  |---- my-ejb.jar
  |---- my-webapp.war
  |---- META-INF/
                |---- application.xml
                |---- MANIFEST.MF
  |
  |----- dependency-1.jar
  |----- dependency-2.jar

So I've checked quickly the SVN repository and it seems that the directory in
which we put "ear utility jar" is hard coded as "WEB-INF/lib" (->
AbstractWtpResourceWritter.addDependency() which is the same for the war and the ear ... )

Are you OK with this packaging ? It can be a good thing if we could configure where wtp will
put these ear utility-jars and by default it would be in "/" or "lib".

Thanks In Advance

Elid OR

Issue Links

• is related to: MECLIPSE-167 .component assumes all dependencies should be packaged in WAR
• relates to: MECLIPSE-360 Optional web app dependencies are not treated the same way as maven-ear-plugin