[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] How to best simulate standalone Equinox deployment in Eclipse
- From: Robert Krüger <krueger@xxxxxxxxxxx>
- Date: Fri, 19 Nov 2010 11:53:21 +0100
- Delivered-to: firstname.lastname@example.org
I'm going through the (so far rather painful) process of trying to deploy my OSGI app developed within Eclipse 3.6 in a standalone Equinox environment for the first time.
The two main things I ran into were having to specify javax.* and other packages included in the JavaSE (like org.xml.sax.*) in org.osgi.framework.system.packages and adding Import-Package entries for these in the respective bundles. The former is not too bad as this only has to be done once. However the latter is a bit tedious in the development process if I always have to go through the export, run, change in IDE, rerun cycle.
How is this done best, from a productivity point of view? Is there a way to configure an eclipse OSGI run configuration in such a way that it behaves like the standalone environment, i.e. throws Exceptions/Errors on classes not imported or even better have the compiler mark this as an error? How does the fact that I have Bundle-RequiredExecutionEnvironment: JavaSE-1.6 specified for all bundles affect all this? What do I have to do to be able to test this realistically within Eclipse?
Thanks in advance for sharing any hints in this matter.