-
Improvement
-
Resolution: Duplicate
-
Major
-
None
doesn't seem that the maven release plugin accommodates a non-standard named pom (i.e., my-pom.xml). Would like to have the release plugin be able to work with this feature.
[JENKINS-12034] Allow Maven Release Plugin to release non-standard pom.xml files
You do this in the normal Jenkins way - nothing special and it has worked before.
Mike Smithson
added a comment - When you say "You do this the normal Jenkins way, nothing special" - we have tried this by specifying the root pom to be the non-standard pom, also passing the -f argument in maven options for the release plugin. Maybe it's just very confusing where you pass the pom you want processed - do you specify in the main job configuration area or do you specify it in the plugin configuration area? We have tried both and have been unsuccessful with the job complaining that it cannot find a pom to process.
Mike Smithson
added a comment - When you say "You do this the normal Jenkins way, nothing special" - we have tried this by specifying the root pom to be the non-standard pom, also passing the -f argument in maven options for the release plugin. Maybe it's just very confusing where you pass the pom you want processed - do you specify in the main job configuration area or do you specify it in the plugin configuration area? We have tried both and have been unsuccessful with the job complaining that it cannot find a pom to process. It is the normal maven build section.
Entering something other than pom.xml as the "Root POM" does the magic.
If this is not the case can you attach the console output, jenkins plugin and jenkins versions and OS info, maven version and a sample maven project (with all plugin versions locked down).
Can you also confirm that running "mvn -f someotherpom.xml release:prepare release:perform" with the same maven version on the same machine with the same user works correctly?
reassigning to m2release