[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4817) WTP EAR deployers don't work correctly when using some classpath containers (Maven, for instance)

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12482872#action_12482872 ] 

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#action_12482337
> 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