While I can see that the usage of the maven-bundle-plugin started being used from M7, it does not necessarily make a working bundle. in this case the usage of the <DynamicImport-Package>*</DynamicImport-Package> should be changed to
pseudo code start <DynamicImport-Package>!junit.framework,*</DynamicImport-Package> pseudo code end I'll try doing so on my wicket clone and get back.. On Thu, Dec 21, 2017 at 11:45 AM, Maxim Solodovnik <[email protected]> wrote: > If I'm not mistaken M7 was made OSGi compatible .... > > On Thu, Dec 21, 2017 at 5:10 PM, nino martinez wael < > [email protected]> wrote: > > > Hi Guys > > > > This makes the build incompatible with OSGI, since it forces the OSGI > > container to provide junit and hamcrest.. > > > > M8 apparently exports some junit packages, but not junit.framework, im > not > > sure why junit package should be exported by wicket? > > > > M7 HAS a lot of imports and exports, the import on junit.framework first > > appears here.. > > > > M6 have no imports or exports in the manifest. Seems something changed to > > the manifest generation > > > > M5 seems not to have the issue... > > > > There's a notion that its provided because of wicket tester in the pom? > > > > We are currently trying to test Wicket 8 out with pax wicket, this is > > stopping us from proceeding.. > > > > Any hints on when a fixed snapshot will be available (hopefully assuming > > this can be fixed)? > > > > -- > > Best regards / Med venlig hilsen > > Nino Martinez > > > > > > -- > WBR > Maxim aka solomax > -- Best regards / Med venlig hilsen Nino Martinez
