On Thu, Jul 16, 2015 at 2:24 PM, Neil Bartlett <[email protected]> wrote: > Benson, you don't need to put the OSGi core jar on your runtime classpath if > you already have an implementation (such as Equinox or Felix) on there. > > The OSGi core spec jar is only intended to be used as a compile-time > dependency.
Neil, I understand that, but due to a combination of stupidity in an IDE and Maven, I'm having trouble getting rid of it. I don't do it in production, it's a problem when running a test from the IDE. > > Neil > > -- > Neil Bartlett > Sent from a phone > > On Thursday, 16 July 2015 at 18:11, Benson Margulies wrote: > > I have ended up with a classpath that contains both the version of > equinox in the subject and also version 5.0.0 of the OSGi core API > jar, and I get stomped on by an incompatibility. It's somewhat > difficult to avoid this state of affairs; can you clue me in on what > version of the OSGi core I need to avoid trouble? > _______________________________________________ > equinox-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > _______________________________________________ > equinox-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
