maven war package corrupts jar import

[Brian Babbage]

This is a crazy problem and I'm tearing my hair out over it...

My POM is building an applet.jar and placing it in a resource folder, then packaging the entire project into a war [including the folder with the applet.jar (and 2 other jars)].
The application will deploy (on jboss) but fails to run. The java console reports "can not find required MainApplet.class" [which is in the applet.jar].

If I manually copy the applet.jar into the war and deploy it the application functions normally. The applet.jar is an archive in the output folder but is not an archive in the war(7-zip reports).
Somehow the maven war packaging is corrupting this freshly built jar (and only this one jar).
Does anyone have any ideas why this is happening?!


jar assembly

<build>
...
<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-assembly-plugin</artifactId>
	<version>2.2.1</version>
	<executions>
		<execution>
			<id>Applet</id>
			<goals>
				<goal>single</goal>
			</goals>
			<phase>compile</phase>
			<configuration>
				<outputDirectory>${basedir}${Applet.jar.path}</outputDirectory>
				<finalName>Applet</finalName>
				<appendAssemblyId>false</appendAssemblyId>
				<descriptors>
					<descriptor>${assembleApplet.path}</descriptor>
				</descriptors>
			</configuration>
		</execution>
	</executions>
</plugin>
...
</build>

war plugin

<profile>
...
<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-war-plugin</artifactId>
	<version>2.1.1</version>
	<configuration>
		<manifest>
			<addClasspath>true</addClasspath>
		</manifest>
		<archive>
			<manifestEntries>
				<Implementation-Build>${build.timestamp}</Implementation-Build>
			</manifestEntries>
		</archive>
		<outputDirectory>${local.assembly.buildPath}</outputDirectory>
		<webResources>
			<resource>
				<directory>${environment.properties.local.path}</directory>
				<filtering>true</filtering>
				<targetPath>WEB-INF</targetPath>
				<excludes>
					<exclude>log4j.properties</exclude>
					<exclude>statsLoggerServer.properties</exclude>
				</excludes>
			</resource>
			<resource>
				<directory>${environment.properties.local.path}</directory>
				<filtering>true</filtering>
				<targetPath>WEB-INF/classes</targetPath>
				<excludes>
					<exclude>environment.properties</exclude>
				</excludes>
			</resource>
			<resource>
				<directory>${web.files.path}</directory>
				<filtering>true</filtering>
				<targetPath>web</targetPath>
			</resource>
		</webResources>
	</configuration>
</plugin>
...
</profile>

[Peter Johnson]

I'd like to help you but there is an important administrative matter you need to deal with first. I'm sure you received some private messages about it.

[Tim Holloway]

Peter's not kidding. I've been ignoring your question for days because you're violating one of the very few rules that we're absolutely insistent about at the Ranch.

[Brian Babbage]

note to self. when searching for "corrupt jar files" remember that a jar file is also a binary file. Maven has this covered but it's under corrupt binary file corruption...

the fix

	<nonFilteredFileExtensions>
		<nonFilteredFileExtension>jar</nonFilteredFileExtension>
	</nonFilteredFileExtensions>

I feel like such a bone head over this

Thanks for the help and advice guys.