[ 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} > <extensions xmlns="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"> > <extension> > <groupId/> > <artifactId/> > <version/> > <configuration> > <parameter>...</parameter> > </configuration> > </extension> > </extensions> > {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)