Thanks Andrea and Jody for your very kind offers. I will be at the Bonn code sprint. I've committed to work on some other tasks, but I think I could keep some time (maybe a day?) for pushing this task. In any case, I'll try to advance some work before the code sprint.
I think I will start by updating the proposal you linked and trying to figure out how to use unit-ri/unit-se (JSR 363 implementations). Any suggestion is welcome. Regards, César On 7 March 2018 at 08:41, Jody Garnett <jody.garn...@gmail.com> wrote: > I saw the activity on jira and found the “withdrawn” proposal - > https://github.com/geotools/geotools/wiki/Replace-JSR-275-Units-Library > > If we can update this with a plan I would be pleased to work on this during > the OSGeo code sprint. > On Tue, Mar 6, 2018 at 9:21 AM Jens Auer <jens.a...@betaversion.net> wrote: >> >> Hi, >> >> I have to admit that I sent the mails last year and wanted to work on >> migrating to jsr363. However, when I quickly ran into problems when I wanted >> to use jsr363 in our project in a limited way just in our own classes. We >> have multiple dependencies that depend on JScience /jsr275, and using both >> jsr363 and jsr275 in a project leads to many problems because both use the >> javax.measure package and some identical class names. I guess it would have >> been easier if jsr363 used another package, but because of these issues I >> stopped working on the migration. >> >> Best wishes, >> Jens >> >> -----Ursprüngliche Nachricht----- >> Von: César Martínez Izquierdo <cesar....@gmail.com> >> Gesendet: Freitag, 2. März 2018 11:28 >> An: geotools-devel@lists.sourceforge.net >> Cc: jens.a...@betaversion.net; Jody Garnett <jody.garn...@gmail.com> >> Betreff: Replace JScience JSR275 with JSR363 >> >> Hi, >> Last year there was a thread on the list regarding the migration from >> JScience/JSR275 to JSR363, although I assume that no progress was finally >> achieved: >> >> >> https://www.mail-archive.com/geotools-devel@lists.sourceforge.net/msg38174.html >> >> I'd like to help on this effort, if there is still interest in migrating >> to JSR363. >> >> The use of JSR275 is a problem since there are collisions on >> package/classes/method signatures between JSR363 and JSR363, so you can't >> combine Geotools with any library using JS363. >> >> Note that JSR275 is used by the "forked" GeoAPI APIs used in Geotools, so >> this change will imply some method signature modifications on that API. >> >> Best regards, >> >> César Martínez >> >> >> -- >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> César Martínez Izquierdo >> GIS developer >> - - - - - - - - - - - - - - - - - - - - >> SCOLAB: http://www.scolab.es >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> >> --- >> Diese E-Mail wurde von AVG auf Viren geprüft. >> http://www.avg.com >> >> > -- > -- > Jody Garnett -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - César Martínez Izquierdo GIS developer - - - - - - - - - - - - - - - - - - - - SCOLAB: http://www.scolab.es - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
