JSR-275 now at Maven Central
Werner Keil
Some things happen often after a very long time.
For those still using the old JSR (Martin) it may be good to hear, that
Sonatype has recently created a mirror of the java.net repository:
http://weblogs.java.net/blog/editor/archive/2011/08/21/sonatype-adds-javanet-projects-its-central-repository
I was approached by Bill Shannon if, we could remove it, since the JSR has
been stopped, but I told him there are several users and also references to
it from places like Groovy/Grails. I would keep it at GeoAPI repository just
in case. Maybe some day somebody at Oracle might remove it, but since back
at the time I wasn't the one who actually published the java.net repository,
I told Bill I cannot do anything about it here ;-)
Regarding a follow-up, there have been promising voices of a few new EC
members. I hope to know more after the next EC F2F meeting in NJ. While I
cannot say, if an official presentation or pre-proposal will make it into
the busy agenda, I would at least like to talk to those who were involved in
this discussion earlier. Meanwhile, Unit-API is likely to be approved by
Eclipse Orbit pretty soon. PMC (an equivalent to the EC at Eclipse ;-)
already sanctioned it, now only legal legwork is required by the IP person.
As soon as that's through, I also hope to put Unit-API into some of the
Eclipse Maven repositories. And via that step it should sooner rather than
later also find its way into Maven Central.
Regards,
Werner
Martin Desruisseaux
Le 04/09/11 19:04, Werner Keil a �crit :
> Some things happen often after a very long time.
> For those still using the old JSR (Martin) it may be good to hear, that
> Sonatype has recently created a mirror of the java.net repository:
> http://weblogs.java.net/blog/editor/archive/2011/08/21/sonatype-adds-javanet-projects-its-central-repository
>
This is an interresting new, thanks for sharing it with us :-). I will remove
the dependency to java.net from GeoAPI and other pom.xml file.
I also noticed that there is a 1.0.0 release of JSR-275 on Maven Central. I was
not aware of that (I was stick to 0.9.3 release). Do you know what are the
differences between 0.9.3 and 1.0.0?
> I was approached by Bill Shannon if, we could remove it, since the JSR has
> been stopped, but I told him there are several users and also references to it
> from places like Groovy/Grails. I would keep it at GeoAPI repository just in
> case. Maybe some day somebody at Oracle might remove it, but since back at the
> time I wasn't the one who actually published the java.net repository, I told
> Bill I cannot do anything about it here ;-)
Well, we should tell to Bill that they can not just kill a project like that. I
agree with the arguments they made against our proposal and I really think that
an other round of API cleanup would have been good. But just killing the project
instead than allowing it to be fixed is problematic for open source projects
that use it.
> Regarding a follow-up, there have been promising voices of a few new EC
> members. I hope to know more after the next EC F2F meeting in NJ. While I
> cannot say, if an official presentation or pre-proposal will make it into the
> busy agenda, I would at least like to talk to those who were involved in this
> discussion earlier. Meanwhile, Unit-API is likely to be approved by Eclipse
> Orbit pretty soon. PMC (an equivalent to the EC at Eclipse ;-) already
> sanctioned it, now only legal legwork is required by the IP person. As soon as
> that's through, I also hope to put Unit-API into some of the Eclipse Maven
> repositories. And via that step it should sooner rather than later also find
> its way into Maven Central.
When talking about Unit-API, do you mean org.unitsofmeasurement? While it be
renamed javax.measure, or while the package name stay org.unitsofmeasurement?
As a side note, I'm doing a talk about GeoAPI next week. While this is not
specifically about JSR-275, it depends on JSR-275
http://2011.foss4g.org/sessions/geoapi-30-java-interfaces-ogc-standard
Regards,
Martin