I can't see how the MWAR one is related, but I probably haven't done as much investigation. Regardless, it can be fixed there and should be left there.
MNG-2045 seems like the one to schedule for a nearer release. - Brett Brian E. Fox wrote: > I'm not sure how a fix in war solves anything? There are a couple > related issues that are apparently caused by the same problem unrelated > to war: > http://jira.codehaus.org/browse/MDEP-2 > http://jira.codehaus.org/browse/MNG-2045 > > I looked into the dependency problem and project.getArtifacts() doesn't > return an artifact for sibling dependencies when run in a reactor. This > seems to imply to me that something fundamental is broken in maven and > is just manifesting itself via different symptoms in plugins. > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 08, 2006 6:36 AM > To: Maven Developers List > Subject: Re: some major issues with reactors and dependency handling > > It won't be ignored, and it needs to be fixed in the war plugin (ie > MWAR). Moving it will delay its release. > > - Brett > > Brian E. Fox wrote: >> Ok, I'm glad this is really a bug because I was pulling my hair out >> trying to understand what the logic was. Should the issue be moved to >> a reactor group so it gets considered for 2.0.4? I'm just afraid that >> having it out in WAR, it might get neglected. >> >> -----Original Message----- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: Monday, March 06, 2006 8:18 AM >> To: Maven Developers List >> Subject: Re: some major issues with reactors and dependency handling >> >> I believe this is solely a reactor issue (it should be naming the >> files at the target, as the source filename could be anything). So >> MWAR-7 is the issue and should be easily fixed. >> >> - Brett >> >> Brian E. Fox wrote: >>> I've seen some major issues with the way maven handles dependencies >>> in >>> a multi project setting. Consider the following project: >>> >>> parent >>> Project A 1.0 - Jar >>> Project B 1.0 - War >>> >>> If I build the parent, when project A is included in the war, it's >>> included as project-a.jar. If I build Project B, then the jar is >>> included as project-a-1.0.jar >>> >>> This is just one example of some weird issues, I know that people >>> have >>> mentioned problems similar to this with compiling. Maven is all about > >>> reproducibility, but this one clearly breaks that because the >>> produced >>> artifact is completely dependant on if it was build standalong or >>> part >>> of a reactor. Can any of the maven developers explain what was >>> attempted to be solved by this and if/when we might see it get fixed. >>> >>> Some jiras I can see that are related to this: >>> http://jira.codehaus.org/browse/MWAR-7 >>> http://jira.codehaus.org/browse/MOJO-286 >>> >>> I don't yet see an actual issue related to this, just the side >>> effects >>> of it on the WAR and Dependency plugin. Should I create a separate >>> one >>> in the MNG group? >>> >>> >> --------------------------------------------------------------------- >> 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] >> > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
