On 17/03/2009, at 8:57 PM, <[email protected]> <[email protected]
> wrote:
The problem is that Archiva accepts deployments of artifacts that
already exist in the repository. I have already modified the code in
the
UploadAction class to block off any duplicates via the upload
section on
the Archiva UI and now I am trying to do the same for Webdav. I am
open
for suggestions if anyone has some, because it seems like doing the
same
for deployments via Webdav is going to be a tough hack.
ArchivaDavResource has an addMember resource that takes care of this,
so you can make the modification there.
If you are able to also add some configuration on the managed
repository as to whether it should allow this or not, this would be a
great change to contribute back. Will you be able to submit a patch
for your changes?
Cheers,
Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
