>>>>> Steinar Bang <[email protected]>:
> I then tried to change the unit tests into a basic, minimal pax exam
> test (basically, just running the code like in the current unit test,
> but with all of the OSGi stuff in place), but then I got the following
> startup error:
> org.ops4j.pax.exam.TestContainerException: No TestContainer implementation
> in Classpath
> Is what I'm doing possible? Or am I trying to use pax exam for
> something it isn't designed for?
Turns out I didn't need to do this...
> Would it be better if I figured out a way to use
> ClasspathResourceAccessor in the unit test and OSGiResourceAccessor when
> running the unit tests?
Actually it was much simpler:
When I used the ClasspathResourceAccessor constructor with a classpath
constructor, like so
ClassLoaderResourceAccessor classLoaderResourceAccessor = new
ClassLoaderResourceAccessor(getClass().getClassLoader());
then liquibase found its files both in the unit tests and when running
in OSGi in karaf and when running in the pax exam integration tests
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
