jDO TCK Conference Call Friday, Mar 9, 9 am Pacific Time
Hi, We will have our regular meeting Friday, March 9 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. README.html under trunk needs to be reviewed. 2. log4j class loader, no enhancer log output with maven 2: https://issues.apache.org/jira/browse/JDO-706? 3. Refactor JDO parent child poms https://issues.apache.org/jira/browse/JDO-707 4. Create JIRA component entry for exectck parent-pom modules https://issues.apache.org/jira/browse/JDO-708 5. Issue with setting autoCreateTables=false 6. What's needed to release 3.1? Go to https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630, click Issues in the menu on the left and then click JDO 3 maintenacnce release 1 (3.1) under Unresolved: By Version 7. Other issues 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. -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680
Re: jDO TCK Conference Call Friday, Mar 9, 9 am Pacific Time
Can't make meeting today -- have conflict. Please review patch for pom refactoring! On Fri, Mar 9, 2012 at 7:09 AM, Michael Bouschen m...@apache.org wrote: Hi, We will have our regular meeting Friday, March 9 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. README.html under trunk needs to be reviewed. 2. log4j class loader, no enhancer log output with maven 2: https://issues.apache.org/**jira/browse/JDO-706https://issues.apache.org/jira/browse/JDO-706 ? 3. Refactor JDO parent child poms https://issues.apache.org/** jira/browse/JDO-707 https://issues.apache.org/jira/browse/JDO-707 4. Create JIRA component entry for exectck parent-pom modules https://issues.apache.org/**jira/browse/JDO-708https://issues.apache.org/jira/browse/JDO-708 5. Issue with setting autoCreateTables=false 6. What's needed to release 3.1? Go to https://issues.apache.org/** jira/secure/BrowseProject.**jspa?id=10630https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630 , click Issues in the menu on the left and then click JDO 3 maintenacnce release 1 (3.1) under Unresolved: By Version 7. Other issues Action Items from weeks past: [April 8 2011] AI Craig comment on https://issues.apache.org/** jira/browse/JDO-617 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. -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 -- @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] [Updated] (JDO-708) Create JIRA component entry for exectck parent-pom modules
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-708: - Component/s: site and infrastructure Create JIRA component entry for exectck parent-pom modules -- Key: JDO-708 URL: https://issues.apache.org/jira/browse/JDO-708 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Fix For: JDO 3 maintenance release 1 (3.1) The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too. -- 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-708) Create JIRA component entry for exectck parent-pom modules
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13226250#comment-13226250 ] Michelle Caisse commented on JDO-708: - Wondering what the benefit is of this change over the existing setup? Create JIRA component entry for exectck parent-pom modules -- Key: JDO-708 URL: https://issues.apache.org/jira/browse/JDO-708 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Fix For: JDO 3 maintenance release 1 (3.1) The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too. -- 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-708) Create JIRA component entry for exectck parent-pom modules
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13226256#comment-13226256 ] Craig L Russell commented on JDO-708: - It's not obvious to me that exectck needs a different JIRA component. The exectck is the execution mechanism for tck so to me they are both logically the same component although they have different physical packaging. Create JIRA component entry for exectck parent-pom modules -- Key: JDO-708 URL: https://issues.apache.org/jira/browse/JDO-708 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Fix For: JDO 3 maintenance release 1 (3.1) The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too. -- 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-707) Refactor JDO parent child poms
[ https://issues.apache.org/jira/browse/JDO-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13226253#comment-13226253 ] Michelle Caisse commented on JDO-707: - Wondering what the benefit is of this change over the existing setup? Refactor JDO parent child poms Key: JDO-707 URL: https://issues.apache.org/jira/browse/JDO-707 Project: JDO Issue Type: Improvement Components: api, tck Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: parent, pom Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-707-1.patch Create a parent-pom module, make modules api, exectck tck inherit from it, then create a simple multimodule root pom which can be used to build all projects. -- 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] [Updated] (JDO-708) Create JIRA component entry for exectck parent-pom modules
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse updated JDO-708: Comment: was deleted (was: Wondering what the benefit is of this change over the existing setup?) Create JIRA component entry for exectck parent-pom modules -- Key: JDO-708 URL: https://issues.apache.org/jira/browse/JDO-708 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Fix For: JDO 3 maintenance release 1 (3.1) The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too. -- 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-707) Refactor JDO parent child poms
[ https://issues.apache.org/jira/browse/JDO-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13226265#comment-13226265 ] Matthew T. Adams commented on JDO-707: -- The improvement comes when we release the 3.1 artifacts to Maven Central. When I released 3.0.1, I had to manually copy information from the parent pom into the JDO API pom. In 3.1, when we release, we should release not only artifact jdo-api, but also parent-pom. Then, there will not have to be any manual copying from the parent pom into the jdo-api pom. Refactor JDO parent child poms Key: JDO-707 URL: https://issues.apache.org/jira/browse/JDO-707 Project: JDO Issue Type: Improvement Components: api, tck Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: parent, pom Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-707-1.patch Create a parent-pom module, make modules api, exectck tck inherit from it, then create a simple multimodule root pom which can be used to build all projects. -- 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, Mar 9, 9 am Pacific Time
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell Agenda: 1. README.html under trunk needs to be reviewed. AI Everyone please READ ME. 2. log4j class loader, no enhancer log output with maven 2: https://issues.apache.org/jira/browse/JDO-706? AI Michelle try some more experiments with the iut and jdori profiles. Specifying -P iut on command line should work, disable the jdori profile. Exectck should be able to ask maven which profile(s) are active. 3. Refactor JDO parent child poms https://issues.apache.org/jira/browse/JDO-707 It's not obvious why a parent pom at the same level as others is better than the current pom in the trunk directory. 4. Create JIRA component entry for exectck parent-pom modules https://issues.apache.org/jira/browse/JDO-708 It's not obvious that exectck and tck are different components even thought they are physically different. 5. Issue with setting autoCreateTables=false The sequence support for Derby is now included in DataNucleus. But it doesn't seem to work. Change the mapping in the orm file to include the schema name. But is this the only way for DN to find the sequence? Maybe need to add schema to the package entry in the orm. 6. What's needed to release 3.1? Go to https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630 , click Issues in the menu on the left and then click JDO 3 maintenacnce release 1 (3.1) under Unresolved: By Version Still waiting for log4j class loader, sequences, and specification updates. 7. Other issues 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!
