[ http://issues.apache.org/jira/browse/JDO-316?page=comments#action_12368278 ]
Michael Bouschen commented on JDO-316: -------------------------------------- Th patch looks good! Just one comment: should we give the new path a better name than 'jndi'?. This path can include any third party library, not only a jndi implementation. How about calling it 'external.libs'? > 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
