Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jnosql-dev] What could be part of initial contribution?
Hello, Werner.
I really prefer to wait till a JSR for same reasons:

  • If approved as JSR we need to change the package to java.nosql
  • We need to change the pom.xml to java.nosql
  • We need to update the drivers




On Mon, Jan 30, 2017 at 2:50 PM, Werner Keil <werner@xxxxxxxxxxx> wrote:

Hi,

Similar to other new Eclipse projects based on one or more existing efforts, there are several modules found in: https://github.com/JNOSQL

Otavio hinted, the Diana API could be proposed as a Java standard (JSR) to the JCP relatively soon.
The minutes from his recent EC Presentation (to probe the feeling in the EC about this idea, e.g. if it was the right time, too early or too late) https://jcp.org/aboutJava/communityprocess/ec-public/materials/2017-01-1011/January-2017-Public-Minutes.html plus a detailed PDF did not sound like "Oh my god" to me (I was also in the call) so does it sound better to wait with an initial contribution to Eclipse till a JSR and Spec Lead Draft of such API existed, or should Diana also be contributed now, knowing it could be a "stub"? (a bit like https://github.com/unitsofmeasurement/uom-legacy still is at Eclipse UOMo until the JSR 363 API at JCP can be used by Eclipse projects)

Not sure, if it was an option to keep Diana as it is, but create a CQ for it? (which would be pretty identical to what we did in UOMo for https://github.com/unitsofmeasurement/uom-legacy)

Suggestions, thoughts?

Thanks,

Werner





_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev




--
Otávio Gonçalves de Santana

Back to the top