Thanks for your response... Another question, if I may... Do you chain your repositories together? (For example, your integration build might use a chain consisting of final, release, integration, returning the last found).
Also, what's your versioning scheme? As I mentioned earlier, namespaces don't seem to transform revision names, so how would you solve the problem of retaining, say, 1.0.0-rc3 as 1.0.0-final in another repository? Or do you just not worry about this? -----Original Message----- From: Gilles Scokart [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2008 6:46 AM To: [email protected] Subject: Re: Common practices for lifecycle and promotion in Ivy At work we use different repository for different stages of the lifecycle. A promotion is done by installing a jar into the next repository. 2008/10/15 Brown, Carlton <[EMAIL PROTECTED]>: > I'm curious if anyone has any good practices for implementing a full > module lifecycle in Ivy, including promoting an artifact from release > candidate status to final status, and sharing artifacts across projects. > I've read Mathias's document already and I'm wondering if anyone else > has anything to add. > > How does the Ivy project itself use Ivy? > > Thanks, > Carlton > > > > ----------------------------------------- > ==================================================== > 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. > ==================================================== -- Gilles Scokart
