ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maarten Coene <maarten_co...@yahoo.com>
Subject Re: ivy extra attributes not available in build.xml?
Date Thu, 07 Jan 2010 23:18:19 GMT
Are you sure you call the ivy:info task?
I don't see this in your build.xml snippet.

Maarten




----- Original Message ----
From: "Baron, Randy" <randy.baron@roche.com>
To: "ivy-user@ant.apache.org" <ivy-user@ant.apache.org>
Sent: Thu, January 7, 2010 3:15:04 PM
Subject: ivy extra attributes not available in build.xml?


hi,
  I've been trying to use ivy "extra attributes" but am not entirely successful.  When I try
the publish ant task and use my extra attribute in the artifact pattern the attribute doesn't
seem to be defined.

Some relevant snippets:
ivy.xml
<ivy-module version="2.0" xmlns:e="http://ant.apache.org/ivy/extra" >
    <info organisation="someorg" module="gvs"  e:submodule="gvs-orm"/>
    <publications>
        ...etc.

build.xml:
<project name="gvs-orm" default="all" basedir="." >
    <import file="ivy-init.xml"/>
...
ivy-init.xml:
     <target name="publish" depends="resolve" description="--> compile test and publish
this project in the local ivy repository">
        <!-- according to http://ant.apache.org/ivy/history/trunk/use/info.html shouldn't
ivy.extra.submodule variable be set now? -->
        <echo message="extra attribute 'submodule': ${ivy.extra.submodule}"/>
        <ivy:publish overwrite="true" resolver="filesystem-inhouse" pubrevision="${software.version}"
>
        <artifacts pattern="dist/${ivy.extra.submodule}-[revision].[ext]"/>
<!--    <artifacts pattern="dist/${ivy.extra.submodule}-[revision].[ext]"/>   this
didn't work either-->
        </ivy:publish>
    </target>


When I run "ant publish" it prints:
        [echo] extra attribute 'submodule': ${ivy.extra.submodule}
so, the apparently variable is undefined, and then puts an ivy file in "dist" but with the
(bad) name "${ivy.extra.submodule}-1.0.9.xml"

I have tried many other things--using [submodule] or [e:submodule] in the pattern, adding
xmlns:e to the build, etc.--but nothing worked so far.

Anyone know what might be going wrong?
regards,
Randy


      

Mime
View raw message