-
Improvement
-
Resolution: Incomplete
-
Major
-
None
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...
[JENKINS-11509] maven release plugin does not allow to set the pom file used
Sedat Guclu
added a comment - OK for me, the real "error" was due to the fact that it seems impossible to declare variables in the pom.xml declaration in the main maven section.
Sedat Guclu
added a comment - OK for me, the real "error" was due to the fact that it seems impossible to declare variables in the pom.xml declaration in the main maven section. 
Christoph Burmeister
added a comment - 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.
Christoph Burmeister
added a comment - 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. 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
It users the pom you set in the normal maven configuration.