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:
>
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:
The static method in a separate class sounds good .. I will try this.
There indeed is a withBnd method but it just calls plain bnd without the
DSAnnotations bnd plugin.
The static method in a separate class sounds good .. I will try this.
There indeed is a withBnd method but it just calls plain bnd without
the DSAnnotations
bnd plugin.
If I succeed then I think we should add this functionality to TinyBundles.
I think it would also be great for users to be able t
> 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
