[
https://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161604#comment-161604
]
SCM/JIRA link daemon commented on JENKINS-8663:
-----------------------------------------------
Code changed in jenkins
User: Vincent Latombe
Path:
changelog.html
maven-plugin/src/main/java/hudson/maven/MavenEmbedderRequest.java
maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
maven-plugin/src/main/java/hudson/maven/MavenUtil.java
http://jenkins-ci.org/commit/jenkins/1421ca15d5a36706214476e613eeab789b9066df
Log:
[FIXED JENKINS-8663] Flag -U is not used during the parsing step of a
Maven Job
If the -U flag is specified in the goals/options of the build step of a
Maven job, it should be used as well in the parsing step.
> Parsing of POM happens before SNAPSHOT-Parents are updated
> ----------------------------------------------------------
>
> Key: JENKINS-8663
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8663
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Environment: Hudson 1.394
> Reporter: Stephan Pauxberger
> Priority: Blocker
>
> Given the following constellation.
> Project A 1.0-SNAPSHOT (POM only)
> Project B 1.0-SNAPSHOT (Jar, has A as parent)
> Both jobs use private Maven repositories.
> Both projects have a separate job.
> Change something in project A, commit. Job A builds and deploys to repository
> Change something in project B that dependes on changes in project A. Commit.
> Job B starts an resolves the POM using the old parent POM, potentially
> leading to a broken build.
> For example: B declares a dependency WITH a version. Now remove the version
> from B and enter a dependencyManagement entry into A. Commit A, later B.
> Result: B fails because pom validation has no valid version for the
> dependency.
> Only solution (since private repositories are used): Clean workspace of B via
> Webinterface, the rebuild B.
--
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
