2008/10/24 Niclas Hedhman <[EMAIL PROTECTED]> > On Fri, Oct 24, 2008 at 12:03 AM, Mike Smoot <[EMAIL PROTECTED]> wrote: > > Hi All, > > > > I've run into a problem with my project which I'm able to reproduce with > the > > http://www.ops4j.org/projects/pax/construct/examples/SPRING_OSGI_EXAMPLE > > script. All you need to do is change the project from Equinox to Felix > and > > then run the script. > > > > Basically, the SLF4J Log4J Binding bundle is not getting loaded due to > the > > exception below. Without this, several other bundles fail to start. This > > appears to be a problem specific for Felix version 1.2.2. Is my best > bet to > > force an older version of felix or is there another configuration option? > > In addition to the exception below, I've attached the entire script > output. > > Can we meanwhile change the sample to pull in Pax Logging instead? In > theory, it should work and wouldn't have these kinds of problems. >
well, you'd still get the warnings/errors from the fragment bundles because they're discovered and pulled in when looking at the Spring-DM dependencies - that's the main point of the example, to show how dependencies can be automatically pulled in so you don't need to explicitly add extra stuff that's why I decided to flip the example to use Equinox until the fragment issue on Felix is sorted out, as this is the real issue - and if you run the example as-is then you get no errors (it works out-of-the-box) the other option was to force it to use an earlier version of Pax-Runner which defaults to Felix 1.0.4 (for example "-Drunner=0.12.0") or explicitly force it to use Felix 1.0.4 once Felix 1.4.0 is out and picked up by Pax-Runner we can flip the example back. Cheers > Niclas > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Stuart
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
