All fair comments. We don't release documentation for each release. site-deploys are independent. And we have perhaps fewer people.
But at the same time I would never want another department to break my build by deploying a snapshot I'm not ready for. Quite possibly we could make more use of snapshots. Did we not start this whole discussion because you wanted artifact resolution to not work transparently with snapshots? i.e. you have to explicitly mention snapshots in the ranges as defined the original maven2 dependency spec. BTW snapshots are not filtered/faulted by the release plugin when defined in ranges, it would appear to work on the defined not resolved dependencies... you have to use the enforcer plugin which works on the resolved tree. cheers -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
