db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <craig.russ...@oracle.com>
Subject Minutes: JDO TCK Conference Call Friday, Mar 23, 9 am Pacific Time
Date Fri, 23 Mar 2012 17:18:32 GMT
Attendees: Michael Bouschen, Matthew Adams, Michelle Caisse, Craig  
Russell

  Agenda:

  1. Patch for README.html under trunk available.

Review on email.

  2. log4j class loader, no enhancer log output with maven 2: https://issues.apache.org/jira/browse/JDO-706?

Once more into the breach. Possible solutions: create a class loader  
to be used as the context class loader to find the log4j.properties  
file; add the directory in which the log4j.properties file resides to  
the class path via a maven resources directive.

  3. Reorganize project sources to abide by maven conventions: https://issues.apache.org/jira/browse/JDO-711?

This proposal changes the directory structure to conform to maven  
conventions. No source code changes. "Just" pom changes. Reduces the  
amount of pom special stuff.

Any objection to make this part of 3.1? Nope, go for it. AI Matthew  
write a detailed description and a proper patch.

  4. Standardize field/property converters: https://issues.apache.org/jira/browse/JDO-709

. Initial thoughts provided by Matthew. Discussion for 3.2.

Good idea. More discussion on email. Examples of converters, annotated  
classes, pmf properties, and xml configuration will help understand  
the proposal.

  5. 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  
maintenance release 1 (3.1)" under "Unresolved: By Version"

  6. Other issues

Notice from infra regarding maven repository. Need to switch to  
repositories.apache.org. AI Craig see how this affects jdo.

What about using git for jdo repository? This is currently not an  
option in apache, but as an experiment, infrastructure is allowing  
projects to use an apache-maintained git repository if they have  
volunteers who are willing to provide extra help to infrastructure. At  
some time in future, projects may be able to choose which repository  
technology to use.

  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.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Mime
View raw message