Matt removed the test scope on July 23 with a comment of “Remove unused maven 
properties and scopes”. To be honest, I am not sure why we have a dependency on 
Maven core at all.  Also, it is declared there in the dependencyManagement, so 
it isn’t actually being declared as a dependency there.  I don’t see it 
referenced anywhere else so it will only impact transitive dependencies.

Ralph

> On Oct 24, 2014, at 5:59 AM, Gary Gregory <[email protected]> wrote:
> 
> 
> In the parent POM I see:
> 
>       <dependency>
>         <groupId>org.apache.maven</groupId>
>         <artifactId>maven-core</artifactId>
>         <version>3.1.0</version>
>       </dependency>
> 
> The only direct reference I see to Maven is in:
> 
> log4j-api/src/test/java/org/apache/logging/log4j/osgi/BundleTestInfo.java
> 
> Shouldn't the dep be <scope>test</scope>?
> 
> Gary
> -- 
> E-Mail: [email protected] <mailto:[email protected]> | 
> [email protected]  <mailto:[email protected]>
> Java Persistence with Hibernate, Second Edition 
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>

Reply via email to