[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:13 PM:
-
I can work on an example project and post it here. I am talking about the flag
{{-U}} aka {{{}\-\-{{{}update-snapshots{}}}{}}}. Sorry, I misspelled the flag
in my initial posting.
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about the flag
{{\-U}} aka {{{}-update-snapshots{}}}. Sorry, I misspelled the flag in my
initial posting.
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:13 PM:
-
I can work on an example project and post it here. I am talking about the flag
{{-U}} aka {{{}\-\-update\-snapshots{}}}. Sorry, I misspelled the flag in my
initial posting.
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about the flag
{{-U}} aka {{{}\-\-{{{}update-snapshots{}}}{}}}. Sorry, I misspelled the flag
in my initial posting.
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:12 PM:
-
I can work on an example project and post it here. I am talking about the flag
{{\-U}} aka {{{}-update-snapshots{}}}. Sorry, I misspelled the flag in my
initial posting.
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about the flag
{{-U}} aka {{{}--update-snapshots{}}}. Sorry, I misspelled the flag in my
initial posting.
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:12 PM:
-
I can work on an example project and post it here. I am talking about the flag
{{-U}} aka {{{}--update-snapshots{}}}. Sorry, I misspelled the flag in my
initial posting.
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{} -U{}}},{{{}--update-snapshots{}}} Forces a check for
missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:11 PM:
-
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{} -U{}}},{{{}--update-snapshots{}}} Forces a check for
missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{{ -U,--update-snapshots Forces a check for missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:10 PM:
-
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{{ -U,--update-snapshots Forces a check for missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{quote} -U,--update-snapshots Forces a check for missing
releases and updated snapshots on
remote repositories
{quote}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:10 PM:
-
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{quote} -U,--update-snapshots Forces a check for missing
releases and updated snapshots on
remote repositories
{quote}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{{ {-}U,{-}-update-snapshots Forces a check for missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:09 PM:
-
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{{ {-}U,{-}-update-snapshots Forces a check for missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{{ -U,--update-snapshots Forces a check for missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
{{ }}}
{{}}}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Muschko updated MSOURCES-148:
--
Description: Executing the build with the flag {{--update-snapshots}}
should only update SNAPSHOT dependencies. The plugin doesn't seem to evaluate
this flag. Running the build with the flag will update SNAPSHOT _and_ final
dependencies leading to a much longer build time. (was: Executing the build
with the flag {{--update-dependencies}} should only update SNAPSHOT
dependencies. The plugin doesn't seem to evaluate this flag. Running the build
with the flag will update SNAPSHOT _and_ final dependencies leading to a much
longer build time.)
Summary: The plugin should respect the --update-snapshots for final
versions (was: The plugin should respect the --update-dependencies for final
versions)
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSOURCES-148) The plugin should respect the --update-snapshots for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko edited comment on MSOURCES-148 at 5/13/24 12:10 PM:
-
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{quote} -U,--update-snapshots Forces a check for missing
releases and updated snapshots on
remote repositories
{quote}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
was (Author: bmuschko):
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{quote} -U,--update-snapshots Forces a check for missing
releases and updated snapshots on
remote repositories
{quote}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
}
}
> The plugin should respect the --update-snapshots for final versions
> ---
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-snapshots}} should only update
> SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
> the build with the flag will update SNAPSHOT _and_ final dependencies leading
> to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSOURCES-148) The plugin should respect the --update-dependencies for final versions
[
https://issues.apache.org/jira/browse/MSOURCES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845896#comment-17845896
]
Benjamin Muschko commented on MSOURCES-148:
---
I can work on an example project and post it here. I am talking about this
flag. Sorry, I misspelled the flag in my initial posting.
{{ -U,--update-snapshots Forces a check for missing}}
{{ releases and updated snapshots on}}
{{ remote repositories}}
You can access Maven runtime configuration via the following code for example:
{{@Parameter(defaultValue = "${session}", readonly = true)}}
{{private MavenSession session;}}
{{public void execute() {}}
{{ if (session.getRequest().isNoSnapshotUpdates()) {}}
{{ ...}}
{{ }}}
{{}}}
> The plugin should respect the --update-dependencies for final versions
> --
>
> Key: MSOURCES-148
> URL: https://issues.apache.org/jira/browse/MSOURCES-148
> Project: Maven Source Plugin
> Issue Type: New Feature
>Reporter: Benjamin Muschko
>Priority: Major
>
> Executing the build with the flag {{--update-dependencies}} should only
> update SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag.
> Running the build with the flag will update SNAPSHOT _and_ final dependencies
> leading to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSOURCES-148) The plugin should respect the --update-dependencies for final versions
Benjamin Muschko created MSOURCES-148:
-
Summary: The plugin should respect the --update-dependencies for
final versions
Key: MSOURCES-148
URL: https://issues.apache.org/jira/browse/MSOURCES-148
Project: Maven Source Plugin
Issue Type: New Feature
Reporter: Benjamin Muschko
Executing the build with the flag {{--update-dependencies}} should only update
SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
the build with the flag will update SNAPSHOT _and_ final dependencies leading
to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8008) Extensions should be configurable centrally for all Maven projects on a single machine
[
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..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)
[jira] [Commented] (MNG-8008) Extensions should be configurable centrally for all Maven projects on a single machine
[
https://issues.apache.org/jira/browse/MNG-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805654#comment-17805654
]
Benjamin Muschko commented on MNG-8008:
---
The directory {{${maven.home}/lib/ext}} only processes a JAR file, not the
{{extensions.xml}} file. The extension already exists on a public repository so
this option wouldn't fulfill my use case.
Example:
{{}}
{{ }}
{{ com.gradle}}
{{ gradle-enterprise-maven-extension}}
{{ 1.20}}
{{ }}
{{}}
> 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)
[jira] [Updated] (MNG-8008) Extensions should be configurable centrally for all Maven projects on a single machine
[
https://issues.apache.org/jira/browse/MNG-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Muschko updated MNG-8008:
--
Description:
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.
was:
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.
> 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)
[jira] [Created] (MNG-8008) Extensions should be configurable centrally for all Maven projects on a single machine
Benjamin Muschko created MNG-8008:
-
Summary: 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
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 message was sent by Atlassian Jira
(v8.20.10#820010)
