-
Improvement
-
Resolution: Fixed
-
Major
-
None
Currently, the behavior of the Maven plugin is to first parse the main pom, then execute pre-build if available.
In our case, this causes a problem because we don't store pom.xml directly in our scm, it needs to be instanciated from a template.
We would need to be able to execute pre-build before parsing the POM.
Judging from hudson.maven.MavenModuleSetBuild class it seems easy enough to do.
- is related to
-
JENKINS-7985 In Maven2 jobs, parsing POM is done *after* calling pre-build steps (using M2-extra-steps-plugin)
-
- Open
-
[JENKINS-5428] In Maven2 jobs, parsing POM is done *before* calling pre-build steps (using M2-extra-steps-plugin)
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
Actually I hesitated when opening this about improvement/bug. But since it is by design, definitely improvement.
I don't really see what brings parsing of POMs before pre-build. Are there use cases where pre-builds needs the information obtained from POM parsing ?
| Attachment | New: JENKINS-5428.patch [ 19084 ] |
Any hope of this getting this integrated? Sorry for being a bit pushy, but i'm depending on this to enable maven2 mode on my projects and I would prefer staying on the mainline rather than deploying a private version just for this patch.
mmorizot
added a comment - i'd be interrested too, in a "create my release" job:
- idea is to sed /SNAPSHOT/MYRELEASEVERSION/g on all the poms,
- run the clean install task.
(the release:perform does too much stuff for me, on which i'd like to keep control, like svn interraction)
currently this kindda fails for me, because it seems like the "maven reactor" is keeping in memory the initial parsing of the poms (with the -SNAPSHOT), hense when i upload my artifacts to our artifact repo (artifactory, with the artifactory plugin), the build info keeps the SNAPSHOT version...
mmorizot
added a comment - i'd be interrested too, in a "create my release" job:
idea is to sed /SNAPSHOT/MYRELEASEVERSION/g on all the poms,
run the clean install task.
(the release:perform does too much stuff for me, on which i'd like to keep control, like svn interraction)
currently this kindda fails for me, because it seems like the "maven reactor" is keeping in memory the initial parsing of the poms (with the -SNAPSHOT), hense when i upload my artifacts to our artifact repo (artifactory, with the artifactory plugin), the build info keeps the SNAPSHOT version... | Assignee | New: Vincent Latombe [ vlatombe ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Changing this to an improvement request, since I don't actually consider the current behavior to be a bug. It's that way by design - the POM parsing happens before everything else build-related. That may be something we could consider changing, but it's not a bug.