[jira] [Commented] (MNG-5897) Make extensions configurable in a more convenient way
[
https://issues.apache.org/jira/browse/MNG-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728347#comment-17728347
]
Guillaume Nodet commented on MNG-5897:
--
I guess the problem is that it would require adding a new xml element in the
POM. This will require a change from 4.0.0 to something else and I'm not sure
how this should be taken care of ...
The initial target was a 5.0.0 pom:
[https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0#POMModelVersion5.0.0-XMLvscustomDSL]
... but maybe we can do it iteratively. The question is how to deal (or not)
with compatibility ...
> Make extensions configurable in a more convenient way
> -
>
> Key: MNG-5897
> URL: https://issues.apache.org/jira/browse/MNG-5897
> Project: Maven
> Issue Type: New Feature
> Components: Core
>Affects Versions: 3.3.3
>Reporter: Karl Heinz Marbaise
>Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Currently you can configure using an extensions via {{.mvn/extensions.xml}}
> to load it.
> But at the moment the only possibility to configure your extensions (or
> control behaviour) is via system properties like {{-Dwhatever=...}}.
> It would be convenient to make configuration possible in
> {{.mvn/extensions.xml}} like the plugin configuration are in pom file...
> {code:xml}
> http://maven.apache.org/EXTENSIONS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0
> http://maven.apache.org/xsd/core-extensions-1.0.0.xsd";>
>
>
>
>
>
> ...
>
>
>
> {code}
> with some kind of replacements like in the pom.xml file (like
> {{$\{project.basedir}}} etc.) ?
> This could make the usage of extensions much more convenient...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-5897) Make extensions configurable in a more convenient way
[
https://issues.apache.org/jira/browse/MNG-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728003#comment-17728003
]
Giovanni van der Schelde commented on MNG-5897:
---
Since it is an old issue, is this still a feature we want in Maven? If so, I'd
be happy to give it a shot and see if I can investigate on how to approach this.
> Make extensions configurable in a more convenient way
> -
>
> Key: MNG-5897
> URL: https://issues.apache.org/jira/browse/MNG-5897
> Project: Maven
> Issue Type: New Feature
> Components: Core
>Affects Versions: 3.3.3
>Reporter: Karl Heinz Marbaise
>Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Currently you can configure using an extensions via {{.mvn/extensions.xml}}
> to load it.
> But at the moment the only possibility to configure your extensions (or
> control behaviour) is via system properties like {{-Dwhatever=...}}.
> It would be convenient to make configuration possible in
> {{.mvn/extensions.xml}} like the plugin configuration are in pom file...
> {code:xml}
> http://maven.apache.org/EXTENSIONS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0
> http://maven.apache.org/xsd/core-extensions-1.0.0.xsd";>
>
>
>
>
>
> ...
>
>
>
> {code}
> with some kind of replacements like in the pom.xml file (like
> {{$\{project.basedir}}} etc.) ?
> This could make the usage of extensions much more convenient...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-5897) Make extensions configurable in a more convenient way
[
https://issues.apache.org/jira/browse/MNG-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690862#comment-17690862
]
Roy Teeuwen commented on MNG-5897:
--
+1 for this feature request. I also have some parameters i'd like to pass to
the core extensions that I want to use
> Make extensions configurable in a more convenient way
> -
>
> Key: MNG-5897
> URL: https://issues.apache.org/jira/browse/MNG-5897
> Project: Maven
> Issue Type: New Feature
> Components: Core
>Affects Versions: 3.3.3
>Reporter: Karl Heinz Marbaise
>Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Currently you can configure using an extensions via {{.mvn/extensions.xml}}
> to load it.
> But at the moment the only possibility to configure your extensions (or
> control behaviour) is via system properties like {{-Dwhatever=...}}.
> It would be convenient to make configuration possible in
> {{.mvn/extensions.xml}} like the plugin configuration are in pom file...
> {code:xml}
> http://maven.apache.org/EXTENSIONS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0
> http://maven.apache.org/xsd/core-extensions-1.0.0.xsd";>
>
>
>
>
>
> ...
>
>
>
> {code}
> with some kind of replacements like in the pom.xml file (like
> {{$\{project.basedir}}} etc.) ?
> This could make the usage of extensions much more convenient...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-5897) Make extensions configurable in a more convenient way.
[
https://issues.apache.org/jira/browse/MNG-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212698#comment-17212698
]
mike duigou commented on MNG-5897:
--
This would be a useful enhancement!
Be aware that more generality of the core extensions mechanism is also needed
to support multi-module and aggregator projects. (See MNG-6995)
> Make extensions configurable in a more convenient way.
> --
>
> Key: MNG-5897
> URL: https://issues.apache.org/jira/browse/MNG-5897
> Project: Maven
> Issue Type: New Feature
> Components: core
>Affects Versions: 3.3.3
>Reporter: Karl Heinz Marbaise
>Priority: Major
>
> Currently you can configure using an extensions via {{.mvn/extensions.xml}}
> to load it.
> But at the moment the only possibility to configure your extensions (or
> control behaviour) is via system properties like {{-Dwhatever=...}}.
> It would be convenient to make configuration possible in
> {{.mvn/extensions.xml}} like the plugin configuration are in pom file...
> {code:xml}
> http://maven.apache.org/EXTENSIONS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0
> http://maven.apache.org/xsd/core-extensions-1.0.0.xsd";>
>
>
>
>
>
> ...
>
>
>
> {code}
> with some kind of replacements like in the pom.xml file (like
> {{$\{project.basedir}}} etc.) ?
> This could make the usage of extensions much more convenient...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-5897) Make extensions configurable in a more convenient way.
[
https://issues.apache.org/jira/browse/MNG-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182858#comment-17182858
]
Falko Modler commented on MNG-5897:
---
Better configuration support for extensions would be very much appreciated!
I am maintaining https://github.com/vackosar/gitflow-incremental-builder (GIB)
and I just recently added a "fake" plugin/mojo to expose the many properties
(and their descriptions) in an IDE and help-plugin friendly way.
This comes at the price of either maintaining the properties twice manually or
at the price of added complexity for generating the plugin parameters (see
[MojoParametersGeneratingByteBuddyPlugin|https://github.com/vackosar/gitflow-incremental-builder/blob/master/src/main/java/com/vackosar/gitflowincrementalbuild/mojo/MojoParametersGeneratingByteBuddyPlugin.java]).
It would be really great if (with the proposed solution) extension parameters
and their descriptions would be picked up by IDEs and the help-plugin.
Another approach might be to enhance the plugin + extension hybrid setup (like
GIB is using) to have `@Parameter` (or something else) recognized on non-mojo
classes.
Btw: The downside of {{.mvn/extensions.xml}} is that you cannot use profiles
there and I am not sure whether tools like GitHub Dependabot will pick up such
extensions (defined outside of {{pom.xml}}).
> Make extensions configurable in a more convenient way.
> --
>
> Key: MNG-5897
> URL: https://issues.apache.org/jira/browse/MNG-5897
> Project: Maven
> Issue Type: New Feature
> Components: core
>Affects Versions: 3.3.3
>Reporter: Karl Heinz Marbaise
>Priority: Major
>
> Currently you can configure using an extensions via {{.mvn/extensions.xml}}
> to load it.
> But at the moment the only possibility to configure your extensions (or
> control behaviour) is via system properties like {{-Dwhatever=...}}.
> It would be convenient to make configuration possible in
> {{.mvn/extensions.xml}} like the plugin configuration are in pom file...
> {code:xml}
> http://maven.apache.org/EXTENSIONS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0
> http://maven.apache.org/xsd/core-extensions-1.0.0.xsd";>
>
>
>
>
>
> ...
>
>
>
> {code}
> with some kind of replacements like in the pom.xml file (like
> {{$\{project.basedir}}} etc.) ?
> This could make the usage of extensions much more convenient...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
