You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/09/27 18:32:00 UTC
[jira] [Commented] (MNG-7772) Allow to register maven core extension in .m2 directory instead of MAVEN_HOME
[ https://issues.apache.org/jira/browse/MNG-7772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769736#comment-17769736 ]
Tamas Cservenak commented on MNG-7772:
--------------------------------------
The reason why this was not considered is how easily makes it possible to shoot yourself in your foot. You have to be _very well aware_ what extension you (at user level?) use, how it alters your local build(s) you execute in your altered "maven home", otherwise builds may end up broken, or just non-transportable ("works for me") or just behave differently (think reproducible builds, etc).
If Maven could "know" what an extension does, and forbid any extension that modifies build, and let only "harmless" (for example alternate resolver transport, etc) extensions, then I'd be 100% with this.
But today, am not opposing, but just want to express my worries about this.
> Allow to register maven core extension in .m2 directory instead of MAVEN_HOME
> ------------------------------------------------------------------------------
>
> Key: MNG-7772
> URL: https://issues.apache.org/jira/browse/MNG-7772
> Project: Maven
> Issue Type: Improvement
> Reporter: Roy Teeuwen
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Currently the way to register a maven core extension is described here: [https://maven.apache.org/guides/mini/guide-using-extensions.html]
> Namely the following ways are supported:
> * Registered via extension jar in {{${maven.home}/lib/ext}}
> * Registered via CLI argument {{mvn -Dmaven.ext.class.path=extension.jar}}
> * Registered via [{{.mvn/extensions.xml}} file|https://maven.apache.org/configure.html#mvn-extensions-xml-file]
> The downside of this is that the ${maven.home} directory is not something that you should touch, seeing as with every update of maven (through for example homebrew), it will replace the directory with the new version, making it required to manually re-register the core extension by dragging the jar in /lib/ext.
> My proposal is to also make it possible to register the extension through the ${user.home}/.m2 directory. This could for example be by also allowing the extensions.xml in the .m2 directory or by creating an ext directory in the .m2 directory.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)