maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (MSHARED-567) remove dependency on Maven core
Date Fri, 08 Jul 2016 23:55:11 GMT


Hudson commented on MSHARED-567:

SUCCESS: Integrated in maven-shared #2530 (See [])
[MSHARED-567] removed compile dependency on Maven core (and discovered hard dependency on
Plexus Container) (hboutemy: [])
* maven-shared-utils/pom.xml
* maven-shared-utils/src/main/java/org/apache/maven/shared/utils/cli/javatool/
* maven-shared-utils/src/main/java/org/apache/maven/shared/utils/cli/javatool/

> remove dependency on Maven core
> -------------------------------
>                 Key: MSHARED-567
>                 URL:
>             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

View raw message