Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 15157 invoked from network); 16 Jun 2006 14:18:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jun 2006 14:18:10 -0000 Received: (qmail 59376 invoked by uid 500); 16 Jun 2006 14:18:09 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 59362 invoked by uid 500); 16 Jun 2006 14:18:08 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Delivered-To: moderator for continuum-users@maven.apache.org Received: (qmail 58609 invoked by uid 99); 16 Jun 2006 13:27:26 -0000 X-ASF-Spam-Status: No, hits=0.8 required=10.0 tests=EXTRA_MPART_TYPE,HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of john.goyer@motricity.com designates 66.179.161.10 as permitted sender) X-ASG-Debug-ID: 1150464422-22078-524-0 X-Barracuda-URL: http://66.179.161.10:8000/cgi-bin/mark.cgi X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C69148.D1990E88" X-ASG-Orig-Subj: Re: Build Version Numbering Subject: Re: Build Version Numbering Date: Fri, 16 Jun 2006 09:26:59 -0400 Message-ID: <661AC1D6951B6C41BDD522EA6107669702A44BBC@callisto> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Build Version Numbering thread-index: AcaRSIv/R6jXeZu4Qi6J59Z/OX6nJw== From: "John Goyer" To: X-Virus-Scanned: by Motricity Mail Gateway at motricity.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C69148.D1990E88 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C69148.D1990E88" ------_=_NextPart_002_01C69148.D1990E88 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable How do I tag a build on success? I am using maven2 and would like to=20 make a new tag after each build that succeeds. I would also like to=20 include a version number (preferred) or date/timestamp in the tag. =20 =20 only builds in succes have a continuum build number. =20 Adam Leggett a =EF=BF=BDcrit : > Thanks Emmanuel, >=20 > I want to display the build version in the built application. The app = is a java gui installer. =20 > My M2 build binds antrun to package phase which invokes an ant = buildfile. The ant build reads the version number property and includes it in the application. >=20 > Im not looking to define a continuum build number. Im just wondering = if all builds (success and failure) could be numbered. >=20 > Thanks >=20 > Adam >=20 > -----Original Message----- > From: Emmanuel Venisse [mailto:emmanuel@venisse.net]=20 > Sent: Friday, June 16, 2006 12:40 PM > To: continuum-users@maven.apache.org > Subject: Re: Build Version Numbering >=20 >=20 > it isn't possible actually to define your own build number in = continuum. The build number generated=20 > by continuum is an internal number. >=20 > what is the interest of your version.properties file? Do you use it in = your code? >=20 > You can tag your code after each success build. >=20 > Emmanuel >=20 > Adam Leggett a =EF=BF=BDcrit : >> Hi all, >>=20 >> I have added a versioning profile to a Maven 2 pom as follows >>=20 >> >> >> version-increment >> =20 >> >> >> =20 >> maven-antrun-plugin >> >> >> =20 >> increment version >> =20 >> generate-sources >> =20 >> >> =20 >> >> =20 >> > classname=3D"ch.oscg.jreleaseinfo.anttask.JReleaseInfoAntTask" >> classpath=3D"maven.plugin.dependency.classpath"> >> >> =20 >> > packageName=3D"uk.co.upco.engage" =20 >> targetDir=3D"${project.build.directory}" >> buildNumFile=3D"${basedir}/version.properties" >> buildNumProperty=3D"buildnum"> >> =20 >> >> =20 >> >> >> =20 >> run >> >> >> >> =20 >> >> =20 >> maven-scm-plugin >> >> >> =20 >> package >> >> =20 >> version.properties >> =20 >> incremented build version >> >> >> =20 >> checkin >> >> >> >> >> >> =20 >> >> >>=20 >> This allows me to display the build version of my app when its=20 >> packaged. I'd like to tie this to my continuum builds somehow. If = only=20 >> continuum runs the profile, it does the increment and checks in the=20 >> version number. I'd like to match the version number to continuums = own=20 >> build number, but I cant figure how to do this. >>=20 >> Continuum seems to >> a) not list failed builds with an id and >> b) log the builds with a different id e.g. my m2 project build#5 is >> logged as 135.log.txt >>=20 >> Does anyone have an idea of how to best approach this issue of=20 >> versioning builds with continuum? >>=20 >> TIA >>=20 >> Adam >>=20 >> Adam Leggett >> Senior Consultant >> UPCO >> Direct Line: 0113 20 10 631 >> Fax: 0113 20 10 666 >> >>=20 >>=20 >>=20 >>=20 >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> =3D=3D=3D=3D=3D >> The contents of this email are intended for the named addresses and = may=20 >> contain confidential and/or privileged material. If received in = error,=20 >> please contact UPCO head office on +44(0)113 201 0600 and then delete = >> the entire mail from your system. Unauthorised review, distribution,=20 >> disclosure or other use of information could constitute a breach of=20 >> confidence. Your co-operation in this matter is greatly appreciated. >>=20 >> Every effort has been taken to ensure that this email and any >> attachments are virus-free. However, UPCO does not make any warranty=20 >> to this effect, and is not liable for any damage done by an infected=20 >> email message or attachment. UPCO recommends that all emails and=20 >> attachments are checked before opening. >>=20 >> All views or opinions expressed in this electronic message and its >> attachements are those of the sender and do not necessarily reflect=20 >> the views and opinions of The Ultimate People Company Ltd. >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >>=20 >>=20 >>=20 >>=20 >>=20 >=20 >=20 >=20 John Goyer Software Engineer =20 (919)=20 (919) 287-7401 - fax www.motricity.com =20 view corporate video =20 =20 NOTICE: This e-mail message is for the sole use of the intended = recipient(s) and may contain confidential and privileged information of = Motricity. Any unauthorized review, use, disclosure or distribution is = prohibited. If you are not the intended recipient, please contact the = sender by reply e-mail and destroy all copies of the original message. ------_=_NextPart_002_01C69148.D1990E88 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable 
How do I tag a build on success? I am using =
maven2 and would like to 
make a =
new tag after each build that succeeds.  I would also like to =

include a =
version number (preferred) or date/timestamp in the =
tag.
 
 
only =
builds in succes have a continuum build =
number.
 
Adam =
Leggett a =EF=BF=BDcrit :
> =
Thanks Emmanuel,
> =

> I =
want to display the build version in the built application. The app is a =
java gui installer.
 
> My =
M2 build binds antrun to package phase which invokes an ant buildfile. =
The ant build
reads the =
version number property and includes it in the =
application.
> =

> Im =
not looking to define a continuum build number. Im just wondering if all =
builds (success
and =
failure) could be numbered.
> =

> =
Thanks
> =

> =
Adam
> =

> =
-----Original Message-----
> =
From: Emmanuel Venisse [mailto:emmanuel@venisse.net] =

> =
Sent: Friday, June 16, 2006 12:40 =
PM
> To: =
continuum-users@maven.apache.org
> =
Subject: Re: Build Version =
Numbering
> =

> =

> it =
isn't possible actually to define your own build number in continuum. =
The build number
generated =

> by =
continuum is an internal =
number.
> =

> what =
is the interest of your version.properties file? Do you use it in your =
code?
> =

> You =
can tag your code after each success =
build.
> =

> =
Emmanuel
> =

> Adam =
Leggett a =EF=BF=BDcrit :
>> =
Hi all,
>> 
<= pre>>> = I have added a versioning profile to a Maven 2 pom as = follows
>> 
<= pre>>> = <profiles>
>>  =
           <profile>
>>  =
                   =
<id>version-increment</id>
>> = <build> = 
>>  =
                           =
<plugins>
>>  =
                                  =
<plugin>
>>  =
    
>> =
<artifactId>maven-antrun-plugin</artifactId>
>>  =
                                          =
<executions>
>>  =
                                                 =
<execution>
>>  =
    
>> =
<id>increment =
version</id>
>>  =
    
>> =
<phase>generate-sources</phase>
>>  =
    
>> =
<configuration>
>>  =
    
>> =
<tasks>
>>  =
    
>> =
<taskdef name=3D"jreleaseinfo" =

>> =
classname=3D"ch.oscg.jreleaseinfo.anttask.JReleaseInfoAntTask"<=
o:p>
>> =
classpath=3D"maven.plugin.dependency.classpath"><=
/span>
>> =
</taskdef>
>>  =
    
>> =
<jreleaseinfo className=3D"SimpleVersionInfo" =

>> =
packageName=3D"uk.co.upco.engage"  =

>> =
targetDir=3D"${project.build.directory}"
>>  =
buildNumFile=3D"${basedir}/version.properties"
>>  =
buildNumProperty=3D"buildnum"></jreleaseinfo>
>>  =
    
>> =
</tasks>
>>  =
    
>> =
</configuration>
>>  =
                                                         =
<goals>
>>  =
    
>> =
<goal>run</goal>
>>  =
                                                         =
</goals>
>>  =
                                                 =
</execution>
>>  =
                                          =
</executions>
>>  =
                                  </plugin>      =

>>  =
                                  =
<plugin>
>>  =
    
>> =
<artifactId>maven-scm-plugin</artifactId>
>>  =
                                        =
<executions>
>>  =
                                                =
<execution>
>>  =
    
>> =
<phase>package</phase>
>>  =
                                                 =
<configuration>
>>  =
    
>> =
<includes>version.properties</includes>
>>  =
    
>> =
<message>incremented build =
version</message>
>>  =
                                                 =
</configuration>
>>  =
                                                 =
<goals>
>>  =
    
>> =
<goal>checkin</goal>
>>  =
                                                 =
</goals>
>>  =
                                               =
</execution>
>>  =
                                      =
</executions>
>>  =
                                    =
</plugin>
>>  =
                           =
</plugins>
>>  =
                   </build>       =

>>  =
           </profile>
>>  =
    </profiles>
>> 
<=
pre>>> =
This allows me to display the build version of my app when its =

>> =
packaged. I'd like to tie this to my continuum builds somehow. If only =

>> =
continuum runs the profile, it does the increment and checks in the =

>> =
version number. I'd like to match the version number to continuums own =

>> =
build number, but I cant figure how to do =
this.
>> 
<= pre>>> = Continuum seems to
>> =
a) not list failed builds with an id =
and
>> =
b) log the builds with a different id e.g. my m2 project build#5 =
is
>> =
logged as 135.log.txt
>> 
<= pre>>> = Does anyone have an idea of how to best approach this issue of = 
>> =
versioning builds with =
continuum?
>> 
<= pre>>> = TIA
>> 
<= pre>>> = Adam
>> 
<= pre>>> = Adam Leggett = <adam.leggett@upco.co.uk>
>> =
Senior Consultant
>> =
UPCO
>> =
Direct Line: 0113 20 10 631
>> =
Fax: 0113 20 10 666
>> =
<http://www.upco.co.uk>
>> 
<= pre>>> <= pre>>> <= pre>>> <= pre>>> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> =
=3D=3D=3D=3D=3D
>> =
The contents of this email are intended for the named addresses and may =

>> =
contain confidential and/or privileged material. If received in error, =

>> =
please contact UPCO head office on +44(0)113 201 0600 and then delete =

>> =
the entire mail from your system. Unauthorised review, distribution, =

>> =
disclosure or other use of information could constitute a breach of =

>> =
confidence. Your co-operation in this matter is greatly =
appreciated.
>> 
<= pre>>> = Every effort has been taken to ensure that this email and = any
>> =
attachments are virus-free. However, UPCO does not make any warranty =

>> =
to this effect, and is not liable for any damage done by an infected =

>> =
email message or attachment. UPCO recommends that all emails and =

>> =
attachments are checked before =
opening.
>> 
<= pre>>> = All views or opinions expressed in this electronic message and = its
>> =
attachements are those of the sender and do not necessarily reflect =

>> =
the views and opinions of The Ultimate People Company =
Ltd.
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

>> 
<= pre>>> <= pre>>> <= pre>>> <= pre>>> <= pre>> = 
> =

> =


John = Goyer
Software = Engineer
3DMotricity
(919)
(919) 287-7401 - fax
www.motricity.com
view corporate video =

 

NOTICE:  This e-mail message is for the sole use of = the intended recipient(s) and may contain confidential and privileged = information of Motricity.  Any unauthorized review, use, disclosure = or distribution is prohibited.  If you are not the intended = recipient, please contact the sender by reply e-mail and destroy all = copies of the original message.

------_=_NextPart_002_01C69148.D1990E88-- ------_=_NextPart_001_01C69148.D1990E88--