RE: [vote] MNG-1577 as the default behavior

I can think of some cases where it might break a build, but most of them
are where a transitive dependency creeps into a build because the user
assumes that MNG-1577 is how it's always worked. That being said, these
issues would be easily remedied since you now have more control, and
anyone using depMgt put those things there for a reason.

We should just include a big notice in the release notes about this
change so people are at least aware of it.

+1 for making this the default.

-----Original Message-----
From: Jason van Zyl [mailto:jason@...]
Sent: Thursday, March 15, 2007 8:33 PM
To: Maven Developers List
Subject: [vote] MNG-1577 as the default behavior

Hi,

After working with it a little this week I would like to propose to  
make MNG-1577 behavior introduced the default. Builds are completely  
and totally unpredictable without this behavior. The behavior in  
2.0.5 is fundamentally broken. To are totally prey to any dependency  
introduced by a dependency which makes no sense and completely  
counter intuitive. I stabilized a massive build this week simply by  
using the behavior present in the 2.0.x branch. I don't think we're  
doing anyone any favors leaving the old behavior in. After watching a  
disaster be recovered by using this new behavior I feel that the  
patch should go in as is and become the default behavior. This puts  
the user in control which is the way it should be.

I propose we make this the default behavior. Can anyone think of a  
case where this degree of control would break an existing build?

This patch saved my bacon this week, I think this behavior makes a  
world of difference to users.

Jason.





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...