Salut,
Paul Sandoz wrote:
> Jeanfrancois Arcand wrote:
>> Contains the resolved version. Before doing a release, I'm always
>> executing the following script (there is some maven plug in that can
>> probably do that, but I'm too lazy to learn them :-)). So when I cut a
>> release, I do:
>>
>> % svn copy trunk tags/1_7_3_2
>> % run the followinhg script
>>
>> ======================
>> #!/bin/sh
>> # sed/changeword
>>
>> prog=`basename $0`
>> old=1.7_SNAPSHOT
>> new=1.7.3.2
>> file=pom.xml
>>
>> for FIL in `find . -name $file -exec grep -l $old {} \;`
>> do
>> echo 'Replacing in '$FIL
>> perl -i -pe s/$old/$new/g $FIL
>> done
>> =======================
>> % This steps replace the 1.7-SNAPSHOT by the proper version in all
>> pom.xml file.
>> % svn commit // commit the branch
>> % mvn deploy
>>
>> The mvn deploy is the operation that takes care for me to:
>>
>> (1) Create the remote folders layout on the remote repository
>> (2) Upload the new archetype (*.jar, -source.jar, md5/sha1)
>>
>
> Ah, i see. Got it now.
>
>
>> My release is done. Now every day I've a script that does:
>>
>> % svn checkout
>> % mvn install deploy
>>
>> which upload the -SNAPSHOT.jar to the remote repository.
>>
>
> The last modified dates shown here:
>
> http://download.java.net/maven/2/com/sun/grizzly/grizzly-http-servlet/1.7-SNAPSHOT/
>
>
> for -SNAPSHOT.jar are between the 13th and 26th of March. Is that correct?
Last one is yesterday:
http://download.java.net/maven/2/com/sun/grizzly/grizzly-http-servlet/1.7-SNAPSHOT/grizzly-http-servlet-1.7-20080422.234234-23.jar
Sorry I explained wrong here. There is no -SNAPSHOT when a timestamp used.
A+
-- Jeanfrancois
>
>>>
>>>
>>>> > <dependency>
>>>> > <groupId>com.sun.grizzly</groupId>
>>>> > <artifactId>grizzly-http-servlet</artifactId>
>>>> > <version>1.7-SNAPSHOT</version>
>>>> > </dependency>
>>>>
>>>> This is the nightly build. If you look here
>>>>
>>>> http://download.java.net/maven/2/com/sun/grizzly/grizzly-http-servlet/1.7-SNAPSHOT/
>>>>
>>>>
>>>> You can see Maven add a timestamp at the end to differentiate
>>>> nightly build.
>>>>
>>>
>>> How do you get maven to do that?
>>
>> When adding in your pom.xml:
>>
>> <version>1.7-SNAPSHOT</version>
>>
>> Maven will download the following file:
>>
>> http://download.java.net/maven/2/com/sun/grizzly/grizzly-http-servlet/1.7-SNAPSHOT/maven-metadata.xml
>>
>>
>> Inside that file, you have the information about the lastest SNASPHOT
>> release:
>>
>> <versioning>
>> <snapshot>
>> <timestamp>20080422.234234</timestamp>
>> <buildNumber>23</buildNumber>
>> </snapshot>
>> <lastUpdated>20080422235222</lastUpdated>
>> </versioning>
>>
>> Maven does that for you automatically.
>>
>
> OK.
>
>
> <snip>
>>>
>>> I am looking at the Grizzly maven infrastructure as a model for Jersey.
>>
>> Let me know if I can be of any help. So far our build haven't suffered
>> any problems related to Maven.
>>
>
> Thanks!
> Paul.
>