Ok. Well, that is what it is supposed to do, though. I just don't quite
understand the problem being had without more investigation. It should
be scheduled for 2.0.4.
Cheers,
Brett
Brian E. Fox wrote:
> To me these are all related because the reactor seems to link the
> sibling directly (for exam
List
Subject: Re: some major issues with reactors and dependency handling
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
o:[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.
>
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
> 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
>
rom: 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 any
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 proje
th the version but B
does not. If I depend directly on A and B, then both A and B loose the
version.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 4:08 PM
To: Maven Developers List
Subject: some major issues with reactors and dependency ha
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 Pr
