Hello, I'm in the process of trying to convert a few projects from ant build scripts to Maven2. In the process, I've run into quite a few issues with the assembly plugin. I started by running into:
http://jira.codehaus.org/browse/MASSEMBLY-213 and/or http://jira.codehaus.org/browse/MASSEMBLY-64 which is allowing jar security files through to the assembled artifact. This breaks jar execution when Java attempts to validate the jar contents. One of the workarounds described (fall back to 2.1 release) didn't work as I was missing all but one of the dependencies in the assembled artifact. The other workaround (add excludes entries into assembly descriptor) doesn't appear to work either as a result of: http://jira.codehaus.org/browse/MASSEMBLY-195 I can manually work around this with the antrun plugin and a chunk of manual target definitions, but the signed artifacts being included in the assembly are used in many other projects as well, meaning that I'd need to replicate this ant hack many times over. I tried creating an intermediate artifact that all the projects depend on but ran into yet more problems with the reactor trying to use the intermediate artifacts "classes" directory (which is empty) versus the intermediate jar artifact when using it to compile another project's source. This appears to only happen if multiple modules are run together, which is my normal mode of operation. Am I missing something obvious here? I wouldn't think that this would be such a rare and/or difficult operation.. -- Mike Cumings --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
