[Fwd: Re: MNG-1577]

[Ralph Goers <Ra...@dslextreme.com>]

I started to edit it but didn't save it. The page that really needs to

be updated is 
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html. 
However, I believe the page I was editing is at 
http://docs.codehaus.org/display/MAVENUSER/Dependency+Mechanism.

To edit all you need is to register and log in.

Ralph

Patrick Schneider wrote:
> We haven't done any documentation yet, no.  I'll certainly be happy to 
> write some up, help you out, review what you have, etc.
>
> Where is the wiki page you were editing?  Is it open to anyone, or do 
> I need to submit changes to it through you or Mike?
>
> On 3/15/07, *Ralph Goers* <Ralph.Goers@dslextreme.com 
> <ma...@dslextreme.com>> wrote:
>
>     Question.  Has Mike or Patrick updated the documentation yet?  I
>     started
>     to update the wiki a couple of months ago but put it off as I didn't
>     want the wiki to reflect something that you couldn't yet
>     use.  Plus the
>     behavior changed slightly since then.
>
>     If they haven't beaten me to it, I'd be happy to do this as I promised
>     (hoping they will review it of course).
>
>     Ralph
>
>     Jason van Zyl wrote:
>     > 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@maven.apache.org
>     <ma...@maven.apache.org>
>     > For additional commands, e-mail: dev-help@maven.apache.org
>     <ma...@maven.apache.org>
>     >
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>     <ma...@maven.apache.org>
>     For additional commands, e-mail: dev-help@maven.apache.org
>     <ma...@maven.apache.org>
>
>


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