[
https://issues.apache.org/jira/browse/MNG-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8338:
---------------------------------
Description:
Ultimately, the following subprojects that should be deprecated and not be
"core" dependencies anymore:
* maven-artifact
* maven-builder-support
* maven-compat
* maven-embedder
* maven-model
* maven-model-builder
* maven-plugin-api
* maven-repository-metadata
* maven-resolver-provider
* maven-resolver-provider
* maven-settings
* maven-settings-builder
* maven-toolchain-builder
* maven-toolchain-model
Subprojects to clean from above dependencies:
* maven-api-impl
* maven-core
* maven-cli
We should keep maven-api-impl as a way to access the resolver through the API,
mostly useful when dealing with dependencies. Maven-core should be kept for
loading and building projects, everything related to plugins, etc...
I think it may be a good time to rename a few more subprojects, to be more
coherent. Maybe rename maven-xml-impl to maven-xml and maven-api-impl to
maven-impl ... ?
was:Subprojects from Maven 3 which have been rewritten to the new Maven 4 API
should become optional and not be linked from maven-core, maven-cling or
maven-api-impl.
> Refactor subprojects to make old ones optional
> ----------------------------------------------
>
> Key: MNG-8338
> URL: https://issues.apache.org/jira/browse/MNG-8338
> Project: Maven
> Issue Type: Improvement
> Reporter: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> Ultimately, the following subprojects that should be deprecated and not be
> "core" dependencies anymore:
> * maven-artifact
> * maven-builder-support
> * maven-compat
> * maven-embedder
> * maven-model
> * maven-model-builder
> * maven-plugin-api
> * maven-repository-metadata
> * maven-resolver-provider
> * maven-resolver-provider
> * maven-settings
> * maven-settings-builder
> * maven-toolchain-builder
> * maven-toolchain-model
> Subprojects to clean from above dependencies:
> * maven-api-impl
> * maven-core
> * maven-cli
> We should keep maven-api-impl as a way to access the resolver through the
> API, mostly useful when dealing with dependencies. Maven-core should be kept
> for loading and building projects, everything related to plugins, etc...
> I think it may be a good time to rename a few more subprojects, to be more
> coherent. Maybe rename maven-xml-impl to maven-xml and maven-api-impl to
> maven-impl ... ?
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
