Re: Interested in contributing codes to Derby

[Katherine Marsden]

On 5/10/17 7:24 PM, Robinson Ma wrote:

Hi Derby Contributors,


My name is Robin, I am a newbie for derby. I'd like to join the project
and make contribution to this project. I have been using Derby for a
while and find out that permission granting in Derby is trivial. For
example, it can only grant permission on tables. It is nice that if it
can grant permission based on schema. One additional thing is that when
drop and recreate a table with the same name under same schema, the
permission has to be grant again.


Is there anyone who can give me some guide on this project? Right now, I
am reading user documents and architecture design document of Derby.




Hi Robin,

Welcome to the Derby community.  The Grant/Revoke implementation is 
based on the SQL Standard, so that might be a good reference resource 
for you to look at. It's been a long time for me, but I used to get it 
from my work but not sure if it is publicly available for download.


I see these notes on the Wiki.
https://wiki.apache.org/db-derby/GrantRevokeImplementation

If you search Jira you might find some interesting documentation 
attached to Grant/Revoke related issues, for example

https://issues.apache.org/jira/browse/DERBY-1928

It might be interesting to look at the diffs on those issues too, to 
help understand what code areas are related.


I haven't been active technically on the Derby project for many years 
but would love to see the community grow, so would be happy to help in 
anyway I can.


Best

Kathey

Re: JDK 9 EA Build 167 and JDK 8u152 build 03 are available on jdk.java.net

[Rick Hillegas]

Thanks, Muneer. Build 167 seems to have fixed that javadoc NPE. I have 
updated https://issues.apache.org/jira/browse/DERBY-6856.


Cheers,
-Rick

On 5/12/17 7:39 AM, Muneer Kolarkunnu wrote:


Hi Rick,

I was following your conversation in the core-libs mailing list. I am 
glad to know that you got some guidance on new Cleaner based finalization.


In the mean time, recently derby reported javadoc issue 
https://bugs.openjdk.java.net/browse/JDK-8177692 is fixed from JDK9 
build 165 onwards.


Can you please confirm the fix. I am not seeing any about this on your 
JIRA id https://issues.apache.org/jira/browse/DERBY-6856


Regards,

Muneer

*From:*Rick Hillegas [mailto:rick.hille...@gmail.com]
*Sent:* Monday, May 08, 2017 9:08 PM
*To:* Muneer Kolarkunnu
*Cc:* Dalibor Topic; Balchandra Vaidya; Rory O'Donnell; 
derby-dev@db.apache.org
*Subject:* Re: JDK 9 EA Build 167 and JDK 8u152 build 03 are available 
on jdk.java.net


Thanks again, Muneer. My conversation with the open-jdk list is linked 
from https://issues.apache.org/jira/browse/DERBY-6932. That issue will 
track the non-trivial work required to re-factor Derby's finalizers 
and migrate them to the Cleaner-based pattern. In the meantime, I have 
suppressed the finalizer deprecation warnings so that Derby will 
continue to compile cleanly under JDK 9.


Thanks,
-Rick

On 5/2/17 7:37 AM, Muneer Kolarkunnu wrote:

Hi Rick,

I have been asked if you could  address your query to
core-libs-dev mailing list, this will of benefit to you and the
community ?

Regards,

Muneer

*From:*Muneer Kolarkunnu
*Sent:* Tuesday, May 02, 2017 3:02 PM
*To:* Rick Hillegas
*Cc:* Dalibor Topic; Balchandra Vaidya; Rory O'Donnell;
derby-dev@db.apache.org 
*Subject:* RE: JDK 9 EA Build 167 and JDK 8u152 build 03 are
available on jdk.java.net

Hi Rick,

We will look into this and get back to you.

Regards,

Muneer

*From:*Rick Hillegas [mailto:rick.hille...@gmail.com]
*Sent:* Sunday, April 30, 2017 12:38 AM
*To:* Rory O'Donnell; derby-dev@db.apache.org

*Cc:* Dalibor Topic; Balchandra Vaidya; Muneer Kolarkunnu
*Subject:* Re: JDK 9 EA Build 167 and JDK 8u152 build 03 are
available on jdk.java.net

Thanks, Rory. When I compile Derby using JDK 9 build 167, I see
several instances of the following warning:

   warning: [deprecation] finalize() in Object has been deprecated

The javadoc for java.lang.Object.finalize() suggests that affected
classes should migrate their finalization to a coding pattern
based on the newly introduced java.lang.ref.Cleaner class. I am
hesitant to try my hand at this without more guidance. Can you
point me at a tutorial or list of best practices for implementing
Cleaner-based finalization?

Thanks,
-Rick


On 4/28/17 2:33 AM, Rory O'Donnell wrote:

Hi Rick,

*JDK 9 Early Access*  build 167  is available at the new
location : - jdk.java.net/9/ 

A summary of all the changes in this build are listed here
.
One change that maybe of interest is :

  *   JEP 291: Deprecate the Concurrent Mark Sweep (CMS)
Garbage Collector [1]

*JDK 8u152 Early Access* build 03 is available at the new
location : - jdk.java.net/8/ 

More information on the change of location for Early Access
builds. [2]

NOTE: - Oracle's JRE and JDK Cryptographic Roadmap has been
updated since last availability email [3]

Rgds,Rory

[1]
http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-April/005766.html


[2]

http://mail.openjdk.java.net/pipermail/adoption-discuss/2017-April/001610.html
[3] https://www.java.com/en/jre-jdk-cryptoroadmap.html

-- 


Rgds,Rory O'Donnell

Quality Engineering Manager

Oracle EMEA , Dublin, Ireland

[jira] [Commented] (DERBY-6856) Make it possible to build Derby using JDK 9

[Rick Hillegas (JIRA)]

[ 
https://issues.apache.org/jira/browse/DERBY-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008207#comment-16008207
 ] 

Rick Hillegas commented on DERBY-6856:
--

JDK 9 build 167 fixed the javadoc NPE reported at 
https://bugs.openjdk.java.net/browse/JDK-8177692

> Make it possible to build Derby using JDK 9
> ---
>
> Key: DERBY-6856
> URL: https://issues.apache.org/jira/browse/DERBY-6856
> Project: Derby
>  Issue Type: Improvement
>  Components: Build tools
>Affects Versions: 10.12.1.1
>Reporter: Rick Hillegas
> Attachments: derby-6856-01-ab-addShardingKey.diff, 
> derby-6856-01-ac-cleanup.diff, derby-6856-02-aa-addShardingKey.diff, 
> derby-6856-03-aa-autoboxingDeprecationWarnings.diff, 
> derby-6856-03-ab-autoboxingDeprecationWarnings.diff, 
> derby-6856-04-aa-autoboxingDeprecationWarnings-part2.diff, 
> derby-6856-04-ab-autoboxingDeprecationWarnings-part2.diff, 
> derby-6856-05-ac-roundingMode-Class.newInstance.diff, 
> derby-6856-05-af-roundingMode-Class.getDeclaredConstructor.diff, 
> derby-6856-05-ag-roundingMode-Class.newInstance.diff, 
> derby-6856-06-aa-observable.diff, derby-6856-07-aa-oneMoreNewInstance.diff, 
> derby-6856-08-aa-cleanupJavadoc.diff, derby-6856-09-aa-javadocEntities.diff, 
> derby-6856-10-aa-disable-permissions-subverting-test.diff, 
> derby-6856-11-aa-jigsawResourceLocation.diff, derby-6856-XX-ab-base.diff, 
> derby-6856-XX-ac-base.diff, derby-6856-XX-ad-base.diff, 
> derby-6856-XX-ae-base.diff, PTest.java, ptestScript
>
>
> Derby can't be built with JDK 9. Java 9 introduces new JDBC classes like 
> java.sql.ShardingKey and methods which refer to these new classes.
> In addition, project Jigsaw has created a new way to name classes (see 
> http://openjdk.java.net/jeps/220). This breaks the PropertySetter build tool 
> which we use so that old JVMs can compile Derby and so that Derby can be 
> compiled to run on old JVMs.
> It is likely that we will need to leave this issue open throughout the 
> development cycle of Java 9.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)