You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Peter Kriens <Pe...@aQute.biz> on 2007/01/22 09:21:54 UTC
Re[2]: Bundle-Classpath and Bnd
Well, it does not make life difficult for bnd, the check is easily
ignored. However, several times in my life I spent time debugging
only to find the error was a spelling error in the Bundle-Classpath.
So I prefer to be strict ... it is only a warning.
Kind regards,
Peter Kriens
RSH> John E. Conlon wrote:
>> Ran across a case where a project bundle was using a Bundle-Classpath
>> entry with the /target/classes/ value in it's manifest even though it
>> had no such path in the bundle. As expected Bnd flagged this as an
>> error.
>>
>> Over at the spring-osgi maillist someone mentioned this practice as a
>> way to get their bundle working in an equinox environment. Don't
>> understand this statement really - Although I run eclipse I don't have
>> much experience with Equinox.
>>
>> Is fudging the behavior of Bundle-Classpath in this manner okay or is
>> this verboten?
RSH> Yes, they are using this trick to get their bundles to work correctly as
RSH> PDE projects (they are working with maven that puts classes in
RSH> target/classes, but PDE doesn't expect them there, so they can add this
RSH> to the bundle class path to get PDE to look in the right place...or
RSH> something like that).
RSH> The spec says that missing class path entries should be ignored, so this
RSH> is ok I guess, but it does make life difficult for BND.
->> richard
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599