You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2010/05/13 23:45:12 UTC

[jira] Updated: (MANTTASKS-170) deploy / install tasks make up names

     [ http://jira.codehaus.org/browse/MANTTASKS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy updated MANTTASKS-170:
------------------------------------

    Description: 
When running a built with the following:
{code:xml}<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>{code}

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.

  was:
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.


> deploy / install tasks make up names
> ------------------------------------
>
>                 Key: MANTTASKS-170
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-170
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: deploy task, install task
>    Affects Versions: 2.1.0
>         Environment: Windows Vista/Ant 1.7.1/Maven ant tasks 2.1.0
>            Reporter: Marcel Ammerlaan
>
> When running a built with the following:
> {code:xml}<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>{code}
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira