[
http://jira.codehaus.org/browse/MANTTASKS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212868#action_212868
]
Greg Vanore edited comment on MANTTASKS-170 at 3/5/10 3:13 PM:
---------------------------------------------------------------
A simpler workaround is to use the writepom task:
Declare your in-memory pom:
<artifact:pom id="template" ... >
...
</artifact:pom>
<macrodef name="bug170workaround">
<attribute name="srcpom"/>
<attribute name="destpom"/>
<attribute name="dir" default="${TEMP.DIR}"/>
<sequential>
<artifact:writepom id="@{srcpom}" file="@{dir}/pom.xml"/>
<artifact:pom id="@{destpom}" file="@{dir}/pom.xml"/>
</sequential>
</macrodef>
[edit: improved snippet]
was (Author: gvanore):
A simpler workaround is to use the writepom task:
<artifact:pom id="temporary" ... >
...
</artifact:pom>
<artifact:writepom id="temporary" file="${TEMP.DIR}/pom.xml"/>
<artifact:pom id="@{pomrefid}" file="${TEMP.DIR}/pom.xml"/>
> 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:
> <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.
--
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
