[
https://issues.apache.org/jira/browse/MNG-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805610#comment-17805610
]
Tamas Cservenak commented on MNG-8008:
--------------------------------------
Extensions can alter Maven behaviour a lot, thus making it non buildable when
not present. Hence, due this I personally prefer {{.mvn/extensions.xml}} that
IS checked in with sources, making project "self contained". Moreover, if you
talk about organization-wide (company even), they a custom (modded) distro can
be a solution as well.
> Extensions should be configurable centrally for all Maven projects on a
> single machine
> --------------------------------------------------------------------------------------
>
> Key: MNG-8008
> URL: https://issues.apache.org/jira/browse/MNG-8008
> Project: Maven
> Issue Type: New Feature
> Affects Versions: 3.9.6
> Reporter: Benjamin Muschko
> Priority: Minor
>
> Extensions can only be configured in the project directory under
> {{{}.mvn/extensions.xml{}}}. Right now, there's no option to provide an
> extension to all Maven projects running on the same machine. Therefore, the
> same boilerplate code needs to be copied from project to project.
> For example, say you want to add the [Develocity Maven
> extension|https://scans.gradle.com/#maven] for all projects built by a CI
> agent, then this currently not possible would checking the XML into every
> project's source code. For bigger enterprises, this would involve a lot of
> labor or require the use or implementation for an automated script/tool.
> It should be possible to place an {{extensions.xml}} in the Maven home
> directory or configure it as part of {{settings.xml}} to provide the
> extension centrally.
> This issue is related to https://issues.apache.org/jira/browse/MNG-5820
> though the mentioned use case is different.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
