actually bnd was behaving itself - the jcl jar had an implementation version manifest entry of "1.7", which bnd automatically picked up and used - for some reason this is not the same as the jcl version.
On 04/05/07, Peter Neubauer <[EMAIL PROTECTED]> wrote: > sorry for the spam, > there is no JCL 1.7, it is the BND tool running wild. > > > /peter > > On 5/4/07, Peter Neubauer <[EMAIL PROTECTED]> wrote: > > Sorry, the exported JCL version in PaxLogging 0.9.4 is JCL version 1.0.4. > > > > /peter > > > > On 5/4/07, Peter Neubauer <[EMAIL PROTECTED]> wrote: > > > Hi there, > > > trying to wrap commons-digester BND is telling me it needs to import > > > org.apache.commons.logging version 1.7.0. PaxLogging JCL is exporting > > > only 0.9.4. > > > > > > Is there any big problem in bumping up the version to recent JCl > > > versions in order to be able to use PaxLogging instead of a wrapped > > > Apache Commons Logging? > > > > > > /peter > > > > > > > _______________________________________________ > 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
