On 10/17/07, Alex Mayorga Adame <[EMAIL PROTECTED]> wrote: > Is there a way to prevent the deployment of a file of artifact, using the > deploy plug-in, when the same file or artifact is already on the remote > repository?
Seems to me that would best (most reliably) be done by the remote repo. The simplest way would just be changing the file system permissions. (Leave the metadata files writeable, they get changed when a new version is deployed.) I think Archiva (repository manager) might already have this as a configurable option. If not it's probably in JIRA, I know we've talked about it. The deploy plugin could probably be convinced to check, though. I think it does grab the existing metadata in order to add the new version, so it should know if the version is already there. What problem are you actually trying to solve with this? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
