[
https://jira.jboss.org/jira/browse/JBIDE-4817?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
I've discovered why using the maven action fixes the three missing files, and it has
nothing to do with either the module factory or the deployer.
It turns out, this action moves 3 files from booking/src/main/resources into
booking/src/main/webapp/webinf/classes
I would imagine the reason they've moved / coppied these three files was because of
the isSingleRoot bug which the m2eclipse team perhaps never discovered, and so their
action found it easier to copy the files directly into a mapped and recognized folder
rather than try to discover the source of this bug.
So... I've satisified my curiousity about that anomoly.
Snjezana: If you can tell me which files exactly are missing from the deployment and
where the files originate from, I'd be very happy to continue investigating this bug.
However at this point I've been unable to replicate it. The web-inf/lib folder *does*
contain libraries even before adjusting the action.
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