On Mon, 2003-07-07 at 12:15, Jason van Zyl wrote: > > > What about deploying (installing) also the POM to the repository, every time > > The POM really only needs to be deployed for releases. I'm not sure it > would be wise to start deploying snapshot POMs though I haven't thought > about it much.
I've thought about it a little. The way I was looking at it was that snapshot artifacts are more-or-less equivalent to tracking the HEAD of CVS for a given project, and so having the snapshot POM deployed to the repository would be needed to automate downloading the current source from CVS if such a facility were to be added to maven. You could also convert a versioned dependency into the corresponding source tree by checking out using the tag in the POM (although that doesn't depend on snapshot POMs). That said, using the POM from an old version of a project might lead to dead links - for example, if a project has moved from one CVS repository to another and the old CVS repository is no-longer available. I can't see that using the most recent POM in the repository is a more correct behaviour, though. We might also think about tightening up the release process that maven implements in its plugins: rather than just building a jar file out of the source tree and copying it somewhere, it maybe should be following the steps in http://maven.apache.org/development/release-process.html as far as tagging things in CVS and building from a freshly exported source tree. -Mark. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
