Re: Proposal to change the tooling version to be 3.0-incubating-SNAPSHOT
Instead of hand carving the version changes through the files. It could be more elegantly written as find . -type f -name '*.xml' -or -name '*.properties' | xargs -l1 grep -l SNAPSHOT | xargs -l1 perl -pi.backup -s 's/(3.0-incubating-SNAPSHOT|3.0-SNAPSHOT|1.0-i ncubating-SNAPSHOT)/3.0-2006-08-02-r427980/' Which can be translated as # # Find all the files that end in XML or properties # find . -type f -name '*.xml' -or -name '*.properties' \ # # filter so we ONLY get the ones that contain the word SNAPSHOT # but just list the file .. (don't grep it's contents) # xargs is a magic little "streamliner" that takes a list and # feeds them into the command that follows, it has a magic option of # -l1, meaning .. 1 at a time .. # xargs -l1 grep -l SNAPSHOT \ # # now do the textual replacement in that file that we have found. # use perl, which we also backup the file before it makes the change # -pi.backup (eg: pom.xml.backup) # # The regexp says, change any occurence of 3.0-incubating-SNAPSHOT, or or # to the version string "3.0-2006-08-02-r427980" # xargs -l1 perl -pi.backup -s 's/(3.0-incubating-SNAPSHOT|3.0-SNAPSHOT|1.0-i ncubating-SNAPSHOT)/3.0-2006-08-02-r427980/' hope that is a little clearer :-) cheers ramon Guillaume Nodet wrote: Wow, thx. I don't understand what it does, but i will try it :) On 8/9/06, Ramon Buckland <[EMAIL PROTECTED]> wrote: +1 here also Here is what I use to do it :-) grep -lR SNAPSHOT * | egrep "(xml|properties)$" | xargs -l1 -iXX perl -pi.sm-b4-IC-change.incubating.orig -e 's/(3.0-incubating-SNAPSHOT|3.0-SNAPSHOT|1.0-i ncubating-SNAPSHOT)/3.0-2006-08-02-r427980/' XX Philip Dodds wrote: > +1 for having everthing sync up on 3.0 > > P > > On 8/8/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> >> I was wondering if we should change the maven plugin / archetype version >> to >> be in sync with the container / components. >> Currently, everything as the same release cycle, so I do not really see >> the >> point in having a 3.0 for container and 1.0 for >> tooling. I think it may be confusing for users. >> >> -- >> Cheers, >> Guillaume Nodet >> >> >
Re: Proposal to change the tooling version to be 3.0-incubating-SNAPSHOT
Wow, thx. I don't understand what it does, but i will try it :) On 8/9/06, Ramon Buckland <[EMAIL PROTECTED]> wrote: +1 here also Here is what I use to do it :-) grep -lR SNAPSHOT * | egrep "(xml|properties)$" | xargs -l1 -iXX perl -pi.sm-b4-IC-change.incubating.orig -e 's/(3.0-incubating-SNAPSHOT|3.0-SNAPSHOT|1.0-i ncubating-SNAPSHOT)/3.0-2006-08-02-r427980/' XX Philip Dodds wrote: > +1 for having everthing sync up on 3.0 > > P > > On 8/8/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> >> I was wondering if we should change the maven plugin / archetype version >> to >> be in sync with the container / components. >> Currently, everything as the same release cycle, so I do not really see >> the >> point in having a 3.0 for container and 1.0 for >> tooling. I think it may be confusing for users. >> >> -- >> Cheers, >> Guillaume Nodet >> >> > -- Cheers, Guillaume Nodet
Re: Proposal to change the tooling version to be 3.0-incubating-SNAPSHOT
+1 here also Here is what I use to do it :-) grep -lR SNAPSHOT * | egrep "(xml|properties)$" | xargs -l1 -iXX perl -pi.sm-b4-IC-change.incubating.orig -e 's/(3.0-incubating-SNAPSHOT|3.0-SNAPSHOT|1.0-i ncubating-SNAPSHOT)/3.0-2006-08-02-r427980/' XX Philip Dodds wrote: +1 for having everthing sync up on 3.0 P On 8/8/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: I was wondering if we should change the maven plugin / archetype version to be in sync with the container / components. Currently, everything as the same release cycle, so I do not really see the point in having a 3.0 for container and 1.0 for tooling. I think it may be confusing for users. -- Cheers, Guillaume Nodet
Re: Proposal to change the tooling version to be 3.0-incubating-SNAPSHOT
+1 for having everthing sync up on 3.0 P On 8/8/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: I was wondering if we should change the maven plugin / archetype version to be in sync with the container / components. Currently, everything as the same release cycle, so I do not really see the point in having a 3.0 for container and 1.0 for tooling. I think it may be confusing for users. -- Cheers, Guillaume Nodet
Proposal to change the tooling version to be 3.0-incubating-SNAPSHOT
I was wondering if we should change the maven plugin / archetype version to be in sync with the container / components. Currently, everything as the same release cycle, so I do not really see the point in having a 3.0 for container and 1.0 for tooling. I think it may be confusing for users. -- Cheers, Guillaume Nodet
