OK i've removed the pax web dependency from the test.. But now I am getting
this, could it be because of blueprint and springdm depends on pax-web
somehow?:
org.ops4j.pax.wicket.service[org.ops4j.pax.wicket.internal.extender.PaxWicketBundleListener]
: Class 'org.ops4j.pax.wicket.spi.blueprint' was found via bundle
javax.activation.DataHandlerDataSource's resource path, but classloader
can't load it (is the jar file
corrupted or a dependant optional dependencies not resolved?)
org.ops4j.pax.wicket.service[org.ops4j.pax.wicket.internal.extender.PaxWicketBundleListener]
: Class 'org.ops4j.pax.wicket.spi.blueprint' was found via bundle
javax.activation.DataSourceDataContentHandler's resource path, but
classloader can't load it (is the j
ar file corrupted or a dependant optional dependencies not resolved?)
org.ops4j.pax.wicket.service[org.ops4j.pax.wicket.internal.extender.PaxWicketBundleListener]
: Class 'org.ops4j.pax.wicket.spi.blueprint' was found via bundle
javax.activation.ObjectDataContentHandler's resource path, but classloader
can't load it (is the jar f
ile corrupted or a dependant optional dependencies not resolved?)
org.ops4j.pax.wicket.service[org.ops4j.pax.wicket.internal.extender.PaxWicketBundleListener]
: Class 'org.ops4j.pax.wicket.spi.blueprint' was found via bundle
javax.activation.SecuritySupport's resource path, but classloader can't
load it (is the jar file corru
pted or a dependant optional dependencies not resolved?)
org.ops4j.pax.wicket.service[org.ops4j.pax.wicket.internal.extender.PaxWicketBundleListener]
: Class 'org.ops4j.pax.wicket.spi.springdm' was found via bundle
javax.activation.DataHandlerDataSource's resource path, but classloader
can't load it (is the jar file
corrupted or a dependant optional dependencies not resolved?)
On Monday, May 22, 2017 at 6:55:09 AM UTC+2, nino martinez wael wrote:
>
> Hi
>
> Over 2 months ago I made the last changes to the 4.x.y branch[1] to
> support wicket 8. I cannot get the "bare" felix tests to work (I seem to be
> missing some dependency, which I cannot figure out)..
>
> The question is, should I just disable the the test, as there are no
> horison on it getting to work and release what we have..? If not, how
> should we get the broken felix tests to work, i'm pretty sure its some
> dependency thing that's out of sync.
>
> [1]https://github.com/ops4j/org.ops4j.pax.wicket/tree/v4.x.y
>
>
> Regard Nino
>
--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
---
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.