db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michelle Caisse (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-301) Update README.txt and RunRules.html
Date Fri, 24 Feb 2006 00:44:38 GMT
     [ http://issues.apache.org/jira/browse/JDO-301?page=all ]

Michelle Caisse updated JDO-301:

    Attachment: readme.mc

n lieu of some comments, I have attached a version (full text, not a diff) that reorganizes
the document a bit, fixes a few nits, and updates the material on using tck20/maven.xml. I
have a few additional comments:

enhancer20 - It might be helpful to explain that this is not the RI enhancer.

JNDI - Do we allow users to provide a non-default jndi implementation?  This document instructs
them to change project.properties, which the Run Rules disallows them from changing.  If we
allow a non-default jndi, we need to put this property in build.properties.

derby - Is it still true that Mac OSX users must uncomment this property?

> Update README.txt and RunRules.html
> -----------------------------------
>          Key: JDO-301
>          URL: http://issues.apache.org/jira/browse/JDO-301
>      Project: JDO
>         Type: Task
>   Components: tck20
>     Versions: JDO 2 beta
>     Reporter: Michelle Caisse
>     Assignee: Craig Russell
>      Fix For: JDO 2 rc1
>  Attachments: README.txt, readme.mc
> Currently the README.txt in the trunk and the beta release differ.  We may need to split
it into two files, one including the information needed to build and run from the source tree
and the other for building and running the TCK from the distribution. The distribution README.html
needs to contain all post-install information the user needs to run the TCK and should point
to RunRules.html. There needs to be an appropriate complementarity of information between
README.html and RunRules.html.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message