[
https://issues.apache.org/jira/browse/MSHARED-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368754#comment-15368754
]
Hudson commented on MSHARED-567:
--------------------------------
SUCCESS: Integrated in maven-shared #2530 (See
[https://builds.apache.org/job/maven-shared/2530/])
[MSHARED-567] removed compile dependency on Maven core (and discovered hard
dependency on Plexus Container) (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1751975])
* maven-shared-utils/pom.xml
*
maven-shared-utils/src/main/java/org/apache/maven/shared/utils/cli/javatool/AbstractJavaTool.java
*
maven-shared-utils/src/main/java/org/apache/maven/shared/utils/cli/javatool/JavaTool.java
> remove dependency on Maven core
> -------------------------------
>
> Key: MSHARED-567
> URL: https://issues.apache.org/jira/browse/MSHARED-567
> Project: Maven Shared Components
> Issue Type: Wish
> Components: maven-shared-utils
> Affects Versions: maven-shared-utils-3.1.0
> Reporter: Hervé Boutemy
>
> while creating an API for java tool in MSHARED-304, Maven core's Toolchain
> API is used: this makes maven-shared-utils dependant on Maven core.
> Since maven-shared-utils is expected to be a fundamental utilities library,
> ideally which could replace plexus-utils, depending on Maven core will cause
> a chicken and egg issue, since Maven core should be able to use
> maven-shared-utils
> for example, I'm working on MSHARED-562 and this dependency makes me think
> that I cannot let the new code in maven-shared-utils and create a dependency
> from Maven core on maven-shared-utils...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
