maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: Scope question
Date Tue, 05 Nov 2013 11:45:10 GMT
Introducing a new scope is not possible without breaking backwards
compatibility. Thus, unlikely to happen in the near future. Your option
right now is to use depMgmt.

/Anders


On Tue, Nov 5, 2013 at 12:15 PM, Guillaume CHAUVET <
guillaume.chauvet@qualiformed.com> wrote:

> Thank you for your quick answers,
>
> Use the dependencyManagement section seems a little bit cumbersome to
> implement, because it implies to define a parent POM for all libraries to
> which I would apply this "retention classes" mechanism.
>
> It's somewhat speculative on my part, but It could be very convenient to
> provide a new scope (or an option like "optional") that allows Maven to
> change the scope of  "z" dependency to "runtime" when the artifact "A" is
> included as dependency of project "B". I think it would be an interesting
> feature.
>
> What do you think about this idea ?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message