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? It wouldn't put CruiseControl on the critical path because it wouldn't be used to deploy officially versioned artifacts. Does anyone know of a better way?
Thanks, Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
