I am using JBoss Tools 3.1 with JBossAS 6.0 M3. I have tried to deploy an ear (seam project) with the deployment option "Deploy projects as compressed archives". The result was an ear which contained some invalid jars: the content of these jars was not at the root level but inside a direcotry named as the jar. It seems that all jars are affected that were determined as module jars: e.g. jboss-seam.jar as ejb-module, mvel2.jar as client module because the manifest contains a "Main-class" entry.
I have not found an issue for that so far, so I would create one with an example.
Besides that, it looks like all archives of the resulting ear are being compressed even the jars. My expectation was only an unexploded ear containing untouched third-party jars.
Sorry for not being clear enough. There is also a mistake in my description.
What I mean with invalid jar, is a jar 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.
I have attached a minimal example ear.
JBIDEtest.ear 1.5 MB