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

Shu-Wei Tan (JIRA) jira-events at lists.jboss.org
Sat May 22 03:48:06 EDT 2010


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

Shu-Wei Tan commented on JBIDE-5952:
------------------------------------

I have managed to reproduce this on Galileo without using Maven. Here's how:

JBoss Tools 3.1, Seam 2.2.0, JBoss AS 5.1.0, Windows XP

1) Create new Seam Web Project EAR using JBoss Tools. You can use default values except choose EAR project instead of WAR project
2) Double click on local server, go to Deployment tab, and choose Deploy as Compressed Archive
3) Publish to Server

You will then see that the published ear archive has a mvel2.jar in its lib folder. This jar contains another jar of the same name. It is the inner jar that is the actual jar. Why is this jar wrapped? The jar isn't wrapped if you deploy as an exploded archive.

> ear dependency jar is wrapped by another jar
> --------------------------------------------
>
>                 Key: JBIDE-5952
>                 URL: https://jira.jboss.org/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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list