[JIRA] Created: (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

Jenkins issues mailing list
Parsing of POM happens before SNAPSHOT-Parents are updated
----------------------------------------------------------

                 Key: JENKINS-8663
                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8663
             Project: Jenkins
          Issue Type: Bug
          Components: maven2
    Affects Versions: current
         Environment: Hudson 1.394
            Reporter: paux
            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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

Jenkins dev mailing list

    [ http://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145470#comment-145470 ]

paux commented on JENKINS-8663:
-------------------------------

Quick workaround using MavenExtraBuildSteps

Create a prebuild step calling "initialize -N", which is called before parsing of the POM.

> Parsing of POM happens before SNAPSHOT-Parents are updated
> ----------------------------------------------------------
>
>                 Key: JENKINS-8663
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8663
>             Project: Jenkins
>          Issue Type: Bug
>          Components: maven2
>    Affects Versions: current
>         Environment: Hudson 1.394
>            Reporter: paux
>            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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

JIRA noreply@jenkins-ci.org
In reply to this post by Jenkins issues mailing list

    [ https://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158615#comment-158615 ]

evernat commented on JENKINS-8663:
----------------------------------

Can the issue be reproduced with a recent version of Jenkins?
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

JIRA noreply@jenkins-ci.org
In reply to this post by Jenkins issues mailing list

    [ 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

JIRA noreply@jenkins-ci.org
In reply to this post by Jenkins issues mailing list

     [ https://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SCM/JIRA link daemon resolved JENKINS-8663.
-------------------------------------------

    Resolution: Fixed
   

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

JIRA noreply@jenkins-ci.org
In reply to this post by Jenkins issues mailing list

    [ https://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161605#comment-161605 ]

SCM/JIRA link daemon commented on JENKINS-8663:
-----------------------------------------------

Code changed in jenkins
User: Olivier Lamy
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/f0130bf1b2410807fccf4f0c9af259201151228a
Log:
  Merge pull request #442 from Vlatombe/JENKINS-8663

[FIXED JENKINS-8663] Flag -U is not used during the parsing step of a Maven Job
good catch !


Compare: https://github.com/jenkinsci/jenkins/compare/0f08dc0...f0130bf


               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

JIRA noreply@jenkins-ci.org
In reply to this post by Jenkins issues mailing list

    [ https://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161610#comment-161610 ]

dogfood commented on JENKINS-8663:
----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1660|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1660/]
     [FIXED JENKINS-8663] Flag -U is not used during the parsing step of a (Revision 1421ca15d5a36706214476e613eeab789b9066df)

     Result = SUCCESS
Vincent Latombe : [1421ca15d5a36706214476e613eeab789b9066df|https://github.com/jenkinsci/jenkins/commit/1421ca15d5a36706214476e613eeab789b9066df]
Files :
* maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
* changelog.html
* maven-plugin/src/main/java/hudson/maven/MavenEmbedderRequest.java
* maven-plugin/src/main/java/hudson/maven/MavenUtil.java

               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

JIRA noreply@jenkins-ci.org
In reply to this post by Jenkins issues mailing list

    [ https://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161854#comment-161854 ]

dogfood commented on JENKINS-8663:
----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_ui-changes_branch #21|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/21/]
     [FIXED JENKINS-8663] Flag -U is not used during the parsing step of a (Revision 1421ca15d5a36706214476e613eeab789b9066df)

     Result = SUCCESS
Vincent Latombe : [1421ca15d5a36706214476e613eeab789b9066df|https://github.com/jenkinsci/jenkins/commit/1421ca15d5a36706214476e613eeab789b9066df]
Files :
* maven-plugin/src/main/java/hudson/maven/MavenEmbedderRequest.java
* maven-plugin/src/main/java/hudson/maven/MavenUtil.java
* changelog.html
* maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java

               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-8663) Parsing of POM happens before SNAPSHOT-Parents are updated

JIRA noreply@jenkins-ci.org
In reply to this post by Jenkins issues mailing list

    [ https://issues.jenkins-ci.org/browse/JENKINS-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163113#comment-163113 ]

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/feddca252bc2bb295e8b37a24a9063c31b37e702
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.
(cherry picked from commit 1421ca15d5a36706214476e613eeab789b9066df)

Conflicts:

        changelog.html



               

> 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