To test MNG-1245 you can just replace your maven-project-2.0.4.jar in MAVEN_HOME/lib with the SNAPSHOT I attached to the issue and see if the issue goes away or changes.
-----Original Message----- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 12, 2006 8:07 AM To: Maven Developers List Subject: RE: J2EE killer: For multi module builds CLASSPATH != resolved dependencies Brett Porter wrote on Wednesday, July 12, 2006 2:18 PM: > In MNG-2424, you say it may be related to MNG-1245 which is > now fixed. > Does that correct that issue? I don't know. I have too less knowledge about the classpath generation in Maven and how it is related to the dependencies - escpecially in multi module mode. > There have been some classspath related archiver fixes that might help > with MEJB-18. MNG-2424 and MEJB-18 is IMHO the same bug. > Would fixing both of these resolve your issue? How do I test this best? I don't want to run into troubles for my standard build environment with all kind of snapshot plugins in my repository. It is already quite complex. Nevertheless the attachments in the issues provide a scenario for a test in an environment with a newer Maven snapshot. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
