[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4817) WTP EAR deployers don't work correctly when using some classpath containers (Maven, for instance)
[
https://jira.jboss.org/jira/browse/JBIDE-4817?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-4817:
--------------------------------------
We are using the same version of WTP.
I have fixed this issue within the booking example by making the booking project not to be
singleRoot -
https://jira.jboss.org/jira/browse/JBIDE-4817?focusedCommentId=12483014#a....
If you want to reproduce the issue again, you need to do the following:
- install/update m2eclipse >= 0.9.9.20090820
- define Seam Runtime 2.1.1.GA and DefaultDS connection profile (they can be set after
checking out Maven projects)
- open the https://svn.jboss.org/repos/jbosstools/workspace/snjeza/booking-mavenized/
directory in the SVN Repositories view
- select the booking, booking-ear, booking-ejb and booking-parent directories and call
"Check out as Maven Project ..."
You will get the booking application that is deployed correctly to the JBoss AS server.
Sometimes, it is necessary to refresh the booking project. I think this is a problem with
m2eclipse maven builder.
- refresh the booking project
- right-click the booking project, select Properties>Java Build Path>Source
- uncheck "Allow output folders for source folders"
- change the default output folder to /booking/src/main/webapp/WEB-INF/classes
This make the booking project a singleRoot project.
- deploy the project (call Full Publish)
WEB-INF/lib isn't deployed correctly within the booking project (as well as the files
Rob mentioned)
Maven>Update Project Configuration adds the above mentioned line to the
org.eclipse.wst.common.component.xml file which makes the booking project non-singleRoot
and fixes the issue.
Anyway, the current booking project isn't singleRoot and can be deployed correctly to
the JBoss AS which, in my opinion, fixes this issue.
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