[
https://issues.jenkins-ci.org/browse/JENKINS-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Burmeister reopened JENKINS-11509:
--------------------------------------------
Actually this ticket must be reopened, because I'm facing the same error now
with Jenkins version 1.454, Plugin version 0.9.1 and Maven 3.0.4. There is no
option to set the pom-name (-f option) for the release:prepare/perform and the
"normal" maven configuration is not used within releases. Any ideas? I have a
project with multiple poms in the same directory, so I have to give different
names for them.
> 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
