[Geoserver-devel] GeoApi version screwup on gs 2.5.x/gs 1.7.x

Hi,
trying to make the GS release we noticed a few inconsistencies
between gs 1.7.x, gt 2.5.x, and gt trunk:
- gs 1.7.x does depend on GeoApi 2.2 M1, and does not use the OSGEO
   repo, but the opengeo one and the old refractions one.
   The first has a March 13 snapshot of GeoApi, the latter has M1
- gt2 2.5.x does depend on refractions and opegeo repos, and does
   depend on GeoApi 2.2-snapshot
- gt trunk depends on a different version of GeoApi, that's not
   surprising, but it's the only one using the osgeo repo

The result of the first two points is that one tests fails because
there's code using the case matching flag added to like filters
in gt2 that is not found in geoapi 2.2 M1.
Refractions has also a M2 sitting there, but it's dated Feb 19,
I believe it's not recent enough to have the case matching change
in?

I'm trying to find a good solution out of this confusion, but
I'm left guessing. My guess is that we should:
- have gt2 2.5.x depend on osgeo repo
- same goes for 1.7.x (assumin osgeo repo has been fixed, it
   seems it is)
- have both depend on a geoapi snapshot for the time being?
   would sure be nice to have an M3 instead of depending on
   a snapshot?

Can anyone confirm this is a viable plan?

Cheers
Andrea

PS: it would all be easier if GeoTools owned its API, but
that's a discussion for another day

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Hi Andrea:

The plan is viable; with one small update ...

I would like to release geoapi 2.2.0 for this release; I can do so
now. I was waiting to hear back if the ignore case option for the like
filter was completed.

Jody

I'm trying to find a good solution out of this confusion, but
I'm left guessing. My guess is that we should:
- have gt2 2.5.x depend on osgeo repo
- same goes for 1.7.x (assumin osgeo repo has been fixed, it seems it is)
- have both depend on a geoapi snapshot for the time being? would sure be nice to have an M3 instead of depending on a snapshot?

Can anyone confirm this is a viable plan?

Cheers
Andrea

PS: it would all be easier if GeoTools owned its API, but
that's a discussion for another day

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Hi Andrea: I have released GeoAPI 2.2.0 ...

The artifacts have been deployed to the osgeo repository (just like trunk):
- http://download.osgeo.org/webdav/geotools/org/opengis/geoapi/2.2.0/

The tag is created here:
- https://geoapi.svn.sourceforge.net/svnroot/geoapi/tags/2.2.0

Jira has been updated here:
- 2.2: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10720&styleName=Html&version=12386
- 2.2.1 has been created allowing us to manage any future patches

Jody

On Thu, Apr 23, 2009 at 1:46 AM, Andrea Aime <aaime@anonymised.com> wrote:

Hi,
trying to make the GS release we noticed a few inconsistencies
between gs 1.7.x, gt 2.5.x, and gt trunk:
- gs 1.7.x does depend on GeoApi 2.2 M1, and does not use the OSGEO
repo, but the opengeo one and the old refractions one.
The first has a March 13 snapshot of GeoApi, the latter has M1
- gt2 2.5.x does depend on refractions and opegeo repos, and does
depend on GeoApi 2.2-snapshot
- gt trunk depends on a different version of GeoApi, that's not
surprising, but it's the only one using the osgeo repo

The result of the first two points is that one tests fails because
there's code using the case matching flag added to like filters
in gt2 that is not found in geoapi 2.2 M1.
Refractions has also a M2 sitting there, but it's dated Feb 19,
I believe it's not recent enough to have the case matching change
in?

I'm trying to find a good solution out of this confusion, but
I'm left guessing. My guess is that we should:
- have gt2 2.5.x depend on osgeo repo
- same goes for 1.7.x (assumin osgeo repo has been fixed, it
seems it is)
- have both depend on a geoapi snapshot for the time being?
would sure be nice to have an M3 instead of depending on
a snapshot?

Can anyone confirm this is a viable plan?

Cheers
Andrea

PS: it would all be easier if GeoTools owned its API, but
that's a discussion for another day

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel