[JBoss JIRA] Created: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
10:10 a.m.
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
Assignee: Rob Stryker
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
10:12 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Gonne updated JBIDE-6320:
-------------------------
Attachment: JBIDE-6320-test.ear
Example ear containing invalid jars
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
Assignee: Rob Stryker
Attachments: JBIDE-6320-test.ear
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
1:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Rob Stryker commented on JBIDE-6320:
------------------------------------
Judging by the description, the jar in the {project}/lib folder should not be published at
all since it is not in a mapped folder (EarContent) and it is not mapped in via the
deployment assembly page / module dependency page. So the seam jar should not be in the
resultant output file at all.
However I was able to replicate the issue and will get a fix in ASAP. patch coming
shortly.
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
Attachments: JBIDE-6320-test.ear
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
1:27 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Rob Stryker updated JBIDE-6320:
-------------------------------
Attachment: JBIDE-6320.patch
Patch fixes it
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
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
2:09 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Rob Stryker resolved JBIDE-6320.
--------------------------------
Fix Version/s: 3.2.0.M1
Resolution: Done
put into the trunk
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.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
8:10 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6320:
---------------------------------------
Fix Version/s: 3.1.x
marked for branch once it is open again
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
8:10 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen reopened JBIDE-6320:
----------------------------------------
this looks like a severe issue that should be fixed in 3.1.x too, right ?
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
10:45 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Shu-Wei Tan commented on JBIDE-6320:
------------------------------------
I would consider this a severe issue and worth putting into 3.1.1
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
5:16 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on JBIDE-6320:
--------------------------------------------
Rob, I don't see any tests added for this. Could we get that so we can get it verified
mechanically.
About 3.1.1 then that probably is too late.
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
5:39 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
Rob Stryker commented on JBIDE-6320:
------------------------------------
Committed test case to trunk... branch still waiting
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
3:40 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://jira.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin.s...
]
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
2:09 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://issues.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin...
]
SBS JIRA Integration updated JBIDE-6320:
----------------------------------------
Forum Reference: http://community.jboss.org/message/544021#544021,
https://community.jboss.org/thread/152211?tstart=0 (was:
https://community.jboss.org/thread/152211?tstart=0)
EAR deployment with option "as compressed archives" results
in ear containing invalid jars
------------------------------------------------------------------------------------------
Key: JBIDE-6320
URL: https://issues.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
Labels: affects_documentation
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:47 a.m.
New subject: [JBoss JIRA] (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
[
https://issues.jboss.org/browse/JBIDE-6320?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-6320:
---------------------------------------
Fix Version/s: 3.1.1
(was: 3.1.x)
Forum Reference: http://community.jboss.org/message/544021#544021,
https://community.jboss.org/thread/152211?tstart=0 (was:
http://community.jboss.org/message/544021#544021,
https://community.jboss.org/thread/152211?tstart=0)
EAR deployment with option "as compressed archives" results
in ear containing invalid jars
------------------------------------------------------------------------------------------
Key: JBIDE-6320
URL: https://issues.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
Labels: affects_documentation
Fix For: 3.1.1, 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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4602
days inactive
5106
days old
jbosstools-issues@lists.jboss.org
12 comments
6 participants
participants (6)
-
Gonne (JIRA) -
Max Rydahl Andersen (JIRA)
-
Max Rydahl Andersen (Updated) (JIRA)
-
Rob Stryker (JIRA)
-
SBS JIRA Integration (JIRA)
-
Shu-Wei Tan (JIRA)