Also, i was thinking that a good bit of info to relay is the hudson build
number (in cases where hudson is doing the building), setting it also to -1
when building locally.
On Tue, Nov 16, 2010 at 1:44 PM, Justin Deoliveira <[email protected]>wrote:
>
>
> On Tue, Nov 16, 2010 at 1:41 PM, Andrea Aime <[email protected]
> > wrote:
>
>> On Tue, Nov 16, 2010 at 8:10 PM, Justin Deoliveira <[email protected]>
>> wrote:
>> > Hi all,
>> > Recently on geoserver-devel we have been discussing adding some
>> versioning
>> > information to build artifacts. This is most important for geoserver
>> when it
>> > comes to nightly builds because currently when someone grabs a nightly
>> build
>> > they really have no idea what version of geotools is included in it. I
>> would
>> > think conveying such information would be of use to any project that
>> depends
>> > on geotools, not just geoserver.
>> > So, I would like to make some modifications to the geotools build
>> process to
>> > add this information. Things to capture at this point are the svn
>> revision,
>> > the build timestamp, and the project version. Open to ideas of what else
>> to
>> > include.
>> > So the main idea will be to add this information to the manifest of each
>> > individual jar file that gets created. So a resulting manifest would
>> look
>> > like this:
>> > Manifest-Version: 1.0
>> > Archiver-Version: Plexus Archiver
>> > Created-By: Apache Maven
>> > Built-By: jdeolive
>> > Build-Jdk: 1.5.0_19
>> > Project-Version: 2.7-SNAPSHOT
>> > Build-Timestamp: 20101116-1134
>> > Svn-Revision: 36212
>> > The second part is to add VERSION.txt file to all the build release
>> > artifacts. Which will look something like this:
>> > version: 2.7-SNAPSHOT
>> > svn revision: 36212
>> > build date : 20101116-1134
>> > What do people think. I created a patch here that does the work:
>> > http://jira.codehaus.org/browse/GEOT-3319
>>
>> I did not inspect the patch myself but I like what I see result wise. +1!
>>
>> Only one question: what happens if you run that with a git checkout?
>> Does it work anyways, or it ends up breaking the build?
>> If it's the latter, can we activate svn revision number tracking with
>> a profile?
>>
>
> Good question. It results in an svn revision of -1. But won't break the
> build at all. So with this patch any devs building from a git repo won't
> have svn information... do you think that is ok?
>
>>
>> Cheers
>> Andrea
>>
>> -----------------------------------------------------
>> Ing. Andrea Aime
>> Senior Software Engineer
>>
>> GeoSolutions S.A.S.
>> Via Poggio alle Viti 1187
>> 55054 Massarosa (LU)
>> Italy
>>
>> phone: +39 0584962313
>> fax: +39 0584962313
>>
>> http://www.geo-solutions.it
>> http://geo-solutions.blogspot.com/
>> http://www.linkedin.com/in/andreaaime
>> http://twitter.com/geowolf
>>
>> -----------------------------------------------------
>>
>
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
