[ 
https://issues.apache.org/jira/browse/MSHARED-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MSHARED-567.
---------------------------------
       Resolution: Fixed
         Assignee: Hervé Boutemy
    Fix Version/s: maven-shared-utils-3.1.0

> 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
>            Assignee: Hervé Boutemy
>             Fix For: maven-shared-utils-3.1.0
>
>
> 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)

Reply via email to