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 "Brown, Carlton" <Ca...@compucredit.com> on 2008/03/12 17:41:30 UTC
Cache basedir attribute no longer valid in beta 2 ?
Since I began using beta 2, Ivy no longer uses the cache directory I
specified in my settings file, which looks like this:
<ivysettings>
<settings defaultResolver="internal-with-m2-fallback"
checkUpToDate="true" />
<cache basedir="c:\ivy2\cache" />
<!-- etcetera-->
Now my default cache is.ivy2/cache in users's home. C:\ivy2\cache is
never referenced or changed.
So, I look at the documentation and apparently <cache> is no longer a
child element of <ivysettings> as of beta-2, it now goes under <caches>.
OK, no problem. I change the settings to:
<ivysettings>
<settings defaultResolver="internal-with-m2-fallback"
checkUpToDate="true" />
<caches>
<cache basedir="c:\ivy2\cache" />
</caches>
<!-- etcetera-->
Still does not work!
So, I decide something is wrong with basedir and I go with the new
settings.
<caches defaultCacheDir="c:\tools\ivy2\cache" />
Finally, success. So is the documentation out of date, or is it a bug?
Thanks,
Carlton
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
</STRONG></P></BODY></HTML>
RE: Cache basedir attribute no longer valid in beta 2 ?
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Wednesday, March 12, 2008 2:16 PM
> To: ivy-user@ant.apache.org
> Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
>
> On Wed, Mar 12, 2008 at 7:02 PM, Brown, Carlton
> <Ca...@compucredit.com> wrote:
> >
> >
> > > -----Original Message-----
> > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> >
> >
> > > Sent: Wednesday, March 12, 2008 1:46 PM
> > > To: ivy-user@ant.apache.org
> > > Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
> > >
> > > On Wed, Mar 12, 2008 at 6:31 PM, Brown, Carlton >
> > <Ca...@compucredit.com> wrote:
> > > >
> > > > > -----Original Message-----
> > > > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com] > Sent:
> > > > Wednesday, March 12, 2008 1:16 PM > To:
> ivy-user@ant.apache.org
> > > > > Subject: Re: Cache basedir attribute no longer valid
> in beta 2 ?
> > > > >
> > > > > On Wed, Mar 12, 2008 at 5:41 PM, Brown, Carlton > > >
> > <Ca...@compucredit.com> wrote:
> > > > > > Since I began using beta 2, Ivy no longer uses
> the cache >
> > > > directory I > > specified in my settings file, which looks >
> > like this:
> > > > > >
> > > > > > <ivysettings>
> > > > > > <settings defaultResolver="internal-with-m2-fallback"
> > > > > > checkUpToDate="true" />
> > > > > > <cache basedir="c:\ivy2\cache" /> > > <!-- >
> etcetera-->
> > > > > > > > Now my default cache is.ivy2/cache in users's home.
> > > > > C:\ivy2\cache is
> > > > > > never referenced or changed.
> > > > > >
> > > > > > So, I look at the documentation and apparently
> > <cache>
> > is > no > > longer a > > child element of <ivysettings> as of
> > beta-2, > it now goes > > > under <caches>.
> > > > > > OK, no problem. I change the settings to:
> > > > > >
> > > > > > <ivysettings>
> > > > > > <settings defaultResolver="internal-with-m2-fallback"
> > > > > > checkUpToDate="true" />
> > > > > > <caches>
> > > > > > <cache basedir="c:\ivy2\cache" />
> > > > > > </caches>
> > > > > > <!-- etcetera-->
> > > > > >
> > > > > > Still does not work!
> > > > > >
> > > > > > So, I decide something is wrong with basedir and
> I go with
> > > > > the new > > settings.
> > > > > > <caches defaultCacheDir="c:\tools\ivy2\cache" /> > >
> > > > > > Finally, success. So is the documentation out of date,
> > > > > or is it a bug?
> > > > >
> > > > > Sorry for the inconvenience with migration, the new
> cache >
> > > > implementation and settings is still a bit experimental.
> > > > > About the documentation, it should be up to date.
> The cache >
> > > > element under caches allow to define one particular cache, >
> > while > > caches is used both as a container element and to > >
> > specify default > > values for all caches.
> > > > >
> > > > > I think the documentation reflects this.
> > > >
> > > > No worries, I think the new scheme is better than the
> old one,
> > but > > I'm not sure this is the correct answer to my
> question about
> > the > > basedir attribute. The documentation says the basedir >
> > attribute is supported.
> > > > But in my testing it doesn't work, even when nesting
> <cache> as
> > a > > child of <caches>.
> > > It should work (defining the basedir of a single cache
> > instance,
> > not all caches like defaultCacheDir). What error > message do you
> > get?
> >
> > There's no error message. The behavior is if I clean the
> cache, set
> > the basedir to c:\foo, and do a resolve, the cache gets populated
> > under the default of ${user.home}/.ivy2/cache
> But do you tell Ivy to use this cache instance? As explained
> on the caches reference page [1], Ivy defines a default cache
> instance called 'default-cache', so if you don't change the
> basedir of this instance or redefine the default cache
> instance to use, you won't see any change.
I see, the current documentation is correct in describing the current
behavior. I did not realize the changes were so extensive from beta-1.
Still, let's keep up the good work. In my organization it seems we are
close to approving Ivy+Ant for our DM solution.
-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
Re: Cache basedir attribute no longer valid in beta 2 ?
Posted by Xavier Hanin <xa...@gmail.com>.
On Wed, Mar 12, 2008 at 7:02 PM, Brown, Carlton
<Ca...@compucredit.com> wrote:
>
>
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
>
>
> > Sent: Wednesday, March 12, 2008 1:46 PM
> > To: ivy-user@ant.apache.org
> > Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
> >
> > On Wed, Mar 12, 2008 at 6:31 PM, Brown, Carlton
> > <Ca...@compucredit.com> wrote:
> > >
> > > > -----Original Message-----
> > > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com] > Sent:
> > > Wednesday, March 12, 2008 1:16 PM > To: ivy-user@ant.apache.org >
> > > Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
> > > >
> > > > On Wed, Mar 12, 2008 at 5:41 PM, Brown, Carlton >
> > > <Ca...@compucredit.com> wrote:
> > > > > Since I began using beta 2, Ivy no longer uses the cache >
> > > directory I > > specified in my settings file, which looks
> > like this:
> > > > >
> > > > > <ivysettings>
> > > > > <settings defaultResolver="internal-with-m2-fallback"
> > > > > checkUpToDate="true" />
> > > > > <cache basedir="c:\ivy2\cache" /> > > <!--
> > etcetera--> > > >
> > > > Now my default cache is.ivy2/cache in users's home.
> > > > C:\ivy2\cache is
> > > > > never referenced or changed.
> > > > >
> > > > > So, I look at the documentation and apparently
> > <cache> is > no
> > > longer a > > child element of <ivysettings> as of beta-2,
> > it now goes
> > > > under <caches>.
> > > > > OK, no problem. I change the settings to:
> > > > >
> > > > > <ivysettings>
> > > > > <settings defaultResolver="internal-with-m2-fallback"
> > > > > checkUpToDate="true" />
> > > > > <caches>
> > > > > <cache basedir="c:\ivy2\cache" />
> > > > > </caches>
> > > > > <!-- etcetera-->
> > > > >
> > > > > Still does not work!
> > > > >
> > > > > So, I decide something is wrong with basedir and I go with >
> > > the new > > settings.
> > > > > <caches defaultCacheDir="c:\tools\ivy2\cache" /> > >
> > > > > Finally, success. So is the documentation out of date,
> > > > or is it a bug?
> > > >
> > > > Sorry for the inconvenience with migration, the new cache >
> > > implementation and settings is still a bit experimental.
> > > > About the documentation, it should be up to date. The cache >
> > > element under caches allow to define one particular cache, > while
> > > caches is used both as a container element and to >
> > specify default
> > > values for all caches.
> > > >
> > > > I think the documentation reflects this.
> > >
> > > No worries, I think the new scheme is better than the old one, but
> > > I'm not sure this is the correct answer to my question about the
> > > basedir attribute. The documentation says the basedir
> > attribute is supported.
> > > But in my testing it doesn't work, even when nesting <cache> as a
> > > child of <caches>.
> > It should work (defining the basedir of a single cache
> > instance, not all caches like defaultCacheDir). What error
> > message do you get?
>
> There's no error message. The behavior is if I clean the cache, set the
> basedir to c:\foo, and do a resolve, the cache gets populated under the
> default of ${user.home}/.ivy2/cache
But do you tell Ivy to use this cache instance? As explained on the
caches reference page [1], Ivy defines a default cache instance called
'default-cache', so if you don't change the basedir of this instance
or redefine the default cache instance to use, you won't see any
change.
Xavier
[1] http://ant.apache.org/ivy/history/latest-milestone/configuration/caches.html
>
> -----------------------------------------
>
>
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL
> information that is intended only for use by the
> named recipient. If you are not the named recipient,
> any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such
> case please notify us and destroy and delete all
> copies of this transmission. Thank you.
> ====================================================
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
RE: Cache basedir attribute no longer valid in beta 2 ?
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Wednesday, March 12, 2008 1:46 PM
> To: ivy-user@ant.apache.org
> Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
>
> On Wed, Mar 12, 2008 at 6:31 PM, Brown, Carlton
> <Ca...@compucredit.com> wrote:
> >
> > > -----Original Message-----
> > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com] > Sent:
> > Wednesday, March 12, 2008 1:16 PM > To: ivy-user@ant.apache.org >
> > Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
> > >
> > > On Wed, Mar 12, 2008 at 5:41 PM, Brown, Carlton >
> > <Ca...@compucredit.com> wrote:
> > > > Since I began using beta 2, Ivy no longer uses the cache >
> > directory I > > specified in my settings file, which looks
> like this:
> > > >
> > > > <ivysettings>
> > > > <settings defaultResolver="internal-with-m2-fallback"
> > > > checkUpToDate="true" />
> > > > <cache basedir="c:\ivy2\cache" /> > > <!--
> etcetera--> > > >
> > > Now my default cache is.ivy2/cache in users's home.
> > > C:\ivy2\cache is
> > > > never referenced or changed.
> > > >
> > > > So, I look at the documentation and apparently
> <cache> is > no
> > longer a > > child element of <ivysettings> as of beta-2,
> it now goes
> > > under <caches>.
> > > > OK, no problem. I change the settings to:
> > > >
> > > > <ivysettings>
> > > > <settings defaultResolver="internal-with-m2-fallback"
> > > > checkUpToDate="true" />
> > > > <caches>
> > > > <cache basedir="c:\ivy2\cache" />
> > > > </caches>
> > > > <!-- etcetera-->
> > > >
> > > > Still does not work!
> > > >
> > > > So, I decide something is wrong with basedir and I go with >
> > the new > > settings.
> > > > <caches defaultCacheDir="c:\tools\ivy2\cache" /> > >
> > > > Finally, success. So is the documentation out of date,
> > > or is it a bug?
> > >
> > > Sorry for the inconvenience with migration, the new cache >
> > implementation and settings is still a bit experimental.
> > > About the documentation, it should be up to date. The cache >
> > element under caches allow to define one particular cache, > while
> > caches is used both as a container element and to >
> specify default
> > values for all caches.
> > >
> > > I think the documentation reflects this.
> >
> > No worries, I think the new scheme is better than the old one, but
> > I'm not sure this is the correct answer to my question about the
> > basedir attribute. The documentation says the basedir
> attribute is supported.
> > But in my testing it doesn't work, even when nesting <cache> as a
> > child of <caches>.
> It should work (defining the basedir of a single cache
> instance, not all caches like defaultCacheDir). What error
> message do you get?
There's no error message. The behavior is if I clean the cache, set the
basedir to c:\foo, and do a resolve, the cache gets populated under the
default of ${user.home}/.ivy2/cache
-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
Re: Cache basedir attribute no longer valid in beta 2 ?
Posted by Xavier Hanin <xa...@gmail.com>.
On Wed, Mar 12, 2008 at 6:31 PM, Brown, Carlton
<Ca...@compucredit.com> wrote:
>
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Wednesday, March 12, 2008 1:16 PM
> > To: ivy-user@ant.apache.org
> > Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
> >
> > On Wed, Mar 12, 2008 at 5:41 PM, Brown, Carlton
> > <Ca...@compucredit.com> wrote:
> > > Since I began using beta 2, Ivy no longer uses the cache
> > directory I
> > > specified in my settings file, which looks like this:
> > >
> > > <ivysettings>
> > > <settings defaultResolver="internal-with-m2-fallback"
> > > checkUpToDate="true" />
> > > <cache basedir="c:\ivy2\cache" />
> > > <!-- etcetera-->
> > >
> > > Now my default cache is.ivy2/cache in users's home.
> > C:\ivy2\cache is
> > > never referenced or changed.
> > >
> > > So, I look at the documentation and apparently <cache> is
> > no longer a
> > > child element of <ivysettings> as of beta-2, it now goes
> > under <caches>.
> > > OK, no problem. I change the settings to:
> > >
> > > <ivysettings>
> > > <settings defaultResolver="internal-with-m2-fallback"
> > > checkUpToDate="true" />
> > > <caches>
> > > <cache basedir="c:\ivy2\cache" />
> > > </caches>
> > > <!-- etcetera-->
> > >
> > > Still does not work!
> > >
> > > So, I decide something is wrong with basedir and I go with
> > the new
> > > settings.
> > > <caches defaultCacheDir="c:\tools\ivy2\cache" />
> > >
> > > Finally, success. So is the documentation out of date,
> > or is it a bug?
> >
> > Sorry for the inconvenience with migration, the new cache
> > implementation and settings is still a bit experimental.
> > About the documentation, it should be up to date. The cache
> > element under caches allow to define one particular cache,
> > while caches is used both as a container element and to
> > specify default values for all caches.
> >
> > I think the documentation reflects this.
>
> No worries, I think the new scheme is better than the old one, but I'm
> not sure this is the correct answer to my question about the basedir
> attribute. The documentation says the basedir attribute is supported.
> But in my testing it doesn't work, even when nesting <cache> as a child
> of <caches>.
It should work (defining the basedir of a single cache instance, not
all caches like defaultCacheDir). What error message do you get?
Xavier
> This means there is a problem with either the
> documentation, the implementation, or my testing. I just want to
> understand which one is the answer.<HTML><BODY><P><hr size=1></P>
>
>
> <P><STRONG>
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL
> information that is intended only for use by the
> named recipient. If you are not the named recipient,
> any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such
> case please notify us and destroy and delete all
> copies of this transmission. Thank you.
> ====================================================
> </STRONG></P></BODY></HTML>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
RE: Cache basedir attribute no longer valid in beta 2 ?
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Wednesday, March 12, 2008 1:16 PM
> To: ivy-user@ant.apache.org
> Subject: Re: Cache basedir attribute no longer valid in beta 2 ?
>
> On Wed, Mar 12, 2008 at 5:41 PM, Brown, Carlton
> <Ca...@compucredit.com> wrote:
> > Since I began using beta 2, Ivy no longer uses the cache
> directory I
> > specified in my settings file, which looks like this:
> >
> > <ivysettings>
> > <settings defaultResolver="internal-with-m2-fallback"
> > checkUpToDate="true" />
> > <cache basedir="c:\ivy2\cache" />
> > <!-- etcetera-->
> >
> > Now my default cache is.ivy2/cache in users's home.
> C:\ivy2\cache is
> > never referenced or changed.
> >
> > So, I look at the documentation and apparently <cache> is
> no longer a
> > child element of <ivysettings> as of beta-2, it now goes
> under <caches>.
> > OK, no problem. I change the settings to:
> >
> > <ivysettings>
> > <settings defaultResolver="internal-with-m2-fallback"
> > checkUpToDate="true" />
> > <caches>
> > <cache basedir="c:\ivy2\cache" />
> > </caches>
> > <!-- etcetera-->
> >
> > Still does not work!
> >
> > So, I decide something is wrong with basedir and I go with
> the new
> > settings.
> > <caches defaultCacheDir="c:\tools\ivy2\cache" />
> >
> > Finally, success. So is the documentation out of date,
> or is it a bug?
>
> Sorry for the inconvenience with migration, the new cache
> implementation and settings is still a bit experimental.
> About the documentation, it should be up to date. The cache
> element under caches allow to define one particular cache,
> while caches is used both as a container element and to
> specify default values for all caches.
>
> I think the documentation reflects this.
No worries, I think the new scheme is better than the old one, but I'm
not sure this is the correct answer to my question about the basedir
attribute. The documentation says the basedir attribute is supported.
But in my testing it doesn't work, even when nesting <cache> as a child
of <caches>. This means there is a problem with either the
documentation, the implementation, or my testing. I just want to
understand which one is the answer.<HTML><BODY><P><hr size=1></P>
<P><STRONG>
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
</STRONG></P></BODY></HTML>
Re: Cache basedir attribute no longer valid in beta 2 ?
Posted by Xavier Hanin <xa...@gmail.com>.
On Wed, Mar 12, 2008 at 5:41 PM, Brown, Carlton
<Ca...@compucredit.com> wrote:
> Since I began using beta 2, Ivy no longer uses the cache directory I
> specified in my settings file, which looks like this:
>
> <ivysettings>
> <settings defaultResolver="internal-with-m2-fallback"
> checkUpToDate="true" />
> <cache basedir="c:\ivy2\cache" />
> <!-- etcetera-->
>
> Now my default cache is.ivy2/cache in users's home. C:\ivy2\cache is
> never referenced or changed.
>
> So, I look at the documentation and apparently <cache> is no longer a
> child element of <ivysettings> as of beta-2, it now goes under <caches>.
> OK, no problem. I change the settings to:
>
> <ivysettings>
> <settings defaultResolver="internal-with-m2-fallback"
> checkUpToDate="true" />
> <caches>
> <cache basedir="c:\ivy2\cache" />
> </caches>
> <!-- etcetera-->
>
> Still does not work!
>
> So, I decide something is wrong with basedir and I go with the new
> settings.
> <caches defaultCacheDir="c:\tools\ivy2\cache" />
>
> Finally, success. So is the documentation out of date, or is it a bug?
Sorry for the inconvenience with migration, the new cache
implementation and settings is still a bit experimental. About the
documentation, it should be up to date. The cache element under caches
allow to define one particular cache, while caches is used both as a
container element and to specify default values for all caches.
I think the documentation reflects this.
Xavier
>
> Thanks,
> Carlton
>
>
>
>
>
>
>
> <HTML><BODY><P><hr size=1></P>
> <P><STRONG>
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL
> information that is intended only for use by the
> named recipient. If you are not the named recipient,
> any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such
> case please notify us and destroy and delete all
> copies of this transmission. Thank you.
> ====================================================
> </STRONG></P></BODY></HTML>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/