Hi Christoph,
2017-10-20 14:11 GMT+02:00 'Christoph Läubrich' via OPS4J <
ops4j@googlegroups.com>:
> We might circumvent the problem in the future since I'm working on a
> feature that allows the seperation of Test-Class + Configure Method, this
> ill then also break the runtime dependencies
I think this is okay, even though in most cases if someone uses
tinybundles there will be a point where it is required to include
tinybundles as a bundle in the test.
We migth circumvent the problem in the future since I'm working on a
feature that allows the seperation of Test-Class +
Hi Christoph,
I now experimented a bit more with the problem of .ClassNotFoundException:
org.ops4j.pax.tinybundles.core.BuildStrategy.
It seems the problem occurs when I use:
InputStream inp = bundle().add(DsService.class).build(withBnd());
It seems the problem is that build(strategey) has a
I created an issue for this:
https://ops4j1.jira.com/browse/PAXTB-28
Christian
2017-10-05 10:09 GMT+02:00 'Christoph Läubrich' via OPS4J <
ops4j@googlegroups.com>:
> That sounds good, the best would be to add a JIRA just now for this :-)
>
> Am 05.10.2017 um 10:07 schrieb Christian Schneider:
>
> I only use this in the @Configuration so my test should not require
> TinyBundles at runtime.
Even though you does not require the code to run in @Configure you still
have an (class-import) dependecy to that code.
Is it a real problem to include tiny-bundles in your test?
If yes you have to
I am trying to tune TinyBundles to create DS xml for standard DS
annotations.
To achieve this I created my own BuildStrategy that adds the bnd plugin for
DS.
I only use this in the @Configuration so my test should not require
TinyBundles at runtime.
Still I get a ClassNotFoundException when I run
