Re: [Geotools-devel] trunk build instabilities

[Rob A. <ro...@so...>]

Martin Desruisseaux wrote:
> Rob Atkinson a écrit :
>   
>> is anyone else having build problems at the moment?
>>     
>
> It work fine for me (Linux, Java 1.4, Maven 2.0.6). Just tried a fresh "mvn
> clean", "mvn install" with revision 25647.
>
>
>   
>> Some issues reported to me - someone with a clean machine trying to
>> build geoserver trunk, and some myself with state of  geoserver trunk.
>>     
>
> I have build Geoserver trunk last week with success (revision 6590). But I do
> not relies on the JAR deployed on Maven. I build Geotools first (so latest
> Geotools JAR are installed in my local Maven repository), then Geoserver.
>
>   
me too, which is why the report came from someone who tried just 
geoserver - i never saw that problem.
> Maybe we just need a volunter for deploying Geotools 2.4-SNAPSHOT jars on the
> Refractions repository? It should just be a matter of running "mvn deploy" on
> Geotools trunk - nothing else to do on a properly configured system. I can do
> that, but do we have a policy on the frequency of 2.4-SNAPSHOT deployment, and
> about who should do them?
>
>   
Yep - at the very least, we should decide if we are allowed to commit to 
geoserver trunk things that rely on updates to geotools?  either way is 
workable - if you work on geoserver trunk then working on geotools trunk 
may not be such a burden. But not being clear is an issue.

Pros and cons..

Stable branches obviously need the geotools libraries deployed. Sticking 
with a sinlge mechanism is easier.
On the other hand, everyone with commit rights to geoserver and 
getotools needs to be able to deploy geotools,unless it is automatically 
built and deployed as a snapshot.

RA
> 	Martin
>
>