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

In Maven2 jobs, variable expansion is not done for the root POM path and alternative settings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • None
    • Hudson 1.349, Clearcase plugin 1.1.1

      I'm trying to convert an existing free-style job to maven2.
      Since I use also the Clearcase plugin, I use the ${CLEARCASE_VIEWNAME}/pom.xml to reference my root pom. Inside a freestyle job, no problem, but when using maven2 job, the variable is not expanded.
      The same applies to the alternative settings. If I provide it in options it is expanded correctly, but not in the dedicaced field. This is problematic because then, it cannot be used for post-build deployment for instance.

            olamy Olivier Lamy
            vlatombe Vincent Latombe
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: