That's because the dependency are now unpacked and bnd is used to bundle all the dependency and project compiled code together.
I will work with David to get these things resolved. Regards, Edward Yakop On 6/15/07, David Leangen <[EMAIL PROTECTED]> wrote: > > It appears that there are some changes to the pax projects over older > versions concerning how they work in Eclipse. > > For example: > > pax-wicket gives errors in the manifest such as: > > "Package wicket.blah does not exist in the plug-in" > > In several classes in pax-logging: > > "The import org.apache cannot be resolved" > > In pax-confman > > "The import org.ops4j.lang cannot be resolved" > > In the latter case, I noticed that this package should be exported from > ops4j-base, but it is not. I am assuming, then, that ops4j-base is > intended to be a library jar and therefore embedded in confman. However, > it is not on the Eclipse classpath. > > > Could somebody (i.e. Efy) please explain how the projects should be set > up in Eclipse, so I don't go messing around with somebody's (i.e. Efy's) > work? ;-) > > > Thanks! > Dave > > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
