Some ideas: One thing you could do is to use different repositories. A promotion can maybe be base on an install task. You can maybe even try to use a dual resolver to keep your jar in an unpromoted repository, and put the ivy.xml into other repositories.
An other idea might be to have you continuous build deploying modules with organisation like 'myorg.continuous'. Then when you want to promote it, you could release an ivy.xml without artefact in 'myorg.release' that only depends the corresponding module in 'myorg.continuous'. My 2c. Gilles > -----Original Message----- > From: Niklas Matthies [mailto:[EMAIL PROTECTED] > Sent: lundi 10 décembre 2007 12:26 > To: [email protected] > Subject: Status promotion > > On the Best Practices page, "Dealing with integration versions" talks > about promoting the status of builds, but remains pretty vague on how > to go about this. Ideally, we'd like to simply relabel (or copy) the > tested build of a module to a better status. Is there a recommended > way how to do this? > > Side note: We'd like to avoid to actually re-build the artifacts of > the module, since it introduces an unnecessary risk of the build not > being 100% the same after all. > > -- Niklas Matthies
