Hi,
I have a very simple ivy setup working (using exact version numbers
for everything). I'm now trying to move to dynamic revision resolution,
but it isn't working.
My ivy-settings.xml contains the following:
<settings defaultResolver="internal" defaultResolveMode="dynamic"
validate="true"/>
My ant build.xml contains the following:
<ivy:retrieve pattern="${libs}/[conf]/[artifact]-[revision].[ext]" />
My local repository contains artifacts such as "spring" (org) "context"
(module) "2.0.8" (revision).
When I reference this dependency using rev="2.0.8", it is found. When I
use revConstraint="2.0.+" it fails as follows:
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve] :::: WARNINGS
[ivy:retrieve] module not found: spring#context;2.0.+
[ivy:retrieve] ==== internal: tried
[ivy:retrieve]
C:\limaloa-svn\code\trunk/ivy-repo/spring/context/ivy.xml
[ivy:retrieve] [work...@internal]
[ivy:retrieve] -- artifact spring#context;2.0.+!context.jar:
[ivy:retrieve]
C:\limaloa-svn\code\trunk/ivy-repo/spring/context/context-[rev
ision].jar
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: UNRESOLVED DEPENDENCIES ::
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: spring#context;2.0.+: not found
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve]
[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
Best Regards,
Chris Nappin
Technical Architect, Application Services
OPSERV - IT Services
Mob: 07824 473044
Part of the Capita Group plc www.capita.co.uk <http://www.capita.co.uk/>
www.capita-its.co.uk <http://www.capita.co.uk/>
'Evolving a great Operational IT Service through OPSERV'
This email and any attachment are intended solely for the addressee, are
strictly confidential and may be legally privileged. If you are not the
intended recipient any reading, dissemination, copying or any other use or
reliance is prohibited. If you have received this email in error please notify
the sender immediately by email and then permanently delete the email.
Copyright reserved.
All communications, incoming and outgoing, may be recorded and are monitored
for legitimate business purposes.
The security and reliability of email transmission cannot be guaranteed. It is
the recipients responsibility to scan this e-mail and any attachment for the
presence of viruses.
The Capita Group plc and its subsidiaries ("Capita") exclude all liability for
any loss or damage whatsoever arising or resulting from the receipt, use or
transmission of this email.
Any views or opinions expressed in this email are those of the author only.
