The decision was we couldn't add scopes until the modelVersion gets a
bump... Which is on the cards for maven 4.0.
On Saturday, 12 April 2014, Benson Margulies wrote:
> On Fri, Apr 11, 2014 at 5:57 PM, Stephen Connolly
> > wrote:
> > That's a sign that we need a new scope...
>
> The person who d
On Fri, Apr 11, 2014 at 5:50 PM, Benson Margulies wrote:
> On Fri, Apr 11, 2014 at 5:29 PM, Stephen Connolly
> wrote:
> > On 11 April 2014 22:10, Benson Margulies wrote:
> >
> >> >
> >> > Fwiw, I don't recall the dependency plugin actually injecting stuff
> into
> >> > the project class path but
On Fri, Apr 11, 2014 at 5:57 PM, Stephen Connolly
wrote:
> That's a sign that we need a new scope...
The person who decided that we couldn't just use an arbitrary custom
value as a scope (thus breaking the tomcat plugin of the time) might
want to reconsider that decision.
>
>
> On 11 April 2014
That's a sign that we need a new scope...
On 11 April 2014 22:50, Benson Margulies wrote:
> On Fri, Apr 11, 2014 at 5:29 PM, Stephen Connolly
> wrote:
> > On 11 April 2014 22:10, Benson Margulies wrote:
> >
> >> >
> >> > Fwiw, I don't recall the dependency plugin actually injecting stuff
> in
On Fri, Apr 11, 2014 at 5:29 PM, Stephen Connolly
wrote:
> On 11 April 2014 22:10, Benson Margulies wrote:
>
>> >
>> > Fwiw, I don't recall the dependency plugin actually injecting stuff into
>> > the project class path but equally wish that the copy/unpack goals could
>> > simply go away regardl
On 11 April 2014 22:10, Benson Margulies wrote:
> >
> > Fwiw, I don't recall the dependency plugin actually injecting stuff into
> > the project class path but equally wish that the copy/unpack goals could
> > simply go away regardless. (in leu of the more normal xxx-dependencies
> > versions)
>
>
> Fwiw, I don't recall the dependency plugin actually injecting stuff into
> the project class path but equally wish that the copy/unpack goals could
> simply go away regardless. (in leu of the more normal xxx-dependencies
> versions)
If you make them go away, please find them a new home. I use
Op Fri, 11 Apr 2014 22:57:01 +0200 schreef Brian Fox :
My proposal is strictly to prohibit a plugin from modifying a project's
classpath implicitly. That this become fully explicit such that I can
remove some of the convoluted logic in the core to account for this.
Not allowing plugins to rand
> My proposal is strictly to prohibit a plugin from modifying a project's
> classpath implicitly. That this become fully explicit such that I can
> remove some of the convoluted logic in the core to account for this.
>
>
Not allowing plugins to randomly inject new dependencies makes sense. I see
so
