[JBoss JIRA] Created: (JBIDE-4817) WTP EAR deployers don't work correctly when using some classpath containers (Maven, for instance)
1:38 p.m.
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
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
1:38 p.m.
New subject: [JBoss JIRA] Updated: (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 updated JBIDE-4817:
---------------------------------
Component/s: JBossAS
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
1:38 p.m.
New subject: [JBoss JIRA] Updated: (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 updated JBIDE-4817:
---------------------------------
Component/s: UpStream
(was: JBossAS)
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
7:10 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
There seemed to be several problems here. After importing the projects, several had
problems as they did not have a JRE / JDK on their build path. So none of them new what
Object or String were.
The web project's component.xml contained the following text:
<wb-module deploy-name="booking">
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
Clearly this is wrong. I am not sure why it was present so often but i suspect m2eclipse
is doing something it should not be doing when it's adding a reference.
Third, the problems view has the following error on the web project:
Cannot nest 'booking/src/main/webapp/WEB-INF/classes' inside 'booking'. To
enable the nesting exclude 'src/' from 'booking'
When I deploy, I don't see the web app at all most likely because of this error.
The Web application seems to be doing many many many odd and bad things. After closing and
re-opening the web project, I see this stack trace below. (Only root cause shown)
Caused by: Java Model Exception: Java Model Status [Source folder 'src/main/java'
in project 'booking' cannot output to library
'src/main/webapp/WEB-INF/classes']
at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:784)
at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:2873)
at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:2904)
at
org.eclipse.jst.j2ee.project.facet.J2EEFacetInstallDelegate.addToClasspath(J2EEFacetInstallDelegate.java:62)
at
org.eclipse.jst.j2ee.web.project.facet.WebFacetInstallDelegate.execute(WebFacetInstallDelegate.java:166)
at
org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1467)
This implies that the project is attempting to output its class files to somewhere in the
src/main folder tree, which is blatently not allowed as it would cause infinite recursion.
(Anything in src gets coppied to the build output folder, so if the output folder is also
in the source folder, it leads to problems). What would be better is if your output
folder was somewhere else in the project, but your component.xml file linked this build
output folder to be in the WEB-INF/classes inside the deployment
As a note, every time i close and re-open the web project, this line is added to the
component.xml file. Eventually there are dozens and dozens:
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
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
7:14 p.m.
New subject: [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...
]
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
7:44 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
trying again actually obeying the version requirements from snjezana instead of using a
May version ;)
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
8:18 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
After installing the correct maven tools, I am unable to replicate this issue. Aside from
a few errors in the html (not closing tags etc) the differences between before and after I
perform "update configuration" seem almost 0.
The only difference seems to be some file sizes (not sure why?) and a few specific
.settings/ files are not in the deployment. I'll attach both files but it seems to me
like this example is working 100% fine. Both before and after "fixing" the libs
are present in WEB-INF/lib
I'm not able to replicate this. It seems to work immediately using 20090820
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
8:34 p.m.
New subject: [JBoss JIRA] Updated: (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...
]
Rob Stryker updated JBIDE-4817:
-------------------------------
Attachment: unfixed.out
The file structure directly after importing the projects and deploying to a jboss server.
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: 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
8:36 p.m.
New subject: [JBoss JIRA] Updated: (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...
]
Rob Stryker updated JBIDE-4817:
-------------------------------
Attachment: fixed.out
After doing the "Update Project Configuration" this is the file structure
output
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
8:56 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
I still receive an NPE, but from what I can tell it's not affecting the output. It
seems the publisher is still publishing it accurately because of the project relationships
inside the workspace.
This error whenever WTPProjectConfigurator.mavenProjectChanged(MavenProjectChangedEvent
event) is called, and it stems from a simple unchecked null value deep in WTP. I'll
try to get the WTP one fixed, but I'm unsure why maven is executing the following when
a project is asked to CLOSE.
EarProjectConfiguratorDelegate.execAddOp(IProgressMonitor, IVirtualComponent,
Map<IVirtualComponent,String>, String) line: 306
EarProjectConfiguratorDelegate.addComponentsToEAR(EarProjectConfiguratorDelegate$EarComponentWrapper,
IProgressMonitor) line: 252
EarProjectConfiguratorDelegate.setModuleDependencies(IProject, MavenProject,
IProgressMonitor) line: 146
WTPProjectConfigurator.mavenProjectChanged(MavenProjectChangedEvent, IProgressMonitor)
line: 61
This seems suspicious to me.
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
8:29 a.m.
New subject: [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:
--------------------------------------
You have to use the latest m2eclipse because it fixes the deployment issue described in
JBIDE-4736.
I can't reproduce the NPE that you got. When I close the booking project, I get the
following NPE:
java.lang.NullPointerException
at
org.jboss.ide.eclipse.as.core.modules.SingleDeployableFactory.getModule(SingleDeployableFactory.java:176)
at
org.jboss.ide.eclipse.as.core.modules.SingleDeployableFactory$FileDeletionListener.visit(SingleDeployableFactory.java:272)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
at
org.jboss.ide.eclipse.as.core.modules.SingleDeployableFactory$FileDeletionListener.resourceChanged(SingleDeployableFactory.java:253)
at
org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at
org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313)
at org.eclipse.core.internal.resources.Workspace.checkpoint(Workspace.java:367)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:265)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:308)
at
org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:220)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at
org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
However, it isn't important here. Are you using the latest JBoss Tools trunk?
Both of the files you attached have incorrectly deployed the WEB-INF/lib directory. They
are in the EAR's root directory instead of in the booking.war directory
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=247090). 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.
This problem isn't related to m2eclipse.
m2eclipse configurators update a project when importing the project, changing pom.xml,
calling Maven>Update Project Configuration. Sometimes they are called when
closing/opening the project, starting Eclipse, etc. m2eclipse WTP Web configurator tries
to remove and add web module facet. Since jsf facet exists in seam project, this
won't succeed. As a result, m2eclipse creates line "<wb-resource
deploy-path="/" source-path="/src/main/webapp"/>'. However,
this bug fixes the wtp deployment bug.
Aside from a few errors in the html (not closing tags etc)
these errors are errors in our XHTML validator and you can avoid them by disabling
it. They aren't related to this bug.
PS
I have changed the resource folder from src/resources to src/main/resources. This will
probably to fix JavaModel error you faced.
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
4:40 p.m.
New subject: [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...
]
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
5:48 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
The only change I've seen in output files between before doing update, and after, is
this part of the diff:
components.properties
messages.propeties
seam.properties
These three files are missing despite that all that changed in the component.xml is the
order of the resource links. /src/main/resources clearly has a mapping so I'll try to
figure out why it's not there.
I've just done some more tracing and for my example this is a duplicate of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=284187
But I still don't know what your issue is, Snjezana. In fact I cannot duplicate your
issue. The only difference I see is the three files listed above not showing up and
that's the duplicate of eclispe bug 284187.
This single-root issue is becoming a real problem IMO.
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
7:54 p.m.
New subject: [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...
]
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
1:52 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-4817:
--------------------------------------------
the three missing files are most likely missing because in maven projects the resources
needs to be "compiled" (i.e. property replacement inside the files) and thus the
resources folder is not on the classpath, where as webinf/classes are. (my guess)
Don't think that has anything to do with isSingleRoot?
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
1:11 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
The three missing files in the unfixed pre-action version *do* 100% have to do with
isSingleRoot. I can guarantee you that.
There is a line in the component.xml which explicitly maps
source-path="booking/src/main/resources" to
deploy-path="/WEB-INF/classes" and they do not make it in because the module
(J2EEFlexProjDeployable) definitely identifies this module as single root.
The post-fix post-action version of the project only has the files because they were
coppied into the one source directory into what the deployable identifies as the single
root.
The component.xml has this line:
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
This line is what causes the deployable's bug to treat src/main/webapp as the single
root. So files sitting in src/main/resources are ignored. In the post-fix action, those
files have been coppied into src/main/webapp/WEB-INF/classes.
So there is still a bug in isSingleRoot which is the same bug I've noticed before and
I need to get around to fixing.
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
7:26 a.m.
New subject: [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:
--------------------------------------
Yes, this is isSingleRoot problem https://bugs.eclipse.org/bugs/show_bug.cgi?id=279360.
I have added a workaround (changed the booking's output directory) to the booking
example. Now it works correctly.
I would mark this issue as resolved.
Max,
do you agree?
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
10:19 a.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
I've linked the two isSingleRoot issues together in eclipse bugzilla so that I
don't lose it again. THat one rarely comes up in my searches as my searches typically
are bugs I create.
I'll be looking at isSingleRoot today and trying to come up with a nice patch for wtp.
The code needs to be cleaned up and more understandable.
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
3:08 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
Snjezana:
Can you please give me a filename for which file *should* be deployed but isn't being
deployet? Is it one of the three files I've mentioned or is there some other file
I'm not noticing is missing?
Thank you.
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
7:32 a.m.
New subject: [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:
--------------------------------------
The complete WAR's WEB-INF/lib directory is missing.
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
6:46 p.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-4817:
------------------------------------
having a very weird time replicating this. I just tried it again (new svn co, new
importm, new publish) and this was my result:
52 ./booking-ear.ear/WEB-INF/lib/jboss-seam-ioc-2.1.1.GA.jar
3936 ./booking-ear.ear/WEB-INF/lib/richfaces-ui-3.3.0.GA.jar
8 ./booking-ear.ear/WEB-INF/lib/jboss-seam-jul-2.1.1.GA.jar
268 ./booking-ear.ear/WEB-INF/lib/jboss-seam-ui-2.1.1.GA.jar
1492 ./booking-ear.ear/WEB-INF/lib/richfaces-impl-3.3.0.GA.jar
20 ./booking-ear.ear/WEB-INF/lib/jboss-seam-debug-2.1.1.GA.jar
196 ./booking-ear.ear/WEB-INF/lib/commons-beanutils-1.7.0.jar
152 ./booking-ear.ear/WEB-INF/lib/commons-digester-1.8.jar
304 ./booking-ear.ear/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar
6436 ./booking-ear.ear/WEB-INF/lib
6444 ./booking-ear.ear/WEB-INF
15408 ./booking-ear.ear
... etc ...
8 ./booking-ear.ear/booking.war/WEB-INF/web.xml
8 ./booking-ear.ear/booking.war/WEB-INF/faces-config.xml
52 ./booking-ear.ear/booking.war/WEB-INF/lib/jboss-seam-ioc-2.1.1.GA.jar
3936 ./booking-ear.ear/booking.war/WEB-INF/lib/richfaces-ui-3.3.0.GA.jar
8 ./booking-ear.ear/booking.war/WEB-INF/lib/jboss-seam-jul-2.1.1.GA.jar
268 ./booking-ear.ear/booking.war/WEB-INF/lib/jboss-seam-ui-2.1.1.GA.jar
1492 ./booking-ear.ear/booking.war/WEB-INF/lib/richfaces-impl-3.3.0.GA.jar
20 ./booking-ear.ear/booking.war/WEB-INF/lib/jboss-seam-debug-2.1.1.GA.jar
196 ./booking-ear.ear/booking.war/WEB-INF/lib/commons-beanutils-1.7.0.jar
152 ./booking-ear.ear/booking.war/WEB-INF/lib/commons-digester-1.8.jar
304 ./booking-ear.ear/booking.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar
6436 ./booking-ear.ear/booking.war/WEB-INF/lib
And tracing through it seems this is what's happening. It seems like it's getting
published under the war's lib, and also duplicated in the parents. I guess I'll
have to try a few more times but for now i'm leavign for the night.
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
12:59 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-4817:
--------------------------------------------
you guys are using the same version of WTP, right ? :)
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
2:30 p.m.
New subject: [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
2:16 p.m.
New subject: [JBoss JIRA] Resolved: (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...
]
Rob Stryker resolved JBIDE-4817.
--------------------------------
Fix Version/s: 3.1.0.M3
Resolution: Done
Closing as there's nothing more that can be done here and Snjezana worked around hte
issue.
The linked eclipse bugs are still valid, though, and I'll be working to get patches
for them in upstream.
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
Fix For: 3.1.0.M3
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
5388
days inactive
5395
days old
jbosstools-issues@lists.jboss.org
23 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Rob Stryker (JIRA)
-
Snjezana Peco (JIRA)