[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4629) Publishing an EAR project with "In Lib Dir" utility jar results in wrong file structure

[Brett Prucha (JIRA)]

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

Brett Prucha updated JBIDE-4629:
--------------------------------

    Attachment: workspace-test.zip


Example projects showing problem

> Publishing an EAR project with "In Lib Dir" utility jar results in wrong file structure
> ---------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4629
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4629
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.GA, 3.0.1.GA, 3.1.0.M2
>         Environment: Eclipse 3.4 and Eclipse 3.5, Windows Vista
>            Reporter: Brett Prucha
>            Assignee: Rob Stryker
>            Priority: Minor
>         Attachments: workspace-test.zip
>
>
> When publishing an EAR project to a JBoss server the "In Lib Dir" checkbox under the Java EE Module Dependencies of the EAR projects properties is not being applied for utility projects.  The jar file created by the utility project is always placed in the root of the EAR folder even if the "In Lib Dir" box is checked.  Exporting the EAR project to an EAR archive file results in a compressed archive that properly places the utility jar in the EARs lib folder.  Checking the "Deploy projects as compressed archive" checkbox produces an EAR archive that improperly has the utility jar in the root of the EAR as well.

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