[
https://jira.jboss.org/jira/browse/JBIDE-4817?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
Snjezana:
All of the bugs I listed in the first few comments were my fault. I was using an old
version of m2eclipse. YOu can ignore those.
The only bug I still have is about the WEB-INF/lib directory being in the ear root instead
of the war's. This is an eclipse bug which you linked to (247090).
Except for this everything seems to work exactly fine.
You say this:
If you add
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
to the booking/.settings/org.eclipse.wst.common.component file, booking.war/WEB-INF/lib
will be created correctly.
But my booking project already has this line in the component.xml directly after import.
Executing the maven -> update on the web project, as you suggest changes:
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/main/resources"/>
into
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/main/resources"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
If you look at this change, you'll see it didn't add or remove anything. It only
changed the order.
WTP EAR deployers don't work correctly when using some classpath
containers (Maven, for instance)
-------------------------------------------------------------------------------------------------
Key: JBIDE-4817
URL:
https://jira.jboss.org/jira/browse/JBIDE-4817
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, UpStream
Affects Versions: 3.1.0.M2
Reporter: Snjezana Peco
Assignee: Rob Stryker
Attachments: fixed.out, unfixed.out
Try the example described in
https://jira.jboss.org/jira/browse/JBIDE-4736?focusedCommentId=12482337#a...
If you try to deploy the booking-ear application, libraries in booking/WEB-INF/lib
won't be deployed.
booking/.settings/org.eclipse.wst.common.component contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="booking">
<wb-resource deploy-path="/"
source-path="/src/main/webapp"/>
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/resources"/>
<property name="context-root" value="booking"/>
<property name="java-output-path"/>
</wb-module>
</project-modules>
if you call Maven>Update Project Configuration,
booking/.settings/org.eclipse.wst.common.component will look as follows:
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="booking">
<wb-resource deploy-path="/"
source-path="/src/main/webapp"/>
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/classes"
source-path="/src/resources"/>
<wb-resource deploy-path="/"
source-path="/src/main/webapp"/>
<property name="context-root" value="booking"/>
<property name="java-output-path"/>
</wb-module>
</project-modules>
the libraries in booking/WEB-INF/lib will be deployed correctly.
The problem exists when using JBoss Tools servers as well as using JBoss WTP Generic
servers.
The problem doesn't exist when using Export>Java EE>EAR File.
PS
The WEB-INF/lib directory and the required libraries are unnecessary added to the
EAR's root directory, but this issue is fixed with the patch attached to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247090.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira