Re: [PROPOSAL] Ading a new tag to ?

2004-11-23 Thread Stephen Nesbitt
rift. Bottom line - a single repository using version identifiers will work so long as: 1) maven can distinguish between a release version, a QA version and a bleeding edge version based on the version tag 2) there is some mech

Re: different repositories WAS: [PROPOSAL] Ading a new tag to ?

2004-11-23 Thread Stephen Nesbitt
eloper can simply indicate they want bleeding edge of m2. If you would like me to write up something formal as a summary, I'd be glad to do so. -steve -- Stephen Nesbitt Senior Configuration Management Engineer The Cobalt Group 206.219.8271 [EMAIL PROTECTED] --

Re: [PROPOSAL] Ading a new tag to ?

2004-11-23 Thread Stephen Nesbitt
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

Re: [PROPOSAL] Ading a new tag to ?

2004-11-23 Thread Stephen Nesbitt
On Tuesday 23 November 2004 04:46, Brett Porter wrote: Hi Brett. You suggested I dive in so I'm going to > > I think this situation is best covered by publishing to different > repositories for each, and then only utilising the remote > repositories appropriate when building. IF you happen to sp

Re: [PROPOSAL] Ading a new tag to ?

2004-11-23 Thread Stephen Nesbitt
x27;m not sure just how much of an edge case this is, but I do think it is important to have some sort of answer (even if it is a manual process of updating your local repo directly) -steve -- Stephen Nesbitt Senior Configuration Management Engineer Th

Re: [PROPOSAL] Ading a new tag to ?

2004-11-22 Thread Stephen Nesbitt
ed that Jörg Schaible's post kinda made the same point with the suggestion of a tag in the dependency element. Hows does any of this fit into"in situ" artifacts? -steve Stephen Nesbitt Senior Configuration Management E