Hi al,
this is just a short notice that I'm about to make GeoServer's master
branch track GWC 1.3-SNAPSHOT, now that 2.2.x is a stable branch and
will continue to track a released GWC version, this will open the
opportunity to commit some fixes to master and be tested there before
back porting to the stable branch.
Cheers,
Gabriel
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Sounds good to me. +1
On Tue, Jul 24, 2012 at 7:46 AM, Gabriel Roldan <groldan@anonymised.com> wrote:
Hi al,
this is just a short notice that I’m about to make GeoServer’s master
branch track GWC 1.3-SNAPSHOT, now that 2.2.x is a stable branch and
will continue to track a released GWC version, this will open the
opportunity to commit some fixes to master and be tested there before
back porting to the stable branch.Cheers,
Gabriel–
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Oh no!
-0.
I always have had major problems with GWC snapshots going stale and breaking my builds, requiring
rm -rf ~/.m2/repository/org/geowebcache/
to get things working again. When trunk (now master) was changed to depend on 1.3-RC3 , it was a great relief and these problems no longer occurred.
Furthermore, now that GeoServer has no snapshot dependencies for the profiles I build except GeoTools, I can build GeoTools and then GeoServer with the "-nsu" flag (no snapshot updates, new in Maven 3.0.4) for improved performance and safety from race conditions between local and remote GeoTools builds.
Can I ask you to reconsider? Would releasing milestones meet your development needs? If you feel really strongly about it, I can start building GWC as well to preserve my snapshots-are-always-local pattern, so I am sure I will survive.
Kind regards,
Ben.
On 24/07/12 22:46, Gabriel Roldan wrote:
Hi al,
this is just a short notice that I'm about to make GeoServer's master
branch track GWC 1.3-SNAPSHOT, now that 2.2.x is a stable branch and
will continue to track a released GWC version, this will open the
opportunity to commit some fixes to master and be tested there before
back porting to the stable branch.Cheers,
Gabriel
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Now that I have built GWC for the first time, I have changed my mind: +1
(Which is handy as Gabriel has already made the change.)
The only trick was realising that 1.3-SNAPSHOT is from the GWC stable branch (not master).
Kind regards,
Ben.
On 25/07/12 10:28, Ben Caradoc-Davies wrote:
Oh no!
-0.
I always have had major problems with GWC snapshots going stale and
breaking my builds, requiringrm -rf ~/.m2/repository/org/geowebcache/
to get things working again. When trunk (now master) was changed to
depend on 1.3-RC3 , it was a great relief and these problems no longer
occurred.Furthermore, now that GeoServer has no snapshot dependencies for the
profiles I build except GeoTools, I can build GeoTools and then
GeoServer with the "-nsu" flag (no snapshot updates, new in Maven 3.0.4)
for improved performance and safety from race conditions between local
and remote GeoTools builds.Can I ask you to reconsider? Would releasing milestones meet your
development needs? If you feel really strongly about it, I can start
building GWC as well to preserve my snapshots-are-always-local pattern,
so I am sure I will survive.Kind regards,
Ben.On 24/07/12 22:46, Gabriel Roldan wrote:
Hi al,
this is just a short notice that I'm about to make GeoServer's master
branch track GWC 1.3-SNAPSHOT, now that 2.2.x is a stable branch and
will continue to track a released GWC version, this will open the
opportunity to commit some fixes to master and be tested there before
back porting to the stable branch.Cheers,
Gabriel
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
It does bring up a good point and the question is how to strike a balance. Personally I would like to see the stable branch of geoserver generally always track a stable release of gwc, be it a recent milestone or release candidate. But master can by definition be unstable in its early stages of a new branch (like now) so I think it should be acceptable to track a gwc snapshot ideally closing in on a fixed version as master matures and moves close to becoming a stable branch (as was the case leading up to 2.2-RC1).
On Tue, Jul 24, 2012 at 8:25 PM, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:
Now that I have built GWC for the first time, I have changed my mind: +1
(Which is handy as Gabriel has already made the change.)
The only trick was realising that 1.3-SNAPSHOT is from the GWC stable
branch (not master).Kind regards,
Ben.On 25/07/12 10:28, Ben Caradoc-Davies wrote:
Oh no!
-0.
I always have had major problems with GWC snapshots going stale and
breaking my builds, requiringrm -rf ~/.m2/repository/org/geowebcache/
to get things working again. When trunk (now master) was changed to
depend on 1.3-RC3 , it was a great relief and these problems no longer
occurred.Furthermore, now that GeoServer has no snapshot dependencies for the
profiles I build except GeoTools, I can build GeoTools and then
GeoServer with the “-nsu” flag (no snapshot updates, new in Maven 3.0.4)
for improved performance and safety from race conditions between local
and remote GeoTools builds.Can I ask you to reconsider? Would releasing milestones meet your
development needs? If you feel really strongly about it, I can start
building GWC as well to preserve my snapshots-are-always-local pattern,
so I am sure I will survive.Kind regards,
Ben.On 24/07/12 22:46, Gabriel Roldan wrote:
Hi al,
this is just a short notice that I’m about to make GeoServer’s master
branch track GWC 1.3-SNAPSHOT, now that 2.2.x is a stable branch and
will continue to track a released GWC version, this will open the
opportunity to commit some fixes to master and be tested there before
back porting to the stable branch.Cheers,
Gabriel–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
word.
On Wed, Jul 25, 2012 at 1:53 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
It does bring up a good point and the question is how to strike a balance.
Personally I would like to see the stable branch of geoserver generally
always track a stable release of gwc, be it a recent milestone or release
candidate. But master can by definition be unstable in its early stages of a
new branch (like now) so I think it should be acceptable to track a gwc
snapshot ideally closing in on a fixed version as master matures and moves
close to becoming a stable branch (as was the case leading up to 2.2-RC1).On Tue, Jul 24, 2012 at 8:25 PM, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com> wrote:Now that I have built GWC for the first time, I have changed my mind: +1
(Which is handy as Gabriel has already made the change.)
The only trick was realising that 1.3-SNAPSHOT is from the GWC stable
branch (not master).Kind regards,
Ben.On 25/07/12 10:28, Ben Caradoc-Davies wrote:
> Oh no!
>
> -0.
>
> I always have had major problems with GWC snapshots going stale and
> breaking my builds, requiring
>
> rm -rf ~/.m2/repository/org/geowebcache/
>
> to get things working again. When trunk (now master) was changed to
> depend on 1.3-RC3 , it was a great relief and these problems no longer
> occurred.
>
> Furthermore, now that GeoServer has no snapshot dependencies for the
> profiles I build except GeoTools, I can build GeoTools and then
> GeoServer with the "-nsu" flag (no snapshot updates, new in Maven 3.0.4)
> for improved performance and safety from race conditions between local
> and remote GeoTools builds.
>
> Can I ask you to reconsider? Would releasing milestones meet your
> development needs? If you feel really strongly about it, I can start
> building GWC as well to preserve my snapshots-are-always-local pattern,
> so I am sure I will survive.
>
> Kind regards,
> Ben.
>
> On 24/07/12 22:46, Gabriel Roldan wrote:
>> Hi al,
>>
>> this is just a short notice that I'm about to make GeoServer's master
>> branch track GWC 1.3-SNAPSHOT, now that 2.2.x is a stable branch and
>> will continue to track a released GWC version, this will open the
>> opportunity to commit some fixes to master and be tested there before
>> back porting to the stable branch.
>>
>> Cheers,
>> Gabriel
>>
>--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.