On 10/19/05, Ballard, Ken <[EMAIL PROTECTED]> wrote: > We're periodically deploying SNAPSHOT verions so that developers can work on > projects that depend on projects that are being actively developed and get > the latest changes. It works, but the problem is that with developers using > jar:deploy (or ear:deploy, etc) themselves to deploy their artifacts to the > remote repository, nothing prevents them from deploying artifacts that are > compiled from source that hasn't been checked in. If we have CruiseControl > deploy our SNAPSHOT artifacts then we know everything that is being shared > has been checked in. Does this sound like a best practice or am I missing > the point?
This is the way we have been doing it for about a year now. I haven't noticed any problems. I-- Esse quam videri (to be rather than to seem) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
