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-316) TCK should allow user to configure their own JNDI provider
Date Tue, 28 Feb 2006 21:17:40 GMT
     [ http://issues.apache.org/jira/browse/JDO-316?page=all ]

Michelle Caisse updated JDO-316:
--------------------------------

    Attachment: JDO-316.patch

I've attached a patch for review.  All jar files in lib/ext are included on the classpath.

> TCK should allow user to configure their own JNDI provider
> ----------------------------------------------------------
>
>          Key: JDO-316
>          URL: http://issues.apache.org/jira/browse/JDO-316
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Versions: JDO 2 rc1
>     Reporter: Craig Russell
>     Assignee: Michelle Caisse
>     Priority: Minor
>      Fix For: JDO 2 final
>  Attachments: JDO-316.patch
>
> Currently, to reconfigure the JNDI provider, the user has to edit both the jndi.properties
file and the project.properties. 
> We should allow the user to only edit the jndi.properties by changing the project.properties
to automatically add all the jar files in lib/ext to the classpath.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message