[
https://issues.jenkins-ci.org/browse/JENKINS-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161724#comment-161724
]
Romain Linsolas commented on JENKINS-6172:
------------------------------------------
In fact, you can put an absolute path in this field, even if an error is
displayed.
I would be good to remove the corresponding check (in
MavenModuleSet.doCheckFileRelative:1087) :
{code}
if ((v.startsWith("/")) || (v.startsWith("\\")) ||
(v.matches("^\\w\\:\\\\.*"))) {
return
FormValidation.error(Messages.MavenModuleSet_AlternateSettingsRelativePath());
}
{code}
> Requirement that alternative maven settings be a relative path is a problem
> ---------------------------------------------------------------------------
>
> Key: JENKINS-6172
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6172
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Reporter: bimargulies
>
>
> Alternate settings file must be a relative path.
> This is a problem. We want to just put the maven settings file in a single,
> global, pathname and put an abs pathname in this slot. I appreciate that this
> could cause a problem, but why should hudson protect us from ourselves in
> this way?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
