[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-9031) Deploying EAR with a module having a sub-module in its component descriptor deploys erroneous ear.

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-9031:
------------------------------------

    Attachment: erroneous-ear.png


> Deploying EAR with a module having a sub-module in its component descriptor deploys erroneous ear.
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-9031
>                 URL: https://issues.jboss.org/browse/JBIDE-9031
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.Final
>         Environment: Tested with Eclipse Indigo Release 20110319-2305 with latest nightly build trunk of JBoss Tools.
> Deploying on a JBoss 4.2 server.
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>            Priority: Critical
>              Labels: component, deployment, descriptor, ear, eclipse, jar, module
>             Fix For: 3.2.1.CR1, 3.3.0.M2
>
>         Attachments: erroneous-ear.png, error-renaming-archive.png, recursive-projects.zip
>
>
> h3.Context:
> For some reasons I have to deploy an EAR webapp with (in its libs) a jar containing itself another jar.
> h3.Environment:
> For this I have a first Java project with the following component descriptor:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
>     <wb-module deploy-name="project1">
>         <wb-resource deploy-path="/" source-path="/src/main/java"/>
>     </wb-module>
> </project-modules>
> {code}
> Then, the second Java project has the component descriptor:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
>     <wb-module deploy-name="project2">
>         <wb-resource deploy-path="/" source-path="/src/main/java"/>
>         <dependent-module archiveName="project1.jar" deploy-path="/lib" handle="module:/resource/project1/project1">
>             <dependency-type>uses</dependency-type>
>         </dependent-module>
>     </wb-module>
> </project-modules>
> {code}
> Then, in Eclipse when exporting the *project2* as a *Module Archive*, I obtain a .jar file featuring both classes from *project2* and a *lib* folder with the project1 compiled jar.
> Now, in the ear project I have the following lines in the component descriptor:
> {code:xml}
>         <dependent-module archiveName=" project1.jar" deploy-path="/lib" handle="module:/resource/ project1/ project1">
>             <dependency-type>uses</dependency-type>
>         </dependent-module>
>         <dependent-module archiveName=" project2.jar" deploy-path="/lib" handle="module:/resource/ project2/ project2">
>             <dependency-type>uses</dependency-type>
>         </dependent-module>
> {code}
> (The EAR needs the 2 jars as well)
> h3.Problem:
> The ear that is deployed actually has project1 and project2 in the root of the EAR.
> !erroneous-ear.png!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira