rock on.
How are you going to implement? I'm presuming you also don't want to
download the previous artifact, so either will trust the metadata, or
maybe have a wagon.exists() method check that can HEAD the file on
HTTP and (whatever else) on the others?
- Brett
On 19/10/2007, at 3:28 PM, Jason van Zyl wrote:
I've been working on some release/deployment tools lately for a
client and I modified their deployments so that you could not
accidentally release the same version of an artifact more then
once. I can stop this on the server side only when running a
repository manager, but we have some simple Apache servers that are
DAV enables and someone release an artifact with the same version
by mistake and wreaked havoc for 4 hours.
I think this one is pretty obvious, I'm not going to write a
proposal I'm just going to fix it because it's not very bright that
we allow the re-release of something that already has been. I'll
leave a option to redeploy if you so choose in the event the driver
knows what he's doing.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
