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

Cannot activate profiles for initially parsing POMs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      Due to the use of the Maven 2.0.x embedder in MavenModuleSetBuild.PomParser, it
      is not possible to activate profiles when initially parsing POMs in the
      top-level job for a Maven project. This can cause parsing to fail if additional
      repositories are activated as part of a profile.

      The current workaround is to have hudson run under a new user with its own .m2
      directory and have whichever profiles are necessary activated by default. That
      way, the profiles are picked up as part of the alignWithUserInstallation
      mechanism in the embedder.

      Solutions discussed include:
      -Use the Maven 2.1 embedder
      -Fork a new Maven instance to parse the poms

        Attachments

          Issue Links

            Activity

            Hide
            kohsuke Kohsuke Kawaguchi added a comment -

            Fixed in 1.170. MavenEmbedder is slightly modified to expose this.

            Show
            kohsuke Kohsuke Kawaguchi added a comment - Fixed in 1.170. MavenEmbedder is slightly modified to expose this.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              gk5885 gk5885
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: