Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26472

Jenkins maven-project plugin doesn't support reactor module exclusion

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • maven-plugin
    • None
    • Jenkins ver. 1.540
      maven-project ver. 2.8

        [JENKINS-26472] Jenkins maven-project plugin doesn't support reactor module exclusion

        Daniel Beck added a comment -

        Please make sure this issue occurs on latest weekly or LTS release of Jenkins and latest available Maven Plugin. Update the issue with that information once you do.

        Reducing priority as this is clearly neither Blocker nor Critical, and since it seems to be rather unusual (it doesn't look like many actually need this) I wouldn't consider it Major loss of functionality either.

        Daniel Beck added a comment - Please make sure this issue occurs on latest weekly or LTS release of Jenkins and latest available Maven Plugin. Update the issue with that information once you do. Reducing priority as this is clearly neither Blocker nor Critical, and since it seems to be rather unusual (it doesn't look like many actually need this) I wouldn't consider it Major loss of functionality either.

        I've confirmed that this is still not supported with 2.8 version of maven-project, but I don't have the time to setup jenkins nightly now.

        > it seems to be rather unusual (it doesn't look like many actually need this) I wouldn't consider it Major loss of functionality either.
        It is a major loss of functionality for me – this was actually the reason to upgrade to maven 3.2 for me
        It might be simply that not many people are aware of the functionality, but the problem is well known and used to be solved by dupicating module declarations over profiles, c.f. https://stackoverflow.com/questions/5539348/how-to-exclude-a-module-from-a-maven-reactor-build (the old answer still has more votes)

        Jakub Bochenski added a comment - I've confirmed that this is still not supported with 2.8 version of maven-project, but I don't have the time to setup jenkins nightly now. > it seems to be rather unusual (it doesn't look like many actually need this) I wouldn't consider it Major loss of functionality either. It is a major loss of functionality for me – this was actually the reason to upgrade to maven 3.2 for me It might be simply that not many people are aware of the functionality, but the problem is well known and used to be solved by dupicating module declarations over profiles, c.f. https://stackoverflow.com/questions/5539348/how-to-exclude-a-module-from-a-maven-reactor-build (the old answer still has more votes)

        Andreas Horst added a comment -

        Please reconsider effectively simply ignoring this issue as it is clearly a fault in the Maven integration in Jenkins. Luckily we were able to workaround this fault but that should not be the regular approach here.

        Andreas Horst added a comment - Please reconsider effectively simply ignoring this issue as it is clearly a fault in the Maven integration in Jenkins. Luckily we were able to workaround this fault but that should not be the regular approach here.

        Yeah it seems to me now I should have just followed the advice on the net and not use the maven plugin at all.

        there is no way you can replicate the injected hooks that Jenkins puts into your Maven build

        When it blows up, and it will blow up, it blows up big

        http://javaadventure.blogspot.com/2013/11/jenkins-maven-job-type-considered-evil.html

        Jakub Bochenski added a comment - Yeah it seems to me now I should have just followed the advice on the net and not use the maven plugin at all. there is no way you can replicate the injected hooks that Jenkins puts into your Maven build When it blows up, and it will blow up, it blows up big http://javaadventure.blogspot.com/2013/11/jenkins-maven-job-type-considered-evil.html

        Daniel Beck added a comment -

        Please reconsider effectively simply ignoring this issue

        I really doubt anyone is actively ignoring this issue. If you're referring to me reducing priority, please note that before I reviewed most of the unresolved core issues in this tracker, we had dozens and dozens of blocker/critical core issues (in many cases, just like this one, they weren't actually that severe), and nobody cared about those either. It's not like an alarm goes off somewhere whenever an issue with high "priority" gets filed.

        As far as I can tell, priority is given to regressions, issues affecting many users, and issues that the developers themselves want to see fixed (and, in the case of Cloudbees employed Jenkins devs, issues from customer support requests). This issue seems to be none of the above.

        Daniel Beck added a comment - Please reconsider effectively simply ignoring this issue I really doubt anyone is actively ignoring this issue. If you're referring to me reducing priority, please note that before I reviewed most of the unresolved core issues in this tracker, we had dozens and dozens of blocker/critical core issues (in many cases, just like this one, they weren't actually that severe), and nobody cared about those either. It's not like an alarm goes off somewhere whenever an issue with high "priority" gets filed. As far as I can tell, priority is given to regressions, issues affecting many users, and issues that the developers themselves want to see fixed (and, in the case of Cloudbees employed Jenkins devs, issues from customer support requests). This issue seems to be none of the above.

        Andreas Horst added a comment -

        Yes, actually I agree with you. I was kind of hit by the Stockholm Syndrome and did not think about simply switching to the regular job type.

        Andreas Horst added a comment - Yes, actually I agree with you. I was kind of hit by the Stockholm Syndrome and did not think about simply switching to the regular job type.

        Hi, I should set sub-projects to build in place of sub-project that isn't to build. That's right?

        Maxsoel Alberton added a comment - Hi, I should set sub-projects to build in place of sub-project that isn't to build. That's right?

        Code changed in jenkins
        User: Olivier Lamy
        Path:
        maven32-interceptor/src/main/java/org/apache/maven/cli/DefaultMavenExecutionRequestBuilder.java
        http://jenkins-ci.org/commit/maven-interceptors/5792f2a7f19f76b1ea879cf2198d37d761790bda
        Log:
        Merge pull request #7 from rmuhic/master

        JENKINS-26472 Updating builder to recognize negation flags in project list

        Compare: https://github.com/jenkinsci/maven-interceptors/compare/57bd99b2f7a9...5792f2a7f19f

        SCM/JIRA link daemon added a comment - Code changed in jenkins User: Olivier Lamy Path: maven32-interceptor/src/main/java/org/apache/maven/cli/DefaultMavenExecutionRequestBuilder.java http://jenkins-ci.org/commit/maven-interceptors/5792f2a7f19f76b1ea879cf2198d37d761790bda Log: Merge pull request #7 from rmuhic/master JENKINS-26472 Updating builder to recognize negation flags in project list Compare: https://github.com/jenkinsci/maven-interceptors/compare/57bd99b2f7a9...5792f2a7f19f

          Unassigned Unassigned
          jbochenski Jakub Bochenski
          Votes:
          9 Vote for this issue
          Watchers:
          12 Start watching this issue

            Created:
            Updated: