[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5952) ear dependency jar is wrapped by another jar

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-5952:
------------------------------------

Sadly I'm not adept at hte Maven stuff but if I had a project with easy instructions on how to import it and debug I could figure this out I'm sure.   Snjezana, can you help at all? 

> ear dependency jar is wrapped by another jar
> --------------------------------------------
>
>                 Key: JBIDE-5952
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5952
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS, maven
>    Affects Versions: 3.1.0.CR2
>         Environment: windows 7 x64, 32-bit JRE, eclipse 3.6 M5 32bit for windows, WTP 3.2 M5, maven 2.2.1, JBossAS Tools 2.1.0.v201002252131N-H17-GA, JBoss Maven Integration 1.0.0.v201002252131N-H17-GA
>            Reporter: Dmitry Malchikov
>            Assignee: Snjezana Peco
>             Fix For: 3.1.1
>
>         Attachments: example.zip
>
>
> Maven project has ear and ejb modules. Ear module depends on ejb module and includes it in result ear file. When deploying ear some kind of ejb dependencies jars are wrapped into another jar. Example of jars: jtds-1.2.2.jar, jibx-run-1.2.1.jar, mvel2-2.0.10.jar. Don't know really why these jars are wrapped into jar package (for example mvel2-2.0.10.jar contains another mvel2-2.0.10.jar package which contains correct jar content) there are many jars that are deployed correctly.

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