Dependency Resolution Problems in RC1
I installed RC1 today and ran the hello-ivy to verify it was working and it was. I had previously been playing with Beta 2. I cleared the cache and the project and tried running again expected this time it failed to compile. I verified the libraries had been resolved to the lib directory. I opened up the JARs in the lib directory and I found that the commons-cli-1.0.jar file contained the javadocs rather than the class files. So I checked the cache and I found that the classes, sources, and javadocs had been downloaded , which is nice. I opened each of those JARs to verify their contents and all was well. I tried cleaning and running the project several times. I observed that commons-lang-2.0.jar contained javadocs rather than classes and occasionally either commons-lang or commons-cli would contain the source files rather than the javadocs or classes. The odd thing is that I never had an issue with the transitive dependency on commons-logging-1.0.jar. By that I mean the correct JAR was always returned. Since I did compile and run the first time I wondered what had changed. I deleted my cache directory and re-installed Beta 2 and ran hello-ivy successfully. I then re-installed RC1, leaving the cache intact and did a clean build and it worked fine. After deleting the cache yet again and re-running RC1 the compile failed due to the reasons I described. There seems to be an issue with using the newer cache directory structure when resolving dependencies.
RE: Dependency Resolution Problems in RC1
-cli-1.0.jar in [default]: 1.0 won [ivy:retrieve] removing conflict looser artifact: commons-cli#commons-cli;1.0!commons-cli.jar(javadoc) [ivy:retrieve] removing conflict looser artifact: commons-cli#commons-cli;1.0!commons-cli.jar [ivy:retrieve] conflict on G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy\lib\commons-lang-2.0.jar in [default]: 2.0 won [ivy:retrieve] removing conflict looser artifact: commons-lang#commons-lang;2.0!commons-lang.jar(source) [ivy:retrieve] removing conflict looser artifact: commons-lang#commons-lang;2.0!commons-lang.jar [ivy:retrieve] retrieving D:\Documents and Settings\skanjo.TRIBUNE\.ivy2\cache\commons-logging\commons-logging\jars \commons-logging-1.0.jar [ivy:retrieve] to G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy\lib\commons-logging-1.0.jar [ivy:retrieve] retrieving D:\Documents and Settings\skanjo.TRIBUNE\.ivy2\cache\commons-lang\commons-lang\javadocs\c ommons-lang-2.0-javadoc.jar [ivy:retrieve] to G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy\lib\commons-lang-2.0.jar [ivy:retrieve] retrieving D:\Documents and Settings\skanjo.TRIBUNE\.ivy2\cache\commons-cli\commons-cli\sources\comm ons-cli-1.0-sources.jar [ivy:retrieve] to G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy\lib\commons-cli-1.0.jar [ivy:retrieve] 3 artifacts copied, 0 already retrieved (536kB/47ms) [ivy:retrieve] retrieve done (47ms) -Original Message- From: Kanjo, Samer [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 1:00 PM To: ivy-user@ant.apache.org Subject: Dependency Resolution Problems in RC1 I installed RC1 today and ran the hello-ivy to verify it was working and it was. I had previously been playing with Beta 2. I cleared the cache and the project and tried running again expected this time it failed to compile. I verified the libraries had been resolved to the lib directory. I opened up the JARs in the lib directory and I found that the commons-cli-1.0.jar file contained the javadocs rather than the class files. So I checked the cache and I found that the classes, sources, and javadocs had been downloaded , which is nice. I opened each of those JARs to verify their contents and all was well. I tried cleaning and running the project several times. I observed that commons-lang-2.0.jar contained javadocs rather than classes and occasionally either commons-lang or commons-cli would contain the source files rather than the javadocs or classes. The odd thing is that I never had an issue with the transitive dependency on commons-logging-1.0.jar. By that I mean the correct JAR was always returned. Since I did compile and run the first time I wondered what had changed. I deleted my cache directory and re-installed Beta 2 and ran hello-ivy successfully. I then re-installed RC1, leaving the cache intact and did a clean build and it worked fine. After deleting the cache yet again and re-running RC1 the compile failed due to the reasons I described. There seems to be an issue with using the newer cache directory structure when resolving dependencies.
RE: Dependency Resolution Problems in RC1
Looks like the trunk is 2.1.x, it worked though. Mow I am checking out
rc2.
-Original Message-
From: Kanjo, Samer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 3:21 PM
To: ivy-user@ant.apache.org
Subject: RE: Dependency Resolution Problems in RC1
Maarten,
Thanks, I am building from the trunk now.
Samer
-Original Message-
From: Maarten Coene [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 3:03 PM
To: ivy-user@ant.apache.org
Subject: Re: Dependency Resolution Problems in RC1
It is a bug that has been fixed in RC2.
RC2 will hopefully be released shortly, there is a vote running for it
atm on the ant-dev list.
Maarten
- Original Message
From: Kanjo, Samer [EMAIL PROTECTED]
To: ivy-user@ant.apache.org
Sent: Wednesday, October 29, 2008 8:00:22 PM
Subject: RE: Dependency Resolution Problems in RC1
I cleaned the hello-ivy project using RC1 and then did a build using
verbose. The following is the output up to the retrieval of the 3
commons projects. You see that the cli sources and the lang javadocs are
retrieved rather than the class jars. Is there a configuration change I
need to make or is this a bug?
G:\lib\ivy-2.0.0-rc1\src\example\hello-ivyant -v Apache Ant version
1.7.0 compiled on December 13 2006
Buildfile: build.xml
Detected Java version: 1.5 in: E:\jdk\jdk1.5.0_11\jre Detected OS:
Windows XP parsing buildfile
G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy\build.xml
with URI = file:/G:/lib/ivy-2.0.0-rc1/src/example/hello-ivy/build.xml
Project base dir set to: G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy
[antlib:org.apache.tools.ant] Could not load definitions from resource
org/apache/tools/ant/antlib.xml. It could not be found.
Build sequence for target(s) `run' is [resolve, run] Complete build
sequence is [resolve, run, report, clean, clean-cache, ]
resolve:
parsing buildfile
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/ant/a
ntlib.xml with URI =
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/ant/a
ntlib.xml
No ivy:settings found for the default reference 'ivy.instance'. A
default instance will be used Loading
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/core/
settings/ivy.properties
searching settings file: trying
G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy\ivysettings.xml
searching settings file: trying
G:\lib\ivy-2.0.0-rc1\src\example\hello-ivy\ivyconf.xml
searching settings file: trying ivysettings.xml searching settings file:
trying ivyconf.xml no settings file found, using default...
[ivy:retrieve] :: Ivy 2.0.0-rc1 - 20080916082609 ::
http://ant.apache.org/ivy/ ::
:: loading settings :: url =
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/core/
settings/ivysettings.xml
no default ivy user dir defined: set to D:\Documents and
Settings\skanjo.TRIBUNE\.ivy2
including url:
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/core/
settings/ivysettings-public.xml
no default cache defined: set to D:\Documents and
Settings\skanjo.TRIBUNE\.ivy2\cache
including url:
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/core/
settings/ivysettings-shared.xml
including url:
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/core/
settings/ivysettings-local.xml
including url:
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/core/
settings/ivysettings-main-chain.xml
including url:
jar:file:/E:/tools/ant-1.7.0/lib/ivy-2.0.0-rc1.jar!/org/apache/ivy/core/
settings/ivysettings-default-chain.xml
settings loaded (188ms)
default cache: D:\Documents and
Settings\skanjo.TRIBUNE\.ivy2\cache
default resolver: default
-- 5 resolvers:
main [chain] [shared, public]
public [ibiblio]
local [file]
shared [file]
default [chain] [local, main]
[ivy:retrieve] no resolved descriptor found: launching default resolve
Overriding previous definition of property ivy.version
[ivy:retrieve] using ivy parser to parse
file:/G:/lib/ivy-2.0.0-rc1/src/example/hello-ivy/ivy.xml
[ivy:retrieve] :: resolving dependencies ::
org.apache#hello-ivy;[EMAIL PROTECTED]
[ivy:retrieve] confs: [default]
[ivy:retrieve] validate = true
[ivy:retrieve] refresh = false
[ivy:retrieve] resolving dependencies for configuration 'default'
[ivy:retrieve] == resolving dependencies for
org.apache#hello-ivy;[EMAIL PROTECTED] [default] [ivy:retrieve] ==
resolving dependencies
org.apache#hello-ivy;[EMAIL PROTECTED]commons-lang#commons-lang;2.0
[default-*]
[ivy:retrieve] default: Checking cache for: dependency:
commons-lang#commons-lang;2.0 {*=[*]}
[ivy:retrieve] default: module revision found in cache:
commons-lang#commons-lang;2.0
[ivy:retrieve] found commons-lang#commons-lang;2.0 in public
[ivy:retrieve] == resolving dependencies
org.apache#hello-ivy;[EMAIL PROTECTED]commons-lang#commons-lang;2.0
[default-runtime]
[ivy:retrieve] == resolving dependencies
org.apache#hello-ivy;[EMAIL PROTECTED]commons-lang#commons-lang;2.0
RE: Test failures in SVN
When I checked out the trunk earlier today there was only one test failure. It was IBiblioResolverTest.testMaven2Listing that failed. The resolution of commons-lang was returning two module entries rather than the expected one. The expected module entry was named commons-lang but an additional module entry named maven2 was unexpectedly returned. I didn't look into any further than that. I bypassed the test in order to complete the build. I just did an update from the trunk and got a few changes since my checkout earlier in the day and ran the tests again. All passed. I checked the logs and see that you checked in four sets of changes after I did my checkout. I guess the merge from RC2 fixed the problem. From: Maarten Coene [mailto:[EMAIL PROTECTED] Sent: Wed 10/29/2008 5:37 PM To: ivy-user@ant.apache.org Subject: Re: Test failures in SVN Yesterday, I had a problem with Ibiblio also and committed a fix for it into SVN trunk. Could you give it a try and see if the tests succeed now? Maarten - Original Message From: Jim White [EMAIL PROTECTED] To: ivy-user@ant.apache.org Sent: Monday, October 27, 2008 5:49:40 PM Subject: Test failures in SVN Speaking of iBiblio, some related tests are failing for me with the current SVN head: http://pastebin.com/m63ca1e7 Jim
