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

maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • pipeline-maven-plugin
    • None
    • Pipeline Maven Integration 3.6.7

      We use the Maven git versioning extension from here
      https://github.com/qoomon/maven-git-versioning-extension

      Very usefull when working with feature branches.

      This produces the following warning:

      [2019-03-21T16:32:15.753Z] [WARNING] [jenkins-event-spy] Unexpected Maven project file name '.git-versioned-pom.xml', problems may occur
      [2019-03-21T16:32:15.753Z] [WARNING] [jenkins-event-spy] Unexpected Maven project file name '.git-versioned-pom.xml', problems may occur
      

      Would be great to get rid of the warning because I get this warning 100 times per build

          [JENKINS-56666] maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'

          Hi Cyrille,

          sadly the extensions changed its behavior again with release 4.1.0, now there is a .git-versioned.pom.xml generated in the target folder.
          Would be great to have a fix for it because this is one of the best maven things I found in the last year.

          Kind regards,
          Michael

          Michael Düsterhus added a comment - Hi Cyrille, sadly the extensions changed its behavior again with release 4.1.0, now there is a .git-versioned.pom.xml generated in the target folder. Would be great to have a fix for it because this is one of the best maven things I found in the last year. Kind regards, Michael

          Cyrille Le Clerc added a comment - reitzmichnicht could you build and test  https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-56666  ? Cyrille

          Will try in the next days

          Michael Düsterhus added a comment - Will try in the next days

          code merged in master branch

          Cyrille Le Clerc added a comment - code merged in master branch

          Cyrille Le Clerc added a comment - Fixed in 3.6.11 https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.11

          Sorry hat no time before to test.
          I tried version 3.6.11 and the error is still the same.
          Did you consider that this plugin modifies the pom.xml to target/.git-versioned.pom.xml
          So its not in the same directory.

          Michael Düsterhus added a comment - Sorry hat no time before to test. I tried version 3.6.11 and the error is still the same. Did you consider that this plugin modifies the pom.xml to target/.git-versioned.pom.xml So its not in the same directory.

          Cyrille Le Clerc added a comment - - edited

          reitzmichnicht can you please share the exact message you get?
          Can you give us details on the type of build agent that you are using? Can you confirm that you don't ue Windows build agents with cygwin (or equivalent)?

          Cyrille Le Clerc added a comment - - edited reitzmichnicht can you please share the exact message you get? Can you give us details on the type of build agent that you are using? Can you confirm that you don't ue Windows build agents with cygwin (or equivalent)?

          We use maven inside linux docker container with sh step.
          Exact message is:

          00:04:18.285  [WARNING] [jenkins-event-spy] Unexpected Maven project file name '.git-versioned-pom.xml', problems may occur
          00:04:18.285  [WARNING] [jenkins-event-spy] Unexpected Maven project file name '.git-versioned-pom.xml', problems may occur
          

          Michael Düsterhus added a comment - We use maven inside linux docker container with sh step. Exact message is: 00:04:18.285 [WARNING] [jenkins-event-spy] Unexpected Maven project file name '.git-versioned-pom.xml', problems may occur 00:04:18.285 [WARNING] [jenkins-event-spy] Unexpected Maven project file name '.git-versioned-pom.xml', problems may occur

          Is working now with 3.6.14. Seems like the file name changed between the versions of the extensions plugin.
          Thank you very much

          Michael Düsterhus added a comment - Is working now with 3.6.14. Seems like the file name changed between the versions of the extensions plugin. Thank you very much

          Cyrille Le Clerc added a comment - - edited

          Thanks reitzmichnicht

          Fixed in 3.6.14

          Cyrille Le Clerc added a comment - - edited Thanks reitzmichnicht Fixed in 3.6.14

            cleclerc Cyrille Le Clerc
            reitzmichnicht Michael Düsterhus
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: