[
http://jira.codehaus.org/browse/MANTTASKS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212288#action_212288
]
Andrew MacLeod edited comment on MANTTASKS-170 at 3/3/10 7:56 AM:
------------------------------------------------------------------
I have been looking for a workaround to this... i tried rolling back to
maven-ant-tasks-2.0.10.jar but to my surprise it tells me:
artifact:pom doesn't support the "version" attribute
... so I'm guessing that in-memory POMs are not supported in 2.0.10, though
there is nothing in the documentation to suggest this (i.e. the example in
https://maven.apache.org/ant-tasks/examples/pom.html), whereas the reference
does not specify options for in-memory POMs either
(https://maven.apache.org/ant-tasks/reference.html#pom).
Until this is fixed, I'm going to generate an actual temporary POM file using
ant <echo> and give up on in-memory POMs (when ever Maven bites me, ant saves
the day :-) ).
was (Author: andrew.macleod):
I have been looking for a workaround to this... i tried rolling back to
maven-ant-tasks-2.0.10.jar but to my surprise it tells me:
artifact:pom doesn't support the "version" attribute
... so I'm guessing that in-memory POMs are not supported in 2.0.10, though
there is nothing in the documentation to suggest this (i.e. the example in
https://maven.apache.org/ant-tasks/examples/pom.html), whereas the reference
does not specify options for in-memory POMs either
(https://maven.apache.org/ant-tasks/reference.html#pom).
I'm going to try and generate XML with writePom and give up on in-memory POMs
until this is fixed.
> 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
