Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Date: Thu, 07 Dec 2006 11:23:57 +0200
From: Ophir Bleiberg <ophir@personeta.com>
Subject: Combining '+' notation with statuses
To: ivy-user@incubator.apache.org
Message-id: <F949FCDE1652A643AF888AED3713541B01C567CA@mailx>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_BAB4qqMb0IVTmUeCCT8eGA)"
Content-class: urn:content-classes:message
Thread-topic: Combining '+' notation with statuses
Thread-index: AccZ4WxF+E01wN6+Rb6lKRKeD2SVkg==

--Boundary_(ID_BAB4qqMb0IVTmUeCCT8eGA)
Content-type: text/plain; charset=windows-1255
Content-transfer-encoding: 7BIT

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

	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 compatible).
	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."


--Boundary_(ID_BAB4qqMb0IVTmUeCCT8eGA)--