On Tuesday 23 November 2004 13:24, Jason van Zyl wrote: > On Tue, 2004-11-23 at 12:17, Stephen Nesbitt wrote: > > Not sure I follow here. Most of the time developers will work > > against the artifacts in the QA repository. > > I'm watching this conversation but I'll jump in here with a > question. Why do you need a separate repository for QA artifacts? > At the moment I'm doing some analysis in a development centre > that has your typical dev/QA/Production setup and I don't see a > need for a separate repository per se.
<snip> > Why does it need to be so complicated. Sorry, I just find that > people tend to make things more complicated for themselves than > required. So you need to use artifacts produced by QA: it's > certainly not a technical requirement that they be in a separate > repository. Are you dealing with policy here? I'm just curious > because I have some of the same problems to deal with where I am > at the moment. Jason, you are absolutely correct - the requirement is *not* separate repositories. I think the fundamental requirement is the ability to classify artifacts and to select artifacts based on classification. As I understand it now, maven supports two "classifications" - released(has a version number) and snapshot (latest). That's not rich enough for our needs. (Indeed I'm not sure snapshot is truly a category, it's more a specifier within a classification). Here are my dependency use cases: 1) set artifact/group to released version of an artifact/group 2) set artifact/group to latest release of an artifact/group 3) set artifact/group to specific version released to QA 4) set artifact/group to latest version released to QA 5) set artifact/group to latest bleeding edge version How those versions are stored is really a design decision and, as you said, should be kept as simple as possible. Sorry for the long reply, but it's nice to have a chance to discuss issues I have been chewing on for years. -steve -- Stephen Nesbitt Senior Configuration Management Engineer The Cobalt Group 206.219.8271 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
