redistribute gt-api classes to gt-metadata and gt-main
Initial classes moved to gt-metadata successfully
api change: org.geotools.decorate → org.geotools.util.decorate
note: DirectPosition3D had to move to gt-referencing (to preserve a package visibility “friend” relationship
everything else moved to gt-main as planned
gt-api successfully removed, and gt-main pom.xml description updated
recording refactoring script and placed into user guide for later
Tomorrow: Continuing on with the core library tomorrow morning, moving on to plugins and extensions tomorrow afternoon. Goal is to finish up on Thursday, and apply these changes to geowebcache and geoserver projects Friday morning.
How to help?
Love to hear how EMF upgrade is going (to see if our models can track api change)
Need a sample application ready to test using geotools on the module path
I computed a quick list of package names outside of the ‘library’ that need to be moved to avoid the split module issues. The attached files have that output.
This won’t necessarily sort all the split modules, but it’d be a handy next step.
redistribute gt-api classes to gt-metadata and gt-main
Initial classes moved to gt-metadata successfully
api change: org.geotools.decorate → org.geotools.util.decorate
note: DirectPosition3D had to move to gt-referencing (to preserve a package visibility “friend” relationship
everything else moved to gt-main as planned
gt-api successfully removed, and gt-main pom.xml description updated
recording refactoring script and placed into user guide for later
Tomorrow: Continuing on with the core library tomorrow morning, moving on to plugins and extensions tomorrow afternoon. Goal is to finish up on Thursday, and apply these changes to geowebcache and geoserver projects Friday morning.
How to help?
Love to hear how EMF upgrade is going (to see if our models can track api change)
Need a sample application ready to test using geotools on the module path
–
Jody Garnett
_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)
recording refactoring script and placed into user guide for later
Gentle reminder that the Eclipse popularity took a nosedive in the last few years, so in the instructions for using
the scripts it’s best not to assume Eclipse familiarity:
Tomorrow: Continuing on with the core library tomorrow morning, moving on to plugins and extensions tomorrow afternoon. Goal is to finish up on Thursday, and apply these changes to geowebcache and geoserver projects Friday morning.
How to help?
Love to hear how EMF upgrade is going (to see if our models can track api change)
I’ll try to help here after the Spring review
Cheers
Andrea
···
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.ithttp://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.