Hi Peter,
On Sep 16, 2008, at 10:41 PM, Peter Niederwieser wrote:
Is 0.4 supposed to be a drop-in replacement for 0.3? Although my build
ultimately succeeds even with 0.4, I get the following error
message in
between:
:: resolution report :: resolve 1349ms :: artifacts dl 6ms
:: modules in use:
#groovy-all;1.6-beta-2-SNAPSHOT from lib in [compile]
asm#asm;2.2.3 from clientModuleChain in [compile]
junit#junit;4.4 from clientModuleChain in [compile]
---------------------------------------------------------------------
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
| compile | 3 | 1 | 0 | 0 || 3 | 0 |
---------------------------------------------------------------------
:: problems summary ::
:::: ERRORS
unknown resolver MavenRepo_poms
unknown resolver MavenRepo_poms
Do I have to be concerned?
No.
This is a known Ivy problem: https://issues.apache.org/jira/browse/
IVY-758
If there is a name difference between the resolver that has
originally resolved a dependency and a resolver which reads that
dependency from the cache you get this message. But you only get it
the first time you run the build with a new resolver name.
The reason why you get this error message is that we have done
changes to the naming schema of our Maven resolvers.
- Hans
Cheers,
Peter
PS: The error message appeared on the first build with Gradle 0.4
but hasn't
appeared since.
--
View this message in context: http://www.nabble.com/Migration-
from-0.3-to-0.4-tp19520172p19520172.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
