[
https://jira.jboss.org/jira/browse/JBIDE-4817?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
I've also found an NPE in jee tools, but its root cause seems to step from an error in
m2eclipse. Specifically, JavaEEBinaryComponentLoadAdapter.recomputeArchivePath() looks for
the following archive path:
M2_REPO/org/jboss/seam/examples/booking/1.0.0/booking-1.0.0.war
This is a var-type path so it's assuming M2_REPO will be replaced with the variable
value from eclipse. It *does* do this, and this resolves to:
/home/rob/.m2/repository/org/jboss/seam/examples/booking/1.0.0/booking-1.0.0.war
However this file does not exist on my machine at all. The closest thing I have in my
maven repo is:
/home/rob/.m2/repository/org/jboss/seam/examples/jboss-seam-booking/2.1.0.GA/
I have not yet figured out why it is asking for this var reference. It is not a reference
listed in the component.xml so I find it highly odd how this is being used by m2eclipse.
Very odd indeed.
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
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