I am trying to generate an instrumented driver for our product that is embedded in WebSphere Application Server. I have been able to get it working for "regular" code, but now I have a problem with our OSGi bundles. The OSGi activators can not be loaded because they are referring to the Clover CoverageRecorder class, which is not in the classpath. We have put the clover jar (and license file) in the WebSphere App Server's lib/ext directory, which was good enough for all other code, but it's evidently not good enough for our code in OSGi bundles.
The only way we've been able to find around this is to directly include the clover JAR and license file in every one of our OSGi bundles. That is obviously not a long-term solution. Is there something we can to do get the clover JAR added to the base OSGi bundle classpath?
Please try to add the following argument to JVM args for WebSphere:
Depending on which tool you're using for instrumentation, this JAR can be found in:
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs