On Fri, Mar 28, 2008 at 4:42 PM, Brown, Carlton < [EMAIL PROTECTED]> wrote:
> In an environment I'm working on, there is a convention to use the > special revision number 0.0 to designate a trunk build. What would be > a valid technique to specify that 0.0.* is a later revision than 1.0, > 2.0, etc? I considered designating 0.0 as a specialMeaning attribute > of a latest-revision, but I thought it may match any revision containing > 0.0, such as 2.0.0. How would that work, does it support regex? > > I'm aware it would be much easier not to use 0.0 as the latest revision, > but it's an established convention in this environment and there are a > number of processes that depend on it. Using special meaning won't work, because they are used only after the version is split (by this expression: [\._\-\+] ). Hence the easiest way is to implement your own latest strategy, which extends LatestRevision and only overrides the default behaviour when you find a 0.0 revision. Xavier > > > > > ----------------------------------------- > ==================================================== > This message contains PRIVILEGED and CONFIDENTIAL > information that is intended only for use by the > named recipient. If you are not the named recipient, > any disclosure, dissemination, or action based on > the contents of this message is prohibited. In such > case please notify us and destroy and delete all > copies of this transmission. Thank you. > ==================================================== -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
