The thing about doing this on the user side is (as always) that you can't really be 100% sure it's taking place. Doing it on the server is safer.
Regarding Nexus and allowing the role to update the metadata file: It (the metdata file) has to be updated when you add new artifacts. So the role of the person deploying the new artifact must have that permission. /Anders On Wed, Sep 9, 2009 at 07:11, Arnaud Bailly <[email protected]> wrote: > Thanks for the answers. I already thought about using nexus management > rights as a possible solution, but was looking for a client-based > solution (ie. more along the MDEPLOY-74). I can see from > > http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-target-is-present-to16329568s177.html#a16353467 > that this feature is in 2.1 and I will check this. > > About the proposed solution in Nexus, I was wondering why the created > role still allow update permission of metadata (this may be more a > nexus question...)? It seems rather odd to me as this seems to imply > metadata > would not be in sync with the real artifacts, but I am surely missing > something. > > Regards, > -- > Arnaud Bailly -- OQube > <software engineering> > http://www.oqube.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
