#48 dependent JARs incorrectly repackaged as JARs

Hello,

The Amazon AWS Toolkit will incorrectly repackage certain dependent JAR files inside another JAR file. This happens for all JARs that are detected as "J2EE Client Modules" or "J2EE EJB Modules". This has been fixed in the normal Tomcat server deployer in Eclipse WTP 3.2 but still occurs in the Amazon EC2 server deployer. For more information please see Eclipse bug 306732.

In my case I have 27 JARs as dependencies and it happens for these three JARs:

jboss-seam-2.1.1.GA.jar --> deployed as jboss-seam-2.1.1.GA.jar.jar (where the deployed JAR only contains the original JAR)
hibernate-core-3.3.2.GA.jar --> deployed as hibernate-core-3.3.2.GA.jar.jar
javassist-3.4.GA.jar --> deployed as javassist.3.4.GA.jar.jar

For Hibernate and Javassist the workaround is to remove the Main-Class entry from the JAR manifest. Then the JAR's are not detected as "J2EE Client Modules" and work fine. I don't know what the workaround is for JBoss. I've removed the manifest and a few other files from META-INF but unfortunately it still detects the JAR as a "J2EE EJB Module".

It would be great if this could be fixed, because otherwise I have to SSH into the AMI and manually unzip the JAR files after each deployment.

Thank you.

[Jason Fulghum]

Thanks for reporting this Frank. I was able to repro the issue using the javassist jar.

I'm still seeing it with the WTP Tomcat server, too in 3.6 (3.5 doesn't seem to have this problem), so next up I want to try the latest WTP Tomcat code and dig around through it to see how they addressed this.

j