[MANTTASKS-170] deploy / install tasks make up names

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.1.0
• Component/s: deploy task, install task
• Environment: Windows Vista/Ant 1.7.1/Maven ant tasks 2.1.0
• Assignee: Unassigned
• Reporter: Marcel Ammerlaan
• Created: 22/Dec/09 09:46
• Updated: 25/Nov/14 14:49
• Resolved: 25/Nov/14 14:49

Description

When running a built with the following:

<target name="deploy-to-nexus" depends="package" description="Move SVN jars to Nexus">
  <artifact:pom id="pom1" groupId="nl.fbn.ullink" artifactId="${module}-${ext}" version="${version}">
   <artifact:dependency groupId="junit" artifactId="junit" version="4.1"/>
   <artifact:dependency groupId="org.codehaus.plexus" artifactId="plexus-utils" version="1.5.5"/>
  </artifact:pom>
		
  <artifact:install file="${workspace}/target/${module}-${ext}.tgz">
    <artifact:pom refid="pom1"/>
  </artifact:install>
</target>

The following is logged: [artifact:install] [INFO] Installing e:\tmp\ullink\target\ULBridge_8080-bin.tgz to C:\Users\X09629\.m2\repository\org\apache\maven\super-pom\2.0\super-pom-2.0.jar

It seems the POM definition is not picked up correctly during the install stage.

Issue Links

• is duplicated by: MANTTASKS-182 deploy task tries to upload things it shouldn't.