maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Barrie Treloar <baerr...@gmail.com>
Subject Re: [Maven 4.0.0] Removing ability for plugins to dynamically inject dependencies
Date Thu, 10 Apr 2014 23:23:42 GMT
On 10 April 2014 23:37, Lennart J├Ârelid <lennart.jorelid@gmail.com> wrote:

> So ... the consequence of your approach would be that POMs throughout a
> maven reactor would have to repeat a dependency declaration if the classes
> in your maven project "directly" import a type. This - to me - seems not
> only complex to resolve in a big reactor, but quite user-unfriendly as
> well. An example shows this, I think:
>

This is the *recommended* best practice.

If you use something directly, then you should be explicit about that
dependency.

http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.htmlwill
report failures for you so you can check.

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