[
https://issues.apache.org/jira/browse/JDO-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638619#action_12638619
]
Craig Russell commented on JDO-500:
-----------------------------------
This is a good start to documenting the jdoconfig tests.
I think the documentation for the JDOConfigTestClassLoader still needs a bit
more work. In particular, the constructor parameter unparent needs to be
described better. This is key to the way the class loader works. The idea is
that the test's class loader contains a whole lot of things that need to be
excluded from the class loader passed to JDOHelper, and there are some parts
that need to be added so JDOHelper can find the resources in the right place.
This needs to be documented either in the JDOConfigTestClassLoader or in
JDOHelperConfigTest.
> Need better documentation for api2 jdoconfig.xml tests
> ------------------------------------------------------
>
> Key: JDO-500
> URL: https://issues.apache.org/jira/browse/JDO-500
> Project: JDO
> Issue Type: Improvement
> Components: api2, api2-legacy
> Affects Versions: JDO 2 maintenance release 1
> Reporter: Craig Russell
> Assignee: Richard Schilling
> Priority: Minor
> Fix For: JDO 2 maintenance release 2
>
> Attachments: JDO-500-JDOConfigTestClassLoader.patch,
> JDO500-JDOHelperConfigTest.patch
>
>
> The api2 tests need a class loader that is configured with or without
> specific files in the path. This requirement is not well-documented and for
> maintainability should be documented better.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
