Re: [VOTE] JDO 3.0.1 release
+1 verified checksums Craig On Nov 5, 2011, at 8:27 AM, Matthew Adams wrote: We have prepared the release artifacts for JDO 3.0.1 and staged them on http://people.apache.org/~madams/jdo3.0.1/dist/db/jdo/3.0.1/ This is a result of the efforts of the JDO expert group and the Apache JDO community. If you get this message more than once, just use it as a reminder to vote. The vote will be open until Friday November 11, 2011. Thanks, Matthew Sent from mobile. Responses sometimes entertaining. Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
Re: [VOTE] JDO 3.0.1 release
+1 On Sat, Nov 5, 2011 at 10:27 AM, Matthew Adams matt...@matthewadams.mewrote: We have prepared the release artifacts for JDO 3.0.1 and staged them on http://people.apache.org/~madams/jdo3.0.1/dist/db/jdo/3.0.1/ This is a result of the efforts of the JDO expert group and the Apache JDO community. If you get this message more than once, just use it as a reminder to vote. The vote will be open until Friday November 11, 2011. Thanks, Matthew Sent from mobile. Responses sometimes entertaining. -- @matthewadams12 mailto:matt...@matthewadams.me skype:matthewadams12 yahoo:matthewadams aol:matthewadams12 google-talk:matthewadam...@gmail.com msn:matt...@matthewadams.me http://matthewadams.me http://www.linkedin.com/in/matthewadams
[jira] [Commented] (JDO-696) Throw on unrecognized javax.jdo options
[ https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148587#comment-13148587 ] Matthew T. Adams commented on JDO-696: -- I will make the check for known javax.jdo properties case-insensitive so that Javax.JDO is considered to be the same as javax.jdo. Speak up if you no likey. Throw on unrecognized javax.jdo options --- Key: JDO-696 URL: https://issues.apache.org/jira/browse/JDO-696 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Attachments: JDO-696.patch If a user specifies an unrecognized option that begins with JDO's standard prefix javax.jdo., then an exception (JDOUserException or a sub) should be thrown by either the implementation or JDOHelper, depending on the bootstrapping mechanism employed by the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148599#comment-13148599 ] Matthew T. Adams commented on JDO-694: -- javax.naming.* should not be optional Automate OSGi bundling in JDO 3.1+ build Key: JDO-694 URL: https://issues.apache.org/jira/browse/JDO-694 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: jdo, osgi Fix For: JDO 3 maintenance release 1 Attachments: JDO-694.patch Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Minutes: JDO TCK Conference Call Friday, Nov 10, 9 am Pacific Time
Attendees: Michael Bouschen, Matthew Adams, Craig Russell Agenda: 1. JDO 3.0.1 release is available for testing! The release was voted and is now pending turning the crank. AI Matthew ship it. Matthew will need to update the KEYS file for the db project. AI Craig send link for how to do it. 2. New feature idea http://osdir.com/ml/jdo-dev-db-apache/2011-11/msg2.html More detail is still needed on the proposal. 3. Other issues What about setting up Facebook page, Google+ account, Twitter? Matthew volunteered to set up some social networking for JDO. https://issues.apache.org/jira/browse/JDO-696 Throw an exception if an unrecognized property with javax.jdo prefix. Should the test be case sensitive? Probably not. Action Items from weeks past: [April 8 2011] AI Craig comment on https://issues.apache.org/jira/browse/JDO-617 re the utility of the update operator. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck. Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
Updating KEYS
Hi Matthew, Here is the file that you need to add your public key to: http://www.apache.org/dist/db/derby/KEYS Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
[jira] [Commented] (JDO-696) Throw on unrecognized javax.jdo options
[ https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148635#comment-13148635 ] Craig L Russell commented on JDO-696: - Since we're trying to avoid type kinds of errors, I agree that it makes sense to flag case-insensitive typos as well. Throw on unrecognized javax.jdo options --- Key: JDO-696 URL: https://issues.apache.org/jira/browse/JDO-696 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Attachments: JDO-696.patch If a user specifies an unrecognized option that begins with JDO's standard prefix javax.jdo., then an exception (JDOUserException or a sub) should be thrown by either the implementation or JDOHelper, depending on the bootstrapping mechanism employed by the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Updating KEYS
Oops, I mean http://www.apache.org/dist/db/jdo/KEYS Craig On Nov 11, 2011, at 10:07 AM, Craig L Russell wrote: Hi Matthew, Here is the file that you need to add your public key to: http://www.apache.org/dist/db/derby/KEYS Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148639#comment-13148639 ] Matthew T. Adams commented on JDO-694: -- I'll defer to bnd's expertise as to what should be listed in the Import-Package header (bnd is the tool that underlies maven-bundle-plugin). For example, we depend on javax.security, yet bnd does not add an import for that package, but it does add an import for javax.naming. Best Craig I could figure is that bnd knows what should shouldn't be listed in Import-Package. We're going with everything as optional because javax.naming javax.rmi are used only if JNDI is used and the XML APIs are used only if a jdoconfig.xml is parsed. Automate OSGi bundling in JDO 3.1+ build Key: JDO-694 URL: https://issues.apache.org/jira/browse/JDO-694 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: jdo, osgi Fix For: JDO 3 maintenance release 1 Attachments: JDO-694.patch Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Updating KEYS
Got it. Should that file go under source control somewhere? On Fri, Nov 11, 2011 at 12:18 PM, Craig L Russell craig.russ...@oracle.comwrote: Oops, I mean http://www.apache.org/dist/db/**jdo/KEYShttp://www.apache.org/dist/db/jdo/KEYS Craig On Nov 11, 2011, at 10:07 AM, Craig L Russell wrote: Hi Matthew, Here is the file that you need to add your public key to: http://www.apache.org/dist/db/**derby/KEYShttp://www.apache.org/dist/db/derby/KEYS Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:Craig.Russell@oracle.**com craig.russ...@oracle.com P.S. A good JDO? O, Gasp! -- @matthewadams12 mailto:matt...@matthewadams.me skype:matthewadams12 yahoo:matthewadams aol:matthewadams12 google-talk:matthewadam...@gmail.com msn:matt...@matthewadams.me http://matthewadams.me http://www.linkedin.com/in/matthewadams
