ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ophir bleiberg" <>
Subject RE: Combining '+' notation with statuses
Date Sun, 10 Dec 2006 07:16:47 GMT
Thanks for your (very fast!) reply.

We could write our own version matcher, probably very easy to do.  The main
issues would be that:
a) It might introduce some proprietary notation to our ivy usage.
b) The IvyDE tool will have to have our additions installed.

These issues are important because we are not merely using Ivy internally in
our organization.  In fact, we are recommending the use of Ivy to our
customers who use our company's service creation environment.  Asking them
to install Ivy and IvyDE is one thing, asking them to patch IvyDE with our
version, and to learn a proprietary syntax is another...

If there is not standard way to perform this, would combining '+' with
statuses be a feature of interest to the ivy community?
If we developed this feature, would this be something you would consider
adding to Ivy?


-----Original Message-----
From: Xavier Hanin [] 
Sent: Thursday, December 07, 2006 12:50 PM
Subject: Re: Combining '+' notation with statuses

On 12/7/06, Ophir Bleiberg <> wrote:
> Hi,


        Is there any way of telling ivy to use a dependency with '+'
> notation from a certain status (e.g. 4.0.1.+.release)?

This is not supported out of the box, but in your case you can know if the
build is an integration build just with the version, so what you need is to
write a very simple VersionMatcher which will handle your specific case. If
you have a look at another VersionMatcher you will see it's pretty easy to
write a custom one which will match your exact need. Have a look at the
subversion matcher for instance (which handles the + notation):


        We are using the following version notation for our modules:
>                 M.M.F.P<-build-BN>
>         where:
>                 - M.M is the major version
>                 - F is a feature number (advances in this number mean 
> backward compatibility with extra features.
>                 - P is the patch number
>                 - For integration builds we use -build.BN where BN is 
> the build number.
>         As you can see, this notation appears to make it impossible 
> for us to declare that we we want to use the latest release patch of a 
> certain version (4.0.1.+) rather than the latest integration build 
> over that patch, or the latest release version (which may not be backward
>         Combining '+' notation with statuses would seem to solve this 
> issue.
>         Is this somehow supported?  Is there any workaround anyone can 
> think of?
>         Thanks,
>                Ophir
>     "Beware of the man who works hard to learn something, learns it, 
> and finds himself no wiser than before.  He is full of murderous 
> resentment of people who are ignorant without having come by their 
> ignorance the hard way."

View raw message