You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "Loehr, Ruel" <rl...@pointserve.com> on 2007/06/25 15:55:07 UTC
publishing and retrieving with ivy - stretching the bounds
Hey guys,
I realize I am stretching the bounds of what ivy was designed for, but
nonetheless, I've ran into some questions.
What I am trying to do:
I have a project which builds an ear. I use ivy to get the
dependencies for building it. That works fine. What I would like to
do is publish a few artifacts after this ear is built:
1) the ear itself
2) a zip of the sql schema changes that go along with that ear
release
So far so good. I can both build and publish these items to the
repository.
<publications>
<artifact name="ServiceNetworkManagement" type="ear"
conf="default"/>
<artifact name="sql" type="zip" conf="default"/>
</publications>
Please note I am not publishing an ivy file along with these items.
Now, to the cruxt of my problem. I have another project where I
would like to retrieve the above artifacts.
<dependency org="pointserve" name="ServiceNetworkManagement"
rev="28.0.0" conf="eso->*">
<artifact name="bde" type="zip" conf="eso->*" ext="zip"/>
<artifact name="bdl" type="zip" conf="eso->*" ext="zip"/>
<artifact name="ServiceNetworkManagement" type="ear"
ext="zip" conf="eso->*"/>
</dependency>
Ivy attempts to download
pointserve/ServiceNetworkManagement/ServiceNetworkManagement.jar. It
does not attempt to download the others.
Is this possible to do? What am I missing here?
Ruel Loehr
Configuration Management
Pointserve, Inc.
110 Wild Basin Road
Suite 300
Austin, Texas 78746
O: 512.617.5314
F: 512.617.0466
RE: publishing and retrieving with ivy - stretching the bounds
Posted by "Loehr, Ruel" <rl...@pointserve.com>.
Thanks for the help.
I figured out my issue.
Before publishing, I was attempting to do a deliver as a separate step.
Instead, it seems to work much better to just use the forcedeliver
attribute in the ivy-publish task.
<target name="ivy-publish" depends="init, ivy-setup, ivy-resolve"
description="--> setup ivy configuration" unless="testrelease">
<!--<ivy-deliver pubrevision="${VERSION}"/>-->
<ivy-publish resolver="internal" revision="${VERSION}"
pubrevision="${VERSION}"
validate="true" publishivy="true" haltonmissing="false"
srcivypattern="${ivy.project.dir}/ivy.xml"
replacedynamicrev="true" forcedeliver="true"
overwrite="false">
</ivy-publish>
The above causes my publication items in ivy.xml
<publications>
<artifact name="ServiceNetworkManagement" type="ear"
conf="default"/>
<artifact name="sql" type="zip" conf="default"/>
<artifact name="bde" type="zip" conf="default"/>
<artifact name="bdl" type="zip" conf="default"/>
</publications>
To all be published along with an ivy.xml, to my local repository.
Then in my second project:
<dependency org="pointserve" name="ServiceNetworkManagement"
rev="28.0.0" conf="eso->*">
<include name="bde" type="zip" conf="eso"/>
<include name="bdl" type="zip" conf="eso"/>
<include name="ServiceNetworkManagement" type="ear"
conf="eso"/>
<exclude type="jar"/>
</dependency>
The 2 zips and the ear downloaded.
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: Monday, June 25, 2007 9:55 AM
To: ivy-user@incubator.apache.org
Subject: Re: publishing and retrieving with ivy - stretching the bounds
On 6/25/07, Loehr, Ruel <rl...@pointserve.com> wrote:
>
> Hey guys,
>
>
>
> I realize I am stretching the bounds of what ivy was designed for, but
> nonetheless, I've ran into some questions.
>
>
>
> What I am trying to do:
>
>
>
> I have a project which builds an ear. I use ivy to get the
> dependencies for building it. That works fine. What I would like
to
> do is publish a few artifacts after this ear is built:
>
>
>
> 1) the ear itself
>
> 2) a zip of the sql schema changes that go along with that ear
> release
>
>
>
> So far so good. I can both build and publish these items to the
> repository.
>
>
>
> <publications>
>
> <artifact name="ServiceNetworkManagement" type="ear"
> conf="default"/>
>
> <artifact name="sql" type="zip" conf="default"/>
>
> </publications>
>
>
>
> Please note I am not publishing an ivy file along with these items.
Why aren't you publishing an ivy file with your module?
Now, to the cruxt of my problem. I have another project where I
> would like to retrieve the above artifacts.
>
>
>
> <dependency org="pointserve" name="ServiceNetworkManagement"
> rev="28.0.0" conf="eso->*">
>
> <artifact name="bde" type="zip" conf="eso->*" ext="zip"/>
>
> <artifact name="bdl" type="zip" conf="eso->*" ext="zip"/>
>
>
> <artifact name="ServiceNetworkManagement" type="ear"
> ext="zip" conf="eso->*"/>
>
> </dependency>
>
>
>
> Ivy attempts to download
> pointserve/ServiceNetworkManagement/ServiceNetworkManagement.jar.
It
> does not attempt to download the others.
Are you talking about a jar? Or an ear? In your publication section you
declare an ear (type=ear). Here you declare an ear with a zip extension.
And
you finally get a jar. A little bit confusing :-) For the other
artifacts
Ivy should try to download them, and fail since bde and bdl have not
beeen
published (according to your publication section above, only a sql
artifact
is published along your ear). But it's difficult to know, maybe you
could
provide more details about your settings (pattern used for instance)?
Xavier
Is this possible to do? What am I missing here?
>
>
>
>
>
> Ruel Loehr
>
> Configuration Management
>
>
>
> Pointserve, Inc.
>
> 110 Wild Basin Road
>
> Suite 300
>
> Austin, Texas 78746
>
> O: 512.617.5314
>
> F: 512.617.0466
>
>
>
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
Re: publishing and retrieving with ivy - stretching the bounds
Posted by Xavier Hanin <xa...@gmail.com>.
On 6/25/07, Loehr, Ruel <rl...@pointserve.com> wrote:
>
> Hey guys,
>
>
>
> I realize I am stretching the bounds of what ivy was designed for, but
> nonetheless, I've ran into some questions.
>
>
>
> What I am trying to do:
>
>
>
> I have a project which builds an ear. I use ivy to get the
> dependencies for building it. That works fine. What I would like to
> do is publish a few artifacts after this ear is built:
>
>
>
> 1) the ear itself
>
> 2) a zip of the sql schema changes that go along with that ear
> release
>
>
>
> So far so good. I can both build and publish these items to the
> repository.
>
>
>
> <publications>
>
> <artifact name="ServiceNetworkManagement" type="ear"
> conf="default"/>
>
> <artifact name="sql" type="zip" conf="default"/>
>
> </publications>
>
>
>
> Please note I am not publishing an ivy file along with these items.
Why aren't you publishing an ivy file with your module?
Now, to the cruxt of my problem. I have another project where I
> would like to retrieve the above artifacts.
>
>
>
> <dependency org="pointserve" name="ServiceNetworkManagement"
> rev="28.0.0" conf="eso->*">
>
> <artifact name="bde" type="zip" conf="eso->*" ext="zip"/>
>
> <artifact name="bdl" type="zip" conf="eso->*" ext="zip"/>
>
>
> <artifact name="ServiceNetworkManagement" type="ear"
> ext="zip" conf="eso->*"/>
>
> </dependency>
>
>
>
> Ivy attempts to download
> pointserve/ServiceNetworkManagement/ServiceNetworkManagement.jar. It
> does not attempt to download the others.
Are you talking about a jar? Or an ear? In your publication section you
declare an ear (type=ear). Here you declare an ear with a zip extension. And
you finally get a jar. A little bit confusing :-) For the other artifacts
Ivy should try to download them, and fail since bde and bdl have not beeen
published (according to your publication section above, only a sql artifact
is published along your ear). But it's difficult to know, maybe you could
provide more details about your settings (pattern used for instance)?
Xavier
Is this possible to do? What am I missing here?
>
>
>
>
>
> Ruel Loehr
>
> Configuration Management
>
>
>
> Pointserve, Inc.
>
> 110 Wild Basin Road
>
> Suite 300
>
> Austin, Texas 78746
>
> O: 512.617.5314
>
> F: 512.617.0466
>
>
>
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/