buildnumber retrieves wrong ivy.revision - ignore status
(milestone/release/integration)
----------------------------------------------------------------------------------------
Key: IVY-449
URL: https://issues.apache.org/jira/browse/IVY-449
Project: Ivy
Issue Type: Improvement
Components: Ant
Affects Versions: 1.4.1
Environment: WIndows, jdk 1.5.0.11, ivy1.4.1
Reporter: Daniel Schwager
Hi,
i want to use use ivy:buildnumber to determine
the next RELEASE-revision.
In my ivy-repository, i will find 3 version of mymod:
1.2 (release)
1.3-dev20070326125300 (integration)
1.3-RC1 (milestone)
I want buildnumber to determine the next RELEASE, means 1.3.
If i try
<ivy:buildnumber
organisation="myorg"
module="mymod"
revision="1." revSep="." defaultBuildNumber="1"
prefix="base"/>
i get alway the revision 1.4. How can i tell the task to use
only the "latest.release" as the searchbase ?
---------- <Answer from mailinglist >--------------------------------------
I'm afraid the buildnumber task cannot do what you want for the moment. Open a
JIRA improvement if you want.
For the moment, the only solution I see except writing your own task or
patching the buildnumber task, is to separate your revisions in different
repositories: one repository for releases, and another for milestones, and
another for integration builds. Then you can use specific settings (ivyconf) to
use only the release repo when you want to get your new release number. I don't
know if it's possible in your case, but it's a good practice to separate them
anyway.
- Xavier
---------- </Answer from mailinglist >--------------------------------------
Maybe a fix to the task:
- include the attribute 'status' (like integration, milestone, release)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
