Jukka Zitting wrote:
Hi,
On Thu, Jun 26, 2008 at 12:25 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
I do not envision weekly releases of single components. But there may well
be one or two releases (or more) per month, yes. We also have this over at
Felix and it works quite well.
OK. I'm just wondering how it looks to a potential end user.
Potential end users should use the "full" download, which is either the
launchpad app or webapp. We will release new versions of the launchpad
several times a year and these will include the latest bundles (there
might be exceptions to that rule of course).
How about merging to simplify end user experience? Unless we can
somehow automate upgrades (wouldn't it be cool if bundles and all the
dependencies were automatically downloaded from the Maven
repository... :-), our users could well end up manually managing a
complex dependency tree. At least we should document the component
dependencies somewhere.
For example, say I have a component that uses some fancy new Map
implementation in a recent commons-collections release. When a user
deploys my component, it would be nice if she didn't need to also
worry about the commons-collections version. IMHO the same reasoning
applies also to things like commons/json.
OSGi has a nice feature called OBR - this is a repository where we will
register each and every new bundle release. The user can then invoke the
webconsole and see which updates are available and update whatever he
wants. The OBR takes care of dependencies and updates other required
bundles as well.
Setting up such an OBR repository is easy: it's just an xml document at
a well-known location which points to the jars in the maven repository.
We're planning to do this very shortly :)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
