On 1/12/06, Martin van der Plas <[EMAIL PROTECTED]> wrote: > Hi, > > It occurs to me from the commands below that maven 2.0.1 has > dependencies to alpha and beta releases.
The alphas and betas are all projects that the Maven developers are involved in. They are in that state because they are not in API lockdown and sufficiently documented for *independant* use. However, the combination is tested and the release of Maven itself will remain backwards compatible unless otherwise noted. Alphas and betas are still tagged. That said, this is high on the list to fix. Wagon is nearing a stable state. Doxia and SCM have received recent work. Some of the others were plugins. Some plugins have had final releases, some have not, and there will always be new plugin releases coming along. In future, alphas will not be released to users by default. > Should a non-snapshot release of maven or any other project depend on > snapshot releases? Definitely not. There are no snapshot releases in distributions as they are not reproducible. > I ask this question because we don't seem to get consistent behaviour of > maven. In our group of > 10 developers some people can sucessfully build > while others can't because of missing artifacts. They all use the same > codebase and settings.xml. Can you provide more details? Are these missing artifacts from your build, or plugins? Usually the cause of this is ibiblio timing out and retrying corrects the problem. We'd definitely like to correct any issues with reproducibility. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
