[
https://issues.jenkins-ci.org/browse/JENKINS-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162671#comment-162671
]
teilo commented on JENKINS-11509:
---------------------------------
You could be running into http://jira.codehaus.org/browse/MRELEASE-568 which
should be fixed for the 2.3 release of the apache maven-release-plugin
> maven release plugin does not allow to set the pom file used
> ------------------------------------------------------------
>
> Key: JENKINS-11509
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11509
> Project: Jenkins
> Issue Type: Improvement
> Components: m2release
> Reporter: Sedat Guclu
> Assignee: teilo
>
> The m2-release-plugin does not allow to define the pom file name and location
> as it is possible in a standard maven-type job. It is blocking for some of
> projects because the pom.xml file is not always located at the job's root
> directory (dotnet project with solution files located in subdirectories).
> An option to set the location (with the default "pom.xml" value) would be
> nice...
--
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
