[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-6320.
--------------------------------

        Labels: affects_documentation  (was: )
    Resolution: Done


The patch works in Branch, however in branch you *still* need to open and close the project again. This is not really fixable because it is upstream WTP-based. Upstream deployable caches the references and seems not to update them. This is fixed in wtp 3.2, but for wtp 3.1.x maintenance, it is not fixable. 

However, there is no longer the lib/lib double nesting. So, thats comforting =] 

> EAR deployment with option "as compressed archives" results in ear containing invalid jars
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-6320
>                 URL: https://jira.jboss.org/browse/JBIDE-6320
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>    Affects Versions: 3.1.0.GA
>         Environment: Windows XP Pro SP3, Java JDK 1.6.0_20, Eclipse IDE for JEE 3.5.2, JBoss Tools 3.1 (JBossAS Tools 2.1.0.v201003050540R-H56-GA), WTP Patches 3.1.2.v201003181725), m2Eclipse 0.10.0
>            Reporter: Gonne Martens
>            Assignee: Rob Stryker
>             Fix For: 3.1.x, 3.2.0.M1
>
>         Attachments: JBIDE-6320-test.ear, JBIDE-6320.patch
>
>
> The deployment of a minimal Enterprise Application Project (consisting of e.g. jboss-seam.jar as ejb-module and mvel2.jar as 3rd-party jar) with the deployment option "Deploy projects as compressed archives" activated, results in an ear containing some invalid jars: These invalid jars are containing only one jar with the same name which finally contains the actual jar content.
> E.g. the mvel2.jar contains a mvel2.jar which contains the "META-INF" and an "org" directory.
> It seems that every supplied jar is affected that is determined as module jar, because it is an ejb-module (e.g. jboss-seam.jar) or its manifest contains a "Main-class" entry marking it as client-module.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira