[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tycho-user] 'strict' mode for OSGi?
- From: Eric Gwin <eric.gwin@xxxxxxxxxx>
- Date: Fri, 05 Oct 2012 08:11:43 -0400
- Delivered-to: firstname.lastname@example.org
- Organization: Oracle Corporation
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:18.104.22.168) Gecko/20110414 Lightning/1.0b2 OracleBeehiveExtension/22.214.171.124-OracleInternal ObetStats/LAFCATCAF_1294839879169-914923201 Thunderbird/3.1.10
We are using Tycho to generate run-time OSGi bundles using a manifest-first methodology. We've discovered some non-standard behavior, and are wondering if there is a resolution already available.
It seems that Tycho is resolving classes that it shouldn't. Specifically, when the manifest doesn't explicitly import packages that are found in the JDK (JEE 6) but not explicitly made available in OSGi's core in the OSGi spec (e.g. javax.xml.bind) resolution and compilation complete successfully, however the bundle will fail at run-time on other containers (e.g Felix) because the manifest isn't correct.
Adding the appropriate imports still compiles, and resolves the portability issues. It looks like Eclipse is "helping" by making the classes available since other containers don't, the bundles generated are non-portable. If there is a "strict mode" in Tycho that we can enable, it may solve the problem, but experimenting on our part has not found any such setting.
One major reason we moved to Tycho was to allow compile-time feedback regarding appropriate manifest settings.
Any help would be appreciated.