title: Jenkins Maven Plugin not using environment property for system dependency
body: <p>I am running into a weird issue, where a "Maven" type job is unable to infer environment for system path
  I have defined a weblogic jar as "system" dependency and I provide path to it as a property defined on command line. My pom looks like:
  <a href="https://i.stack.imgur.com/DmTN5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DmTN5.png" alt="enter image description here"></a>
  I have weblogic.home defined in my pom as windows style (for developers), and in my Jenkins job, I pass the server location. In my job job, I run my Maven command as </p>
  
  <pre><code>mvn clean package -Dweblogic.home=/systemPath
  </code></pre>
  
  <p>The command works fine when the job is a freestyle job, but it fails when the job is Maven type, with :</p>
  
  <blockquote>
    <p>[ERROR] 'dependencies.dependency.systemPath' for com.oracle.weblogic:weblogic:jar must specify an absolute path but is C:/localWeblogicPath/server/lib/weblogic.jar @ line 190, column 16</p>
  </blockquote>
  
  <p>The problem happens irrespective of whether I run the maven command as Maven Build Step, or as post build shell script.</p>
  
  <p>To make matters more confusing, in the build, I run exec-maven-plugin which shows the java class being executed and it shows up that correct weblogic.home is passed to it, as shown in snapshot below:</p>
  
  <p><a href="https://i.stack.imgur.com/6hAKE.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/6hAKE.png" alt="enter image description here"></a></p>
  
  <p>Any suggestion on what can I do to make this Maven job pick the right dependency?</p>