On 28/03/2008, MATHUS Baptiste <[EMAIL PROTECTED]> wrote: > Hi all, > > Is it already possible with archiva to forbid that a released artifact be > overridden? > I checked the archiva interface, and it seems it doesn't, but I prefer > re-checking here. > > I didn't find any feature request about this in the tracker, I guess this > should be added, shouldn't I?
Not yet, but it is filed: http://jira.codehaus.org/browse/MRM-747 Cheers, Brett > > Thanks a lot. > -- > Baptiste > > -----Message d'origine----- > De : Wayne Fay [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 27 mars 2008 16:22 > À : Maven Users List > Objet : Re: [deploy-plugin] Abort deploy when a target is present > > Others have asked about this previously. I would imagine it is filed in JIRA > if you go look for it. > > The general response is, you can manage the rwx bits on your deployed > artifacts to avoid this happening. Off the top of my head, I think a cron job > that modifies the ACLs for deployed non-snapshot artifacts that runs once an > hour should do it. Or perhaps you could modify the umask for the user that > runs the deploys. Or any number of alternatives. > > Also I would assume the various repo managers are building this > functionality into their products (eg, do not allow to overwrite, return fail > when attempted). > > If you're just using a dumb file repo, you're going to have to be > responsible for this on your own for now, at least until someone gets > inspired to add bits to wagon and other places to support the feature. > > Wayne > > On 3/27/08, Jeff MAURY <[EMAIL PROTECTED]> wrote: > > I think it should be defined at the repository definition level. > > > > Jeff MAURY > > > > On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste <[EMAIL PROTECTED]> wrote: > > > > > Hi all, > > > > > > Recently, some developers did a release manually. So they put a > > > release version in the pom and triggered a deploy. Everything fine but... > > > The thing is: they forgot to re-update the pom.version to a new > > > snapshot version. > > > > > > So, as the code is continuously integrated, at each new commit, the > > > recent release was "automatically" overridden many times with the > > > snapshot code before realizing it :-/. > > > So, what I would like is to be able to put an additional option for > > > maven when run inside the continuous integration server, something > > > like -DdontOverrideRelease, that would make fail the deployment if > > > the released artefact is already present. > > > > > > I've taken a quick look at > > > http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html > > > but it seems it's not currently possible. > > > What do you think? Can a file an feature request about it in the > > > plugin tracker? > > > > > > Thanks a lot. > > > > > > Cheers. > > > -- > > > Baptiste > > > > > > > > > > > > -- > > La mélancolie c'est communiste > > Tout le monde y a droit de temps en temps La mélancolie n'est pas > > capitaliste C'est même gratuit pour les perdants La mélancolie c'est > > pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça > > existe Elle se prend même avec des gants La mélancolie c'est pour les > > syndicalistes Il faut juste sa carte de permanent > > > > Miossec (2006) > > > > http://www.jeffmaury.com > > http://riadiscuss.jeffmaury.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Brett Porter Blog: http://blogs.exist.com/bporter/
