Hi Toni, So Sigil is new here at Felix too, we're currently in a migration phase at the moment as this used to be hosted at http://sigil.codecauldron.org, but there's some docs here:
http://felix.apache.org/site/apache-felix-sigil.html and I've set up a bunch of issues here: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310100&component=12312962&resolution=-1&sorter/field=priority&sorter/order=DESC I have sigil to a stage where it can build itself - i.e. resolve dependencies from external repositories based on import/require OSGi meta data and compile and build the bundles to then be manually installed in eclipse. There's currently no netbeans integration mainly due to bandwidth but the underlying model is pretty portable as it can be used in both ivy and eclipse environments. The plan at the moment for the debug support is to use the Felix launcher which is now able to launch any other OSGi framework via the new OSGi 4.2 launcher api - of course there's still work to plugin the process control to the IDE and visualise the various options for OSGi launching. Feel free to post questions here or on the dev mailing list if you're interested in getting involved :) Regards, Dave On Wed, Aug 12, 2009 at 11:43 AM, eppleton<[email protected]> wrote: > > Hi David, > > no this is the first time IM on this list. Sure, maybe we can join forces. > Do you have a thread for this? > > --Toni > > > > David Savage-3 wrote: >> >> Hi Toni, >> >> Sorry off topic from your question but, just wondering if you've seen >> sigil here on felix, which is attempting to build a common set of osgi >> developer tools. I'm currently looking runtime support in eclipse >> wondering if you'd be interested in joining forces to work on netbeans >> integration? >> >> Regards, >> >> Dave >> >> >> >> On 12 Aug 2009, at 10:10, eppleton <[email protected]> wrote: >> >>> >>> Hi, >>> >>> Is there a way to get the classes of the OSGi API and the Felix >>> implementation in two separate JARs? >>> >>> I'm creating a plugin for NetBeans to register and administrate OSGi >>> containers. Felix ist the default, but I want my tool to rely on the >>> API >>> only in order to be able to plugin other implementations (e.g. >>> Knopflerfish). So the UI can display information for a Bundle >>> regardless >>> where it comes from. >>> >>> If there's nothing like that out-of-the-box, I'll do it manually. The >>> question then is: Would that work since it seems I'll also have to >>> split up >>> the manifest then... >>> >>> Thanks >>> >>> --Toni >>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/APi-and-Implementation-in-separate-JARs-tp24931883p24931883.html >>> Sent from the Apache Felix - Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > -- > View this message in context: > http://www.nabble.com/APi-and-Implementation-in-separate-JARs-tp24931883p24933924.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
