use artifacts for path, not dependencies

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113596 13f79535-47bb-0310-9956-ffa450edef68

jboss/plugin.jelly

@@ -184,14 +184,14 @@
     description="Creates a specific JBoss server configuration"
     prereqs="jboss:init,jboss:configure">
 
-    <j:forEach var="dep" items="${pom.dependencies}">
+    <j:forEach var="lib" items="${pom.artifacts}">
+      <j:set var="dep" value="${lib.dependency}"/>
       <j:if test="${dep.getProperty('jboss.bundle')=='true'}">
         <ant:echo>Bundling: (${dep.groupId}, ${dep.artifactId}, ${dep.type})</ant:echo>
 
         <!-- TODO: Use getDependencyPath() once it supports artifacts other 
         	 than jars -->
-        <ant:copy todir="${maven.jboss.build.deploy.dir}"
-          file="${maven.repo.local}/${dep.artifactDirectory}/${dep.type}s/${dep.artifact}"/>
+        <ant:copy todir="${maven.jboss.build.deploy.dir}" file="${lib.path}"/>
       </j:if>
     </j:forEach>
     

jboss/xdocs/changes.xml

@@ -8,6 +8,9 @@
   <body>
 
     <release version="1.2" date="in CVS">
+      <action dev="dion" type="fix">
+        Copy dependencies using artifact path to allow jar overrides to work
+      </action>
       <action dev="vmassol" type="add">
         The plugin now supports JBoss 3.2.x by default. Support for
         JBoss 3.0.x is still available by setting the