Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-09 Thread Jody Garnett 
 Core-geonetwork was able to migrate to *java.xml.bind.annotation* classes:

   - javax.xml.bind.annotation.XmlElement
   - javax.xml.bind.annotation.XmlElement
   XmlAccessorType(XmlAccessType.PUBLIC_MEMBER)


I think that is sensible advice we can add to our update instructions.
--
Jody Garnett


On Oct 7, 2023 at 12:21:52 AM, Jody Garnett  wrote:

> Well apparently we should of tested geonetwork, ... it was using one of
> the annotations that we removed: @XmlElement
>
> I am going to ask if this was just used for documentation or was required
> to support some reflection. For now I have migrated the annotation to the
> geonetwork so the pull-request can build:
> https://github.com/geonetwork/core-geonetwork/pull/7416
> --
> Jody Garnett
>
>
> On Oct 1, 2023 at 3:29:08 PM, Jody Garnett  wrote:
>
>> Wow this has been a journey, the GeoTools Project Management committee -
>> and especially the crew attending the Bolsena code sprint
>>  are pleased to
>> share the GeoTools 30-RC Release Candidate with you.
>>
>> The blog post is here:
>> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>>
>> This is a very unusual and ambitious update for the GeoTools project -
>> with some deliberate breaking API changes (gasp how rude). Indeed in
>> response to a request from OGC members we are making some changes to the
>> structure of our library.
>>
>> But fear not there is a script to help, from the user manual upgrade page
>> :
>>
>> *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
>> project directory)*
>>
>> As for the refactor:
>>
>>
>>1. The package org.opengis has changed org.geotools.api.
>>2. The main data access interfaces have been moved from
>>org.geotools.data to org.geotools.api.data. This includes, DataStore,
>>FeatureSource, FeatureIterator, and many others.
>>As part of the move, the datastore registration files found in
>>META-INF/services need to be moved as well.
>>3. Most of the "org.geotools.metadata" package is gone, as these
>>classes and interfaces were not used.
>>4. Internationalized error message support has been removed.
>>5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>>and supporting classes) were no longer in use. The direct use of JTS
>>Topology Suite Geometry is now used throughout the library
>>6. The org.opengis.geometry and org.opengis.geometry.coordinates
>>interfaces for positions, envelopes and bounding boxes have been revised 
>> as
>>part of their refactor to org.geotools.api.
>>7. The interface "org.opengis.geometry.Envelope" has been renamed
>>"org.geotools.api.geometry.Bounds" and some of the confusion related to 
>> the
>>proliferation of envelope-related classes has been cleaned up.
>>
>>
>> The nice thing is that after all this work the library is easier to use
>> with dead code and duplication removed.
>>
>> We have had lots of great feedback from downstream projects and early
>> testers - with this release candidate we wish to cast a wider net asking
>> for YOUR help!
>>
>>
>>- GeoWebCache 
>>- mapfish-print-v2
>>
>>- GeoMesa  - project
>>has created a small script
>> to update Scala
>>projects!
>>- GeoServer 
>>- geotools-devel mailing list
>>
>>
>> Please reply to this email with your success on running the script and
>> updating to GeoTools 30-RC.
>>
>> We look forward to hearing from you!
>> --
>> GeoTools Project Management Committee
>>
>
___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-07 Thread Jody Garnett 
 Well apparently we should of tested geonetwork, ... it was using one of
the annotations that we removed: @XmlElement

I am going to ask if this was just used for documentation or was required
to support some reflection. For now I have migrated the annotation to the
geonetwork so the pull-request can build:
https://github.com/geonetwork/core-geonetwork/pull/7416
--
Jody Garnett


On Oct 1, 2023 at 3:29:08 PM, Jody Garnett  wrote:

> Wow this has been a journey, the GeoTools Project Management committee -
> and especially the crew attending the Bolsena code sprint
>  are pleased to
> share the GeoTools 30-RC Release Candidate with you.
>
> The blog post is here:
> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>
> This is a very unusual and ambitious update for the GeoTools project -
> with some deliberate breaking API changes (gasp how rude). Indeed in
> response to a request from OGC members we are making some changes to the
> structure of our library.
>
> But fear not there is a script to help, from the user manual upgrade page
> :
>
> *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
> project directory)*
>
> As for the refactor:
>
>
>1. The package org.opengis has changed org.geotools.api.
>2. The main data access interfaces have been moved from
>org.geotools.data to org.geotools.api.data. This includes, DataStore,
>FeatureSource, FeatureIterator, and many others.
>As part of the move, the datastore registration files found in
>META-INF/services need to be moved as well.
>3. Most of the "org.geotools.metadata" package is gone, as these
>classes and interfaces were not used.
>4. Internationalized error message support has been removed.
>5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>and supporting classes) were no longer in use. The direct use of JTS
>Topology Suite Geometry is now used throughout the library
>6. The org.opengis.geometry and org.opengis.geometry.coordinates
>interfaces for positions, envelopes and bounding boxes have been revised as
>part of their refactor to org.geotools.api.
>7. The interface "org.opengis.geometry.Envelope" has been renamed
>"org.geotools.api.geometry.Bounds" and some of the confusion related to the
>proliferation of envelope-related classes has been cleaned up.
>
>
> The nice thing is that after all this work the library is easier to use
> with dead code and duplication removed.
>
> We have had lots of great feedback from downstream projects and early
> testers - with this release candidate we wish to cast a wider net asking
> for YOUR help!
>
>
>- GeoWebCache 
>- mapfish-print-v2
>
>- GeoMesa  - project
>has created a small script
> to update Scala
>projects!
>- GeoServer 
>- geotools-devel mailing list
>
>
> Please reply to this email with your success on running the script and
> updating to GeoTools 30-RC.
>
> We look forward to hearing from you!
> --
> GeoTools Project Management Committee
>
___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-06 Thread Ian Turton 
On Fri, 6 Oct 2023 at 17:20, Jody Garnett  wrote:

> Nice,
>
> Do you have examples of the 'ReferencedEnvelope.create(' lines that did
> not get picked up? Maybe we can adjust the script ..
>


They are split over 2 lines which I think caused the problem:

ReferencedEnvelope bounds = ReferencedEnvelope.create(new Envelope(xMin,
xMax, yMin, yMax),
coordinateReferenceSystem);

Ian

>
> I am going to get core-geonetwork today and report back.
>
> Jody
>
> On Fri, Oct 6, 2023 at 8:29 AM Ian Turton  wrote:
>
>>
>> Everything went pretty well in the repos I've tested - a few
>> `ReferencedEnvelope.creates(` didn't get picked up by the conversion tool
>> but nothing too severe
>>
>> Ian
>>
>>
>> On Sun, 1 Oct 2023 at 23:30, Jody Garnett  wrote:
>>
>>> Wow this has been a journey, the GeoTools Project Management committee -
>>> and especially the crew attending the Bolsena code sprint
>>>  are pleased to
>>> share the GeoTools 30-RC Release Candidate with you.
>>>
>>> The blog post is here:
>>> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>>>
>>> This is a very unusual and ambitious update for the GeoTools project -
>>> with some deliberate breaking API changes (gasp how rude). Indeed in
>>> response to a request from OGC members we are making some changes to the
>>> structure of our library.
>>>
>>> But fear not there is a script to help, from the user manual upgrade
>>> page :
>>>
>>> *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
>>> project directory)*
>>>
>>> As for the refactor:
>>>
>>>
>>>1. The package org.opengis has changed org.geotools.api.
>>>2. The main data access interfaces have been moved from
>>>org.geotools.data to org.geotools.api.data. This includes, DataStore,
>>>FeatureSource, FeatureIterator, and many others.
>>>As part of the move, the datastore registration files found in
>>>META-INF/services need to be moved as well.
>>>3. Most of the "org.geotools.metadata" package is gone, as these
>>>classes and interfaces were not used.
>>>4. Internationalized error message support has been removed.
>>>5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>>>and supporting classes) were no longer in use. The direct use of JTS
>>>Topology Suite Geometry is now used throughout the library
>>>6. The org.opengis.geometry and org.opengis.geometry.coordinates
>>>interfaces for positions, envelopes and bounding boxes have been revised 
>>> as
>>>part of their refactor to org.geotools.api.
>>>7. The interface "org.opengis.geometry.Envelope" has been renamed
>>>"org.geotools.api.geometry.Bounds" and some of the confusion related to 
>>> the
>>>proliferation of envelope-related classes has been cleaned up.
>>>
>>>
>>> The nice thing is that after all this work the library is easier to use
>>> with dead code and duplication removed.
>>>
>>> We have had lots of great feedback from downstream projects and early
>>> testers - with this release candidate we wish to cast a wider net asking
>>> for YOUR help!
>>>
>>>
>>>- GeoWebCache
>>>
>>>- mapfish-print-v2
>>>
>>>- GeoMesa  - project
>>>has created a small script
>>> to update Scala
>>>projects!
>>>- GeoServer 
>>>- geotools-devel mailing list
>>>
>>>
>>> Please reply to this email with your success on running the script and
>>> updating to GeoTools 30-RC.
>>>
>>> We look forward to hearing from you!
>>> --
>>> GeoTools Project Management Committee
>>> ___
>>> GeoTools-GT2-Users mailing list
>>> GeoTools-GT2-Users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>>>
>>
>>
>> --
>> Ian Turton
>>
>

-- 
Ian Turton
___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-06 Thread Jody Garnett 
Nice,

Do you have examples of the 'ReferencedEnvelope.create(' lines that did not
get picked up? Maybe we can adjust the script ..

I am going to get core-geonetwork today and report back.

Jody

On Fri, Oct 6, 2023 at 8:29 AM Ian Turton  wrote:

>
> Everything went pretty well in the repos I've tested - a few
> `ReferencedEnvelope.creates(` didn't get picked up by the conversion tool
> but nothing too severe
>
> Ian
>
>
> On Sun, 1 Oct 2023 at 23:30, Jody Garnett  wrote:
>
>> Wow this has been a journey, the GeoTools Project Management committee -
>> and especially the crew attending the Bolsena code sprint
>>  are pleased to
>> share the GeoTools 30-RC Release Candidate with you.
>>
>> The blog post is here:
>> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>>
>> This is a very unusual and ambitious update for the GeoTools project -
>> with some deliberate breaking API changes (gasp how rude). Indeed in
>> response to a request from OGC members we are making some changes to the
>> structure of our library.
>>
>> But fear not there is a script to help, from the user manual upgrade page
>> :
>>
>> *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
>> project directory)*
>>
>> As for the refactor:
>>
>>
>>1. The package org.opengis has changed org.geotools.api.
>>2. The main data access interfaces have been moved from
>>org.geotools.data to org.geotools.api.data. This includes, DataStore,
>>FeatureSource, FeatureIterator, and many others.
>>As part of the move, the datastore registration files found in
>>META-INF/services need to be moved as well.
>>3. Most of the "org.geotools.metadata" package is gone, as these
>>classes and interfaces were not used.
>>4. Internationalized error message support has been removed.
>>5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>>and supporting classes) were no longer in use. The direct use of JTS
>>Topology Suite Geometry is now used throughout the library
>>6. The org.opengis.geometry and org.opengis.geometry.coordinates
>>interfaces for positions, envelopes and bounding boxes have been revised 
>> as
>>part of their refactor to org.geotools.api.
>>7. The interface "org.opengis.geometry.Envelope" has been renamed
>>"org.geotools.api.geometry.Bounds" and some of the confusion related to 
>> the
>>proliferation of envelope-related classes has been cleaned up.
>>
>>
>> The nice thing is that after all this work the library is easier to use
>> with dead code and duplication removed.
>>
>> We have had lots of great feedback from downstream projects and early
>> testers - with this release candidate we wish to cast a wider net asking
>> for YOUR help!
>>
>>
>>- GeoWebCache 
>>- mapfish-print-v2
>>
>>- GeoMesa  - project
>>has created a small script
>> to update Scala
>>projects!
>>- GeoServer 
>>- geotools-devel mailing list
>>
>>
>> Please reply to this email with your success on running the script and
>> updating to GeoTools 30-RC.
>>
>> We look forward to hearing from you!
>> --
>> GeoTools Project Management Committee
>> ___
>> GeoTools-GT2-Users mailing list
>> GeoTools-GT2-Users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>>
>
>
> --
> Ian Turton
>
___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-06 Thread Ian Turton 
Everything went pretty well in the repos I've tested - a few
`ReferencedEnvelope.creates(` didn't get picked up by the conversion tool
but nothing too severe

Ian


On Sun, 1 Oct 2023 at 23:30, Jody Garnett  wrote:

> Wow this has been a journey, the GeoTools Project Management committee -
> and especially the crew attending the Bolsena code sprint
>  are pleased to
> share the GeoTools 30-RC Release Candidate with you.
>
> The blog post is here:
> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>
> This is a very unusual and ambitious update for the GeoTools project -
> with some deliberate breaking API changes (gasp how rude). Indeed in
> response to a request from OGC members we are making some changes to the
> structure of our library.
>
> But fear not there is a script to help, from the user manual upgrade page
> :
>
> *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
> project directory)*
>
> As for the refactor:
>
>
>1. The package org.opengis has changed org.geotools.api.
>2. The main data access interfaces have been moved from
>org.geotools.data to org.geotools.api.data. This includes, DataStore,
>FeatureSource, FeatureIterator, and many others.
>As part of the move, the datastore registration files found in
>META-INF/services need to be moved as well.
>3. Most of the "org.geotools.metadata" package is gone, as these
>classes and interfaces were not used.
>4. Internationalized error message support has been removed.
>5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>and supporting classes) were no longer in use. The direct use of JTS
>Topology Suite Geometry is now used throughout the library
>6. The org.opengis.geometry and org.opengis.geometry.coordinates
>interfaces for positions, envelopes and bounding boxes have been revised as
>part of their refactor to org.geotools.api.
>7. The interface "org.opengis.geometry.Envelope" has been renamed
>"org.geotools.api.geometry.Bounds" and some of the confusion related to the
>proliferation of envelope-related classes has been cleaned up.
>
>
> The nice thing is that after all this work the library is easier to use
> with dead code and duplication removed.
>
> We have had lots of great feedback from downstream projects and early
> testers - with this release candidate we wish to cast a wider net asking
> for YOUR help!
>
>
>- GeoWebCache 
>- mapfish-print-v2
>
>- GeoMesa  - project
>has created a small script
> to update Scala
>projects!
>- GeoServer 
>- geotools-devel mailing list
>
>
> Please reply to this email with your success on running the script and
> updating to GeoTools 30-RC.
>
> We look forward to hearing from you!
> --
> GeoTools Project Management Committee
> ___
> GeoTools-GT2-Users mailing list
> GeoTools-GT2-Users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>


-- 
Ian Turton
___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-05 Thread Jody Garnett 
Thanks Mark!

Anyone else in position to test :)

On Mon, Oct 2, 2023 at 1:04 AM mark  wrote:

> Op 02-10-2023 om 00:29 schreef Jody Garnett:
>
> > Please reply to this email with your success on running the script and
> > updating to GeoTools 30-RC.
>
> Upgraded some of our projects last week, most of them took me less than
> 10 mins to produce a PR. All testsuites pass.
>
> Only thing I ran into was we had our own "Bounds" object somewhere in
> our own API and that started conflicting with the upgraded code which
> replaces (opengis)Envelope with (geotools)Bounds, but that is a trivial fix
>
> Mark
>
>
> ___
> GeoTools-GT2-Users mailing list
> GeoTools-GT2-Users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>
___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-02 Thread mark 

Op 02-10-2023 om 00:29 schreef Jody Garnett:

Please reply to this email with your success on running the script and 
updating to GeoTools 30-RC.


Upgraded some of our projects last week, most of them took me less than 
10 mins to produce a PR. All testsuites pass.


Only thing I ran into was we had our own "Bounds" object somewhere in 
our own API and that started conflicting with the upgraded code which 
replaces (opengis)Envelope with (geotools)Bounds, but that is a trivial fix


Mark


___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

[Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

2023-10-01 Thread Jody Garnett 
Wow this has been a journey, the GeoTools Project Management committee -
and especially the crew attending the Bolsena code sprint
 are pleased to
share the GeoTools 30-RC Release Candidate with you.

The blog post is here:
https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html

This is a very unusual and ambitious update for the GeoTools project - with
some deliberate breaking API changes (gasp how rude). Indeed in response to
a request from OGC members we are making some changes to the structure of
our library.

But fear not there is a script to help, from the user manual upgrade page
:

*ant -f remove-opengis.xml -Dproject.dir=(absolute path to your project
directory)*

As for the refactor:


   1. The package org.opengis has changed org.geotools.api.
   2. The main data access interfaces have been moved from
   org.geotools.data to org.geotools.api.data. This includes, DataStore,
   FeatureSource, FeatureIterator, and many others.
   As part of the move, the datastore registration files found in
   META-INF/services need to be moved as well.
   3. Most of the "org.geotools.metadata" package is gone, as these classes
   and interfaces were not used.
   4. Internationalized error message support has been removed.
   5. The org.opengis.geometry interfaces (for Point, Curve and Surface and
   supporting classes) were no longer in use. The direct use of JTS Topology
   Suite Geometry is now used throughout the library
   6. The org.opengis.geometry and org.opengis.geometry.coordinates
   interfaces for positions, envelopes and bounding boxes have been revised as
   part of their refactor to org.geotools.api.
   7. The interface "org.opengis.geometry.Envelope" has been renamed
   "org.geotools.api.geometry.Bounds" and some of the confusion related to the
   proliferation of envelope-related classes has been cleaned up.


The nice thing is that after all this work the library is easier to use
with dead code and duplication removed.

We have had lots of great feedback from downstream projects and early
testers - with this release candidate we wish to cast a wider net asking
for YOUR help!


   - GeoWebCache 
   - mapfish-print-v2
   
   - GeoMesa  - project
   has created a small script
    to update Scala
   projects!
   - GeoServer 
   - geotools-devel mailing list


Please reply to this email with your success on running the script and
updating to GeoTools 30-RC.

We look forward to hearing from you!
--
GeoTools Project Management Committee
___
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users