[jira] [Commented] (MNG-5820) Allow extensions in settings.xml
[ https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434824#comment-16434824 ] James Z.M. Gao commented on MNG-5820: - When settings.xml parser meeting unknown tags, it seems only report a warning, not fail the building. > Allow extensions in settings.xml > > > Key: MNG-5820 > URL: https://issues.apache.org/jira/browse/MNG-5820 > Project: Maven > Issue Type: Improvement > Components: Bootstrap Build >Affects Versions: 3.3.1 >Reporter: Yuri >Priority: Minor > Fix For: Issues to be reviewed for 4.x > > > Since 3.3.1, we are now allowed to specify extensions in the > projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a > case where repo urls are externalized to ~/.m2/settings.xml and these urls > require an extension. Right now, the url and the extension that goes along > with it are managed in two completely different places. > Ideally, I would like to see the option to add an extension to our existing > ~/.m2/settings.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5820) Allow extensions in settings.xml
[ https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047020#comment-16047020 ] Yuri commented on MNG-5820: --- Is there any point in the future where a backward compatible change to settings.xml can be made? It seems that this is a limitation of the settings.xml parser by not ignoring what it doesn't understand. Unless this behavior changes it means that any changes to settings.xml will be postponed to an indefinite future. Can we fix the parser at least now so this can happen in the future? > Allow extensions in settings.xml > > > Key: MNG-5820 > URL: https://issues.apache.org/jira/browse/MNG-5820 > Project: Maven > Issue Type: Improvement > Components: Bootstrap & Build >Affects Versions: 3.3.1 >Reporter: Yuri >Priority: Minor > Fix For: Issues to be reviewed for 4.x > > > Since 3.3.1, we are now allowed to specify extensions in the > projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a > case where repo urls are externalized to ~/.m2/settings.xml and these urls > require an extension. Right now, the url and the extension that goes along > with it are managed in two completely different places. > Ideally, I would like to see the option to add an extension to our existing > ~/.m2/settings.xml. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-5820) Allow extensions in settings.xml
[
https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16046765#comment-16046765
]
Karl Heinz Marbaise commented on MNG-5820:
--
Having an extensions entry in your {{settings.xml}} can only being read by a
version which supports this. All earlier versions would fail with that This
means breaking backwards compatibility.
> Allow extensions in settings.xml
>
>
> Key: MNG-5820
> URL: https://issues.apache.org/jira/browse/MNG-5820
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.3.1
>Reporter: Yuri
>Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
>
> Since 3.3.1, we are now allowed to specify extensions in the
> projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a
> case where repo urls are externalized to ~/.m2/settings.xml and these urls
> require an extension. Right now, the url and the extension that goes along
> with it are managed in two completely different places.
> Ideally, I would like to see the option to add an extension to our existing
> ~/.m2/settings.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-5820) Allow extensions in settings.xml
[
https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16046531#comment-16046531
]
Yuri commented on MNG-5820:
---
I am wondering why such change would break backwards compatibility. Wouldn't
this mean basically a new, optional element along side ,
etc?
{code:xml}
io.takari.polyglot
polyglot-ruby
0.1.5
{code}
> Allow extensions in settings.xml
>
>
> Key: MNG-5820
> URL: https://issues.apache.org/jira/browse/MNG-5820
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.3.1
>Reporter: Yuri
>Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
>
> Since 3.3.1, we are now allowed to specify extensions in the
> projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a
> case where repo urls are externalized to ~/.m2/settings.xml and these urls
> require an extension. Right now, the url and the extension that goes along
> with it are managed in two completely different places.
> Ideally, I would like to see the option to add an extension to our existing
> ~/.m2/settings.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-5820) Allow extensions in settings.xml
[
https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995651#comment-14995651
]
Karl Heinz Marbaise commented on MNG-5820:
--
The problem here is simply changing the {{settings.xml}} format..which would
break many things...BTW: Can you give an example of those URL's which you have
externalized to {{settings.xml}}...
> Allow extensions in settings.xml
>
>
> Key: MNG-5820
> URL: https://issues.apache.org/jira/browse/MNG-5820
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.3.1
>Reporter: Yuri
>Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
>
> Since 3.3.1, we are now allowed to specify extensions in the
> projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a
> case where repo urls are externalized to ~/.m2/settings.xml and these urls
> require an extension. Right now, the url and the extension that goes along
> with it are managed in two completely different places.
> Ideally, I would like to see the option to add an extension to our existing
> ~/.m2/settings.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5820) Allow extensions in settings.xml
[
https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995818#comment-14995818
]
Yuri commented on MNG-5820:
---
Here is an example of what I want to have working without having to add
anything else to the source tree in SCM.
My parent pom.xml has something along the following lines:
{code:xml}
maven-dev
Releases
${repository.releases}
false
maven-dev
Snapshots
${repository.snapshots}
false
{code}
My settings.xml has the following:
{code:xml}
default
default
s3://dev.repo/releases
s3://dev.repo/snapshots
maven-dev
MYS3ACCESSKEY
MYS3PRIVATEKEY
MYS3PRIVATEKEY
{code}
This doesn't work since Maven doesn't know how to handle S3 and the only way
around is to add the S3 Wagon to the Maven installation, which is a bit of a
pain in a team environment and new releases coming ever other month.
Now, I understand how changing settings.xml is concerning since it will/may
break backwards compatibility. However, what about allowing the same
extensions.xml but also in ~/.m2/extensions.xml? The minimum requirement here,
imo, is just to be able to specific a custom repository URL in settings.xml and
have it also work without having to change somewhere else either in the source
tree in SCM or in the Maven install. I would be happy to be able to add an
extensions.xml alongside settings.xml. Now on boarding new devs will simply
mean copying these two files to ~/.m2/ folder and everything should work. When
time comes to move the repo somewhere else, I only need to send updated
settings.xml/extensions.xml and everything should work.
> Allow extensions in settings.xml
>
>
> Key: MNG-5820
> URL: https://issues.apache.org/jira/browse/MNG-5820
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.3.1
>Reporter: Yuri
>Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
>
> Since 3.3.1, we are now allowed to specify extensions in the
> projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a
> case where repo urls are externalized to ~/.m2/settings.xml and these urls
> require an extension. Right now, the url and the extension that goes along
> with it are managed in two completely different places.
> Ideally, I would like to see the option to add an extension to our existing
> ~/.m2/settings.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5820) Allow extensions in settings.xml
[ https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538250#comment-14538250 ] Chris Pimlott commented on MNG-5820: I agree, this issue basically makes it impossible to add a mirror using a non-standard protocol, e.g. scpexe, in a safe and consistent way. Allow extensions in settings.xml Key: MNG-5820 URL: https://issues.apache.org/jira/browse/MNG-5820 Project: Maven Issue Type: Improvement Components: Bootstrap Build Affects Versions: 3.3.1 Reporter: Yuri Priority: Minor Since 3.3.1, we are now allowed to specify extensions in the projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a case where repo urls are externalized to ~/.m2/settings.xml and these urls require an extension. Right now, the url and the extension that goes along with it are managed in two completely different places. Ideally, I would like to see the option to add an extension to our existing ~/.m2/settings.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
