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 "Foreman, Alex (IT)" <Al...@morganstanley.com> on 2008/09/16 18:06:28 UTC
URL=.... Behaviour
I have a feature request I asked about before but may have ben lost.
If you have a url and its not in its place in its repository then Ivy will download it and ignore local='true' as it did not find it in the reolver correctly but elsewhere. This obiously can be anywhere as it's a URL and we want to consider it remote.
Is there or can there be a way to force the resover to always be local. Eg even if it's a url use that location when using a cache path rarther than the local cache position.
Maybe <cache useOrigin="always" /> in ivy-settings.
I have been considering doing this via a trigger but might be nice if Ivy supported it directly.
Many thanks,
Alex Foreman
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5732
Alexander.Foreman@morganstanley.com
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
RE: URL=.... Behaviour
Posted by "Foreman, Alex (IT)" <Al...@morganstanley.com>.
The Repository is a Read-only file system. We use this for buildtime and also running production programs.
WE cannot use the cache for production programs (I build and create a runscript which a prod system uses but is pointing to stuff in my cache. I delete that cache.) It must reference the RO FS.
So It has to be on our RO file system. Unfortunatly Some projects have been placed in a non-standrad way. This is either due to ignorance or limitations of the programs we were installing.
Thus we want to force everything to be origin.
I have a work around for this working currently.
Simply we have a trigger that looks for runtime and then creates an extra path called runtime_script_path when cachepath=runtime.
I make sure the origin for everything is put in that and that is what gets written to the runtime_script_path not the 'runtime' created by standard.
Maybe my use case is rare but It would be nice to have that option built into ivy as it would also speed up our resolutions :)
Many thanks,
Alex Foreman
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5732
Alexander.Foreman@morganstanley.com
-----Original Message-----
From: paul.newport@targetgroup.net [mailto:paul.newport@targetgroup.net]
Sent: 17 September 2008 10:12
To: ivy-user@ant.apache.org
Subject: RE: URL=.... Behaviour
"We have a standard resolver where 90% of our projects exist in the correct place.
10% of projects are in the same filesystem but not standardly placed.
We cannot change the place they exist at.
So anything unstandard is located via a url="file://....." link for the artifact.
We wish to use there origin location rarther than the place in the cache."
Can you explain why you have the requirement of non-standard locations ? At first glance this could make builds quite fragile - why can't you publish stuff off the file system into a repository and then use the cached version after you do a resolve ?
Target
www.targetgroup.net
Target is a trading name of Target Group Limited, registered in England and Wales No. 1208137 Registered office: Target House, Cowbridge Road East, Cardiff CF11 9AU
**********************************************************************
DISCLAIMER.
This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient you must not copy, distribute or take any action or reliance upon it.
The content of this message may also contain personal views of an employee of this company and does not necessarily represent the view of the company.
**********************************************************************
This message has been scanned by Norton Anti-Virus.
It has also been scanned by MAILsweeper to enforce our e-mail policy. If you have any concerns or comments about the content of this message, please e-mail support@targetgroup.net.
**********************************************************************
_____________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
RE: URL=.... Behaviour
Posted by "Foreman, Alex (IT)" <Al...@morganstanley.com>.
https://issues.apache.org/jira/browse/IVY-906
I added it to an unspecified version. As I realise 2.0.0 has all its JIRAs complete :)
It would be nice to have for us next version tho. (2.0.1?)
In the mean time im going to have to hack our use case via triggers.
Many thanks,
Alex Foreman
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5732
Alexander.Foreman@morganstanley.com
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: 17 September 2008 09:54
To: ivy-user@ant.apache.org
Subject: Re: URL=.... Behaviour
On Wed, Sep 17, 2008 at 10:50 AM, Foreman, Alex (IT) < Alexander.Foreman@morganstanley.com> wrote:
> We have a standard resolver where 90% of our projects exist in the
> correct place.
> 10% of projects are in the same filesystem but not standardly placed.
> We cannot change the place they exist at.
>
> So anything unstandard is located via a url="file://....." link for
> the artifact.
>
> We wish to use there origin location rarther than the place in the cache.
Ok, I see, this is not supported yet, so please file an improvement in JIRA.
Xavier
>
>
> Thanks for the help.
>
>
> Alex Foreman
> Morgan Stanley | Technology
> 20 Cabot Square | Canary Wharf | Floor 06 London, E14 4QW
> Phone: +44 20 7677-5732
> Alexander.Foreman@morganstanley.com
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: 16 September 2008 17:36
> To: ivy-user@ant.apache.org
> Subject: Re: URL=.... Behaviour
>
> On Tue, Sep 16, 2008 at 6:06 PM, Foreman, Alex (IT) <
> Alexander.Foreman@morganstanley.com> wrote:
>
> > I have a feature request I asked about before but may have ben lost.
> >
> > If you have a url and its not in its place in its repository then
> > Ivy will download it and ignore local='true' as it did not find it
> > in the reolver correctly but elsewhere. This obiously can be
> > anywhere as it's a URL and we want to consider it remote.
> >
> > Is there or can there be a way to force the resover to always be
> > local. Eg even if it's a url use that location when using a cache
> > path rarther than the local cache position.
> >
> > Maybe <cache useOrigin="always" /> in ivy-settings.
> >
> > I have been considering doing this via a trigger but might be nice
> > if Ivy supported it directly.
>
> The problem is that after resolve, Ivy requires all your artifacts to
> be accessible as java.io.File objects, so a URL is not possible,
> unless it's a file URL. Could you detail your use case?
>
> Xavier
>
>
> >
> > Many thanks,
> >
> > Alex Foreman
> > Morgan Stanley | Technology
> > 20 Cabot Square | Canary Wharf | Floor 06 London, E14 4QW
> > Phone: +44 20 7677-5732
> > Alexander.Foreman@morganstanley.com
> > --------------------------------------------------------
> >
> > NOTICE: If received in error, please destroy and notify sender.
> > Sender does not intend to waive confidentiality or privilege. Use of
> > this email is prohibited when received in error.
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant BordeauxJUG co leader -
> http://www.bordeauxjug.org/ Blogger - http://xhab.blogspot.com/ Apache
> Ivy Creator - http://ant.apache.org/ivy/
> --------------------------------------------------------
>
> NOTICE: If received in error, please destroy and notify sender. Sender
> does not intend to waive confidentiality or privilege. Use of this
> email is prohibited when received in error.
>
--
Xavier Hanin - Independent Java Consultant BordeauxJUG co leader - http://www.bordeauxjug.org/ Blogger - http://xhab.blogspot.com/ Apache Ivy Creator - http://ant.apache.org/ivy/
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
Re: URL=.... Behaviour
Posted by Xavier Hanin <xa...@gmail.com>.
On Wed, Sep 17, 2008 at 10:50 AM, Foreman, Alex (IT) <
Alexander.Foreman@morganstanley.com> wrote:
> We have a standard resolver where 90% of our projects exist in the correct
> place.
> 10% of projects are in the same filesystem but not standardly placed.
> We cannot change the place they exist at.
>
> So anything unstandard is located via a url="file://....." link for the
> artifact.
>
> We wish to use there origin location rarther than the place in the cache.
Ok, I see, this is not supported yet, so please file an improvement in JIRA.
Xavier
>
>
> Thanks for the help.
>
>
> Alex Foreman
> Morgan Stanley | Technology
> 20 Cabot Square | Canary Wharf | Floor 06
> London, E14 4QW
> Phone: +44 20 7677-5732
> Alexander.Foreman@morganstanley.com
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: 16 September 2008 17:36
> To: ivy-user@ant.apache.org
> Subject: Re: URL=.... Behaviour
>
> On Tue, Sep 16, 2008 at 6:06 PM, Foreman, Alex (IT) <
> Alexander.Foreman@morganstanley.com> wrote:
>
> > I have a feature request I asked about before but may have ben lost.
> >
> > If you have a url and its not in its place in its repository then Ivy
> > will download it and ignore local='true' as it did not find it in the
> > reolver correctly but elsewhere. This obiously can be anywhere as
> > it's a URL and we want to consider it remote.
> >
> > Is there or can there be a way to force the resover to always be
> > local. Eg even if it's a url use that location when using a cache
> > path rarther than the local cache position.
> >
> > Maybe <cache useOrigin="always" /> in ivy-settings.
> >
> > I have been considering doing this via a trigger but might be nice if
> > Ivy supported it directly.
>
> The problem is that after resolve, Ivy requires all your artifacts to be
> accessible as java.io.File objects, so a URL is not possible, unless it's a
> file URL. Could you detail your use case?
>
> Xavier
>
>
> >
> > Many thanks,
> >
> > Alex Foreman
> > Morgan Stanley | Technology
> > 20 Cabot Square | Canary Wharf | Floor 06 London, E14 4QW
> > Phone: +44 20 7677-5732
> > Alexander.Foreman@morganstanley.com
> > --------------------------------------------------------
> >
> > NOTICE: If received in error, please destroy and notify sender. Sender
> > does not intend to waive confidentiality or privilege. Use of this
> > email is prohibited when received in error.
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant BordeauxJUG co leader -
> http://www.bordeauxjug.org/ Blogger - http://xhab.blogspot.com/ Apache Ivy
> Creator - http://ant.apache.org/ivy/
> --------------------------------------------------------
>
> NOTICE: If received in error, please destroy and notify sender. Sender does
> not intend to waive confidentiality or privilege. Use of this email is
> prohibited when received in error.
>
--
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/
RE: URL=.... Behaviour
Posted by pa...@targetgroup.net.
"We have a standard resolver where 90% of our projects exist in the correct
place.
10% of projects are in the same filesystem but not standardly placed.
We cannot change the place they exist at.
So anything unstandard is located via a url="file://....." link for the
artifact.
We wish to use there origin location rarther than the place in the cache."
Can you explain why you have the requirement of non-standard locations ? At
first glance this could make builds quite fragile - why can't you publish
stuff off the file system into a repository and then use the cached version
after you do a resolve ?
Target
www.targetgroup.net
Target is a trading name of Target Group Limited,
registered in England and Wales No. 1208137
Registered office: Target House, Cowbridge Road East, Cardiff CF11 9AU
**********************************************************************
DISCLAIMER.
This message is intended only for the use of the Addressee and may
contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient you must not copy,
distribute or take any action or reliance upon it.
The content of this message may also contain personal
views of an employee of this company and does
not necessarily represent the view of the company.
**********************************************************************
This message has been scanned by Norton Anti-Virus.
It has also been scanned by MAILsweeper to enforce our e-mail
policy. If you have any concerns or comments about the content
of this message, please e-mail support@targetgroup.net.
**********************************************************************
_____________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
RE: URL=.... Behaviour
Posted by "Foreman, Alex (IT)" <Al...@morganstanley.com>.
We have a standard resolver where 90% of our projects exist in the correct place.
10% of projects are in the same filesystem but not standardly placed.
We cannot change the place they exist at.
So anything unstandard is located via a url="file://....." link for the artifact.
We wish to use there origin location rarther than the place in the cache.
Thanks for the help.
Alex Foreman
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5732
Alexander.Foreman@morganstanley.com
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: 16 September 2008 17:36
To: ivy-user@ant.apache.org
Subject: Re: URL=.... Behaviour
On Tue, Sep 16, 2008 at 6:06 PM, Foreman, Alex (IT) < Alexander.Foreman@morganstanley.com> wrote:
> I have a feature request I asked about before but may have ben lost.
>
> If you have a url and its not in its place in its repository then Ivy
> will download it and ignore local='true' as it did not find it in the
> reolver correctly but elsewhere. This obiously can be anywhere as
> it's a URL and we want to consider it remote.
>
> Is there or can there be a way to force the resover to always be
> local. Eg even if it's a url use that location when using a cache
> path rarther than the local cache position.
>
> Maybe <cache useOrigin="always" /> in ivy-settings.
>
> I have been considering doing this via a trigger but might be nice if
> Ivy supported it directly.
The problem is that after resolve, Ivy requires all your artifacts to be accessible as java.io.File objects, so a URL is not possible, unless it's a file URL. Could you detail your use case?
Xavier
>
> Many thanks,
>
> Alex Foreman
> Morgan Stanley | Technology
> 20 Cabot Square | Canary Wharf | Floor 06 London, E14 4QW
> Phone: +44 20 7677-5732
> Alexander.Foreman@morganstanley.com
> --------------------------------------------------------
>
> NOTICE: If received in error, please destroy and notify sender. Sender
> does not intend to waive confidentiality or privilege. Use of this
> email is prohibited when received in error.
>
--
Xavier Hanin - Independent Java Consultant BordeauxJUG co leader - http://www.bordeauxjug.org/ Blogger - http://xhab.blogspot.com/ Apache Ivy Creator - http://ant.apache.org/ivy/
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
Re: URL=.... Behaviour
Posted by Xavier Hanin <xa...@gmail.com>.
On Tue, Sep 16, 2008 at 6:06 PM, Foreman, Alex (IT) <
Alexander.Foreman@morganstanley.com> wrote:
> I have a feature request I asked about before but may have ben lost.
>
> If you have a url and its not in its place in its repository then Ivy will
> download it and ignore local='true' as it did not find it in the reolver
> correctly but elsewhere. This obiously can be anywhere as it's a URL and we
> want to consider it remote.
>
> Is there or can there be a way to force the resover to always be local. Eg
> even if it's a url use that location when using a cache path rarther than
> the local cache position.
>
> Maybe <cache useOrigin="always" /> in ivy-settings.
>
> I have been considering doing this via a trigger but might be nice if Ivy
> supported it directly.
The problem is that after resolve, Ivy requires all your artifacts to be
accessible as java.io.File objects, so a URL is not possible, unless it's a
file URL. Could you detail your use case?
Xavier
>
> Many thanks,
>
> Alex Foreman
> Morgan Stanley | Technology
> 20 Cabot Square | Canary Wharf | Floor 06
> London, E14 4QW
> Phone: +44 20 7677-5732
> Alexander.Foreman@morganstanley.com
> --------------------------------------------------------
>
> NOTICE: If received in error, please destroy and notify sender. Sender does
> not intend to waive confidentiality or privilege. Use of this email is
> prohibited when received in error.
>
--
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/