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 "Leamon, Pat" <Pa...@sensis.com.au> on 2011/01/11 07:09:49 UTC
Managing external tool with ivy
Hi,
I'm trying to manage versions of a tool used as part of the build
process, not a dependency of the app itself. I've packaged it into a
zip and put it into our local repository. This zip is then resolved by
ivy and the appropriate version is downloaded, then the build itself
unpacks the zip ready for the tool to be used.
At the moment I'm doing an ant <condition/><filesmatch></condition> to
check if the tool zip has changed since the last build (I keep a copy
when I unpack it separately). This saves me unpacking it every build,
but since the tool zip is large I still get a 5-10 second penalty for
the binary file comparison.
Is there any way I can get feedback from ivy to say if the dependency
has changed?
Thanks,
Pat
Sensis. Helping you find, buy and sell.
www.sensis.com.au - www.yellow.com.au - www.whitepages.com.au - www.citysearch.com.au - www.whereis.com.au
Sensis cares for the environment - think before you print.
This email and any attachments are intended only for the use of the recipient and may be confidential and/or legally privileged. Sensis Pty Ltd disclaims liability for any errors, omissions, viruses, loss and/or damage arising from using, opening or transmitting this email. If you are not the intended recipient you must not use, interfere with, disclose, copy or retain this email and you should notify the sender immediately by return email or by contacting Sensis Pty Ltd by telephone on [+61 3 8653 5000]
Re: Managing external tool with ivy
Posted by Geoff Clitheroe <g....@gmail.com>.
Hi Pat,
is it an option to use the ant 'get' task? This can use time stamping (for
http) to reduce downloads
http://ant.apache.org/manual/Tasks/get.html
<http://ant.apache.org/manual/Tasks/get.html> This is how we boot strap Ivy
itself. We use an ant property for the Ivy version.
Cheers,
Geoff
On Tue, Jan 11, 2011 at 7:09 PM, Leamon, Pat <Pa...@sensis.com.au>wrote:
>
> Hi,
>
> I'm trying to manage versions of a tool used as part of the build
> process, not a dependency of the app itself. I've packaged it into a
> zip and put it into our local repository. This zip is then resolved by
> ivy and the appropriate version is downloaded, then the build itself
> unpacks the zip ready for the tool to be used.
>
>
>
> At the moment I'm doing an ant <condition/><filesmatch></condition> to
> check if the tool zip has changed since the last build (I keep a copy
> when I unpack it separately). This saves me unpacking it every build,
> but since the tool zip is large I still get a 5-10 second penalty for
> the binary file comparison.
>
>
>
> Is there any way I can get feedback from ivy to say if the dependency
> has changed?
>
>
>
> Thanks,
>
> Pat
>
>
>
> Sensis. Helping you find, buy and sell.
>
> www.sensis.com.au - www.yellow.com.au - www.whitepages.com.au -
> www.citysearch.com.au - www.whereis.com.au
>
> Sensis cares for the environment - think before you print.
>
> This email and any attachments are intended only for the use of the
> recipient and may be confidential and/or legally privileged. Sensis Pty Ltd
> disclaims liability for any errors, omissions, viruses, loss and/or damage
> arising from using, opening or transmitting this email. If you are not the
> intended recipient you must not use, interfere with, disclose, copy or
> retain this email and you should notify the sender immediately by return
> email or by contacting Sensis Pty Ltd by telephone on [+61 3 8653 5000]
RE: Managing external tool with ivy
Posted by "Leamon, Pat" <Pa...@sensis.com.au>.
The triggers look promising, I'll look into that.
Thanks,
Pat
-----Original Message-----
From: Hekmat, Payam [mailto:phekmat@onenetwork.com]
Sent: Tuesday, 11 January 2011 8:30 PM
To: ivy-user@ant.apache.org
Subject: RE: Managing external tool with ivy
If you have the current revision of the zip handy, you can use the Ivy
buildnumber Ant task and compare on that. Another option may be to check
the timestamp of the current zip and compare it to the timestamp of the
zip after it's resolved.
Depending on your build, you may also be able to use Ivy's triggers
(http://ant.apache.org/ivy/history/latest-milestone/settings/triggers.ht
ml) to do the unzip after the first download (the post-download-artifact
trigger). If I recall correctly, the trigger won't fire if you already
have the artifact in the cache.
-----Original Message-----
From: Leamon, Pat [mailto:Pat.Leamon@sensis.com.au]
Sent: Tuesday, January 11, 2011 12:10 AM
To: ivy-user@ant.apache.org
Subject: Managing external tool with ivy
Hi,
I'm trying to manage versions of a tool used as part of the build
process, not a dependency of the app itself. I've packaged it into a
zip and put it into our local repository. This zip is then resolved by
ivy and the appropriate version is downloaded, then the build itself
unpacks the zip ready for the tool to be used.
At the moment I'm doing an ant <condition/><filesmatch></condition> to
check if the tool zip has changed since the last build (I keep a copy
when I unpack it separately). This saves me unpacking it every build,
but since the tool zip is large I still get a 5-10 second penalty for
the binary file comparison.
Is there any way I can get feedback from ivy to say if the dependency
has changed?
Thanks,
Pat
Sensis. Helping you find, buy and sell.
www.sensis.com.au - www.yellow.com.au - www.whitepages.com.au -
www.citysearch.com.au - www.whereis.com.au
Sensis cares for the environment - think before you print.
This email and any attachments are intended only for the use of the
recipient and may be confidential and/or legally privileged. Sensis Pty
Ltd disclaims liability for any errors, omissions, viruses, loss and/or
damage arising from using, opening or transmitting this email. If you
are not the intended recipient you must not use, interfere with,
disclose, copy or retain this email and you should notify the sender
immediately by return email or by contacting Sensis Pty Ltd by telephone
on [+61 3 8653 5000]
RE: Managing external tool with ivy
Posted by "Hekmat, Payam" <ph...@onenetwork.com>.
If you have the current revision of the zip handy, you can use the Ivy
buildnumber Ant task and compare on that. Another option may be to check
the timestamp of the current zip and compare it to the timestamp of the
zip after it's resolved.
Depending on your build, you may also be able to use Ivy's triggers
(http://ant.apache.org/ivy/history/latest-milestone/settings/triggers.ht
ml) to do the unzip after the first download (the post-download-artifact
trigger). If I recall correctly, the trigger won't fire if you already
have the artifact in the cache.
-----Original Message-----
From: Leamon, Pat [mailto:Pat.Leamon@sensis.com.au]
Sent: Tuesday, January 11, 2011 12:10 AM
To: ivy-user@ant.apache.org
Subject: Managing external tool with ivy
Hi,
I'm trying to manage versions of a tool used as part of the build
process, not a dependency of the app itself. I've packaged it into a
zip and put it into our local repository. This zip is then resolved by
ivy and the appropriate version is downloaded, then the build itself
unpacks the zip ready for the tool to be used.
At the moment I'm doing an ant <condition/><filesmatch></condition> to
check if the tool zip has changed since the last build (I keep a copy
when I unpack it separately). This saves me unpacking it every build,
but since the tool zip is large I still get a 5-10 second penalty for
the binary file comparison.
Is there any way I can get feedback from ivy to say if the dependency
has changed?
Thanks,
Pat
Sensis. Helping you find, buy and sell.
www.sensis.com.au - www.yellow.com.au - www.whitepages.com.au -
www.citysearch.com.au - www.whereis.com.au
Sensis cares for the environment - think before you print.
This email and any attachments are intended only for the use of the
recipient and may be confidential and/or legally privileged. Sensis Pty
Ltd disclaims liability for any errors, omissions, viruses, loss and/or
damage arising from using, opening or transmitting this email. If you
are not the intended recipient you must not use, interfere with,
disclose, copy or retain this email and you should notify the sender
immediately by return email or by contacting Sensis Pty Ltd by telephone
on [+61 3 8653 5000]