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 Shawn Castrianni <Sh...@halliburton.com> on 2008/04/11 12:31:51 UTC
cache problem?
Maybe I never paid any attention to the cache, but right now I am doing a resolve and I am getting all configurations downloaded to the cache. Shouldn't just the configuration I asked for come down? Also, the retrieve is also getting all configurations instead of the current one. Is this the way it is supposed to work? If so, what is the point in specifying the configuration during a resolve if it always gets all of them.
---
Shawn Castrianni
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
RE: cache problem?
Posted by Shawn Castrianni <Sh...@halliburton.com>.
Solution: READ THE DOCUMENTATION!!! I added a configuration mapping to my dependency like this:
conf="*->@"
to make the win32 conf of this module be dependent on the win32 conf of the dependency, win64 to be dependent on win64, etc.
For some reason, I just assumed this was the default so I never bothered to read the conf mapping documentation.
Now it only downloads the single configuration that I requested.
---
Shawn Castrianni
CM Chief Architect
Landmark
Halliburton Drilling, Evaluation and Digital Solutions Building 2
2101 City West Blvd.
Houston, TX 77042
Work: 713-839-3086
Cell: 832-654-0888
Fax: 713-839-2758
-----Original Message-----
From: Shawn Castrianni
Sent: Friday, April 11, 2008 11:08 AM
To: 'ivy-user@ant.apache.org'
Subject: RE: cache problem?
Here is a portion of the verbose build. I see some win32->* and *=[*] that seem worrisome.
dependencies.resolve:
[ivy:resolve] using ivy parser to parse file:/D:/CVS/HEAD/tahoe/ivy.xml
[ivy:resolve] :: resolving dependencies :: Landmark#dsinfra#HEAD;working@borg
[ivy:resolve] confs: [win32]
[ivy:resolve] validate = true
[ivy:resolve] refresh = false
[ivy:resolve] resolving dependencies for configuration 'win32'
[ivy:resolve] == resolving dependencies for Landmark#dsinfra#HEAD;working@borg [win32]
[ivy:resolve] == resolving dependencies Landmark#dsinfra#HEAD;working@borg->Landmark#carto#spdm;latest.development [win32->*]
[ivy:resolve] published: Checking cache for: dependency: Landmark#carto#spdm;latest.development {*=[*]}
[ivy:resolve] no cached resolved revision for Landmark#carto#spdm;latest.development
[ivy:resolve] no cached resolved revision for Landmark#carto#spdm;latest.development
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/latest.development/ivy/ivy.xml
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/[revision]/ivy/ivy.xml
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/latest.development/jar/[home]/[homeType]/[path]/carto.jar
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/[revision]/jar/[home]/[homeType]/[path]/carto.jar
[ivy:resolve] published.local: no ivy file nor artifact found for Landmark#carto#spdm;latest.development
[ivy:resolve] no cached resolved revision for Landmark#carto#spdm;latest.development
[ivy:resolve] tried \\houfiler04.lgc.com\BuildStageArea\lgcbuilds/DS_R5000_0_1/carto/spdm/latest.development/ivy/ivy.xml
[ivy:resolve] tried \\houfiler04.lgc.com\BuildStageArea\lgcbuilds/DS_R5000_0_1/carto/spdm/[revision]/ivy/ivy.xml
[ivy:resolve] published.repository do not support transaction. ivy pattern does not use revision as last directory
[ivy:resolve] published.repository: found md file for Landmark#carto#spdm;latest.development
[ivy:resolve] => \\houfiler04.lgc.com\BuildStageArea\lgcbuilds\DS_R5000_0_1\carto\spdm\DS_R5000_0_1.spdm.1\ivy\ivy.xml (DS_R5000_0_1.spdm.1)
[ivy:resolve] downloading \\houfiler04.lgc.com\BuildStageArea\lgcbuilds\DS_R5000_0_1\carto\spdm\DS_R5000_0_1.spdm.1\ivy\ivy.xml ...
[ivy:resolve] published.repository: downloading \\houfiler04.lgc.com\BuildStageArea\lgcbuilds\DS_R5000_0_1\carto\spdm\DS_R5000_0_1.spdm.1\ivy\ivy.xml
[ivy:resolve] [SUCCESSFUL ] Landmark#carto#spdm;DS_R5000_0_1.spdm.1!ivy.original.xml(ivy) (250ms)
[ivy:resolve] [DS_R5000_0_1.spdm.1] Landmark#carto
[ivy:resolve] found Landmark#carto#spdm;DS_R5000_0_1.spdm.1 in published.repository
[ivy:resolve] [DS_R5000_0_1.spdm.1] Landmark#carto#spdm;latest.development
---
Shawn Castrianni
-----Original Message-----
From: Shawn Castrianni
Sent: Friday, April 11, 2008 10:44 AM
To: 'ivy-user@ant.apache.org'
Subject: RE: cache problem?
I have an ivy.xml file with different platform configs, {win32, win64, linux, linux64, and solaris}. I have my artifacts for that module separated out into these configs so that dlls are {win32,win64} and sos are {linux, linux64, and solaris}. I built and published that module with all configurations inside. I then make a new module that depends on the first. My dependency does NOT list any config mapping stuff. I then do a resolve conf="win32" and I see that all the artifacts regardless of the configuration gets downloaded to the cache. I then do a retrieve and all the artifacts downloaded to the cache get copied to my dependencies directory. Since I specified conf="win32" I should only get dlls copied to my dependencies.
Here is my ivy.xml file with the configurations:
<?xml version="1.0" encoding="UTF-8"?>
<ivy-module version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd" xmlns:ext="http://ant.apache.org/ivy/extra">
<info organisation="XXXXX" module="carto" branch="spdm">
<description>This module contains the carto devkit.</description>
</info>
<configurations>
<conf name="win32"/>
<conf name="win64"/>
<conf name="linux"/>
<conf name="linux64"/>
<conf name="solaris"/>
</configurations>
<publications>
<artifact name="module" type="homes" ext="xml" ext:path="" ext:home="carto" ext:homeType="config"/>
<artifact name="com_lgc_jcartointf" type="jar" ext="jar" ext:path="" ext:home="" ext:homeType=""/>
<artifact name="cartointf60_2" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="cartointf80_2" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalc60" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalc80" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalcPBW60" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalcPBW80" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="xerces-c60_2_6" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="xerces-c80_2_6" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="cartointf80_2" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="GeoCalc80" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="GeoCalcPBW80" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="xerces-c80_2_6" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
</publications>
</ivy-module>
---
Shawn Castrianni
CM Chief Architect
Landmark
Halliburton Drilling, Evaluation and Digital Solutions Building 2
2101 City West Blvd.
Houston, TX 77042
Work: 713-839-3086
Cell: 832-654-0888
Fax: 713-839-2758
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: Friday, April 11, 2008 6:55 AM
To: ivy-user@ant.apache.org
Subject: Re: cache problem?
You should get only the configuration you ask. Could you give more details
on what you do and how you conclude you get all of them?
Xavier
On Fri, Apr 11, 2008 at 12:31 PM, Shawn Castrianni <
Shawn.Castrianni@halliburton.com> wrote:
> Maybe I never paid any attention to the cache, but right now I am doing a
> resolve and I am getting all configurations downloaded to the cache.
> Shouldn't just the configuration I asked for come down? Also, the retrieve
> is also getting all configurations instead of the current one. Is this the
> way it is supposed to work? If so, what is the point in specifying the
> configuration during a resolve if it always gets all of them.
>
> ---
> Shawn Castrianni
>
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
RE: cache problem?
Posted by Shawn Castrianni <Sh...@halliburton.com>.
Here is a portion of the verbose build. I see some win32->* and *=[*] that seem worrisome.
dependencies.resolve:
[ivy:resolve] using ivy parser to parse file:/D:/CVS/HEAD/tahoe/ivy.xml
[ivy:resolve] :: resolving dependencies :: Landmark#dsinfra#HEAD;working@borg
[ivy:resolve] confs: [win32]
[ivy:resolve] validate = true
[ivy:resolve] refresh = false
[ivy:resolve] resolving dependencies for configuration 'win32'
[ivy:resolve] == resolving dependencies for Landmark#dsinfra#HEAD;working@borg [win32]
[ivy:resolve] == resolving dependencies Landmark#dsinfra#HEAD;working@borg->Landmark#carto#spdm;latest.development [win32->*]
[ivy:resolve] published: Checking cache for: dependency: Landmark#carto#spdm;latest.development {*=[*]}
[ivy:resolve] no cached resolved revision for Landmark#carto#spdm;latest.development
[ivy:resolve] no cached resolved revision for Landmark#carto#spdm;latest.development
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/latest.development/ivy/ivy.xml
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/[revision]/ivy/ivy.xml
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/latest.development/jar/[home]/[homeType]/[path]/carto.jar
[ivy:resolve] tried E:/modules/DS_R5000_0_1/carto/spdm/[revision]/jar/[home]/[homeType]/[path]/carto.jar
[ivy:resolve] published.local: no ivy file nor artifact found for Landmark#carto#spdm;latest.development
[ivy:resolve] no cached resolved revision for Landmark#carto#spdm;latest.development
[ivy:resolve] tried \\houfiler04.lgc.com\BuildStageArea\lgcbuilds/DS_R5000_0_1/carto/spdm/latest.development/ivy/ivy.xml
[ivy:resolve] tried \\houfiler04.lgc.com\BuildStageArea\lgcbuilds/DS_R5000_0_1/carto/spdm/[revision]/ivy/ivy.xml
[ivy:resolve] published.repository do not support transaction. ivy pattern does not use revision as last directory
[ivy:resolve] published.repository: found md file for Landmark#carto#spdm;latest.development
[ivy:resolve] => \\houfiler04.lgc.com\BuildStageArea\lgcbuilds\DS_R5000_0_1\carto\spdm\DS_R5000_0_1.spdm.1\ivy\ivy.xml (DS_R5000_0_1.spdm.1)
[ivy:resolve] downloading \\houfiler04.lgc.com\BuildStageArea\lgcbuilds\DS_R5000_0_1\carto\spdm\DS_R5000_0_1.spdm.1\ivy\ivy.xml ...
[ivy:resolve] published.repository: downloading \\houfiler04.lgc.com\BuildStageArea\lgcbuilds\DS_R5000_0_1\carto\spdm\DS_R5000_0_1.spdm.1\ivy\ivy.xml
[ivy:resolve] [SUCCESSFUL ] Landmark#carto#spdm;DS_R5000_0_1.spdm.1!ivy.original.xml(ivy) (250ms)
[ivy:resolve] [DS_R5000_0_1.spdm.1] Landmark#carto
[ivy:resolve] found Landmark#carto#spdm;DS_R5000_0_1.spdm.1 in published.repository
[ivy:resolve] [DS_R5000_0_1.spdm.1] Landmark#carto#spdm;latest.development
---
Shawn Castrianni
-----Original Message-----
From: Shawn Castrianni
Sent: Friday, April 11, 2008 10:44 AM
To: 'ivy-user@ant.apache.org'
Subject: RE: cache problem?
I have an ivy.xml file with different platform configs, {win32, win64, linux, linux64, and solaris}. I have my artifacts for that module separated out into these configs so that dlls are {win32,win64} and sos are {linux, linux64, and solaris}. I built and published that module with all configurations inside. I then make a new module that depends on the first. My dependency does NOT list any config mapping stuff. I then do a resolve conf="win32" and I see that all the artifacts regardless of the configuration gets downloaded to the cache. I then do a retrieve and all the artifacts downloaded to the cache get copied to my dependencies directory. Since I specified conf="win32" I should only get dlls copied to my dependencies.
Here is my ivy.xml file with the configurations:
<?xml version="1.0" encoding="UTF-8"?>
<ivy-module version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd" xmlns:ext="http://ant.apache.org/ivy/extra">
<info organisation="XXXXX" module="carto" branch="spdm">
<description>This module contains the carto devkit.</description>
</info>
<configurations>
<conf name="win32"/>
<conf name="win64"/>
<conf name="linux"/>
<conf name="linux64"/>
<conf name="solaris"/>
</configurations>
<publications>
<artifact name="module" type="homes" ext="xml" ext:path="" ext:home="carto" ext:homeType="config"/>
<artifact name="com_lgc_jcartointf" type="jar" ext="jar" ext:path="" ext:home="" ext:homeType=""/>
<artifact name="cartointf60_2" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="cartointf80_2" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalc60" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalc80" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalcPBW60" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalcPBW80" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="xerces-c60_2_6" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="xerces-c80_2_6" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="cartointf80_2" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="GeoCalc80" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="GeoCalcPBW80" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="xerces-c80_2_6" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
</publications>
</ivy-module>
---
Shawn Castrianni
CM Chief Architect
Landmark
Halliburton Drilling, Evaluation and Digital Solutions Building 2
2101 City West Blvd.
Houston, TX 77042
Work: 713-839-3086
Cell: 832-654-0888
Fax: 713-839-2758
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: Friday, April 11, 2008 6:55 AM
To: ivy-user@ant.apache.org
Subject: Re: cache problem?
You should get only the configuration you ask. Could you give more details
on what you do and how you conclude you get all of them?
Xavier
On Fri, Apr 11, 2008 at 12:31 PM, Shawn Castrianni <
Shawn.Castrianni@halliburton.com> wrote:
> Maybe I never paid any attention to the cache, but right now I am doing a
> resolve and I am getting all configurations downloaded to the cache.
> Shouldn't just the configuration I asked for come down? Also, the retrieve
> is also getting all configurations instead of the current one. Is this the
> way it is supposed to work? If so, what is the point in specifying the
> configuration during a resolve if it always gets all of them.
>
> ---
> Shawn Castrianni
>
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
RE: cache problem?
Posted by Shawn Castrianni <Sh...@halliburton.com>.
I have an ivy.xml file with different platform configs, {win32, win64, linux, linux64, and solaris}. I have my artifacts for that module separated out into these configs so that dlls are {win32,win64} and sos are {linux, linux64, and solaris}. I built and published that module with all configurations inside. I then make a new module that depends on the first. My dependency does NOT list any config mapping stuff. I then do a resolve conf="win32" and I see that all the artifacts regardless of the configuration gets downloaded to the cache. I then do a retrieve and all the artifacts downloaded to the cache get copied to my dependencies directory. Since I specified conf="win32" I should only get dlls copied to my dependencies.
Here is my ivy.xml file with the configurations:
<?xml version="1.0" encoding="UTF-8"?>
<ivy-module version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd" xmlns:ext="http://ant.apache.org/ivy/extra">
<info organisation="XXXXX" module="carto" branch="spdm">
<description>This module contains the carto devkit.</description>
</info>
<configurations>
<conf name="win32"/>
<conf name="win64"/>
<conf name="linux"/>
<conf name="linux64"/>
<conf name="solaris"/>
</configurations>
<publications>
<artifact name="module" type="homes" ext="xml" ext:path="" ext:home="carto" ext:homeType="config"/>
<artifact name="com_lgc_jcartointf" type="jar" ext="jar" ext:path="" ext:home="" ext:homeType=""/>
<artifact name="cartointf60_2" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="cartointf80_2" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalc60" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalc80" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalcPBW60" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="GeoCalcPBW80" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="xerces-c60_2_6" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="xerces-c80_2_6" type="bin" ext="dll" ext:path="win32" ext:home="" ext:homeType="" conf="win32"/>
<artifact name="cartointf80_2" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="GeoCalc80" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="GeoCalcPBW80" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="xerces-c80_2_6" type="bin" ext="dll" ext:path="win64" ext:home="" ext:homeType="" conf="win64"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="linux" ext:home="" ext:homeType="" conf="linux"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="linux64" ext:home="" ext:homeType="" conf="linux64"/>
<artifact name="libcartointf" type="bin" ext="so.2" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libGeoCalc" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libGeoCalcPBW" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so.26" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
<artifact name="libxerces-c" type="bin" ext="so.26.0" ext:path="solaris" ext:home="" ext:homeType="" conf="solaris"/>
</publications>
</ivy-module>
---
Shawn Castrianni
CM Chief Architect
Landmark
Halliburton Drilling, Evaluation and Digital Solutions Building 2
2101 City West Blvd.
Houston, TX 77042
Work: 713-839-3086
Cell: 832-654-0888
Fax: 713-839-2758
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: Friday, April 11, 2008 6:55 AM
To: ivy-user@ant.apache.org
Subject: Re: cache problem?
You should get only the configuration you ask. Could you give more details
on what you do and how you conclude you get all of them?
Xavier
On Fri, Apr 11, 2008 at 12:31 PM, Shawn Castrianni <
Shawn.Castrianni@halliburton.com> wrote:
> Maybe I never paid any attention to the cache, but right now I am doing a
> resolve and I am getting all configurations downloaded to the cache.
> Shouldn't just the configuration I asked for come down? Also, the retrieve
> is also getting all configurations instead of the current one. Is this the
> way it is supposed to work? If so, what is the point in specifying the
> configuration during a resolve if it always gets all of them.
>
> ---
> Shawn Castrianni
>
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
Re: cache problem?
Posted by Xavier Hanin <xa...@gmail.com>.
You should get only the configuration you ask. Could you give more details
on what you do and how you conclude you get all of them?
Xavier
On Fri, Apr 11, 2008 at 12:31 PM, Shawn Castrianni <
Shawn.Castrianni@halliburton.com> wrote:
> Maybe I never paid any attention to the cache, but right now I am doing a
> resolve and I am getting all configurations downloaded to the cache.
> Shouldn't just the configuration I asked for come down? Also, the retrieve
> is also getting all configurations instead of the current one. Is this the
> way it is supposed to work? If so, what is the point in specifying the
> configuration during a resolve if it always gets all of them.
>
> ---
> Shawn Castrianni
>
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/