Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. (JDO-591) Enhancer Invocation API: A number of comments have been posted to the JIRA, mostly positive with regard to using output directory as a switch to tell enhance-in-place; specifying a class loader for the input classes; more discussion needed on using file names vs. resource names.

There is a maven plugin that provides enhancement services that would be good to review as a use-case for the enhancer API.

2. (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies: The trunk has been updated with the suggested patch. One additional suggestion is to add a pom.xml and explicitly publish api2 as a maven 2 project. This works for the api2 component but isn't applicable to the other projects. For the tck2, you need to use the source distribution.

3. Other issues

Deprecate api2-legacy. Any objections to requiring jdk1.5 for JDO 2.3 and subsequent releases? No more planned releases of api2-legacy. AI Michael file a JIRA with some implementation details for the project if we deprecate it.

JDO-615 Metadata specification API: Andy suggests adding a programmatic way to specify metadata. Seems like a good idea especially for dynamically created classes. AI everyone comment on the JIRA.

Action Items from weeks past:

[Nov 30 2007] AI Christiaan propose more details on Update/copy by query for post-JDO 2.1.

[May 25 2007] AI everyone download the Grails demo from grails.org and check it out. Also look at Grails/Groovy ExpandoMetaClass that has the magic to avoid reflection and enhancement.

[May 25 2007] AI Matthew Adams prepare a proposal with just the basics of schema synchronization with jdo and orm metadata.

[Sep 2 2005] AI: To recruit members: Articles on TheServerSide directing attention to the site. T-shirts. AI: Craig write a ServerSide article.

-- Michelle

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to