On 8/5/09 14:26, Marcel Offermans wrote:
On Aug 5, 2009, at 18:04 , David Savage wrote:
I've found the http://felix.apache.org/obr/releases.xml OBR
repository, which is great it just plugs in neatly to sigil and I can
pull binary dependencies from it into my development environment.
However the one binary I can't pull from here is felix.jar. I
understand in a runtime this makes no sense as the jar is already
there but in sigil at development time it would be neat if I could
just point my development environment at this file and have it link to
the felix.jar to satisfy import package requirements.
Thoughts?
One related thought that came to mind was, if we include felix.jar
like this, we could also try making it a bundle itself. That way we
could also start experimenting with embedding felix in felix (or some
other framework).
Technically, it is already packaged as a bundle, but I am not sure what
else you mean.
Another thing we could then try is to make a launcher which fetches an
instance of a framework an launches it through the new API. That way
our launcher would be even simpler and more lightweight, and it could
also be used to launch other framework implementations.
To some degree, that is what the launcher does. However, it still has
some Felixisms since I didn't want to break what people have come to
expect. To make it work for any framework we'd have to make it retrieve
the framework factory using META-INF/services and we'd have to refactor
AutoActivator to do its auto-property processing externally. Both of
these changes would be fairly simple.
-> richard
Greetings, Marcel
