Is there an estimate for when the released version of 2.1 will be available?
Thanks for your help.
Charlie
On Tue, Apr 12, 2011 at 4:35 PM, Cacciato, Charles P - GS
<CHARLES.CACCIATO@anonymised.com> wrote:
Is there an estimate for when the released version of 2.1 will be available?
Hmm... I don't really have one. We are going to release RC5 later this
week (or beginning of next),
if we don't see any other major issue we'll release it as final,
otherwise another RC, and so on.
Things look pretty solid, but they have been looking that way since
RC3 and people still
managed to find small regressions here and there in special cases
(some cql expressions,
particular combinations of raster data types associated with certain
color maps and background
colors and so on).
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
On Tue, Apr 12, 2011 at 10:53 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:
Things look pretty solid, but they have been looking that way since
RC3 and people still
managed to find small regressions here and there in special cases
(some cql expressions,
particular combinations of raster data types associated with certain
color maps and background
colors and so on).
It would be really swell if someone could take a peek at GEOS-4127
before 2.1 final. 
It's not a show stopper, but it is a regression
from 2.0, and the workaround makes ugly blank spaces in the legends.
On Tue, Apr 12, 2011 at 5:24 PM, Joshua M. Thompson
<joshua.thompson@anonymised.com> wrote:
On Tue, Apr 12, 2011 at 10:53 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:Things look pretty solid, but they have been looking that way since
RC3 and people still
managed to find small regressions here and there in special cases
(some cql expressions,
particular combinations of raster data types associated with certain
color maps and background
colors and so on).It would be really swell if someone could take a peek at GEOS-4127
before 2.1 final.
from 2.0, and the workaround makes ugly blank spaces in the legends.
Developers are overloaded already, if it's important for you I'd suggest
to try and provide a patch yourself? Who know, it might be funny 
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
Hi Joshua, Andrea.
I wanted to fix this obvious possible NPE but there is no class
DefaultRasterLegendProducer.java
in the current 2.1.x branch.
@Joshua, could you test with a nightly build ?
Quoting Andrea Aime <andrea.aime@anonymised.com>:
On Tue, Apr 12, 2011 at 5:24 PM, Joshua M. Thompson
<joshua.thompson@anonymised.com> wrote:On Tue, Apr 12, 2011 at 10:53 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:Things look pretty solid, but they have been looking that way since
RC3 and people still
managed to find small regressions here and there in special cases
(some cql expressions,
particular combinations of raster data types associated with certain
color maps and background
colors and so on).It would be really swell if someone could take a peek at GEOS-4127
before 2.1 final.
from 2.0, and the workaround makes ugly blank spaces in the legends.Developers are overloaded already, if it's important for you I'd suggest
to try and provide a patch yourself? Who know, it might be funnyCheers
Andrea--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech leadVia Poggio alle Viti 1187
55054 Massarosa (LU)
Italyphone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf-------------------------------------------------------
------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
On Wed, Apr 13, 2011 at 7:48 AM, <christian.mueller@anonymised.com> wrote:
Hi Joshua, Andrea.
I wanted to fix this obvious possible NPE but there is no class
DefaultRasterLegendProducer.java
in the current 2.1.x branch.
@Joshua, could you test with a nightly build ?
Hi Christian,
Thanks for taking the time to look at this. I took a peek at the
source last night myself and it appears that at some point the code
was refactored and the bug was fixed. However, the ticket didn't get
updated or closed, so I didn't realize this was already fixed. I ran
some tests with 2.1RC4 just to make sure and I can no longer cause
Geoserver to throw the NPE.
On a side note it appears label-only rules now always take up legend
space. Previously if there was no Title or Name then the rule was
simply not in the legend; now it leaves a blank white placeholder.
That's a considerably more involved fix from the look of things, and I
personally don't feel the need to fix it. I can just force my label
rules to be listed last which puts the whitespace at the end of the
legend.
So the short answer is: it's fixed and the ticket can be closed.