Hi again,
After another try, I managed to properly import the JTS io GeoJSON part.
Here is the dependency to use:
<dependency>
<groupId>org.locationtech.jts.io</groupId>
<artifactId>jts-io-common</artifactId>
<version>1.17.0</version>
</dependency>
And not:
<dependency>
<groupId>org.locationtech.jts</groupId>
<artifactId>jts-io</artifactId>
<version>1.17.0</version>
<type>pom</type>
</dependency>
This solves all the remaining problems with JTS and JTS imports,
excluding the ones which are link with some code modifications between
the two versions (1.14 and 1.17). I'll manage these ones later manually.
I also managed to solve the deegree-core 3 imports. Rather than using a
pom type, the easiest solution is to import each individual module, such as:
<dependency>
<groupId>org.deegree</groupId>
<artifactId>deegree-core-commons</artifactId>
<version>3.4.13</version>
</dependency>
Now it's just a game to see where the different classes and concepts
have been moved, such as org.deegree.cs.* replacing
org.deegree.model.crs.* with different paths. For example,
org.deegree.model.crs.UnknownCRSException replaced
org.deegree.cs.exceptions.UnknownCRSException,
org.deegree.commons.utils.StringUtils/ ArrayUtils replacing
org.deegree.framework.util.StringTools, or
org.deegree.commons.xml.CommonNamespaces replacing
org.deegree.ogcbase.CommonNamespaces. Behind the scene, it's apparently
the exact same code, which is a good news.
That's me for today. Hope it helps.
Best,
Eric
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
