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

[Brett Porter]

Hi,
Stephen Nesbitt wrote:
 

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 specify
more than one remote repository, you get the newest which should
be correct.
   

Not sure I follow here. Most of the time developers will work 
against the artifacts in the QA repository. In some instances they 
will want to work against QA artifacts except for those artifacts 
associated with a specific group (or possibly a specific artifact). 
Using a simple list of repositories with first one that matches 
wins won't work(unless there is a way to tag an artifact with a 
user specified identifier)
 

I'm still not sure what you need here. When you use a SNAPSHOT, it is 
not first wins, but newest - all are checked.

But you talk about changing repositories per group - aren't the 
repositories paritioned enough such that the set of groups affected have 
their own?
I'm thinking you might be talking about a release management issue more 
than this. If they are using one from 'bleeding edge' and the rest from 
'QA', maybe
QA should be somewhere where the version is incremented to a 
pre-release, and they change their dependencies to that.

If this is incorrect, can you spell out an example we can work through?
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]