Juri, It was a possible work around for the original poster who didnt want to use snap shots.
Although Olivier's suggestion was better, imo. Ben On 5/24/06, Artamonov, Juri <[EMAIL PROTECTED]> wrote:
Also just small question. What is the reason and benefit to have two repositories if released versions can also be with SNAPSHOTS versions? -----Original Message----- From: Artamonov, Juri [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 7:12 PM To: Maven Users List Subject: RE: How to prevent from deploying the same version of artefact twice? Thank you very much, Fay, for your comprehensive answer. Best regards, Juri. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 7:01 PM To: Maven Users List Subject: Re: How to prevent from deploying the same version of artefact twice? Juri, he's suggesting the following approach: 1. Set up a Maven prerelease repository. Your developers etc will deploy artifacts here so they will need read/write access. 2. Set up a Maven release repo. Your developers will only use this repo to pull down dependencies, so they will need read-only access. You will appoint a particular person to be "release repo manager" who will copy artifacts from prerelease over to release repo as needed. Thus, your prerelease repo will be constantly overwritten with each deployment. But the release repo will be the master source of your artifacts. This requires that you do *not* add the pre-release repo in your poms as a repo -- only the release repo. You will only use the pre-release repo as a staging area for built artifacts. Wayne On 5/24/06, ben short <[EMAIL PROTECTED]> wrote: > Juri, > > Im sorry i dont understand what you are asking > > Ben > > On 5/24/06, Artamonov, Juri <[EMAIL PROTECTED]> wrote: > > Hi Ben, > > > > what do you mean under prelease and release sites? What is the site > > here? > > > > > > -----Original Message----- > > From: ben short [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 23, 2006 3:05 PM > > To: Maven Users List > > Subject: Re: How to prevent from deploying the same version of > > artefact twice? > > > > > > Ah i see what you are saying. > > > > Assuming that your developers are using svn ( or other source > > control > > ) in a correct manner, the release plugin should sort you out. > > > > http://maven.apache.org/plugins/maven-release-plugin/introduction.ht > > ml > > > > But i guess if you want to make doubley sure you could have a > > release site and a prerelease site. the developers release to the > > prerelease site and then someone vets the release and if ok moves it > > to the release site. > > > > > > On 5/23/06, Plygawko Dariusz (Centrala PZUSA) <[EMAIL PROTECTED]> > > wrote: > > > Yes, developing should be done using SNAPHOTs. But still from time > > > to time someone will have to deploy "stable" version (without > > > "-SNAPSHOT") and I after it would like to make this file completly > > > safe and "read-only"(automatically). But I don't know how to... > > > > > > -----Original Message----- > > > From: ben short [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, May 23, 2006 12:48 PM > > > To: Maven Users List > > > Subject: Re: How to prevent from deploying the same version of > > > artefact twice? > > > > > > > > > Kind of going against the whole idea of maven then. > > > > > > On 5/23/06, Plygawko Dariusz (Centrala PZUSA) <[EMAIL PROTECTED]> > > > wrote: > > > > Is it possible to workaround this problem if I don't want to use > > > > snapshots? :) > > > > > > > > > > > > -----Original Message----- > > > > From: Wim Deblauwe [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, May 23, 2006 12:14 PM > > > > To: Maven Users List > > > > Subject: Re: How to prevent from deploying the same version of > > > > artefact twice? > > > > > > > > > > > > Use the release plugin, this will automatically change the > > > > version to the next SNAPSHOT version. > > > > > > > > 2006/5/23, dariusz.p <[EMAIL PROTECTED]>: > > > > > > > > > > > > > > > It's possible to overwrite the same version of an artefact > > > > > (when you forget to increment version in pom.xml after you > > > > > changed something in source code). How to prevent from it? I > > > > > use ftp server as internal repository (I > > can > > > > > switch to sth else if it's necessary). I would prefer to fix > > > > > it on > > the > > > > > server side instead of pachting deploy-plugin (there is always > > > > > a > > chance > > > > > that > > > > > someone will have a wrong version of it). We have a big team > > > > > of > > developers > > > > > and I'm affraid we might have some problems with maven > > (uncontrolled > > > > > overwriting). > > > > > > > > > > Thank You a lot in advance, > > > > > Dariusz > > > > > -- > > > > > View this message in context: > > > > > http://www.nabble.com/How+to+prevent+from+deploying+the+same+v > > > > > ersi > > > > > on+of+artefact+twice--t1668061.html#a4520449 > > > > > Sent from the Maven - Users forum at Nabble.com. > > > > > > > > > > > > > > > -------------------------------------------------------------- > > > > > ---- > > > > > --- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------- > > > > ---- > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > --- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > ------------------------------------------------------------------ > > > --- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > -------------------------------------------------------------------- > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -------------------------------------------------------------------- > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -------------------------------------------------------------------- > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
