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 "Fernandes, Gerard" <ge...@lehman.com> on 2007/10/01 11:59:10 UTC
Cache Path and Ant console logging
Using Cache path in Ant results in one resolution per use of the cached
path reference. This is undesirable as the cached path is cached once
(globally) at the beginning of the Ant script and used throughout the
ant script and also in called scripts.
The desirable behavior would be to have Cache path resolve exactly ONCE
each time it is actually invoked.
See the Ant log console below - it seems almost as if at every Ant
Target being executed, the cache path is being invoked and executed as
well.
************************************************************************
*****************************************
Buildfile: C:\Java\Projects\Fire\fire-server\build.xml
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: Ivy 1.4.1 - 20061109165313 ::
http://ivy.jayasoft.org/ ::
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
build:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
build-dependent:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
---------------------------------------------------------------------
java.compile:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
---------------------------------------------------------------------
java.compile.target:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
---------------------------------------------------------------------
java.compile.target:
jar:
build:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
java.compile:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
java.compile.target:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
java.compile.target:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
jar:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
jar:
[ivy:configure] Loading
jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4.1
.jar!/fr/jayasoft/ivy/ivy.properties
[ivy:configure] :: configuring :: file =
C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
[ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
working@lofidw041141 ]
[ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
[ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
externalLibraries
[ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
externalLibraries
[ivy:resolve] found [ coherence | coherence | 3.1 ] in
externalLibraries
[ivy:resolve] found [ coherence | tangosol | 3.1 ] in
externalLibraries
[ivy:resolve] found [ grinder | grinder | 2.8.6 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-beanutils | commons-beanutils |
1.7.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ] in
externalLibraries
[ivy:resolve] found [ jakarta-commons-lang | commons-lang | 2.2 ] in
externalLibraries
[ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in externalLibraries
[ivy:resolve] found [ jdom | saxpath | 1.0 ] in externalLibraries
[ivy:resolve] found [ lehman-ua | utr | 1.04 ] in externalLibraries
[ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 | 1.1 ]
in externalLibraries
[ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
externalLibraries
[ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
externalLibraries
[ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1 ] in
externalLibraries
[ivy:resolve] found [ spring | spring | 2.0.6 ] in externalLibraries
[ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
externalLibraries
[ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in externalLibraries
[ivy:resolve] found [ weblogic | weblogic | 9.2 ] in externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
externalLibraries
[ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
externalLibraries
[ivy:resolve] found [ cglib | cglib | 2.1_03 ] in externalLibraries
[ivy:resolve] found [ hibernate | asm | 3.0.5 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-collections |
commons-collections | 3.1 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jakarta-commons-logging | commons-logging-api |
1.0.4 ] in externalLibraries
[ivy:resolve] found [ jencks | jencks-all | 1.0 ] in externalLibraries
[ivy:resolve] found [ jencks | concurrent | 1.0 ] in externalLibraries
[ivy:resolve] found [ junit | junit | 4.1 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock | 2.2.0 ] in externalLibraries
[ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ] in
externalLibraries
[ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in externalLibraries
[ivy:resolve] found [ xerces | xerces | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in externalLibraries
[ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0 ] in
externalLibraries
[ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
externalLibraries
[ivy:resolve] :: resolution report ::
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| COMPILE | 29 | 0 | 0 | 0 || 31 |
0 |
| RUNTIME | 35 | 0 | 0 | 0 || 35 |
0 |
| TEST | 18 | 0 | 0 | 0 || 18 |
0 |
| FIRE | 6 | 0 | 0 | 0 || 6 |
0 |
| DEPLOY | 1 | 0 | 0 | 0 || 1 |
0 |
---------------------------------------------------------------------
jar:
BUILD SUCCESSFUL
Total time: 9 seconds
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
RE: IvyDE source artifact not recognised
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
I think it's perfectly acceptable for the source artifact to have "-src" in it's name and IvyDE should recognise this. It is a common java practice.
Why should one have to work around the settings to accommodate IvyDE? And why should one have to work around by changing the source artifact name?
The source and binary artifacts are produced by a third party - in this case Commons-CLI. And the source and binary artifacts are produced by Maven. Again, this is a common pattern. Why can IvyDE not recognise it?
Gerard
-----Original Message-----
From: Nicolas Lalevée [mailto:nicolas.lalevee@anyware-tech.com]
Sent: 11 December 2007 20:06
To: ivy-user@incubator.apache.org
Subject: Re: IvyDE source artifact not recognised
Le 11 déc. 07 à 11:11, John Gill a écrit :
> I believe that one of the limitations of ivyDE source linking is that
> the names must match. You can have a different type/ext like
> ".src.jar"
> but
> that's it. The only way I have ever got it to work is with matching
> names.
And I think that it is an error to have different names. Because having different names means talking about different artifact.
So the ivy.xml have to look like that :
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source" ext="zip"
conf="COMPILE" />
</dependency>
Then there is the problem with the real artifact name : commons-cli- src-1.1.zip That can be fixed easily with a proper pattern :
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
[artifact]-src-[revision].[ext]"/>
Nicolas
>
>
> On Dec 11, 2007 6:16 PM, Fernandes, Gerard
> <gerard.fernandes@lehman.com
> >
> wrote:
>
>>
>> IvyDE doesn't recognise source artifacts with a different name than
>> the binary artifact.
>>
>> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
>> called commons-cli-src-1.1.zip, an Ivy configuration with the
>> following will resolve and the sources are downloaded (can be
>> confirmed by the Ivy report as well as checking the cache) but will
>> NOT attach sources in
>> Eclipse:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli-src" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> Ivy settings are:
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> </filesystem>
>>
>> The only way to make this work is to change Ivy settings to:
>>
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
>> [ext]"
>> />
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> -src.[ext]"/>
>> </filesystem>
>>
>> And rename
>> commons-cli-src-1.1.zip
>> To
>> commons-cli-1.1-src.zip
>>
>> And finally change the Ivy configuration to:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>>
>> Gerard
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - - -
>> - - - - - - -
>>
>> This message is intended only for the personal and confidential use
>> of the designated recipient(s) named above. If you are not the
>> intended recipient of this message you are hereby notified that any
>> review, dissemination, distribution or copying of this message is
>> strictly prohibited. This communication is for information purposes
>> only and should not be regarded as an offer to sell or as a
>> solicitation of an offer to buy any financial product, an official
>> confirmation of any transaction, or as an official statement of
>> Lehman Brothers. Email transmission cannot be guaranteed to be
>> secure or error-free. Therefore, we do not represent that this
>> information
>> is complete or accurate and it should not be relied upon as such.
>> All
>> information is subject to change without notice.
>>
>>
>>
>>
>
>
> --
> Regards,
> John Gill
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
RE: IvyDE source artifact not recognised
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
Note that the cglib 2.1_03 source artifact is named: cglib-src-2.1_03.jar
-----Original Message-----
From: Fernandes, Gerard
Sent: 12 December 2007 09:39
To: 'ivy-user@incubator.apache.org'
Subject: RE: IvyDE source artifact not recognised
In my opinion, it is very important that the "-src" part be acceptable and recognised by IvyDE. If one has to workaround by:
1- changing the source artifact name
2- adding "-src" in ivysettings
One runs the risk of Ivy resolving source artifacts instead of binaries.
E.g. Try having cglib 2.1_03 and commons-cli and configuring Ivy with the cglib binary only and commons-cli with binary and source artifacts by working around in the ivysettings. The cglib artifact attached is the source artifact! Of course Eclipse compilation breaks.
Try with the ivysettings as you've mentioned below and Ivy configuration:
<dependency org="cglib" name="cglib" rev="2.1_03" conf="COMPILE,RUNTIME,TEST->default"/>
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source" ext="zip" conf="COMPILE" />
</dependency>
This kind of workaround also affects Ivy and breaks the ant build as well! This means my CruiseControl build is no longer working because of the workaround in ivysettings and the above configuration to accommodate IvyDE for attaching sources in Eclipse.
Gerard
-----Original Message-----
From: Nicolas Lalevée [mailto:nicolas.lalevee@anyware-tech.com]
Sent: 11 December 2007 20:06
To: ivy-user@incubator.apache.org
Subject: Re: IvyDE source artifact not recognised
Le 11 déc. 07 à 11:11, John Gill a écrit :
> I believe that one of the limitations of ivyDE source linking is that
> the names must match. You can have a different type/ext like
> ".src.jar"
> but
> that's it. The only way I have ever got it to work is with matching
> names.
And I think that it is an error to have different names. Because having different names means talking about different artifact.
So the ivy.xml have to look like that :
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source" ext="zip"
conf="COMPILE" />
</dependency>
Then there is the problem with the real artifact name : commons-cli- src-1.1.zip That can be fixed easily with a proper pattern :
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
[artifact]-src-[revision].[ext]"/>
Nicolas
>
>
> On Dec 11, 2007 6:16 PM, Fernandes, Gerard
> <gerard.fernandes@lehman.com
> >
> wrote:
>
>>
>> IvyDE doesn't recognise source artifacts with a different name than
>> the binary artifact.
>>
>> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
>> called commons-cli-src-1.1.zip, an Ivy configuration with the
>> following will resolve and the sources are downloaded (can be
>> confirmed by the Ivy report as well as checking the cache) but will
>> NOT attach sources in
>> Eclipse:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli-src" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> Ivy settings are:
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> </filesystem>
>>
>> The only way to make this work is to change Ivy settings to:
>>
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
>> [ext]"
>> />
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> -src.[ext]"/>
>> </filesystem>
>>
>> And rename
>> commons-cli-src-1.1.zip
>> To
>> commons-cli-1.1-src.zip
>>
>> And finally change the Ivy configuration to:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>>
>> Gerard
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - - -
>> - - - - - - -
>>
>> This message is intended only for the personal and confidential use
>> of the designated recipient(s) named above. If you are not the
>> intended recipient of this message you are hereby notified that any
>> review, dissemination, distribution or copying of this message is
>> strictly prohibited. This communication is for information purposes
>> only and should not be regarded as an offer to sell or as a
>> solicitation of an offer to buy any financial product, an official
>> confirmation of any transaction, or as an official statement of
>> Lehman Brothers. Email transmission cannot be guaranteed to be
>> secure or error-free. Therefore, we do not represent that this
>> information
>> is complete or accurate and it should not be relied upon as such.
>> All
>> information is subject to change without notice.
>>
>>
>>
>>
>
>
> --
> Regards,
> John Gill
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
RE: IvyDE source artifact not recognised
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
In my opinion, it is very important that the "-src" part be acceptable and recognised by IvyDE. If one has to workaround by:
1- changing the source artifact name
2- adding "-src" in ivysettings
One runs the risk of Ivy resolving source artifacts instead of binaries.
E.g. Try having cglib 2.1_03 and commons-cli and configuring Ivy with the cglib binary only and commons-cli with binary and source artifacts by working around in the ivysettings. The cglib artifact attached is the source artifact! Of course Eclipse compilation breaks.
Try with the ivysettings as you've mentioned below and Ivy configuration:
<dependency org="cglib" name="cglib" rev="2.1_03" conf="COMPILE,RUNTIME,TEST->default"/>
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source" ext="zip" conf="COMPILE" />
</dependency>
This kind of workaround also affects Ivy and breaks the ant build as well! This means my CruiseControl build is no longer working because of the workaround in ivysettings and the above configuration to accommodate IvyDE for attaching sources in Eclipse.
Gerard
-----Original Message-----
From: Nicolas Lalevée [mailto:nicolas.lalevee@anyware-tech.com]
Sent: 11 December 2007 20:06
To: ivy-user@incubator.apache.org
Subject: Re: IvyDE source artifact not recognised
Le 11 déc. 07 à 11:11, John Gill a écrit :
> I believe that one of the limitations of ivyDE source linking is that
> the names must match. You can have a different type/ext like
> ".src.jar"
> but
> that's it. The only way I have ever got it to work is with matching
> names.
And I think that it is an error to have different names. Because having different names means talking about different artifact.
So the ivy.xml have to look like that :
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source" ext="zip"
conf="COMPILE" />
</dependency>
Then there is the problem with the real artifact name : commons-cli- src-1.1.zip That can be fixed easily with a proper pattern :
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
[artifact]-src-[revision].[ext]"/>
Nicolas
>
>
> On Dec 11, 2007 6:16 PM, Fernandes, Gerard
> <gerard.fernandes@lehman.com
> >
> wrote:
>
>>
>> IvyDE doesn't recognise source artifacts with a different name than
>> the binary artifact.
>>
>> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
>> called commons-cli-src-1.1.zip, an Ivy configuration with the
>> following will resolve and the sources are downloaded (can be
>> confirmed by the Ivy report as well as checking the cache) but will
>> NOT attach sources in
>> Eclipse:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli-src" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> Ivy settings are:
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> </filesystem>
>>
>> The only way to make this work is to change Ivy settings to:
>>
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
>> [ext]"
>> />
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> -src.[ext]"/>
>> </filesystem>
>>
>> And rename
>> commons-cli-src-1.1.zip
>> To
>> commons-cli-1.1-src.zip
>>
>> And finally change the Ivy configuration to:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>>
>> Gerard
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - - -
>> - - - - - - -
>>
>> This message is intended only for the personal and confidential use
>> of the designated recipient(s) named above. If you are not the
>> intended recipient of this message you are hereby notified that any
>> review, dissemination, distribution or copying of this message is
>> strictly prohibited. This communication is for information purposes
>> only and should not be regarded as an offer to sell or as a
>> solicitation of an offer to buy any financial product, an official
>> confirmation of any transaction, or as an official statement of
>> Lehman Brothers. Email transmission cannot be guaranteed to be
>> secure or error-free. Therefore, we do not represent that this
>> information
>> is complete or accurate and it should not be relied upon as such.
>> All
>> information is subject to change without notice.
>>
>>
>>
>>
>
>
> --
> Regards,
> John Gill
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
RE: IvyDE source artifact not recognised
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
Thank you. Issue IVYDE-66 logged and updated with work-around posted by Xavier.
-----Original Message-----
From: Nicolas Lalevée [mailto:nicolas.lalevee@anyware-tech.com]
Sent: 13 December 2007 19:29
To: ivy-user@incubator.apache.org
Subject: Re: IvyDE source artifact not recognised
Le 13 déc. 07 à 19:04, Fernandes, Gerard a écrit :
>
> Thank you for the reply.
>
> How do I log an issue with IvyDE?
https://issues.apache.org/jira/browse/IVYDE
Nicolas
>
>
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: 13 December 2007 17:30
> To: ivy-user@incubator.apache.org
> Subject: Re: IvyDE source artifact not recognised
>
> There are other ways to implement what you want without having to use
> multiple patterns. You can for instance use a custom attribute on your
> source artifact, and put this token in your pattern. For
> instance:
> <artifact name="commons-cli" suffix="-src" type="source" ext="zip"
> conf="COMPILE" />
> ${ivy.conf.dir}/[organisation]/[revision]/[artifact][suffix].[ext]
>
> But I agree that making IvyDE more flexible by recognizing artifact
> name suffix for sources could make things easier to use. Feel free to
> open a new issue.
>
> Xavier
>
> On Dec 12, 2007 10:22 AM, Fernandes, Gerard
> <gerard.fernandes@lehman.com
> >
> wrote:
>
>>
>> It's fairly common in the Java world to have the pattern:
>>
>> artifact.ext for a binary and
>> artifact-src.ext for it's source.
>>
>> All things being equal, IvyDE should be smart enough to pair a binary
>> with it's source if the only difference between the name is the
>> existence of "-src" in the source artifacts name.
>>
>> As it stands at the moment, IvyDE doesn't do that. It requires that
>> the source artifact have the EXACT SAME name as the binary artifact
>> with the only difference being a possibly different extension.
>>
>> Therefore, for IvyDE to work, one must perform the following 3 steps:
>>
>> (1) "commons-cli-1.1.jar" MUST have the source artifact named
>> as "
>> commons-cli-1.1-src.[jar/zip]". The original source artifact produced
>> by the Commons-CLI maven build is named "commons-cli-src-1.1.zip".
>>
>> (2) AND, the ivysettings must be set to resolve artifacts of the
>> pattern
>>
>> <filesystem name="externalLibraries">
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact].[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-src.[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-[revision]-src.[ext]"/>
>> </filesystem>
>>
>>
>> (3) AND, the ivy.xml MUST have the source artifact name set to
>> exactly
>> the same as the binary artifact name (Note that this is possible only
>> because of the above ivysettings which in my opinion is not ideal -
>> you should not have to add the "-src" bit to ivysettings)
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> Ideally, the ivysettings should be:
>>
>> <filesystem name="externalLibraries">
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact].[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
>> </filesystem>
>>
>> And the ivy configuration should look like:
>>
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli-src" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> But IvyDE will NOT attach the source if so configured.
>>
>> Gerard
>>
>> -----Original Message-----
>> From: John Gill [mailto:llignhoj@gmail.com]
>> Sent: 12 December 2007 00:18
>> To: ivy-user@incubator.apache.org
>> Subject: Re: IvyDE source artifact not recognised
>>
>> I think the problem is that is you had a package that had several
>> jars and several source jars, how would ivy know how to match them
>> together?
>>
>> The same goes for javadoc zips/jars.
>>
>> On Dec 12, 2007 5:05 AM, Nicolas Lalevée
>> <nicolas.lalevee@anyware-tech.com
>>>
>> wrote:
>>
>>>
>>> Le 11 déc. 07 à 11:11, John Gill a écrit :
>>>
>>>> I believe that one of the limitations of ivyDE source linking is
>>>> that the names must match. You can have a different type/ext like
>>>> ".src.jar"
>>>> but
>>>> that's it. The only way I have ever got it to work is with matching
>>>> names.
>>>
>>> And I think that it is an error to have different names. Because
>>> having different names means talking about different artifact.
>>>
>>> So the ivy.xml have to look like that :
>>> <dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
>>> conf="COMPILE,RUNTIME,TEST->default">
>>> <artifact name="commons-cli" type="jar"/> <artifact
>>> name="commons-cli" type="source" ext="zip"
>>> conf="COMPILE" />
>>> </dependency>
>>>
>>> Then there is the problem with the real artifact name : commons-cli-
>>> src-1.1.zip That can be fixed easily with a proper pattern :
>>>
>>> <artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
>>> [artifact]-src-[revision].[ext]"/>
>>>
>>> Nicolas
>>>
>>>
>>>>
>>>>
>>>> On Dec 11, 2007 6:16 PM, Fernandes, Gerard
>>>> <gerard.fernandes@lehman.com
>>>>>
>>>> wrote:
>>>>
>>>>>
>>>>> IvyDE doesn't recognise source artifacts with a different name
>>>>> than the binary artifact.
>>>>>
>>>>> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
>>>>> called commons-cli-src-1.1.zip, an Ivy configuration with the
>>>>> following will resolve and the sources are downloaded (can be
>>>>> confirmed by the Ivy report as well as checking the cache) but
>>>>> will NOT attach sources in
>>>>> Eclipse:
>>>>> <dependency org="jakarta-commons-cli"
>>>>> name="commons- cli"
>>>>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>>>>> <artifact name="commons-cli" type="jar"/>
>>>>> <artifact name="commons-cli-src"
>>>>> type="source"
>>>>> ext="zip" conf="COMPILE" />
>>>>> </dependency>
>>>>>
>>>>> Ivy settings are:
>>>>> <filesystem name="externalLibraries">
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>>>>> [ext]"/>
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>>>>> [revision]
>>>>> .[ext]"/>
>>>>> </filesystem>
>>>>>
>>>>> The only way to make this work is to change Ivy settings to:
>>>>>
>>>>> <filesystem name="externalLibraries">
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>>>>> [ext]"/>
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
>>>>> [ext]"
>>>>> />
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>>>>> [revision]
>>>>> .[ext]"/>
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>>>>> [revision]
>>>>> -src.[ext]"/>
>>>>> </filesystem>
>>>>>
>>>>> And rename
>>>>> commons-cli-src-1.1.zip
>>>>> To
>>>>> commons-cli-1.1-src.zip
>>>>>
>>>>> And finally change the Ivy configuration to:
>>>>> <dependency org="jakarta-commons-cli"
>>>>> name="commons- cli"
>>>>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>>>>> <artifact name="commons-cli" type="jar"/>
>>>>> <artifact name="commons-cli" type="source"
>>>>> ext="zip" conf="COMPILE" />
>>>>> </dependency>
>>>>>
>>>>>
>>>>> Gerard
>>>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>>>> -
>>>>> - - -
>>>>> - - - - - - -
>>>>>
>>>>> This message is intended only for the personal and confidential
>>>>> use of the designated recipient(s) named above. If you are not
>>>>> the intended recipient of this message you are hereby notified
>>>>> that any review, dissemination, distribution or copying of this
>>>>> message is strictly prohibited. This communication is for
>>>>> information purposes only and should not be regarded as an offer
>>>>> to sell or as a solicitation of an offer to buy any financial
>>>>> product, an official confirmation of any transaction, or as an
>>>>> official statement of Lehman Brothers. Email transmission cannot
>>>>> be guaranteed to be secure or error-free. Therefore, we do not
>>>>> represent that this information is complete or accurate and it
>>>>> should not be relied upon as such.
>>>>> All
>>>>> information is subject to change without notice.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> John Gill
>>>
>>>
>>
>>
>> --
>> Regards,
>> John Gill
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - -
>> - - - - - - -
>>
>> This message is intended only for the personal and confidential use
>> of the designated recipient(s) named above. If you are not the
>> intended recipient of this message you are hereby notified that any
>> review, dissemination, distribution or copying of this message is
>> strictly prohibited. This communication is for information purposes
>> only and should not be regarded as an offer to sell or as a
>> solicitation of an offer to buy any financial product, an official
>> confirmation of any transaction, or as an official statement of
>> Lehman Brothers. Email transmission cannot be guaranteed to be
>> secure or error-free.
>> Therefore, we do not represent that this information is complete or
>> accurate and it should not be relied upon as such. All information
>> is subject to change without notice.
>>
>>
>>
>>
>
>
> --
> Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/
> http://ant.apache.org/ivy/ http://www.xoocode.org/
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - - - - - -
>
> This message is intended only for the personal and confidential use of
> the designated recipient(s) named above. If you are not the intended
> recipient of this message you are hereby notified that any review,
> dissemination, distribution or copying of this message is strictly
> prohibited. This communication is for information purposes only and
> should not be regarded as an offer to sell or as a solicitation of an
> offer to buy any financial product, an official confirmation of any
> transaction, or as an official statement of Lehman Brothers. Email
> transmission cannot be guaranteed to be secure or error-free.
> Therefore, we do not represent that this information is complete or
> accurate and it should not be relied upon as such. All information is
> subject to change without notice.
>
>
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Re: IvyDE source artifact not recognised
Posted by Nicolas Lalevée <ni...@anyware-tech.com>.
Le 13 déc. 07 à 19:04, Fernandes, Gerard a écrit :
>
> Thank you for the reply.
>
> How do I log an issue with IvyDE?
https://issues.apache.org/jira/browse/IVYDE
Nicolas
>
>
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: 13 December 2007 17:30
> To: ivy-user@incubator.apache.org
> Subject: Re: IvyDE source artifact not recognised
>
> There are other ways to implement what you want without having to
> use multiple patterns. You can for instance use a custom attribute
> on your source artifact, and put this token in your pattern. For
> instance:
> <artifact name="commons-cli" suffix="-src" type="source" ext="zip"
> conf="COMPILE" />
> ${ivy.conf.dir}/[organisation]/[revision]/[artifact][suffix].[ext]
>
> But I agree that making IvyDE more flexible by recognizing artifact
> name suffix for sources could make things easier to use. Feel free
> to open a new issue.
>
> Xavier
>
> On Dec 12, 2007 10:22 AM, Fernandes, Gerard <gerard.fernandes@lehman.com
> >
> wrote:
>
>>
>> It's fairly common in the Java world to have the pattern:
>>
>> artifact.ext for a binary and
>> artifact-src.ext for it's source.
>>
>> All things being equal, IvyDE should be smart enough to pair a binary
>> with it's source if the only difference between the name is the
>> existence of "-src" in the source artifacts name.
>>
>> As it stands at the moment, IvyDE doesn't do that. It requires that
>> the source artifact have the EXACT SAME name as the binary artifact
>> with the only difference being a possibly different extension.
>>
>> Therefore, for IvyDE to work, one must perform the following 3 steps:
>>
>> (1) "commons-cli-1.1.jar" MUST have the source artifact named
>> as "
>> commons-cli-1.1-src.[jar/zip]". The original source artifact produced
>> by the Commons-CLI maven build is named "commons-cli-src-1.1.zip".
>>
>> (2) AND, the ivysettings must be set to resolve artifacts of the
>> pattern
>>
>> <filesystem name="externalLibraries">
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact].[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-src.[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-[revision]-src.[ext]"/>
>> </filesystem>
>>
>>
>> (3) AND, the ivy.xml MUST have the source artifact name set to
>> exactly
>> the same as the binary artifact name (Note that this is possible only
>> because of the above ivysettings which in my opinion is not ideal -
>> you should not have to add the "-src" bit to ivysettings)
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> Ideally, the ivysettings should be:
>>
>> <filesystem name="externalLibraries">
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact].[ext]"/>
>> <artifact pattern="${ivy.conf.dir
>> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
>> </filesystem>
>>
>> And the ivy configuration should look like:
>>
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli-src" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> But IvyDE will NOT attach the source if so configured.
>>
>> Gerard
>>
>> -----Original Message-----
>> From: John Gill [mailto:llignhoj@gmail.com]
>> Sent: 12 December 2007 00:18
>> To: ivy-user@incubator.apache.org
>> Subject: Re: IvyDE source artifact not recognised
>>
>> I think the problem is that is you had a package that had several
>> jars
>> and several source jars, how would ivy know how to match them
>> together?
>>
>> The same goes for javadoc zips/jars.
>>
>> On Dec 12, 2007 5:05 AM, Nicolas Lalevée
>> <nicolas.lalevee@anyware-tech.com
>>>
>> wrote:
>>
>>>
>>> Le 11 déc. 07 à 11:11, John Gill a écrit :
>>>
>>>> I believe that one of the limitations of ivyDE source linking is
>>>> that the names must match. You can have a different type/ext like
>>>> ".src.jar"
>>>> but
>>>> that's it. The only way I have ever got it to work is with
>>>> matching names.
>>>
>>> And I think that it is an error to have different names. Because
>>> having different names means talking about different artifact.
>>>
>>> So the ivy.xml have to look like that :
>>> <dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
>>> conf="COMPILE,RUNTIME,TEST->default">
>>> <artifact name="commons-cli" type="jar"/>
>>> <artifact name="commons-cli" type="source" ext="zip"
>>> conf="COMPILE" />
>>> </dependency>
>>>
>>> Then there is the problem with the real artifact name : commons-cli-
>>> src-1.1.zip That can be fixed easily with a proper pattern :
>>>
>>> <artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
>>> [artifact]-src-[revision].[ext]"/>
>>>
>>> Nicolas
>>>
>>>
>>>>
>>>>
>>>> On Dec 11, 2007 6:16 PM, Fernandes, Gerard
>>>> <gerard.fernandes@lehman.com
>>>>>
>>>> wrote:
>>>>
>>>>>
>>>>> IvyDE doesn't recognise source artifacts with a different name
>>>>> than the binary artifact.
>>>>>
>>>>> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
>>>>> called commons-cli-src-1.1.zip, an Ivy configuration with the
>>>>> following will resolve and the sources are downloaded (can be
>>>>> confirmed by the Ivy report as well as checking the cache) but
>>>>> will NOT attach sources in
>>>>> Eclipse:
>>>>> <dependency org="jakarta-commons-cli"
>>>>> name="commons- cli"
>>>>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>>>>> <artifact name="commons-cli" type="jar"/>
>>>>> <artifact name="commons-cli-src"
>>>>> type="source"
>>>>> ext="zip" conf="COMPILE" />
>>>>> </dependency>
>>>>>
>>>>> Ivy settings are:
>>>>> <filesystem name="externalLibraries">
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>>>>> [ext]"/>
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>>>>> [revision]
>>>>> .[ext]"/>
>>>>> </filesystem>
>>>>>
>>>>> The only way to make this work is to change Ivy settings to:
>>>>>
>>>>> <filesystem name="externalLibraries">
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>>>>> [ext]"/>
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
>>>>> [ext]"
>>>>> />
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>>>>> [revision]
>>>>> .[ext]"/>
>>>>> <artifact
>>>>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>>>>> [revision]
>>>>> -src.[ext]"/>
>>>>> </filesystem>
>>>>>
>>>>> And rename
>>>>> commons-cli-src-1.1.zip
>>>>> To
>>>>> commons-cli-1.1-src.zip
>>>>>
>>>>> And finally change the Ivy configuration to:
>>>>> <dependency org="jakarta-commons-cli"
>>>>> name="commons- cli"
>>>>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>>>>> <artifact name="commons-cli" type="jar"/>
>>>>> <artifact name="commons-cli" type="source"
>>>>> ext="zip" conf="COMPILE" />
>>>>> </dependency>
>>>>>
>>>>>
>>>>> Gerard
>>>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>>>> -
>>>>> - - -
>>>>> - - - - - - -
>>>>>
>>>>> This message is intended only for the personal and confidential
>>>>> use of the designated recipient(s) named above. If you are not
>>>>> the intended recipient of this message you are hereby notified
>>>>> that any review, dissemination, distribution or copying of this
>>>>> message is strictly prohibited. This communication is for
>>>>> information purposes only and should not be regarded as an offer
>>>>> to sell or as a solicitation of an offer to buy any financial
>>>>> product, an official confirmation of any transaction, or as an
>>>>> official statement of Lehman Brothers. Email transmission cannot
>>>>> be guaranteed to be secure or error-free. Therefore, we do not
>>>>> represent that this information is complete or accurate and it
>>>>> should not be relied upon as such.
>>>>> All
>>>>> information is subject to change without notice.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> John Gill
>>>
>>>
>>
>>
>> --
>> Regards,
>> John Gill
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - -
>> - - - - - - -
>>
>> This message is intended only for the personal and confidential use
>> of
>> the designated recipient(s) named above. If you are not the intended
>> recipient of this message you are hereby notified that any review,
>> dissemination, distribution or copying of this message is strictly
>> prohibited. This communication is for information purposes only and
>> should not be regarded as an offer to sell or as a solicitation of an
>> offer to buy any financial product, an official confirmation of any
>> transaction, or as an official statement of Lehman Brothers. Email
>> transmission cannot be guaranteed to be secure or error-free.
>> Therefore, we do not represent that this information is complete or
>> accurate and it should not be relied upon as such. All information
>> is subject to change without notice.
>>
>>
>>
>>
>
>
> --
> Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/
> http://www.xoocode.org/
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - - - - - -
>
> This message is intended only for the personal and confidential use
> of the designated recipient(s) named above. If you are not the
> intended recipient of this message you are hereby notified that any
> review, dissemination, distribution or copying of this message is
> strictly prohibited. This communication is for information purposes
> only and should not be regarded as an offer to sell or as a
> solicitation of an offer to buy any financial product, an official
> confirmation of any transaction, or as an official statement of
> Lehman Brothers. Email transmission cannot be guaranteed to be
> secure or error-free. Therefore, we do not represent that this
> information is complete or accurate and it should not be relied upon
> as such. All information is subject to change without notice.
>
>
>
Re: IvyDE source artifact not recognised
Posted by Gilles Scokart <gs...@gmail.com>.
https://issues.apache.org/jira/browse/IVYDE
Gilles
2007/12/13, Fernandes, Gerard <ge...@lehman.com>:
>
> Thank you for the reply.
>
> How do I log an issue with IvyDE?
>
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: 13 December 2007 17:30
> To: ivy-user@incubator.apache.org
> Subject: Re: IvyDE source artifact not recognised
>
> There are other ways to implement what you want without having to use multiple patterns. You can for instance use a custom attribute on your source artifact, and put this token in your pattern. For instance:
> <artifact name="commons-cli" suffix="-src" type="source" ext="zip"
> conf="COMPILE" />
> ${ivy.conf.dir}/[organisation]/[revision]/[artifact][suffix].[ext]
>
> But I agree that making IvyDE more flexible by recognizing artifact name suffix for sources could make things easier to use. Feel free to open a new issue.
>
> Xavier
>
> On Dec 12, 2007 10:22 AM, Fernandes, Gerard <ge...@lehman.com>
> wrote:
>
> >
> > It's fairly common in the Java world to have the pattern:
> >
> > artifact.ext for a binary and
> > artifact-src.ext for it's source.
> >
> > All things being equal, IvyDE should be smart enough to pair a binary
> > with it's source if the only difference between the name is the
> > existence of "-src" in the source artifacts name.
> >
> > As it stands at the moment, IvyDE doesn't do that. It requires that
> > the source artifact have the EXACT SAME name as the binary artifact
> > with the only difference being a possibly different extension.
> >
> > Therefore, for IvyDE to work, one must perform the following 3 steps:
> >
> > (1) "commons-cli-1.1.jar" MUST have the source artifact named as "
> > commons-cli-1.1-src.[jar/zip]". The original source artifact produced
> > by the Commons-CLI maven build is named "commons-cli-src-1.1.zip".
> >
> > (2) AND, the ivysettings must be set to resolve artifacts of the
> > pattern
> >
> > <filesystem name="externalLibraries">
> > <artifact pattern="${ivy.conf.dir
> > }/[organisation]/[revision]/[artifact].[ext]"/>
> > <artifact pattern="${ivy.conf.dir
> > }/[organisation]/[revision]/[artifact]-src.[ext]"/>
> > <artifact pattern="${ivy.conf.dir
> > }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> > <artifact pattern="${ivy.conf.dir
> > }/[organisation]/[revision]/[artifact]-[revision]-src.[ext]"/>
> > </filesystem>
> >
> >
> > (3) AND, the ivy.xml MUST have the source artifact name set to exactly
> > the same as the binary artifact name (Note that this is possible only
> > because of the above ivysettings which in my opinion is not ideal -
> > you should not have to add the "-src" bit to ivysettings)
> > <dependency org="jakarta-commons-cli" name="commons-cli"
> > rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > <artifact name="commons-cli" type="jar"/>
> > <artifact name="commons-cli" type="source"
> > ext="zip" conf="COMPILE" />
> > </dependency>
> >
> > Ideally, the ivysettings should be:
> >
> > <filesystem name="externalLibraries">
> > <artifact pattern="${ivy.conf.dir
> > }/[organisation]/[revision]/[artifact].[ext]"/>
> > <artifact pattern="${ivy.conf.dir
> > }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> > </filesystem>
> >
> > And the ivy configuration should look like:
> >
> > <dependency org="jakarta-commons-cli" name="commons-cli"
> > rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > <artifact name="commons-cli" type="jar"/>
> > <artifact name="commons-cli-src" type="source"
> > ext="zip" conf="COMPILE" />
> > </dependency>
> >
> > But IvyDE will NOT attach the source if so configured.
> >
> > Gerard
> >
> > -----Original Message-----
> > From: John Gill [mailto:llignhoj@gmail.com]
> > Sent: 12 December 2007 00:18
> > To: ivy-user@incubator.apache.org
> > Subject: Re: IvyDE source artifact not recognised
> >
> > I think the problem is that is you had a package that had several jars
> > and several source jars, how would ivy know how to match them together?
> >
> > The same goes for javadoc zips/jars.
> >
> > On Dec 12, 2007 5:05 AM, Nicolas Lalevée
> > <nicolas.lalevee@anyware-tech.com
> > >
> > wrote:
> >
> > >
> > > Le 11 déc. 07 à 11:11, John Gill a écrit :
> > >
> > > > I believe that one of the limitations of ivyDE source linking is
> > > > that the names must match. You can have a different type/ext like
> > > > ".src.jar"
> > > > but
> > > > that's it. The only way I have ever got it to work is with
> > > > matching names.
> > >
> > > And I think that it is an error to have different names. Because
> > > having different names means talking about different artifact.
> > >
> > > So the ivy.xml have to look like that :
> > > <dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
> > > conf="COMPILE,RUNTIME,TEST->default">
> > > <artifact name="commons-cli" type="jar"/>
> > > <artifact name="commons-cli" type="source" ext="zip"
> > > conf="COMPILE" />
> > > </dependency>
> > >
> > > Then there is the problem with the real artifact name : commons-cli-
> > > src-1.1.zip That can be fixed easily with a proper pattern :
> > >
> > > <artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
> > > [artifact]-src-[revision].[ext]"/>
> > >
> > > Nicolas
> > >
> > >
> > > >
> > > >
> > > > On Dec 11, 2007 6:16 PM, Fernandes, Gerard
> > > > <gerard.fernandes@lehman.com
> > > > >
> > > > wrote:
> > > >
> > > >>
> > > >> IvyDE doesn't recognise source artifacts with a different name
> > > >> than the binary artifact.
> > > >>
> > > >> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
> > > >> called commons-cli-src-1.1.zip, an Ivy configuration with the
> > > >> following will resolve and the sources are downloaded (can be
> > > >> confirmed by the Ivy report as well as checking the cache) but
> > > >> will NOT attach sources in
> > > >> Eclipse:
> > > >> <dependency org="jakarta-commons-cli"
> > > >> name="commons- cli"
> > > >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > > >> <artifact name="commons-cli" type="jar"/>
> > > >> <artifact name="commons-cli-src" type="source"
> > > >> ext="zip" conf="COMPILE" />
> > > >> </dependency>
> > > >>
> > > >> Ivy settings are:
> > > >> <filesystem name="externalLibraries">
> > > >> <artifact
> > > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> > > >> [ext]"/>
> > > >> <artifact
> > > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > > >> [revision]
> > > >> .[ext]"/>
> > > >> </filesystem>
> > > >>
> > > >> The only way to make this work is to change Ivy settings to:
> > > >>
> > > >> <filesystem name="externalLibraries">
> > > >> <artifact
> > > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> > > >> [ext]"/>
> > > >> <artifact
> > > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
> > > >> [ext]"
> > > >> />
> > > >> <artifact
> > > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > > >> [revision]
> > > >> .[ext]"/>
> > > >> <artifact
> > > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > > >> [revision]
> > > >> -src.[ext]"/>
> > > >> </filesystem>
> > > >>
> > > >> And rename
> > > >> commons-cli-src-1.1.zip
> > > >> To
> > > >> commons-cli-1.1-src.zip
> > > >>
> > > >> And finally change the Ivy configuration to:
> > > >> <dependency org="jakarta-commons-cli"
> > > >> name="commons- cli"
> > > >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > > >> <artifact name="commons-cli" type="jar"/>
> > > >> <artifact name="commons-cli" type="source"
> > > >> ext="zip" conf="COMPILE" />
> > > >> </dependency>
> > > >>
> > > >>
> > > >> Gerard
> > > >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > > >> -
> > > >> - - -
> > > >> - - - - - - -
> > > >>
> > > >> This message is intended only for the personal and confidential
> > > >> use of the designated recipient(s) named above. If you are not
> > > >> the intended recipient of this message you are hereby notified
> > > >> that any review, dissemination, distribution or copying of this
> > > >> message is strictly prohibited. This communication is for
> > > >> information purposes only and should not be regarded as an offer
> > > >> to sell or as a solicitation of an offer to buy any financial
> > > >> product, an official confirmation of any transaction, or as an
> > > >> official statement of Lehman Brothers. Email transmission cannot
> > > >> be guaranteed to be secure or error-free. Therefore, we do not
> > > >> represent that this information is complete or accurate and it
> > > >> should not be relied upon as such.
> > > >> All
> > > >> information is subject to change without notice.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Regards,
> > > > John Gill
> > >
> > >
> >
> >
> > --
> > Regards,
> > John Gill
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > - -
> > - - - - - - -
> >
> > This message is intended only for the personal and confidential use of
> > the designated recipient(s) named above. If you are not the intended
> > recipient of this message you are hereby notified that any review,
> > dissemination, distribution or copying of this message is strictly
> > prohibited. This communication is for information purposes only and
> > should not be regarded as an offer to sell or as a solicitation of an
> > offer to buy any financial product, an official confirmation of any
> > transaction, or as an official statement of Lehman Brothers. Email
> > transmission cannot be guaranteed to be secure or error-free.
> > Therefore, we do not represent that this information is complete or
> > accurate and it should not be relied upon as such. All information is subject to change without notice.
> >
> >
> >
> >
>
>
> --
> Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
>
>
>
>
RE: IvyDE source artifact not recognised
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
Thank you for the reply.
How do I log an issue with IvyDE?
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: 13 December 2007 17:30
To: ivy-user@incubator.apache.org
Subject: Re: IvyDE source artifact not recognised
There are other ways to implement what you want without having to use multiple patterns. You can for instance use a custom attribute on your source artifact, and put this token in your pattern. For instance:
<artifact name="commons-cli" suffix="-src" type="source" ext="zip"
conf="COMPILE" />
${ivy.conf.dir}/[organisation]/[revision]/[artifact][suffix].[ext]
But I agree that making IvyDE more flexible by recognizing artifact name suffix for sources could make things easier to use. Feel free to open a new issue.
Xavier
On Dec 12, 2007 10:22 AM, Fernandes, Gerard <ge...@lehman.com>
wrote:
>
> It's fairly common in the Java world to have the pattern:
>
> artifact.ext for a binary and
> artifact-src.ext for it's source.
>
> All things being equal, IvyDE should be smart enough to pair a binary
> with it's source if the only difference between the name is the
> existence of "-src" in the source artifacts name.
>
> As it stands at the moment, IvyDE doesn't do that. It requires that
> the source artifact have the EXACT SAME name as the binary artifact
> with the only difference being a possibly different extension.
>
> Therefore, for IvyDE to work, one must perform the following 3 steps:
>
> (1) "commons-cli-1.1.jar" MUST have the source artifact named as "
> commons-cli-1.1-src.[jar/zip]". The original source artifact produced
> by the Commons-CLI maven build is named "commons-cli-src-1.1.zip".
>
> (2) AND, the ivysettings must be set to resolve artifacts of the
> pattern
>
> <filesystem name="externalLibraries">
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-src.[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-[revision]-src.[ext]"/>
> </filesystem>
>
>
> (3) AND, the ivy.xml MUST have the source artifact name set to exactly
> the same as the binary artifact name (Note that this is possible only
> because of the above ivysettings which in my opinion is not ideal -
> you should not have to add the "-src" bit to ivysettings)
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli" type="source"
> ext="zip" conf="COMPILE" />
> </dependency>
>
> Ideally, the ivysettings should be:
>
> <filesystem name="externalLibraries">
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> </filesystem>
>
> And the ivy configuration should look like:
>
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli-src" type="source"
> ext="zip" conf="COMPILE" />
> </dependency>
>
> But IvyDE will NOT attach the source if so configured.
>
> Gerard
>
> -----Original Message-----
> From: John Gill [mailto:llignhoj@gmail.com]
> Sent: 12 December 2007 00:18
> To: ivy-user@incubator.apache.org
> Subject: Re: IvyDE source artifact not recognised
>
> I think the problem is that is you had a package that had several jars
> and several source jars, how would ivy know how to match them together?
>
> The same goes for javadoc zips/jars.
>
> On Dec 12, 2007 5:05 AM, Nicolas Lalevée
> <nicolas.lalevee@anyware-tech.com
> >
> wrote:
>
> >
> > Le 11 déc. 07 à 11:11, John Gill a écrit :
> >
> > > I believe that one of the limitations of ivyDE source linking is
> > > that the names must match. You can have a different type/ext like
> > > ".src.jar"
> > > but
> > > that's it. The only way I have ever got it to work is with
> > > matching names.
> >
> > And I think that it is an error to have different names. Because
> > having different names means talking about different artifact.
> >
> > So the ivy.xml have to look like that :
> > <dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
> > conf="COMPILE,RUNTIME,TEST->default">
> > <artifact name="commons-cli" type="jar"/>
> > <artifact name="commons-cli" type="source" ext="zip"
> > conf="COMPILE" />
> > </dependency>
> >
> > Then there is the problem with the real artifact name : commons-cli-
> > src-1.1.zip That can be fixed easily with a proper pattern :
> >
> > <artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
> > [artifact]-src-[revision].[ext]"/>
> >
> > Nicolas
> >
> >
> > >
> > >
> > > On Dec 11, 2007 6:16 PM, Fernandes, Gerard
> > > <gerard.fernandes@lehman.com
> > > >
> > > wrote:
> > >
> > >>
> > >> IvyDE doesn't recognise source artifacts with a different name
> > >> than the binary artifact.
> > >>
> > >> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
> > >> called commons-cli-src-1.1.zip, an Ivy configuration with the
> > >> following will resolve and the sources are downloaded (can be
> > >> confirmed by the Ivy report as well as checking the cache) but
> > >> will NOT attach sources in
> > >> Eclipse:
> > >> <dependency org="jakarta-commons-cli"
> > >> name="commons- cli"
> > >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > >> <artifact name="commons-cli" type="jar"/>
> > >> <artifact name="commons-cli-src" type="source"
> > >> ext="zip" conf="COMPILE" />
> > >> </dependency>
> > >>
> > >> Ivy settings are:
> > >> <filesystem name="externalLibraries">
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> > >> [ext]"/>
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > >> [revision]
> > >> .[ext]"/>
> > >> </filesystem>
> > >>
> > >> The only way to make this work is to change Ivy settings to:
> > >>
> > >> <filesystem name="externalLibraries">
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> > >> [ext]"/>
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
> > >> [ext]"
> > >> />
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > >> [revision]
> > >> .[ext]"/>
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > >> [revision]
> > >> -src.[ext]"/>
> > >> </filesystem>
> > >>
> > >> And rename
> > >> commons-cli-src-1.1.zip
> > >> To
> > >> commons-cli-1.1-src.zip
> > >>
> > >> And finally change the Ivy configuration to:
> > >> <dependency org="jakarta-commons-cli"
> > >> name="commons- cli"
> > >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > >> <artifact name="commons-cli" type="jar"/>
> > >> <artifact name="commons-cli" type="source"
> > >> ext="zip" conf="COMPILE" />
> > >> </dependency>
> > >>
> > >>
> > >> Gerard
> > >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > >> -
> > >> - - -
> > >> - - - - - - -
> > >>
> > >> This message is intended only for the personal and confidential
> > >> use of the designated recipient(s) named above. If you are not
> > >> the intended recipient of this message you are hereby notified
> > >> that any review, dissemination, distribution or copying of this
> > >> message is strictly prohibited. This communication is for
> > >> information purposes only and should not be regarded as an offer
> > >> to sell or as a solicitation of an offer to buy any financial
> > >> product, an official confirmation of any transaction, or as an
> > >> official statement of Lehman Brothers. Email transmission cannot
> > >> be guaranteed to be secure or error-free. Therefore, we do not
> > >> represent that this information is complete or accurate and it
> > >> should not be relied upon as such.
> > >> All
> > >> information is subject to change without notice.
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > > --
> > > Regards,
> > > John Gill
> >
> >
>
>
> --
> Regards,
> John Gill
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - -
> - - - - - - -
>
> This message is intended only for the personal and confidential use of
> the designated recipient(s) named above. If you are not the intended
> recipient of this message you are hereby notified that any review,
> dissemination, distribution or copying of this message is strictly
> prohibited. This communication is for information purposes only and
> should not be regarded as an offer to sell or as a solicitation of an
> offer to buy any financial product, an official confirmation of any
> transaction, or as an official statement of Lehman Brothers. Email
> transmission cannot be guaranteed to be secure or error-free.
> Therefore, we do not represent that this information is complete or
> accurate and it should not be relied upon as such. All information is subject to change without notice.
>
>
>
>
--
Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Re: IvyDE source artifact not recognised
Posted by Xavier Hanin <xa...@gmail.com>.
There are other ways to implement what you want without having to use
multiple patterns. You can for instance use a custom attribute on your
source artifact, and put this token in your pattern. For instance:
<artifact name="commons-cli" suffix="-src" type="source" ext="zip"
conf="COMPILE" />
${ivy.conf.dir}/[organisation]/[revision]/[artifact][suffix].[ext]
But I agree that making IvyDE more flexible by recognizing artifact name
suffix for sources could make things easier to use. Feel free to open a new
issue.
Xavier
On Dec 12, 2007 10:22 AM, Fernandes, Gerard <ge...@lehman.com>
wrote:
>
> It's fairly common in the Java world to have the pattern:
>
> artifact.ext for a binary and
> artifact-src.ext for it's source.
>
> All things being equal, IvyDE should be smart enough to pair a binary with
> it's source if the only difference between the name is the existence of
> "-src" in the source artifacts name.
>
> As it stands at the moment, IvyDE doesn't do that. It requires that the
> source artifact have the EXACT SAME name as the binary artifact with the
> only difference being a possibly different extension.
>
> Therefore, for IvyDE to work, one must perform the following 3 steps:
>
> (1) "commons-cli-1.1.jar" MUST have the source artifact named as "
> commons-cli-1.1-src.[jar/zip]". The original source artifact produced by
> the Commons-CLI maven build is named "commons-cli-src-1.1.zip".
>
> (2) AND, the ivysettings must be set to resolve artifacts of the
> pattern
>
> <filesystem name="externalLibraries">
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-src.[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-[revision]-src.[ext]"/>
> </filesystem>
>
>
> (3) AND, the ivy.xml MUST have the source artifact name set to exactly
> the same as the binary artifact name (Note that this is possible only
> because of the above ivysettings which in my opinion is not ideal - you
> should not have to add the "-src" bit to ivysettings)
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli" type="source"
> ext="zip" conf="COMPILE" />
> </dependency>
>
> Ideally, the ivysettings should be:
>
> <filesystem name="externalLibraries">
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact pattern="${ivy.conf.dir
> }/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> </filesystem>
>
> And the ivy configuration should look like:
>
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli-src" type="source"
> ext="zip" conf="COMPILE" />
> </dependency>
>
> But IvyDE will NOT attach the source if so configured.
>
> Gerard
>
> -----Original Message-----
> From: John Gill [mailto:llignhoj@gmail.com]
> Sent: 12 December 2007 00:18
> To: ivy-user@incubator.apache.org
> Subject: Re: IvyDE source artifact not recognised
>
> I think the problem is that is you had a package that had several jars and
> several source jars, how would ivy know how to match them together?
>
> The same goes for javadoc zips/jars.
>
> On Dec 12, 2007 5:05 AM, Nicolas Lalevée <nicolas.lalevee@anyware-tech.com
> >
> wrote:
>
> >
> > Le 11 déc. 07 à 11:11, John Gill a écrit :
> >
> > > I believe that one of the limitations of ivyDE source linking is
> > > that the names must match. You can have a different type/ext like
> > > ".src.jar"
> > > but
> > > that's it. The only way I have ever got it to work is with matching
> > > names.
> >
> > And I think that it is an error to have different names. Because
> > having different names means talking about different artifact.
> >
> > So the ivy.xml have to look like that :
> > <dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
> > conf="COMPILE,RUNTIME,TEST->default">
> > <artifact name="commons-cli" type="jar"/>
> > <artifact name="commons-cli" type="source" ext="zip"
> > conf="COMPILE" />
> > </dependency>
> >
> > Then there is the problem with the real artifact name : commons-cli-
> > src-1.1.zip That can be fixed easily with a proper pattern :
> >
> > <artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
> > [artifact]-src-[revision].[ext]"/>
> >
> > Nicolas
> >
> >
> > >
> > >
> > > On Dec 11, 2007 6:16 PM, Fernandes, Gerard
> > > <gerard.fernandes@lehman.com
> > > >
> > > wrote:
> > >
> > >>
> > >> IvyDE doesn't recognise source artifacts with a different name than
> > >> the binary artifact.
> > >>
> > >> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
> > >> called commons-cli-src-1.1.zip, an Ivy configuration with the
> > >> following will resolve and the sources are downloaded (can be
> > >> confirmed by the Ivy report as well as checking the cache) but will
> > >> NOT attach sources in
> > >> Eclipse:
> > >> <dependency org="jakarta-commons-cli" name="commons-
> > >> cli"
> > >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > >> <artifact name="commons-cli" type="jar"/>
> > >> <artifact name="commons-cli-src" type="source"
> > >> ext="zip" conf="COMPILE" />
> > >> </dependency>
> > >>
> > >> Ivy settings are:
> > >> <filesystem name="externalLibraries">
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> > >> [ext]"/>
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > >> [revision]
> > >> .[ext]"/>
> > >> </filesystem>
> > >>
> > >> The only way to make this work is to change Ivy settings to:
> > >>
> > >> <filesystem name="externalLibraries">
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> > >> [ext]"/>
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
> > >> [ext]"
> > >> />
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > >> [revision]
> > >> .[ext]"/>
> > >> <artifact
> > >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> > >> [revision]
> > >> -src.[ext]"/>
> > >> </filesystem>
> > >>
> > >> And rename
> > >> commons-cli-src-1.1.zip
> > >> To
> > >> commons-cli-1.1-src.zip
> > >>
> > >> And finally change the Ivy configuration to:
> > >> <dependency org="jakarta-commons-cli" name="commons-
> > >> cli"
> > >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> > >> <artifact name="commons-cli" type="jar"/>
> > >> <artifact name="commons-cli" type="source"
> > >> ext="zip" conf="COMPILE" />
> > >> </dependency>
> > >>
> > >>
> > >> Gerard
> > >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > >> - - -
> > >> - - - - - - -
> > >>
> > >> This message is intended only for the personal and confidential use
> > >> of the designated recipient(s) named above. If you are not the
> > >> intended recipient of this message you are hereby notified that any
> > >> review, dissemination, distribution or copying of this message is
> > >> strictly prohibited. This communication is for information
> > >> purposes only and should not be regarded as an offer to sell or as
> > >> a solicitation of an offer to buy any financial product, an
> > >> official confirmation of any transaction, or as an official
> > >> statement of Lehman Brothers. Email transmission cannot be
> > >> guaranteed to be secure or error-free. Therefore, we do not
> > >> represent that this information is complete or accurate and it
> > >> should not be relied upon as such.
> > >> All
> > >> information is subject to change without notice.
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > > --
> > > Regards,
> > > John Gill
> >
> >
>
>
> --
> Regards,
> John Gill
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - - -
>
> This message is intended only for the personal and confidential use of the
> designated recipient(s) named above. If you are not the intended recipient
> of this message you are hereby notified that any review, dissemination,
> distribution or copying of this message is strictly prohibited. This
> communication is for information purposes only and should not be regarded as
> an offer to sell or as a solicitation of an offer to buy any financial
> product, an official confirmation of any transaction, or as an official
> statement of Lehman Brothers. Email transmission cannot be guaranteed to be
> secure or error-free. Therefore, we do not represent that this information
> is complete or accurate and it should not be relied upon as such. All
> information is subject to change without notice.
>
>
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
RE: IvyDE source artifact not recognised
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
It's fairly common in the Java world to have the pattern:
artifact.ext for a binary and
artifact-src.ext for it's source.
All things being equal, IvyDE should be smart enough to pair a binary with it's source if the only difference between the name is the existence of "-src" in the source artifacts name.
As it stands at the moment, IvyDE doesn't do that. It requires that the source artifact have the EXACT SAME name as the binary artifact with the only difference being a possibly different extension.
Therefore, for IvyDE to work, one must perform the following 3 steps:
(1) "commons-cli-1.1.jar" MUST have the source artifact named as "commons-cli-1.1-src.[jar/zip]". The original source artifact produced by the Commons-CLI maven build is named "commons-cli-src-1.1.zip".
(2) AND, the ivysettings must be set to resolve artifacts of the pattern
<filesystem name="externalLibraries">
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.[ext]"/>
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]-src.[ext]"/>
</filesystem>
(3) AND, the ivy.xml MUST have the source artifact name set to exactly the same as the binary artifact name (Note that this is possible only because of the above ivysettings which in my opinion is not ideal - you should not have to add the "-src" bit to ivysettings)
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source" ext="zip" conf="COMPILE" />
</dependency>
Ideally, the ivysettings should be:
<filesystem name="externalLibraries">
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
</filesystem>
And the ivy configuration should look like:
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli-src" type="source" ext="zip" conf="COMPILE" />
</dependency>
But IvyDE will NOT attach the source if so configured.
Gerard
-----Original Message-----
From: John Gill [mailto:llignhoj@gmail.com]
Sent: 12 December 2007 00:18
To: ivy-user@incubator.apache.org
Subject: Re: IvyDE source artifact not recognised
I think the problem is that is you had a package that had several jars and several source jars, how would ivy know how to match them together?
The same goes for javadoc zips/jars.
On Dec 12, 2007 5:05 AM, Nicolas Lalevée <ni...@anyware-tech.com>
wrote:
>
> Le 11 déc. 07 à 11:11, John Gill a écrit :
>
> > I believe that one of the limitations of ivyDE source linking is
> > that the names must match. You can have a different type/ext like
> > ".src.jar"
> > but
> > that's it. The only way I have ever got it to work is with matching
> > names.
>
> And I think that it is an error to have different names. Because
> having different names means talking about different artifact.
>
> So the ivy.xml have to look like that :
> <dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
> conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli" type="source" ext="zip"
> conf="COMPILE" />
> </dependency>
>
> Then there is the problem with the real artifact name : commons-cli-
> src-1.1.zip That can be fixed easily with a proper pattern :
>
> <artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
> [artifact]-src-[revision].[ext]"/>
>
> Nicolas
>
>
> >
> >
> > On Dec 11, 2007 6:16 PM, Fernandes, Gerard
> > <gerard.fernandes@lehman.com
> > >
> > wrote:
> >
> >>
> >> IvyDE doesn't recognise source artifacts with a different name than
> >> the binary artifact.
> >>
> >> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
> >> called commons-cli-src-1.1.zip, an Ivy configuration with the
> >> following will resolve and the sources are downloaded (can be
> >> confirmed by the Ivy report as well as checking the cache) but will
> >> NOT attach sources in
> >> Eclipse:
> >> <dependency org="jakarta-commons-cli" name="commons-
> >> cli"
> >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> >> <artifact name="commons-cli" type="jar"/>
> >> <artifact name="commons-cli-src" type="source"
> >> ext="zip" conf="COMPILE" />
> >> </dependency>
> >>
> >> Ivy settings are:
> >> <filesystem name="externalLibraries">
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> >> [ext]"/>
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> >> [revision]
> >> .[ext]"/>
> >> </filesystem>
> >>
> >> The only way to make this work is to change Ivy settings to:
> >>
> >> <filesystem name="externalLibraries">
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> >> [ext]"/>
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
> >> [ext]"
> >> />
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> >> [revision]
> >> .[ext]"/>
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> >> [revision]
> >> -src.[ext]"/>
> >> </filesystem>
> >>
> >> And rename
> >> commons-cli-src-1.1.zip
> >> To
> >> commons-cli-1.1-src.zip
> >>
> >> And finally change the Ivy configuration to:
> >> <dependency org="jakarta-commons-cli" name="commons-
> >> cli"
> >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> >> <artifact name="commons-cli" type="jar"/>
> >> <artifact name="commons-cli" type="source"
> >> ext="zip" conf="COMPILE" />
> >> </dependency>
> >>
> >>
> >> Gerard
> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> - - -
> >> - - - - - - -
> >>
> >> This message is intended only for the personal and confidential use
> >> of the designated recipient(s) named above. If you are not the
> >> intended recipient of this message you are hereby notified that any
> >> review, dissemination, distribution or copying of this message is
> >> strictly prohibited. This communication is for information
> >> purposes only and should not be regarded as an offer to sell or as
> >> a solicitation of an offer to buy any financial product, an
> >> official confirmation of any transaction, or as an official
> >> statement of Lehman Brothers. Email transmission cannot be
> >> guaranteed to be secure or error-free. Therefore, we do not
> >> represent that this information is complete or accurate and it
> >> should not be relied upon as such.
> >> All
> >> information is subject to change without notice.
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Regards,
> > John Gill
>
>
--
Regards,
John Gill
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Re: IvyDE source artifact not recognised
Posted by John Gill <ll...@gmail.com>.
I think the problem is that is you had a package that had several jars and
several source jars, how would ivy know how to match them together?
The same goes for javadoc zips/jars.
On Dec 12, 2007 5:05 AM, Nicolas Lalevée <ni...@anyware-tech.com>
wrote:
>
> Le 11 déc. 07 à 11:11, John Gill a écrit :
>
> > I believe that one of the limitations of ivyDE source linking is
> > that the
> > names must match. You can have a different type/ext like ".src.jar"
> > but
> > that's it. The only way I have ever got it to work is with matching
> > names.
>
> And I think that it is an error to have different names. Because
> having different names means talking about different artifact.
>
> So the ivy.xml have to look like that :
> <dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
> conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli" type="source" ext="zip"
> conf="COMPILE" />
> </dependency>
>
> Then there is the problem with the real artifact name : commons-cli-
> src-1.1.zip
> That can be fixed easily with a proper pattern :
>
> <artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
> [artifact]-src-[revision].[ext]"/>
>
> Nicolas
>
>
> >
> >
> > On Dec 11, 2007 6:16 PM, Fernandes, Gerard <gerard.fernandes@lehman.com
> > >
> > wrote:
> >
> >>
> >> IvyDE doesn't recognise source artifacts with a different name than
> >> the
> >> binary artifact.
> >>
> >> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
> >> called
> >> commons-cli-src-1.1.zip, an Ivy configuration with the following will
> >> resolve and the sources are downloaded (can be confirmed by the Ivy
> >> report as well as checking the cache) but will NOT attach sources in
> >> Eclipse:
> >> <dependency org="jakarta-commons-cli" name="commons-
> >> cli"
> >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> >> <artifact name="commons-cli" type="jar"/>
> >> <artifact name="commons-cli-src" type="source"
> >> ext="zip" conf="COMPILE" />
> >> </dependency>
> >>
> >> Ivy settings are:
> >> <filesystem name="externalLibraries">
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> >> [ext]"/>
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> >> [revision]
> >> .[ext]"/>
> >> </filesystem>
> >>
> >> The only way to make this work is to change Ivy settings to:
> >>
> >> <filesystem name="externalLibraries">
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
> >> [ext]"/>
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
> >> [ext]"
> >> />
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> >> [revision]
> >> .[ext]"/>
> >> <artifact
> >> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
> >> [revision]
> >> -src.[ext]"/>
> >> </filesystem>
> >>
> >> And rename
> >> commons-cli-src-1.1.zip
> >> To
> >> commons-cli-1.1-src.zip
> >>
> >> And finally change the Ivy configuration to:
> >> <dependency org="jakarta-commons-cli" name="commons-
> >> cli"
> >> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> >> <artifact name="commons-cli" type="jar"/>
> >> <artifact name="commons-cli" type="source"
> >> ext="zip" conf="COMPILE" />
> >> </dependency>
> >>
> >>
> >> Gerard
> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> - - -
> >> - - - - - - -
> >>
> >> This message is intended only for the personal and confidential use
> >> of the
> >> designated recipient(s) named above. If you are not the intended
> >> recipient
> >> of this message you are hereby notified that any review,
> >> dissemination,
> >> distribution or copying of this message is strictly prohibited. This
> >> communication is for information purposes only and should not be
> >> regarded as
> >> an offer to sell or as a solicitation of an offer to buy any
> >> financial
> >> product, an official confirmation of any transaction, or as an
> >> official
> >> statement of Lehman Brothers. Email transmission cannot be
> >> guaranteed to be
> >> secure or error-free. Therefore, we do not represent that this
> >> information
> >> is complete or accurate and it should not be relied upon as such.
> >> All
> >> information is subject to change without notice.
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Regards,
> > John Gill
>
>
--
Regards,
John Gill
Re: IvyDE source artifact not recognised
Posted by Nicolas Lalevée <ni...@anyware-tech.com>.
Le 11 déc. 07 à 11:11, John Gill a écrit :
> I believe that one of the limitations of ivyDE source linking is
> that the
> names must match. You can have a different type/ext like ".src.jar"
> but
> that's it. The only way I have ever got it to work is with matching
> names.
And I think that it is an error to have different names. Because
having different names means talking about different artifact.
So the ivy.xml have to look like that :
<dependency org="jakarta-commons-cli" name="commons-cli" rev="1.1"
conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source" ext="zip"
conf="COMPILE" />
</dependency>
Then there is the problem with the real artifact name : commons-cli-
src-1.1.zip
That can be fixed easily with a proper pattern :
<artifact pattern="${ivy.conf.dir}/[organisation]/[revision]/
[artifact]-src-[revision].[ext]"/>
Nicolas
>
>
> On Dec 11, 2007 6:16 PM, Fernandes, Gerard <gerard.fernandes@lehman.com
> >
> wrote:
>
>>
>> IvyDE doesn't recognise source artifacts with a different name than
>> the
>> binary artifact.
>>
>> E.g., If I have a JAR called commons-cli-1.1.jar and it's source
>> called
>> commons-cli-src-1.1.zip, an Ivy configuration with the following will
>> resolve and the sources are downloaded (can be confirmed by the Ivy
>> report as well as checking the cache) but will NOT attach sources in
>> Eclipse:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli-src" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>> Ivy settings are:
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> </filesystem>
>>
>> The only way to make this work is to change Ivy settings to:
>>
>> <filesystem name="externalLibraries">
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].
>> [ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.
>> [ext]"
>> />
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> .[ext]"/>
>> <artifact
>> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-
>> [revision]
>> -src.[ext]"/>
>> </filesystem>
>>
>> And rename
>> commons-cli-src-1.1.zip
>> To
>> commons-cli-1.1-src.zip
>>
>> And finally change the Ivy configuration to:
>> <dependency org="jakarta-commons-cli" name="commons-
>> cli"
>> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
>> <artifact name="commons-cli" type="jar"/>
>> <artifact name="commons-cli" type="source"
>> ext="zip" conf="COMPILE" />
>> </dependency>
>>
>>
>> Gerard
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - - -
>> - - - - - - -
>>
>> This message is intended only for the personal and confidential use
>> of the
>> designated recipient(s) named above. If you are not the intended
>> recipient
>> of this message you are hereby notified that any review,
>> dissemination,
>> distribution or copying of this message is strictly prohibited. This
>> communication is for information purposes only and should not be
>> regarded as
>> an offer to sell or as a solicitation of an offer to buy any
>> financial
>> product, an official confirmation of any transaction, or as an
>> official
>> statement of Lehman Brothers. Email transmission cannot be
>> guaranteed to be
>> secure or error-free. Therefore, we do not represent that this
>> information
>> is complete or accurate and it should not be relied upon as such.
>> All
>> information is subject to change without notice.
>>
>>
>>
>>
>
>
> --
> Regards,
> John Gill
Re: IvyDE source artifact not recognised
Posted by John Gill <ll...@gmail.com>.
I believe that one of the limitations of ivyDE source linking is that the
names must match. You can have a different type/ext like ".src.jar" but
that's it. The only way I have ever got it to work is with matching names.
On Dec 11, 2007 6:16 PM, Fernandes, Gerard <ge...@lehman.com>
wrote:
>
> IvyDE doesn't recognise source artifacts with a different name than the
> binary artifact.
>
> E.g., If I have a JAR called commons-cli-1.1.jar and it's source called
> commons-cli-src-1.1.zip, an Ivy configuration with the following will
> resolve and the sources are downloaded (can be confirmed by the Ivy
> report as well as checking the cache) but will NOT attach sources in
> Eclipse:
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli-src" type="source"
> ext="zip" conf="COMPILE" />
> </dependency>
>
> Ivy settings are:
> <filesystem name="externalLibraries">
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]
> .[ext]"/>
> </filesystem>
>
> The only way to make this work is to change Ivy settings to:
>
> <filesystem name="externalLibraries">
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.[ext]"
> />
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]
> .[ext]"/>
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]
> -src.[ext]"/>
> </filesystem>
>
> And rename
> commons-cli-src-1.1.zip
> To
> commons-cli-1.1-src.zip
>
> And finally change the Ivy configuration to:
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli" type="source"
> ext="zip" conf="COMPILE" />
> </dependency>
>
>
> Gerard
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - - -
>
> This message is intended only for the personal and confidential use of the
> designated recipient(s) named above. If you are not the intended recipient
> of this message you are hereby notified that any review, dissemination,
> distribution or copying of this message is strictly prohibited. This
> communication is for information purposes only and should not be regarded as
> an offer to sell or as a solicitation of an offer to buy any financial
> product, an official confirmation of any transaction, or as an official
> statement of Lehman Brothers. Email transmission cannot be guaranteed to be
> secure or error-free. Therefore, we do not represent that this information
> is complete or accurate and it should not be relied upon as such. All
> information is subject to change without notice.
>
>
>
>
--
Regards,
John Gill
IvyDE source artifact not recognised
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
IvyDE doesn't recognise source artifacts with a different name than the
binary artifact.
E.g., If I have a JAR called commons-cli-1.1.jar and it's source called
commons-cli-src-1.1.zip, an Ivy configuration with the following will
resolve and the sources are downloaded (can be confirmed by the Ivy
report as well as checking the cache) but will NOT attach sources in
Eclipse:
<dependency org="jakarta-commons-cli" name="commons-cli"
rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli-src" type="source"
ext="zip" conf="COMPILE" />
</dependency>
Ivy settings are:
<filesystem name="externalLibraries">
<artifact
pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
<artifact
pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]
.[ext]"/>
</filesystem>
The only way to make this work is to change Ivy settings to:
<filesystem name="externalLibraries">
<artifact
pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
<artifact
pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.[ext]"
/>
<artifact
pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]
.[ext]"/>
<artifact
pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]
-src.[ext]"/>
</filesystem>
And rename
commons-cli-src-1.1.zip
To
commons-cli-1.1-src.zip
And finally change the Ivy configuration to:
<dependency org="jakarta-commons-cli" name="commons-cli"
rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
<artifact name="commons-cli" type="jar"/>
<artifact name="commons-cli" type="source"
ext="zip" conf="COMPILE" />
</dependency>
Gerard
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Re: Using Extra Attributes
Posted by Xavier Hanin <xa...@gmail.com>.
On 10/7/07, John Gill <ll...@gmail.com> wrote:
>
> Sounds like there is never going to be a 1.4.2 release of ivy, even though
> in JIRA there is an ivy 1.4.2 release. Maybe the issues against 1.4.2should
> be moved to a 2.0xxx release.
The problem is that there will never be an Apache 1.4.2 version. If the
community wants a 1.4.2 version, the community will have to work on it and
release it. Jayasoft, as the copyright owner of the 1.4.1 version, is not
opposed to this, but can't engage any work in this direction. And we, the
Ivy team, are concentrated on the 2.0 version. So I agree it's likely that
there will never be a 1.4.2 version.
For the issue tracking, all issues raised with a fix for 1.4.2 have also a
fixed version on the 2.x stream. So I see no problem to have some issues for
the 1.4.2 version, just in case the community finally takes the task to
release a 1.4.2 version.
And Nascif, I understand your concern about 2.0 alpha. The situation for the
moment is very special and due to the migration to the ASF. We should make
an ASF final release asap to avoid this kind of trouble in choosing the
version to use (latest stable but almost unsupported or latest ASF version
but still not stable). I hope we will have enough time and energy to meet
some of our objectives in this area.
Xavier
On 10/7/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> >
> > I am using 1.4.1 because it is the stable version. It would be easier
> > for our team to fix bugs and provide patches against the beta once it is
> > released. Unfortunately this is for production and consumed by a really
> > large number of developers in our corporation, and management just
> > doesn't like the sound of "alpha"...
> >
> > I will add the unit test to a jira entry.
> >
> > Thanks,
> > Nascif
> >
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Saturday, October 06, 2007 11:18 AM
> > To: ivy-user@incubator.apache.org
> > Subject: Re: Using Extra Attributes
> >
> > On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> > >
> > > Thanks for the explanation. Perhaps some clarification that using
> > extra
> > > attributes require that you use the attribute as part of the pattern
> > if
> > > they are to be used to resolve dynamic versions should be added to the
> > > web site.
> >
> >
> > Indeed, extra attributes would deserve some more documentation. Maybe a
> > tutorial, or a follow up to another tutorial... Since you have worked in
> > this direction, maybe you could contribute something in this area?
> >
> >
> > This is all I found in
> > > http://incubator.apache.org/ivy/history/trunk/concept.html#extra
> > >
> > > Then you can use the extra attribute when you declare a dependency on
> > > foo:
> > > <dependency org="apache" name="foo" color="blue" rev="1.5+" />
> > >
> > > And since "1.5+" is a dynamic version I got the impression thar color
> > > could be used to influence how it would be resolved.
> >
> >
> > It should be possible if you use the color in your pattern.
> >
> > Anyway I tried to create a unit test to validate my use case:
> > > public void testExtraAttributesWithLatestInPattern() throws
> > > Exception {
> > > Ivy ivy = new Ivy();
> > > ivy.configure(new
> > >
> > File("test/repositories/extra-attributes-multiple-versions/ivyconf.xml")
> > > );
> > >
> > > // without extra attribute in pattern
> > > //ResolveReport report =
> > >
> > ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-no-patte
> > > rn.xml"),
> > >
> > > //with extra attribute in pattern
> > > ResolveReport report =
> > >
> > ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-in-patte
> > > rn.xml"),
> > > null, new String[] {"*"}, _cache, null, false);
> > > assertFalse(report.hasError());
> > >
> > > assertTrue(new File(_cache,
> > > "jayasoft/mymodule/task1/1854/ivy.xml").exists());
> > > assertTrue(new File(_cache,
> > > "jayasoft/mymodule/task1/1854/mymodule-windows.jar").exists());
> > > assertTrue(new File(_cache,
> > > "jayasoft/mymodule/task1/1854/mymodule-linux.jar").exists());
> > > }
> > >
> > > Where mymodule has also another version, 2854 with eatt == task2, and
> > > where I use "eatt" in the pattern as in the original test case. The
> > > result was not much better:
> > >
> > > <testcase classname="fr.jayasoft.ivy.ResolveTest"
> > > name="testExtraAttributesWithLatestInPattern" time="0.031">
> > > <error
> > > type="java.lang.NullPointerException">java.lang.NullPointerException
> > > at
> > >
> > fr.jayasoft.ivy.repository.url.URLResource.getName(URLResource.java:30)
> > > at
> > >
> > fr.jayasoft.ivy.external.m2.PomModuleDescriptorParser.accept(PomModuleDe
> > > scriptorParser.java:262)
> > > at
> > >
> > fr.jayasoft.ivy.parser.ModuleDescriptorParserRegistry.getParser(ModuleDe
> > > scriptorParserRegistry.java:58)
> > > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1083)
> > > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1071)
> > > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1068)
> > > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1025)
> > > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1022)
> > > at
> > >
> > fr.jayasoft.ivy.ResolveTest.testExtraAttributesWithLatestInPattern(Resol
> > > veTest.java:2595)
> >
> >
> > Could you open an issue and provide your unit test as a patch? It would
> > be
> > easier for us to see exactly what you are testing, and to include the
> > test
> > if it is relevant. BTW, it seems you are using 1.4, a patch against
> > current
> > trunk would be more appreciated :-)
> >
> > Xavier
> >
> > I think I found another way to implement my needs though.
> > > Thanks,
> > > Nascif
> > >
> > > -----Original Message-----
> > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > Sent: Friday, October 05, 2007 1:01 PM
> > > To: ivy-user@incubator.apache.org
> > > Subject: Re: Using Extra Attributes
> > >
> > > On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> > > >
> > > > I apologise, I should have included the snippets in the first
> > e-mail.
> > > >
> > > > I am testing this by making changes to the multi-project example.
> > > > So I tweaked ivy.xml and published the following revisions of the
> > > > "version" project (below are snippets for each version's published
> > > > ivy.xml in the repository):
> > > >
> > > > <ivy-module version="1.0">
> > > > <info organisation="jayasoft" module="version" revision="7"
> > > > status="release" publication="20071004180756" week="41"/>
> > > >
> > > > <ivy-module version="1.0">
> > > > <info organisation="jayasoft" module="version" revision="8"
> > > > status="release" publication="20071004180824" week="42"/>
> > > >
> > > > <ivy-module version="1.0">
> > > > <info organisation="jayasoft" module="version" revision="9"
> > > > status="integration" publication="20071004180848"/>
> > > >
> > > > The in the consumer project "list", I changed the dependency to
> > read:
> > > > <dependency name="version" rev="latest.release" conf="core"
> > > > week="41"/>
> > > >
> > > > and executed "ant resolve" with a clean cache. From the logs I can
> > see
> > > > that Ivy goes over all the versions
> > > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > > matcher
> > > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > > version | latest.release ] parsed=[ jayasoft | version | 7 ]
> > > >
> > > >
> > > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > > matcher
> > > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > > version | latest.release ] parsed=[ jayasoft | version | 8 ]
> > > >
> > > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > > matcher
> > > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> > > >
> > > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > > matcher
> > > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> > > >
> > > > After reading all the revisions in the repository, Ivy decides to
> > ask
> > > > for the revision "8" jar file.
> > > >
> > > > [ivy:retrieve] listing all in
> > > >
> > >
> > C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > > ayasoft/version/ivy-[revision].xml
> > > > [ivy:retrieve] using tpj to list all in
> > > >
> > >
> > C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > > > ayasoft/version
> > > > [ivy:retrieve] tpj: unable to list resources for [ jayasoft |
> > version
> > > |
> > > > latest.release ]:
> > > >
> > >
> > pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > > > ../tpj/[organisation]/[module]/ivy-[revision].[ext]
> > > > [ivy:retrieve] trying
> > > >
> > >
> > C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > > ayasoft/version/jars/version-latest.release.jar
> > > > [ivy:retrieve] listing all in
> > > >
> > >
> > C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > > ayasoft/version/jars/version-[revision].jar
> > > > [ivy:retrieve] using tpj to list all in
> > > >
> > >
> > C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > > > ayasoft/version/jars
> > > > [ivy:retrieve] tpj: unable to list resources for [ jayasoft |
> > version
> > > |
> > > > latest.release ]:
> > > >
> > >
> > pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > > > ../tpj/[organisation]/[module]/jars/[artifact]-[revision].[ext]
> > > > [ivy:retrieve] tpj: no ivy file nor artifact found for [ jayasoft |
> > > > version | latest.release ]
> > > > [ivy:retrieve] tried
> > > >
> > >
> > C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > > ayasoft/version/ivy-latest.release.xml
> > > > [ivy:retrieve] tried
> > > >
> > >
> > C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > > ayasoft/version/ivy-[any release].xml
> > > > [ivy:retrieve] tried
> > > >
> > >
> > C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > > ayasoft/version/jars/version-latest.release.jar
> > > > [ivy:retrieve] found [ jayasoft | version | 8 ] in shared
> > > > [ivy:retrieve] [8] [ jayasoft | version | latest.release ]
> > > >
> > > > I would think it should ask for revision "7" since it is the one
> > with
> > > > the "week=41" attribute.
> > >
> > >
> > > Ok, let's say that this is a limitation of what you can do with extra
> > > attributes. With most of the version matchers Ivy tries to avoid to
> > > read
> > > the module descriptor to know if a version match or not. In your case
> > > you
> > > use a version constraint which needs to load the ivy files, but Ivy do
> > > not
> > > take advantage of this to filter the extra attributes. This could be
> > > changed, but then it would be strange that when you use
> > > latest.integration(which do not require module descriptor loading),
> > > Ivy wouldn't take care of
> > > the extra attribute. Loading module descriptors systematically as soon
> > > as
> > > you use extra attributes is not a good idea either: may users use
> > extra
> > > attributes without this need.
> > >
> > > So, what's the solution? You need to add your extra attribute in your
> > > pattern, so that Ivy can know the value of the extra attribute
> > depending
> > > on
> > > the ivy file location only, and not its content. Then your
> > > latest.releasewith your "week" extra attribute should work properly.
> > >
> > > On a related question, can I use the "publication" attribute to
> > retrieve
> > > > a dependency?
> > >
> > >
> > > Do you mean as a constraint on the dependency you select? Out of the
> > box
> > > you
> > > can't, but maybe you can write a custom VersionMatcher for that. But
> > you
> > > will need to parse the module descriptor to do so, which can be quite
> > > expensive.
> > >
> > > Xavier
> > >
> > > Thanks,
> > > > Nascif
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > > Sent: Friday, October 05, 2007 3:21 AM
> > > > To: ivy-user@incubator.apache.org
> > > > Subject: Re: Using Extra Attributes
> > > >
> > > > On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com>
> > wrote:
> > > > >
> > > > > I can't get extra attributes to work in 1.4.1, is this really
> > > > supported?
> > > > > I am looking at the functionality described in
> > > > > http://incubator.apache.org/ivy/history/1.4.html
> > > > > Under "Core features"
> > > > >
> > > > > and I tried a lot of combinations with extra attribute. I can see
> > > them
> > > > > in the published ivy.xml, but there is no way that I can use them
> > to
> > > > > influence the result of my retrieve as suggested in the examples.
> > > > >
> > > > > Is anybody using this feature?
> > > >
> > > >
> > > > I have in the past, and we have some unit tests checking it's
> > working,
> > > > so
> > > > I'd be surprised if it doesn't work at all. Could you provide some
> > > > snippets
> > > > of what you do and what you expect?
> > > >
> > > > Xavier
> > > >
> > > > Thanks,
> > > > > Nascif
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Xavier Hanin - Independent Java Consultant
> > > > http://xhab.blogspot.com/
> > > > http://incubator.apache.org/ivy/
> > > > http://www.xoocode.org/
> > > >
> > >
> > >
> > >
> > > --
> > > Xavier Hanin - Independent Java Consultant
> > > http://xhab.blogspot.com/
> > > http://incubator.apache.org/ivy/
> > > http://www.xoocode.org/
> > >
> >
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://incubator.apache.org/ivy/
> > http://www.xoocode.org/
> >
>
>
>
> --
> Regards,
> John Gill
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: Using Extra Attributes
Posted by John Gill <ll...@gmail.com>.
Sounds like there is never going to be a 1.4.2 release of ivy, even though
in JIRA there is an ivy 1.4.2 release. Maybe the issues against 1.4.2 should
be moved to a 2.0xxx release.
On 10/7/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
>
> I am using 1.4.1 because it is the stable version. It would be easier
> for our team to fix bugs and provide patches against the beta once it is
> released. Unfortunately this is for production and consumed by a really
> large number of developers in our corporation, and management just
> doesn't like the sound of "alpha"...
>
> I will add the unit test to a jira entry.
>
> Thanks,
> Nascif
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Saturday, October 06, 2007 11:18 AM
> To: ivy-user@incubator.apache.org
> Subject: Re: Using Extra Attributes
>
> On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> >
> > Thanks for the explanation. Perhaps some clarification that using
> extra
> > attributes require that you use the attribute as part of the pattern
> if
> > they are to be used to resolve dynamic versions should be added to the
> > web site.
>
>
> Indeed, extra attributes would deserve some more documentation. Maybe a
> tutorial, or a follow up to another tutorial... Since you have worked in
> this direction, maybe you could contribute something in this area?
>
>
> This is all I found in
> > http://incubator.apache.org/ivy/history/trunk/concept.html#extra
> >
> > Then you can use the extra attribute when you declare a dependency on
> > foo:
> > <dependency org="apache" name="foo" color="blue" rev="1.5+" />
> >
> > And since "1.5+" is a dynamic version I got the impression thar color
> > could be used to influence how it would be resolved.
>
>
> It should be possible if you use the color in your pattern.
>
> Anyway I tried to create a unit test to validate my use case:
> > public void testExtraAttributesWithLatestInPattern() throws
> > Exception {
> > Ivy ivy = new Ivy();
> > ivy.configure(new
> >
> File("test/repositories/extra-attributes-multiple-versions/ivyconf.xml")
> > );
> >
> > // without extra attribute in pattern
> > //ResolveReport report =
> >
> ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-no-patte
> > rn.xml"),
> >
> > //with extra attribute in pattern
> > ResolveReport report =
> >
> ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-in-patte
> > rn.xml"),
> > null, new String[] {"*"}, _cache, null, false);
> > assertFalse(report.hasError());
> >
> > assertTrue(new File(_cache,
> > "jayasoft/mymodule/task1/1854/ivy.xml").exists());
> > assertTrue(new File(_cache,
> > "jayasoft/mymodule/task1/1854/mymodule-windows.jar").exists());
> > assertTrue(new File(_cache,
> > "jayasoft/mymodule/task1/1854/mymodule-linux.jar").exists());
> > }
> >
> > Where mymodule has also another version, 2854 with eatt == task2, and
> > where I use "eatt" in the pattern as in the original test case. The
> > result was not much better:
> >
> > <testcase classname="fr.jayasoft.ivy.ResolveTest"
> > name="testExtraAttributesWithLatestInPattern" time="0.031">
> > <error
> > type="java.lang.NullPointerException">java.lang.NullPointerException
> > at
> >
> fr.jayasoft.ivy.repository.url.URLResource.getName(URLResource.java:30)
> > at
> >
> fr.jayasoft.ivy.external.m2.PomModuleDescriptorParser.accept(PomModuleDe
> > scriptorParser.java:262)
> > at
> >
> fr.jayasoft.ivy.parser.ModuleDescriptorParserRegistry.getParser(ModuleDe
> > scriptorParserRegistry.java:58)
> > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1083)
> > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1071)
> > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1068)
> > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1025)
> > at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1022)
> > at
> >
> fr.jayasoft.ivy.ResolveTest.testExtraAttributesWithLatestInPattern(Resol
> > veTest.java:2595)
>
>
> Could you open an issue and provide your unit test as a patch? It would
> be
> easier for us to see exactly what you are testing, and to include the
> test
> if it is relevant. BTW, it seems you are using 1.4, a patch against
> current
> trunk would be more appreciated :-)
>
> Xavier
>
> I think I found another way to implement my needs though.
> > Thanks,
> > Nascif
> >
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Friday, October 05, 2007 1:01 PM
> > To: ivy-user@incubator.apache.org
> > Subject: Re: Using Extra Attributes
> >
> > On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> > >
> > > I apologise, I should have included the snippets in the first
> e-mail.
> > >
> > > I am testing this by making changes to the multi-project example.
> > > So I tweaked ivy.xml and published the following revisions of the
> > > "version" project (below are snippets for each version's published
> > > ivy.xml in the repository):
> > >
> > > <ivy-module version="1.0">
> > > <info organisation="jayasoft" module="version" revision="7"
> > > status="release" publication="20071004180756" week="41"/>
> > >
> > > <ivy-module version="1.0">
> > > <info organisation="jayasoft" module="version" revision="8"
> > > status="release" publication="20071004180824" week="42"/>
> > >
> > > <ivy-module version="1.0">
> > > <info organisation="jayasoft" module="version" revision="9"
> > > status="integration" publication="20071004180848"/>
> > >
> > > The in the consumer project "list", I changed the dependency to
> read:
> > > <dependency name="version" rev="latest.release" conf="core"
> > > week="41"/>
> > >
> > > and executed "ant resolve" with a clean cache. From the logs I can
> see
> > > that Ivy goes over all the versions
> > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > matcher
> > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > version | latest.release ] parsed=[ jayasoft | version | 7 ]
> > >
> > >
> > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > matcher
> > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > version | latest.release ] parsed=[ jayasoft | version | 8 ]
> > >
> > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > matcher
> > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> > >
> > > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> > matcher
> > > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> > >
> > > After reading all the revisions in the repository, Ivy decides to
> ask
> > > for the revision "8" jar file.
> > >
> > > [ivy:retrieve] listing all in
> > >
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > ayasoft/version/ivy-[revision].xml
> > > [ivy:retrieve] using tpj to list all in
> > >
> >
> C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > > ayasoft/version
> > > [ivy:retrieve] tpj: unable to list resources for [ jayasoft |
> version
> > |
> > > latest.release ]:
> > >
> >
> pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > > ../tpj/[organisation]/[module]/ivy-[revision].[ext]
> > > [ivy:retrieve] trying
> > >
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > ayasoft/version/jars/version-latest.release.jar
> > > [ivy:retrieve] listing all in
> > >
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > ayasoft/version/jars/version-[revision].jar
> > > [ivy:retrieve] using tpj to list all in
> > >
> >
> C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > > ayasoft/version/jars
> > > [ivy:retrieve] tpj: unable to list resources for [ jayasoft |
> version
> > |
> > > latest.release ]:
> > >
> >
> pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > > ../tpj/[organisation]/[module]/jars/[artifact]-[revision].[ext]
> > > [ivy:retrieve] tpj: no ivy file nor artifact found for [ jayasoft |
> > > version | latest.release ]
> > > [ivy:retrieve] tried
> > >
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > ayasoft/version/ivy-latest.release.xml
> > > [ivy:retrieve] tried
> > >
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > ayasoft/version/ivy-[any release].xml
> > > [ivy:retrieve] tried
> > >
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > > ayasoft/version/jars/version-latest.release.jar
> > > [ivy:retrieve] found [ jayasoft | version | 8 ] in shared
> > > [ivy:retrieve] [8] [ jayasoft | version | latest.release ]
> > >
> > > I would think it should ask for revision "7" since it is the one
> with
> > > the "week=41" attribute.
> >
> >
> > Ok, let's say that this is a limitation of what you can do with extra
> > attributes. With most of the version matchers Ivy tries to avoid to
> > read
> > the module descriptor to know if a version match or not. In your case
> > you
> > use a version constraint which needs to load the ivy files, but Ivy do
> > not
> > take advantage of this to filter the extra attributes. This could be
> > changed, but then it would be strange that when you use
> > latest.integration(which do not require module descriptor loading),
> > Ivy wouldn't take care of
> > the extra attribute. Loading module descriptors systematically as soon
> > as
> > you use extra attributes is not a good idea either: may users use
> extra
> > attributes without this need.
> >
> > So, what's the solution? You need to add your extra attribute in your
> > pattern, so that Ivy can know the value of the extra attribute
> depending
> > on
> > the ivy file location only, and not its content. Then your
> > latest.releasewith your "week" extra attribute should work properly.
> >
> > On a related question, can I use the "publication" attribute to
> retrieve
> > > a dependency?
> >
> >
> > Do you mean as a constraint on the dependency you select? Out of the
> box
> > you
> > can't, but maybe you can write a custom VersionMatcher for that. But
> you
> > will need to parse the module descriptor to do so, which can be quite
> > expensive.
> >
> > Xavier
> >
> > Thanks,
> > > Nascif
> > >
> > >
> > > -----Original Message-----
> > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > Sent: Friday, October 05, 2007 3:21 AM
> > > To: ivy-user@incubator.apache.org
> > > Subject: Re: Using Extra Attributes
> > >
> > > On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com>
> wrote:
> > > >
> > > > I can't get extra attributes to work in 1.4.1, is this really
> > > supported?
> > > > I am looking at the functionality described in
> > > > http://incubator.apache.org/ivy/history/1.4.html
> > > > Under "Core features"
> > > >
> > > > and I tried a lot of combinations with extra attribute. I can see
> > them
> > > > in the published ivy.xml, but there is no way that I can use them
> to
> > > > influence the result of my retrieve as suggested in the examples.
> > > >
> > > > Is anybody using this feature?
> > >
> > >
> > > I have in the past, and we have some unit tests checking it's
> working,
> > > so
> > > I'd be surprised if it doesn't work at all. Could you provide some
> > > snippets
> > > of what you do and what you expect?
> > >
> > > Xavier
> > >
> > > Thanks,
> > > > Nascif
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Xavier Hanin - Independent Java Consultant
> > > http://xhab.blogspot.com/
> > > http://incubator.apache.org/ivy/
> > > http://www.xoocode.org/
> > >
> >
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://incubator.apache.org/ivy/
> > http://www.xoocode.org/
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>
--
Regards,
John Gill
RE: Using Extra Attributes
Posted by Nascif Abousalh-Neto <Na...@sas.com>.
I am using 1.4.1 because it is the stable version. It would be easier
for our team to fix bugs and provide patches against the beta once it is
released. Unfortunately this is for production and consumed by a really
large number of developers in our corporation, and management just
doesn't like the sound of "alpha"...
I will add the unit test to a jira entry.
Thanks,
Nascif
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: Saturday, October 06, 2007 11:18 AM
To: ivy-user@incubator.apache.org
Subject: Re: Using Extra Attributes
On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
>
> Thanks for the explanation. Perhaps some clarification that using
extra
> attributes require that you use the attribute as part of the pattern
if
> they are to be used to resolve dynamic versions should be added to the
> web site.
Indeed, extra attributes would deserve some more documentation. Maybe a
tutorial, or a follow up to another tutorial... Since you have worked in
this direction, maybe you could contribute something in this area?
This is all I found in
> http://incubator.apache.org/ivy/history/trunk/concept.html#extra
>
> Then you can use the extra attribute when you declare a dependency on
> foo:
> <dependency org="apache" name="foo" color="blue" rev="1.5+" />
>
> And since "1.5+" is a dynamic version I got the impression thar color
> could be used to influence how it would be resolved.
It should be possible if you use the color in your pattern.
Anyway I tried to create a unit test to validate my use case:
> public void testExtraAttributesWithLatestInPattern() throws
> Exception {
> Ivy ivy = new Ivy();
> ivy.configure(new
>
File("test/repositories/extra-attributes-multiple-versions/ivyconf.xml")
> );
>
> // without extra attribute in pattern
> //ResolveReport report =
>
ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-no-patte
> rn.xml"),
>
> //with extra attribute in pattern
> ResolveReport report =
>
ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-in-patte
> rn.xml"),
> null, new String[] {"*"}, _cache, null, false);
> assertFalse(report.hasError());
>
> assertTrue(new File(_cache,
> "jayasoft/mymodule/task1/1854/ivy.xml").exists());
> assertTrue(new File(_cache,
> "jayasoft/mymodule/task1/1854/mymodule-windows.jar").exists());
> assertTrue(new File(_cache,
> "jayasoft/mymodule/task1/1854/mymodule-linux.jar").exists());
> }
>
> Where mymodule has also another version, 2854 with eatt == task2, and
> where I use "eatt" in the pattern as in the original test case. The
> result was not much better:
>
> <testcase classname="fr.jayasoft.ivy.ResolveTest"
> name="testExtraAttributesWithLatestInPattern" time="0.031">
> <error
> type="java.lang.NullPointerException">java.lang.NullPointerException
> at
>
fr.jayasoft.ivy.repository.url.URLResource.getName(URLResource.java:30)
> at
>
fr.jayasoft.ivy.external.m2.PomModuleDescriptorParser.accept(PomModuleDe
> scriptorParser.java:262)
> at
>
fr.jayasoft.ivy.parser.ModuleDescriptorParserRegistry.getParser(ModuleDe
> scriptorParserRegistry.java:58)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1083)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1071)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1068)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1025)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1022)
> at
>
fr.jayasoft.ivy.ResolveTest.testExtraAttributesWithLatestInPattern(Resol
> veTest.java:2595)
Could you open an issue and provide your unit test as a patch? It would
be
easier for us to see exactly what you are testing, and to include the
test
if it is relevant. BTW, it seems you are using 1.4, a patch against
current
trunk would be more appreciated :-)
Xavier
I think I found another way to implement my needs though.
> Thanks,
> Nascif
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Friday, October 05, 2007 1:01 PM
> To: ivy-user@incubator.apache.org
> Subject: Re: Using Extra Attributes
>
> On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> >
> > I apologise, I should have included the snippets in the first
e-mail.
> >
> > I am testing this by making changes to the multi-project example.
> > So I tweaked ivy.xml and published the following revisions of the
> > "version" project (below are snippets for each version's published
> > ivy.xml in the repository):
> >
> > <ivy-module version="1.0">
> > <info organisation="jayasoft" module="version" revision="7"
> > status="release" publication="20071004180756" week="41"/>
> >
> > <ivy-module version="1.0">
> > <info organisation="jayasoft" module="version" revision="8"
> > status="release" publication="20071004180824" week="42"/>
> >
> > <ivy-module version="1.0">
> > <info organisation="jayasoft" module="version" revision="9"
> > status="integration" publication="20071004180848"/>
> >
> > The in the consumer project "list", I changed the dependency to
read:
> > <dependency name="version" rev="latest.release" conf="core"
> > week="41"/>
> >
> > and executed "ant resolve" with a clean cache. From the logs I can
see
> > that Ivy goes over all the versions
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 7 ]
> >
> >
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 8 ]
> >
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> >
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> >
> > After reading all the revisions in the repository, Ivy decides to
ask
> > for the revision "8" jar file.
> >
> > [ivy:retrieve] listing all in
> >
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/ivy-[revision].xml
> > [ivy:retrieve] using tpj to list all in
> >
>
C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > ayasoft/version
> > [ivy:retrieve] tpj: unable to list resources for [ jayasoft |
version
> |
> > latest.release ]:
> >
>
pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > ../tpj/[organisation]/[module]/ivy-[revision].[ext]
> > [ivy:retrieve] trying
> >
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/jars/version-latest.release.jar
> > [ivy:retrieve] listing all in
> >
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/jars/version-[revision].jar
> > [ivy:retrieve] using tpj to list all in
> >
>
C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > ayasoft/version/jars
> > [ivy:retrieve] tpj: unable to list resources for [ jayasoft |
version
> |
> > latest.release ]:
> >
>
pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > ../tpj/[organisation]/[module]/jars/[artifact]-[revision].[ext]
> > [ivy:retrieve] tpj: no ivy file nor artifact found for [ jayasoft |
> > version | latest.release ]
> > [ivy:retrieve] tried
> >
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/ivy-latest.release.xml
> > [ivy:retrieve] tried
> >
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/ivy-[any release].xml
> > [ivy:retrieve] tried
> >
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/jars/version-latest.release.jar
> > [ivy:retrieve] found [ jayasoft | version | 8 ] in shared
> > [ivy:retrieve] [8] [ jayasoft | version | latest.release ]
> >
> > I would think it should ask for revision "7" since it is the one
with
> > the "week=41" attribute.
>
>
> Ok, let's say that this is a limitation of what you can do with extra
> attributes. With most of the version matchers Ivy tries to avoid to
> read
> the module descriptor to know if a version match or not. In your case
> you
> use a version constraint which needs to load the ivy files, but Ivy do
> not
> take advantage of this to filter the extra attributes. This could be
> changed, but then it would be strange that when you use
> latest.integration(which do not require module descriptor loading),
> Ivy wouldn't take care of
> the extra attribute. Loading module descriptors systematically as soon
> as
> you use extra attributes is not a good idea either: may users use
extra
> attributes without this need.
>
> So, what's the solution? You need to add your extra attribute in your
> pattern, so that Ivy can know the value of the extra attribute
depending
> on
> the ivy file location only, and not its content. Then your
> latest.releasewith your "week" extra attribute should work properly.
>
> On a related question, can I use the "publication" attribute to
retrieve
> > a dependency?
>
>
> Do you mean as a constraint on the dependency you select? Out of the
box
> you
> can't, but maybe you can write a custom VersionMatcher for that. But
you
> will need to parse the module descriptor to do so, which can be quite
> expensive.
>
> Xavier
>
> Thanks,
> > Nascif
> >
> >
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Friday, October 05, 2007 3:21 AM
> > To: ivy-user@incubator.apache.org
> > Subject: Re: Using Extra Attributes
> >
> > On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com>
wrote:
> > >
> > > I can't get extra attributes to work in 1.4.1, is this really
> > supported?
> > > I am looking at the functionality described in
> > > http://incubator.apache.org/ivy/history/1.4.html
> > > Under "Core features"
> > >
> > > and I tried a lot of combinations with extra attribute. I can see
> them
> > > in the published ivy.xml, but there is no way that I can use them
to
> > > influence the result of my retrieve as suggested in the examples.
> > >
> > > Is anybody using this feature?
> >
> >
> > I have in the past, and we have some unit tests checking it's
working,
> > so
> > I'd be surprised if it doesn't work at all. Could you provide some
> > snippets
> > of what you do and what you expect?
> >
> > Xavier
> >
> > Thanks,
> > > Nascif
> > >
> > >
> > >
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://incubator.apache.org/ivy/
> > http://www.xoocode.org/
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: Using Extra Attributes
Posted by Xavier Hanin <xa...@gmail.com>.
On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
>
> Thanks for the explanation. Perhaps some clarification that using extra
> attributes require that you use the attribute as part of the pattern if
> they are to be used to resolve dynamic versions should be added to the
> web site.
Indeed, extra attributes would deserve some more documentation. Maybe a
tutorial, or a follow up to another tutorial... Since you have worked in
this direction, maybe you could contribute something in this area?
This is all I found in
> http://incubator.apache.org/ivy/history/trunk/concept.html#extra
>
> Then you can use the extra attribute when you declare a dependency on
> foo:
> <dependency org="apache" name="foo" color="blue" rev="1.5+" />
>
> And since "1.5+" is a dynamic version I got the impression thar color
> could be used to influence how it would be resolved.
It should be possible if you use the color in your pattern.
Anyway I tried to create a unit test to validate my use case:
> public void testExtraAttributesWithLatestInPattern() throws
> Exception {
> Ivy ivy = new Ivy();
> ivy.configure(new
> File("test/repositories/extra-attributes-multiple-versions/ivyconf.xml")
> );
>
> // without extra attribute in pattern
> //ResolveReport report =
> ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-no-patte
> rn.xml"),
>
> //with extra attribute in pattern
> ResolveReport report =
> ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-in-patte
> rn.xml"),
> null, new String[] {"*"}, _cache, null, false);
> assertFalse(report.hasError());
>
> assertTrue(new File(_cache,
> "jayasoft/mymodule/task1/1854/ivy.xml").exists());
> assertTrue(new File(_cache,
> "jayasoft/mymodule/task1/1854/mymodule-windows.jar").exists());
> assertTrue(new File(_cache,
> "jayasoft/mymodule/task1/1854/mymodule-linux.jar").exists());
> }
>
> Where mymodule has also another version, 2854 with eatt == task2, and
> where I use "eatt" in the pattern as in the original test case. The
> result was not much better:
>
> <testcase classname="fr.jayasoft.ivy.ResolveTest"
> name="testExtraAttributesWithLatestInPattern" time="0.031">
> <error
> type="java.lang.NullPointerException">java.lang.NullPointerException
> at
> fr.jayasoft.ivy.repository.url.URLResource.getName(URLResource.java:30)
> at
> fr.jayasoft.ivy.external.m2.PomModuleDescriptorParser.accept(PomModuleDe
> scriptorParser.java:262)
> at
> fr.jayasoft.ivy.parser.ModuleDescriptorParserRegistry.getParser(ModuleDe
> scriptorParserRegistry.java:58)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1083)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1071)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1068)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1025)
> at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1022)
> at
> fr.jayasoft.ivy.ResolveTest.testExtraAttributesWithLatestInPattern(Resol
> veTest.java:2595)
Could you open an issue and provide your unit test as a patch? It would be
easier for us to see exactly what you are testing, and to include the test
if it is relevant. BTW, it seems you are using 1.4, a patch against current
trunk would be more appreciated :-)
Xavier
I think I found another way to implement my needs though.
> Thanks,
> Nascif
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Friday, October 05, 2007 1:01 PM
> To: ivy-user@incubator.apache.org
> Subject: Re: Using Extra Attributes
>
> On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> >
> > I apologise, I should have included the snippets in the first e-mail.
> >
> > I am testing this by making changes to the multi-project example.
> > So I tweaked ivy.xml and published the following revisions of the
> > "version" project (below are snippets for each version's published
> > ivy.xml in the repository):
> >
> > <ivy-module version="1.0">
> > <info organisation="jayasoft" module="version" revision="7"
> > status="release" publication="20071004180756" week="41"/>
> >
> > <ivy-module version="1.0">
> > <info organisation="jayasoft" module="version" revision="8"
> > status="release" publication="20071004180824" week="42"/>
> >
> > <ivy-module version="1.0">
> > <info organisation="jayasoft" module="version" revision="9"
> > status="integration" publication="20071004180848"/>
> >
> > The in the consumer project "list", I changed the dependency to read:
> > <dependency name="version" rev="latest.release" conf="core"
> > week="41"/>
> >
> > and executed "ant resolve" with a clean cache. From the logs I can see
> > that Ivy goes over all the versions
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 7 ]
> >
> >
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 8 ]
> >
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> >
> > [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
> matcher
> > [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> > version | latest.release ] parsed=[ jayasoft | version | 9 ]
> >
> > After reading all the revisions in the repository, Ivy decides to ask
> > for the revision "8" jar file.
> >
> > [ivy:retrieve] listing all in
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/ivy-[revision].xml
> > [ivy:retrieve] using tpj to list all in
> >
> C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > ayasoft/version
> > [ivy:retrieve] tpj: unable to list resources for [ jayasoft | version
> |
> > latest.release ]:
> >
> pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > ../tpj/[organisation]/[module]/ivy-[revision].[ext]
> > [ivy:retrieve] trying
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/jars/version-latest.release.jar
> > [ivy:retrieve] listing all in
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/jars/version-[revision].jar
> > [ivy:retrieve] using tpj to list all in
> >
> C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> > ayasoft/version/jars
> > [ivy:retrieve] tpj: unable to list resources for [ jayasoft | version
> |
> > latest.release ]:
> >
> pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> > ../tpj/[organisation]/[module]/jars/[artifact]-[revision].[ext]
> > [ivy:retrieve] tpj: no ivy file nor artifact found for [ jayasoft |
> > version | latest.release ]
> > [ivy:retrieve] tried
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/ivy-latest.release.xml
> > [ivy:retrieve] tried
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/ivy-[any release].xml
> > [ivy:retrieve] tried
> >
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> > ayasoft/version/jars/version-latest.release.jar
> > [ivy:retrieve] found [ jayasoft | version | 8 ] in shared
> > [ivy:retrieve] [8] [ jayasoft | version | latest.release ]
> >
> > I would think it should ask for revision "7" since it is the one with
> > the "week=41" attribute.
>
>
> Ok, let's say that this is a limitation of what you can do with extra
> attributes. With most of the version matchers Ivy tries to avoid to
> read
> the module descriptor to know if a version match or not. In your case
> you
> use a version constraint which needs to load the ivy files, but Ivy do
> not
> take advantage of this to filter the extra attributes. This could be
> changed, but then it would be strange that when you use
> latest.integration(which do not require module descriptor loading),
> Ivy wouldn't take care of
> the extra attribute. Loading module descriptors systematically as soon
> as
> you use extra attributes is not a good idea either: may users use extra
> attributes without this need.
>
> So, what's the solution? You need to add your extra attribute in your
> pattern, so that Ivy can know the value of the extra attribute depending
> on
> the ivy file location only, and not its content. Then your
> latest.releasewith your "week" extra attribute should work properly.
>
> On a related question, can I use the "publication" attribute to retrieve
> > a dependency?
>
>
> Do you mean as a constraint on the dependency you select? Out of the box
> you
> can't, but maybe you can write a custom VersionMatcher for that. But you
> will need to parse the module descriptor to do so, which can be quite
> expensive.
>
> Xavier
>
> Thanks,
> > Nascif
> >
> >
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Friday, October 05, 2007 3:21 AM
> > To: ivy-user@incubator.apache.org
> > Subject: Re: Using Extra Attributes
> >
> > On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> > >
> > > I can't get extra attributes to work in 1.4.1, is this really
> > supported?
> > > I am looking at the functionality described in
> > > http://incubator.apache.org/ivy/history/1.4.html
> > > Under "Core features"
> > >
> > > and I tried a lot of combinations with extra attribute. I can see
> them
> > > in the published ivy.xml, but there is no way that I can use them to
> > > influence the result of my retrieve as suggested in the examples.
> > >
> > > Is anybody using this feature?
> >
> >
> > I have in the past, and we have some unit tests checking it's working,
> > so
> > I'd be surprised if it doesn't work at all. Could you provide some
> > snippets
> > of what you do and what you expect?
> >
> > Xavier
> >
> > Thanks,
> > > Nascif
> > >
> > >
> > >
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://incubator.apache.org/ivy/
> > http://www.xoocode.org/
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
RE: Using Extra Attributes
Posted by Nascif Abousalh-Neto <Na...@sas.com>.
Thanks for the explanation. Perhaps some clarification that using extra
attributes require that you use the attribute as part of the pattern if
they are to be used to resolve dynamic versions should be added to the
web site. This is all I found in
http://incubator.apache.org/ivy/history/trunk/concept.html#extra
Then you can use the extra attribute when you declare a dependency on
foo:
<dependency org="apache" name="foo" color="blue" rev="1.5+" />
And since "1.5+" is a dynamic version I got the impression thar color
could be used to influence how it would be resolved.
Anyway I tried to create a unit test to validate my use case:
public void testExtraAttributesWithLatestInPattern() throws
Exception {
Ivy ivy = new Ivy();
ivy.configure(new
File("test/repositories/extra-attributes-multiple-versions/ivyconf.xml")
);
// without extra attribute in pattern
//ResolveReport report =
ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-no-patte
rn.xml"),
//with extra attribute in pattern
ResolveReport report =
ivy.resolve(ResolveTest.class.getResource("ivy-extra-att-latest-in-patte
rn.xml"),
null, new String[] {"*"}, _cache, null, false);
assertFalse(report.hasError());
assertTrue(new File(_cache,
"jayasoft/mymodule/task1/1854/ivy.xml").exists());
assertTrue(new File(_cache,
"jayasoft/mymodule/task1/1854/mymodule-windows.jar").exists());
assertTrue(new File(_cache,
"jayasoft/mymodule/task1/1854/mymodule-linux.jar").exists());
}
Where mymodule has also another version, 2854 with eatt == task2, and
where I use "eatt" in the pattern as in the original test case. The
result was not much better:
<testcase classname="fr.jayasoft.ivy.ResolveTest"
name="testExtraAttributesWithLatestInPattern" time="0.031">
<error
type="java.lang.NullPointerException">java.lang.NullPointerException
at
fr.jayasoft.ivy.repository.url.URLResource.getName(URLResource.java:30)
at
fr.jayasoft.ivy.external.m2.PomModuleDescriptorParser.accept(PomModuleDe
scriptorParser.java:262)
at
fr.jayasoft.ivy.parser.ModuleDescriptorParserRegistry.getParser(ModuleDe
scriptorParserRegistry.java:58)
at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1083)
at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1071)
at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1068)
at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1025)
at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1022)
at
fr.jayasoft.ivy.ResolveTest.testExtraAttributesWithLatestInPattern(Resol
veTest.java:2595)
I think I found another way to implement my needs though.
Thanks,
Nascif
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: Friday, October 05, 2007 1:01 PM
To: ivy-user@incubator.apache.org
Subject: Re: Using Extra Attributes
On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
>
> I apologise, I should have included the snippets in the first e-mail.
>
> I am testing this by making changes to the multi-project example.
> So I tweaked ivy.xml and published the following revisions of the
> "version" project (below are snippets for each version's published
> ivy.xml in the repository):
>
> <ivy-module version="1.0">
> <info organisation="jayasoft" module="version" revision="7"
> status="release" publication="20071004180756" week="41"/>
>
> <ivy-module version="1.0">
> <info organisation="jayasoft" module="version" revision="8"
> status="release" publication="20071004180824" week="42"/>
>
> <ivy-module version="1.0">
> <info organisation="jayasoft" module="version" revision="9"
> status="integration" publication="20071004180848"/>
>
> The in the consumer project "list", I changed the dependency to read:
> <dependency name="version" rev="latest.release" conf="core"
> week="41"/>
>
> and executed "ant resolve" with a clean cache. From the logs I can see
> that Ivy goes over all the versions
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 7 ]
>
>
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 8 ]
>
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 9 ]
>
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default
matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 9 ]
>
> After reading all the revisions in the repository, Ivy decides to ask
> for the revision "8" jar file.
>
> [ivy:retrieve] listing all in
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/ivy-[revision].xml
> [ivy:retrieve] using tpj to list all in
>
C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> ayasoft/version
> [ivy:retrieve] tpj: unable to list resources for [ jayasoft | version
|
> latest.release ]:
>
pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> ../tpj/[organisation]/[module]/ivy-[revision].[ext]
> [ivy:retrieve] trying
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/jars/version-latest.release.jar
> [ivy:retrieve] listing all in
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/jars/version-[revision].jar
> [ivy:retrieve] using tpj to list all in
>
C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> ayasoft/version/jars
> [ivy:retrieve] tpj: unable to list resources for [ jayasoft | version
|
> latest.release ]:
>
pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> ../tpj/[organisation]/[module]/jars/[artifact]-[revision].[ext]
> [ivy:retrieve] tpj: no ivy file nor artifact found for [ jayasoft |
> version | latest.release ]
> [ivy:retrieve] tried
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/ivy-latest.release.xml
> [ivy:retrieve] tried
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/ivy-[any release].xml
> [ivy:retrieve] tried
>
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/jars/version-latest.release.jar
> [ivy:retrieve] found [ jayasoft | version | 8 ] in shared
> [ivy:retrieve] [8] [ jayasoft | version | latest.release ]
>
> I would think it should ask for revision "7" since it is the one with
> the "week=41" attribute.
Ok, let's say that this is a limitation of what you can do with extra
attributes. With most of the version matchers Ivy tries to avoid to
read
the module descriptor to know if a version match or not. In your case
you
use a version constraint which needs to load the ivy files, but Ivy do
not
take advantage of this to filter the extra attributes. This could be
changed, but then it would be strange that when you use
latest.integration(which do not require module descriptor loading),
Ivy wouldn't take care of
the extra attribute. Loading module descriptors systematically as soon
as
you use extra attributes is not a good idea either: may users use extra
attributes without this need.
So, what's the solution? You need to add your extra attribute in your
pattern, so that Ivy can know the value of the extra attribute depending
on
the ivy file location only, and not its content. Then your
latest.releasewith your "week" extra attribute should work properly.
On a related question, can I use the "publication" attribute to retrieve
> a dependency?
Do you mean as a constraint on the dependency you select? Out of the box
you
can't, but maybe you can write a custom VersionMatcher for that. But you
will need to parse the module descriptor to do so, which can be quite
expensive.
Xavier
Thanks,
> Nascif
>
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Friday, October 05, 2007 3:21 AM
> To: ivy-user@incubator.apache.org
> Subject: Re: Using Extra Attributes
>
> On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> >
> > I can't get extra attributes to work in 1.4.1, is this really
> supported?
> > I am looking at the functionality described in
> > http://incubator.apache.org/ivy/history/1.4.html
> > Under "Core features"
> >
> > and I tried a lot of combinations with extra attribute. I can see
them
> > in the published ivy.xml, but there is no way that I can use them to
> > influence the result of my retrieve as suggested in the examples.
> >
> > Is anybody using this feature?
>
>
> I have in the past, and we have some unit tests checking it's working,
> so
> I'd be surprised if it doesn't work at all. Could you provide some
> snippets
> of what you do and what you expect?
>
> Xavier
>
> Thanks,
> > Nascif
> >
> >
> >
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: Using Extra Attributes
Posted by Xavier Hanin <xa...@gmail.com>.
On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
>
> I apologise, I should have included the snippets in the first e-mail.
>
> I am testing this by making changes to the multi-project example.
> So I tweaked ivy.xml and published the following revisions of the
> "version" project (below are snippets for each version's published
> ivy.xml in the repository):
>
> <ivy-module version="1.0">
> <info organisation="jayasoft" module="version" revision="7"
> status="release" publication="20071004180756" week="41"/>
>
> <ivy-module version="1.0">
> <info organisation="jayasoft" module="version" revision="8"
> status="release" publication="20071004180824" week="42"/>
>
> <ivy-module version="1.0">
> <info organisation="jayasoft" module="version" revision="9"
> status="integration" publication="20071004180848"/>
>
> The in the consumer project "list", I changed the dependency to read:
> <dependency name="version" rev="latest.release" conf="core"
> week="41"/>
>
> and executed "ant resolve" with a clean cache. From the logs I can see
> that Ivy goes over all the versions
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 7 ]
>
>
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 8 ]
>
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 9 ]
>
> [ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
> [ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
> version | latest.release ] parsed=[ jayasoft | version | 9 ]
>
> After reading all the revisions in the repository, Ivy decides to ask
> for the revision "8" jar file.
>
> [ivy:retrieve] listing all in
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/ivy-[revision].xml
> [ivy:retrieve] using tpj to list all in
> C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> ayasoft/version
> [ivy:retrieve] tpj: unable to list resources for [ jayasoft | version |
> latest.release ]:
> pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> ../tpj/[organisation]/[module]/ivy-[revision].[ext]
> [ivy:retrieve] trying
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/jars/version-latest.release.jar
> [ivy:retrieve] listing all in
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/jars/version-[revision].jar
> [ivy:retrieve] using tpj to list all in
> C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
> ayasoft/version/jars
> [ivy:retrieve] tpj: unable to list resources for [ jayasoft | version |
> latest.release ]:
> pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
> ../tpj/[organisation]/[module]/jars/[artifact]-[revision].[ext]
> [ivy:retrieve] tpj: no ivy file nor artifact found for [ jayasoft |
> version | latest.release ]
> [ivy:retrieve] tried
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/ivy-latest.release.xml
> [ivy:retrieve] tried
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/ivy-[any release].xml
> [ivy:retrieve] tried
> C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
> ayasoft/version/jars/version-latest.release.jar
> [ivy:retrieve] found [ jayasoft | version | 8 ] in shared
> [ivy:retrieve] [8] [ jayasoft | version | latest.release ]
>
> I would think it should ask for revision "7" since it is the one with
> the "week=41" attribute.
Ok, let's say that this is a limitation of what you can do with extra
attributes. With most of the version matchers Ivy tries to avoid to read
the module descriptor to know if a version match or not. In your case you
use a version constraint which needs to load the ivy files, but Ivy do not
take advantage of this to filter the extra attributes. This could be
changed, but then it would be strange that when you use
latest.integration(which do not require module descriptor loading),
Ivy wouldn't take care of
the extra attribute. Loading module descriptors systematically as soon as
you use extra attributes is not a good idea either: may users use extra
attributes without this need.
So, what's the solution? You need to add your extra attribute in your
pattern, so that Ivy can know the value of the extra attribute depending on
the ivy file location only, and not its content. Then your
latest.releasewith your "week" extra attribute should work properly.
On a related question, can I use the "publication" attribute to retrieve
> a dependency?
Do you mean as a constraint on the dependency you select? Out of the box you
can't, but maybe you can write a custom VersionMatcher for that. But you
will need to parse the module descriptor to do so, which can be quite
expensive.
Xavier
Thanks,
> Nascif
>
>
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Friday, October 05, 2007 3:21 AM
> To: ivy-user@incubator.apache.org
> Subject: Re: Using Extra Attributes
>
> On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
> >
> > I can't get extra attributes to work in 1.4.1, is this really
> supported?
> > I am looking at the functionality described in
> > http://incubator.apache.org/ivy/history/1.4.html
> > Under "Core features"
> >
> > and I tried a lot of combinations with extra attribute. I can see them
> > in the published ivy.xml, but there is no way that I can use them to
> > influence the result of my retrieve as suggested in the examples.
> >
> > Is anybody using this feature?
>
>
> I have in the past, and we have some unit tests checking it's working,
> so
> I'd be surprised if it doesn't work at all. Could you provide some
> snippets
> of what you do and what you expect?
>
> Xavier
>
> Thanks,
> > Nascif
> >
> >
> >
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
RE: Using Extra Attributes
Posted by Nascif Abousalh-Neto <Na...@sas.com>.
I apologise, I should have included the snippets in the first e-mail.
I am testing this by making changes to the multi-project example.
So I tweaked ivy.xml and published the following revisions of the
"version" project (below are snippets for each version's published
ivy.xml in the repository):
<ivy-module version="1.0">
<info organisation="jayasoft" module="version" revision="7"
status="release" publication="20071004180756" week="41"/>
<ivy-module version="1.0">
<info organisation="jayasoft" module="version" revision="8"
status="release" publication="20071004180824" week="42"/>
<ivy-module version="1.0">
<info organisation="jayasoft" module="version" revision="9"
status="integration" publication="20071004180848"/>
The in the consumer project "list", I changed the dependency to read:
<dependency name="version" rev="latest.release" conf="core"
week="41"/>
and executed "ant resolve" with a clean cache. From the logs I can see
that Ivy goes over all the versions
[ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
[ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
version | latest.release ] parsed=[ jayasoft | version | 7 ]
[ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
[ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
version | latest.release ] parsed=[ jayasoft | version | 8 ]
[ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
[ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
version | latest.release ] parsed=[ jayasoft | version | 9 ]
[ivy:retrieve] pre 1.3 ivy file: using exactOrRegexp as default matcher
[ivy:retrieve] shared: parsed downloaded md file for [ jayasoft |
version | latest.release ] parsed=[ jayasoft | version | 9 ]
After reading all the revisions in the repository, Ivy decides to ask
for the revision "8" jar file.
[ivy:retrieve] listing all in
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
ayasoft/version/ivy-[revision].xml
[ivy:retrieve] using tpj to list all in
C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
ayasoft/version
[ivy:retrieve] tpj: unable to list resources for [ jayasoft | version |
latest.release ]:
pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
../tpj/[organisation]/[module]/ivy-[revision].[ext]
[ivy:retrieve] trying
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
ayasoft/version/jars/version-latest.release.jar
[ivy:retrieve] listing all in
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
ayasoft/version/jars/version-[revision].jar
[ivy:retrieve] using tpj to list all in
C:/home/dev/IvyNextGen/multi-project/projects/list/../../common/../tpj/j
ayasoft/version/jars
[ivy:retrieve] tpj: unable to list resources for [ jayasoft | version |
latest.release ]:
pattern=C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/
../tpj/[organisation]/[module]/jars/[artifact]-[revision].[ext]
[ivy:retrieve] tpj: no ivy file nor artifact found for [ jayasoft |
version | latest.release ]
[ivy:retrieve] tried
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
ayasoft/version/ivy-latest.release.xml
[ivy:retrieve] tried
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
ayasoft/version/ivy-[any release].xml
[ivy:retrieve] tried
C:\home\dev\IvyNextGen\multi-project\projects\list/../../common/../tpj/j
ayasoft/version/jars/version-latest.release.jar
[ivy:retrieve] found [ jayasoft | version | 8 ] in shared
[ivy:retrieve] [8] [ jayasoft | version | latest.release ]
I would think it should ask for revision "7" since it is the one with
the "week=41" attribute.
On a related question, can I use the "publication" attribute to retrieve
a dependency?
Thanks,
Nascif
-----Original Message-----
From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
Sent: Friday, October 05, 2007 3:21 AM
To: ivy-user@incubator.apache.org
Subject: Re: Using Extra Attributes
On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
>
> I can't get extra attributes to work in 1.4.1, is this really
supported?
> I am looking at the functionality described in
> http://incubator.apache.org/ivy/history/1.4.html
> Under "Core features"
>
> and I tried a lot of combinations with extra attribute. I can see them
> in the published ivy.xml, but there is no way that I can use them to
> influence the result of my retrieve as suggested in the examples.
>
> Is anybody using this feature?
I have in the past, and we have some unit tests checking it's working,
so
I'd be surprised if it doesn't work at all. Could you provide some
snippets
of what you do and what you expect?
Xavier
Thanks,
> Nascif
>
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: Using Extra Attributes
Posted by Xavier Hanin <xa...@gmail.com>.
On 10/5/07, Nascif Abousalh-Neto <Na...@sas.com> wrote:
>
> I can't get extra attributes to work in 1.4.1, is this really supported?
> I am looking at the functionality described in
> http://incubator.apache.org/ivy/history/1.4.html
> Under "Core features"
>
> and I tried a lot of combinations with extra attribute. I can see them
> in the published ivy.xml, but there is no way that I can use them to
> influence the result of my retrieve as suggested in the examples.
>
> Is anybody using this feature?
I have in the past, and we have some unit tests checking it's working, so
I'd be surprised if it doesn't work at all. Could you provide some snippets
of what you do and what you expect?
Xavier
Thanks,
> Nascif
>
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Using Extra Attributes
Posted by Nascif Abousalh-Neto <Na...@sas.com>.
I can't get extra attributes to work in 1.4.1, is this really supported?
I am looking at the functionality described in
http://incubator.apache.org/ivy/history/1.4.html
Under "Core features"
and I tried a lot of combinations with extra attribute. I can see them
in the published ivy.xml, but there is no way that I can use them to
influence the result of my retrieve as suggested in the examples.
Is anybody using this feature?
Thanks,
Nascif
RE: Cache Path and Ant console logging
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
Ok, I've got it sorted out - moved the Ivy resolution bits into an
"init" target, wired up dependencies to "init", and finally, passed each
required Path referece with the Ant <reference> element within each Ant
Call that required it.
Thanks for the pointer Steve.
Gerard.
-----Original Message-----
From: Fernandes, Gerard
Sent: 04 October 2007 16:49
To: 'ivy-user@incubator.apache.org'
Subject: RE: Cache Path and Ant console logging
Thanks for the post Steve. I can see how this would be good, although I
personally would prefer to break out a common build system that supplied
(via Ivy) a global repository with artefacts and then use Ivy again to
manage dependencies in modules that needed them. That way, the build
system need only be concerned with building it's own artefact(s).
A packaging system could then manage, again via Ivy, the packaging of a
deployable unit along with all it's dependencies.
But of course, that's a different issue. :)
Could you point me to such global datatypes in Ant that can be
inherited?
Thanks again.
Gerard.
-----Original Message-----
From: Steve Loughran [mailto:stevel@apache.org]
Sent: 04 October 2007 15:23
To: ivy-user@incubator.apache.org
Subject: Re: Cache Path and Ant console logging
Fernandes, Gerard wrote:
>
> Ok, I've tried to debug this a bit and it seems the problem is not Ivy
> - it's the way Ant handles global declarations when calling out to
> external build scripts. This causes the global cache-path tasks to be
> re-invoked each time a call to an externally defined target happens,
> therefore triggering repeated resolutions.
>
> This is not an Ivy issue. It is an Ant build script structure issue.
yes, if you use <antcall> or <subant> then things get triggered
repeatedly. This can be a good thing if you want sub projects to have
different dependencies. To pass state down , get the data into ant
datatypes that can be inherited.
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
RE: Cache Path and Ant console logging
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
Thanks for the post Steve. I can see how this would be good, although I
personally would prefer to break out a common build system that supplied
(via Ivy) a global repository with artefacts and then use Ivy again to
manage dependencies in modules that needed them. That way, the build
system need only be concerned with building it's own artefact(s).
A packaging system could then manage, again via Ivy, the packaging of a
deployable unit along with all it's dependencies.
But of course, that's a different issue. :)
Could you point me to such global datatypes in Ant that can be
inherited?
Thanks again.
Gerard.
-----Original Message-----
From: Steve Loughran [mailto:stevel@apache.org]
Sent: 04 October 2007 15:23
To: ivy-user@incubator.apache.org
Subject: Re: Cache Path and Ant console logging
Fernandes, Gerard wrote:
>
> Ok, I've tried to debug this a bit and it seems the problem is not Ivy
> - it's the way Ant handles global declarations when calling out to
> external build scripts. This causes the global cache-path tasks to be
> re-invoked each time a call to an externally defined target happens,
> therefore triggering repeated resolutions.
>
> This is not an Ivy issue. It is an Ant build script structure issue.
yes, if you use <antcall> or <subant> then things get triggered
repeatedly. This can be a good thing if you want sub projects to have
different dependencies. To pass state down , get the data into ant
datatypes that can be inherited.
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Re: Cache Path and Ant console logging
Posted by Steve Loughran <st...@apache.org>.
Fernandes, Gerard wrote:
>
> Ok, I've tried to debug this a bit and it seems the problem is not Ivy -
> it's the way Ant handles global declarations when calling out to
> external build scripts. This causes the global cache-path tasks to be
> re-invoked each time a call to an externally defined target happens,
> therefore triggering repeated resolutions.
>
> This is not an Ivy issue. It is an Ant build script structure issue.
yes, if you use <antcall> or <subant> then things get triggered
repeatedly. This can be a good thing if you want sub projects to have
different dependencies. To pass state down , get the data into ant
datatypes that can be inherited.
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
RE: Cache Path and Ant console logging
Posted by "Fernandes, Gerard" <ge...@lehman.com>.
Ok, I've tried to debug this a bit and it seems the problem is not Ivy -
it's the way Ant handles global declarations when calling out to
external build scripts. This causes the global cache-path tasks to be
re-invoked each time a call to an externally defined target happens,
therefore triggering repeated resolutions.
This is not an Ivy issue. It is an Ant build script structure issue.
> _____________________________________________
> From: Fernandes, Gerard
> Sent: 01 October 2007 10:59
> To: 'ivy-user@incubator.apache.org'
> Subject: Cache Path and Ant console logging
>
> Using Cache path in Ant results in one resolution per use of the
> cached path reference. This is undesirable as the cached path is
> cached once (globally) at the beginning of the Ant script and used
> throughout the ant script and also in called scripts.
>
> The desirable behavior would be to have Cache path resolve exactly
> ONCE each time it is actually invoked.
>
> See the Ant log console below - it seems almost as if at every Ant
> Target being executed, the cache path is being invoked and executed as
> well.
>
> **********************************************************************
> *******************************************
> Buildfile: C:\Java\Projects\Fire\fire-server\build.xml
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: Ivy 1.4.1 - 20061109165313 ::
> http://ivy.jayasoft.org/ ::
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> build:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> build-dependent:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
>
> ---------------------------------------------------------------------
> java.compile:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
>
> ---------------------------------------------------------------------
> java.compile.target:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
>
> ---------------------------------------------------------------------
> java.compile.target:
> jar:
> build:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> java.compile:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> java.compile.target:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> java.compile.target:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> jar:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> jar:
> [ivy:configure] Loading
> jar:file:/C:/Java/Projects/Fire/fid-3rdParty/package/ivy/1.4.1/ivy-1.4
> .1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: configuring :: file =
> C:\Java\Projects\Fire\fid-3rdParty\package\ivyconf.xml
> [ivy:resolve] :: resolving dependencies :: [ lehman-fid | hydra |
> working@lofidw041141 ]
> [ivy:resolve] confs: [COMPILE, RUNTIME, TEST, FIRE, DEPLOY]
> [ivy:resolve] found [ aspectj | aspectjlib | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ aspectj | aspectjtools | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] found [ apache-log4j | log4j | 1.2.12 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | coherence | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ coherence | tangosol | 3.1 ] in
> externalLibraries
> [ivy:resolve] found [ grinder | grinder | 2.8.6 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-beanutils |
> commons-beanutils | 1.7.0 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-io | commons-io | 1.3 ]
> in externalLibraries
> [ivy:resolve] found [ jakarta-commons-lang | commons-lang |
> 2.2 ] in externalLibraries
> [ivy:resolve] found [ jdom | jdom | 1.0 ] in externalLibraries
> [ivy:resolve] found [ jdom | jaxen-core | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | jaxen-jdom | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jdom | saxpath | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-ua | utr | 1.04 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | AuthToken | 1.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-authtoken | etg-framework-4.0.2 |
> 1.1 ] in externalLibraries
> [ivy:resolve] found [ lehman-authtoken | lehmanSSOHelper | 1.1
> ] in externalLibraries
> [ivy:resolve] found [ lehman-dialtone | Jdialtone | 8.0.1 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-elmo | elmo-client | 2.0 ] in
> externalLibraries
> [ivy:resolve] found [ lehman-phoenix | PhoenixAgent | 072707R1
> ] in externalLibraries
> [ivy:resolve] found [ spring | spring | 2.0.6 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibcrypt | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsadmin | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibjmsapps | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ tibems | tibrvjms | 4.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ weblogic | weblogic | 9.2 ] in
> externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc_license_cu | 8.1_FP10 ]
> in externalLibraries
> [ivy:resolve] found [ db2_udb | db2jcc | 8.1_FP10 ] in
> externalLibraries
> [ivy:resolve] found [ apache-xmlbeans | xbean | 1.0.4 ] in
> externalLibraries
> [ivy:resolve] found [ cglib | cglib | 2.1_03 ] in
> externalLibraries
> [ivy:resolve] found [ hibernate | asm | 3.0.5 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | jsr173 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jsr-173 | sjsxp-1.0 | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jakarta-commons-collections |
> commons-collections | 3.1 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jakarta-commons-logging |
> commons-logging-api | 1.0.4 ] in externalLibraries
> [ivy:resolve] found [ jencks | jencks-all | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ jencks | concurrent | 1.0 ] in
> externalLibraries
> [ivy:resolve] found [ junit | junit | 4.1 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | jmock-junit4 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-core-1.1 | 2.2.0 ] in
> externalLibraries
> [ivy:resolve] found [ jmock | hamcrest-library-1.1 | 2.2.0 ]
> in externalLibraries
> [ivy:resolve] found [ hsqldb | hsqldb | 1.7.3.3 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xerces | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ xerces | xml-apis | 2.8.0 ] in
> externalLibraries
> [ivy:resolve] found [ sybase-jconn2 | com.sybase.jconn2 | 1.0
> ] in externalLibraries
> [ivy:resolve] found [ aspectj | aspectjweaver | 1.5.3 ] in
> externalLibraries
> [ivy:resolve] :: resolution report ::
>
> ---------------------------------------------------------------------
> | | modules ||
> artifacts |
> | conf | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
> | COMPILE | 29 | 0 | 0 | 0 || 31 |
> 0 |
> | RUNTIME | 35 | 0 | 0 | 0 || 35 |
> 0 |
> | TEST | 18 | 0 | 0 | 0 || 18 |
> 0 |
> | FIRE | 6 | 0 | 0 | 0 || 6 |
> 0 |
> | DEPLOY | 1 | 0 | 0 | 0 || 1 |
> 0 |
>
> ---------------------------------------------------------------------
> jar:
> BUILD SUCCESSFUL
> Total time: 9 seconds
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.