On 3/9/2012 11:18 AM, Craig L Russell wrote:
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.
This page seems to indicate that there is no programmatic way of
determining which profile is active. It suggests using an environment
variable, as I've done in exectck.
http://maven.40175.n5.nabble.com/get-active-profile-in-pom-td108838.html
This page documents that an activeByDefault profile will deactivate when
another profile is activated /by any available means.
/http://maven.apache.org/guides/introduction/introduction-to-profiles.html:
Profiles can also be active by default using a configuration like
the following:
<profiles>
<profile>
<id>profile-1</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
...
</profile>
</profiles>
This profile will automatically be active for all builds/unless
another profile in the same POM is activated using one of the
previously described methods. All profiles that are active by
default are automatically deactivated when a profile in the POM is
activated on the command line or through its activation config./ [My
italics.]
Thus my setup in exectck pom.xml should work fine.
-- Michelle
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!
