I think Alex was pointing to example installers for Directory, not
Felix, but that does raise an issue that I have been meaning to post for
a week or so now.
I think it is very important that we get an easily
downloaded/installable release of Felix out the door as soon as
possible...actually, it is long overdue. :-(
Of the outstanding issues for Felix, my original thinking was that I
wanted to target re-enabling security before making a public release.
However, my mind has been changed on this and I now think we should
target fixing security in the next public release.
I think we are ready with a stable, usable Felix release right now. In
the last two months there have been a lot of changes to Felix, such as:
* Complete refactoring of the Module Loader layer to provide better
modularity abstractions to support OSGi R4 features; there are
still a few more things to be done here, but overall it is in good
shape.
* Implemented support for directories on the class path.
* Implemented support for Bundle.getEntry()/getEntryPaths().
* Implemented support for installing bundles by reference and as
exploded JAR files.
* Improved several concurrency issues to lessen the possibility of
deadlocks.
* Fixed some low-level bugs/issues, some of which were around since
the Oscar days, like improperly handling the order of bundle class
path entries and ensuring that embedded JAR names do not clash.
* Added many minor bug fixes too.
And these changes are only in the last two months, there are many more
improvements before then (like the rewriting of the URL Handlers service
to support multiple framework instances). I am confident to say that
Felix is ready for more wide-scale usage. This means that we need to
make a public release.
Currently, Felix reports itself as 0.7.0...I think we should follow a
release model where odd numbered point releases are experimental and
even numbered point releases are stable. I propose that we declare the
next release to be 0.8.0, with the subsequent development occurring in
0.9.0, followed by the 1.0.0 release.
I have one outstanding thing that I would like to commit for the 0.8.0
release, which is some experimentation that I have been doing with OBR.
This should be done within a week (unfortunately, I have had some other
priorities or else this would be done already), but we could even go
ahead without it.
If people have familiarity with making releases here at Apache, your
input would be greatly appreciated, because this is all new to me.
Comments and suggestions are encouraged. Let's get this thing out the
door ASAP.
-> richard
Peter Kriens wrote:
Any progress? I am working on the OSGi tutorial and would love to be
able to point to an installer page ... Preferably with the option to
run it as a service/deamon
Kind regards,
Peter Kriens
AK> Hi all,
AK> This is for those anxiously awaiting an installer. I think we have
AK> something better than expected.
AK> I'm almost done building a maven plugin which generates installers for a
AK> project whose final product is a UNIX daemon or a Windows service using
AK> jakarta commons daemon jsvc and procrun respectively. The plugin will
AK> generate multiple installers when asked for a project. We're using it
AK> already for ApacheDS and we have generalized it for any server
AK> application. It should be ready right after the soon to arrive 1.0-RC1
AK> release. The plugin has rough edges but we should be fine making it work.
AK> Here's the URL for it now. This might move over to the maven repo at
AK> some point though (after I clean it up a bit):
AK> http://svn.apache.org/repos/asf/directory/trunks/daemon/
AK> Here's what some generated installers look like using apacheds as an
AK> example:
AK> http://people.apache.org/~akarasulu/apacheds/
AK> Alex
