[
https://issues.apache.org/jira/browse/MNG-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805749#comment-17805749
]
Benjamin Muschko commented on MNG-8008:
---------------------------------------
My concrete use case is the following:
* I want to build a GitHub Action that configures a Maven extension
automatically for any build run with a workflow.
* A build step of that workflow can specify a working directory
({{{}jobs.<job-name>.steps.working-directory{}}}) so deriving a {{.mvn}}
directory relative to the root project directory isn't known at that point of
execution. It can be relative to the checked out directory but doesn't have to
be.
* A centrally-configurable {{extensions.xml}} would solve the problem as it
would be picked up by any Maven build independent of the working directory.
* A custom distribution is not a suitable solution for me as I'd have to host
it on a public server. This isn't meant for company-internal purposes
necessarily and I'd assume that end users would be very cautious about using a
custom distro due to security concerns. I guess I could build a custom Maven
distribution on-the-fly as part of the GitHub Action but that is far more
complicated than it should be for this use case.
I don't see another option that would be fitting to solve my use case. I guess
you can close the ticket if there are no plans to support a "global"
{{{}extensions.xml{}}}.
> 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)
