[
https://issues.apache.org/jira/browse/DERBY-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436890#comment-13436890
]
Myrna van Lunteren commented on DERBY-5902:
-------------------------------------------
Regarding how to 'hang' such a test in e.g. suites.All; you could make running
this test optional, by making it dependent on some essential class, or jar from
the Pax Exam being available in the classpath. If not available, print
something - but not an error or warning - out to the console, when
derby.tests.trace is true. We've used that sort of construct before - I think
LDAPAuthenticationTest does something like this if it's missing required
parameters, and the upgrade tests used to give warnings if somehow required
older versions were missing - so there's a precedent to this.
This would enable individual developers to run suites.All without having the
OSGI items downloaded, but regular nightly tests would be expected to get this
set up...
We can alternatively/later decide to add some automatic download of the jars.
Or we could perhaps add them to the repository under tools/java - we've done
that for e.g. jakarta-oro (required for derbyall) but we'd have to check on the
licensing for that - does Pax Exam have a compatible license?.
> Test Derby OSGi bundle
> ----------------------
>
> Key: DERBY-5902
> URL: https://issues.apache.org/jira/browse/DERBY-5902
> Project: Derby
> Issue Type: Task
> Reporter: Mohamed Nufail
> Assignee: Mohamed Nufail
> Priority: Minor
> Attachments: OSGiTest.java, PlumbingOSGiTest.java, pom.xml, Probe.java
>
>
> There is a lack of tests that test Derby's support for OSGi. I hope to
> provide some integration tests to Derby OSGi bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
