[jira] [Created] (JDO-710) Edit poms so that the maven eclipse plugin doesn't throw on import
Edit poms so that the maven eclipse plugin doesn't throw on import -- Key: JDO-710 URL: https://issues.apache.org/jira/browse/JDO-710 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 Fix For: JDO 3 maintenance release 1 (3.1) Relative paths using .. in poms cause the maven eclipse plugin to throw a NPE. This request is to fix poms so that they don't cause maven eclipse plugin to throw. -- 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 16, 9 am Pacific Time
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell Agenda: 1. README.html under trunk needs to be reviewed. Maven: need at least maven 2 to build. But should we remove the reference to mevenide? Yes. AI Michael send a patch with more review. 2. log4j class loader, no enhancer log output with maven 2: https://issues.apache.org/jira/browse/JDO-706? When activating the iut profile, all other profiles are deactivated. You have to specify all profiles that you want. 3. Refactor JDO parent child poms https://issues.apache.org/jira/browse/JDO-707 Seems like a good pattern. Ship it. 4. Create JIRA component entry for exectck parent-pom modules https://issues.apache.org/jira/browse/JDO-708 Close as won't fix. 5. Issues fixed with setting autoCreateTables=false Michael changed the mapping by adding the schema to the package. With these settings (checked in) the tck now runs on Derby without auto create tables. Separately, we might consider changing the specification to require using the schema with sequence names. AI Michael create a JIRA for the specification change. 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. Standardize field/property converters: https://issues.apache.org/jira/browse/JDO-709 How does the user specify conversions of field values? This is a topic currently being discussed in another expert group. AI Matthew update the JIRA. 8. Other issues The latest tck run shows an error on runonce signature test. Embedded.java has a new method for the discriminator: /** * Discriminator for cases where the embedded object has inheritance. * @return the discriminator for inheritance determination */ Discriminator discriminatorColumnName() default @Discriminator; The signature test parser isn't prepared to deal with this construction. AI Michael file a JIRA for this. 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!
[jira] [Created] (JDO-711) Reorganize project sources to abide by maven conventions
Reorganize project sources to abide by maven conventions Key: JDO-711 URL: https://issues.apache.org/jira/browse/JDO-711 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 Priority: Trivial The current source trees for the JDO projects api tck don't abide by maven conventions. This request is to reorganize the source trees so that they do, reducing required pom metadata and enabling new developers to easily comprehend the 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] [Commented] (JDO-711) Reorganize project sources to abide by maven conventions
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13231396#comment-13231396 ] Matthew T. Adams commented on JDO-711: -- Anyone object to my doing this for 3.1 since we're going all maven 2 with this release? Reorganize project sources to abide by maven conventions Key: JDO-711 URL: https://issues.apache.org/jira/browse/JDO-711 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 Priority: Trivial Labels: maven, pom The current source trees for the JDO projects api tck don't abide by maven conventions. This request is to reorganize the source trees so that they do, reducing required pom metadata and enabling new developers to easily comprehend the 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-710) Edit poms so that the maven eclipse plugin doesn't throw on import
[ https://issues.apache.org/jira/browse/JDO-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-710: - Attachment: JDO-710.patch Patch. Really a minor change that duplicates NOTICE.txt in api tck projects. Will commit this face flogging if any is to be had. Edit poms so that the maven eclipse plugin doesn't throw on import -- Key: JDO-710 URL: https://issues.apache.org/jira/browse/JDO-710 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: m2e, maven-eclipse-plugin, pom Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-710.patch Relative paths using .. in poms cause the maven eclipse plugin to throw a NPE. This request is to fix poms so that they don't cause maven eclipse plugin to throw. -- 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-710) Edit poms so that the maven eclipse plugin doesn't throw on import
[ https://issues.apache.org/jira/browse/JDO-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13231408#comment-13231408 ] Matthew T. Adams commented on JDO-710: -- Committed: R:\os\jdo\trunksvn ci -m JDO-710, Edit poms so that the maven eclipse plugin doesn't throw on import Sendingapi\pom.xml Adding api\src\main Adding api\src\main\resources Adding api\src\main\resources\META-INF Adding api\src\main\resources\META-INF\NOTICE.txt Sendingtck\pom.xml Adding tck\src\main Adding tck\src\main\resources Adding tck\src\main\resources\META-INF Adding tck\src\main\resources\META-INF\NOTICE.txt Transmitting file data Committed revision 1301658. Edit poms so that the maven eclipse plugin doesn't throw on import -- Key: JDO-710 URL: https://issues.apache.org/jira/browse/JDO-710 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: m2e, maven-eclipse-plugin, pom Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-710.patch Relative paths using .. in poms cause the maven eclipse plugin to throw a NPE. This request is to fix poms so that they don't cause maven eclipse plugin to throw. -- 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-709) Standardize field/property converters
[ https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-709: - Attachment: JDO-709-01.patch Initial thoughts. Including revision number in patch filename, as I expect we'll iterate on this. Standardize field/property converters - Key: JDO-709 URL: https://issues.apache.org/jira/browse/JDO-709 Project: JDO Issue Type: New Feature Components: api Reporter: Matthew T. Adams Assignee: Matthew T. Adams Priority: Minor Labels: converstion, converter, jdo, type, type-converter Fix For: JDO 3 maintenance release 2 (3.2) Attachments: JDO-709-01.patch This request is to standardize a user's ability to specify conversions of fields or properties of persistence-capable classes. Currently, this is left to vendor extensions. -- 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
