On Feb 15, 2007, at 3:28 PM, Brian E. Fox wrote:
Heh. Are you mocking me or just behind in thread mail? ;p
Not intending to mock you... do you feel mocked?
I assume you mean because of the require-maven-version stuff? Dain
asked me if I could add a version check, just like we do for Java so
that we can have quick failing builds when the wrong Maven version is
used. I remembered that Maven already had prerequisites, but as I
thought, it did not work as desired, so I fired off this email, and
then quickly whipped up a mojo to do what I really wanted.
BTW: Is this reply threading correctly now?
Think so.
--jason
-----Original Message-----
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Thursday, February 15, 2007 4:24 PM
To: Maven Developers List
Subject: Why is prerequisites not inherited?
I just found out that Geronimo *has* to move 2.0.5, because there are
some issues with the maven-dependencies-plugin and 2.0.4. No big
deal, but if I add this to the top-level pom:
----8<----
<prerequisites>
<maven>2.0.5</maven>
</prerequisites>
---->8----
and someone tries to build a child, like:
(cd modules && mvn install)
The child build does not complain, and will end up failing if you use
Maven 2.0.4.
So... why isn't the prerequisites passed on to children?
* * *
I will have to fix this by adding a new goal to our tools-maven-
plugin, similar to how require-java-version works.
--jason
---------------------------------------------------------------------
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]
