As one of those "users" of sling the launchpad structures are working
well for us. At the moment we take launchpad/bundles as is, and
package with something close to lauchpad/app.
We do however have some patches against the raw source so are running
a branch, although, long term I would hope to be taking a standard
build.
We are intending to give our UI developers an executable Jar to work
with because when ever I say "you just have to download it and build
it" they give me a really weird look like, like I have escaped from
somewhere.
Many of them are used to a pre configured lamp binary for getting up
and going on development fast, building from source doesnt appear to
be in their vocab.
Ian
On 11 May 2009, at 20:03, Felix Meschberger wrote:
Hi all,
Carsten and I have been reasoning about the releases in the future,
mainly the ones for end-users who just want to grab a binary and
fire it
off.
Basically, we will start releasing single bundles using the regular
ASF
release process. This should enable us to release much quicker than
with
big release we have done until now.
For the consumer releases we are talking about 4 projects mainly:
* launchpad/base - contains the launcher code, Felix framework
and the OSGi core and compendium libraries.
* launchpad/bundles - a very simple project to just pack together
existing bundles
* launchpad/app, launchpad/webapp - projects to create final app
and web app from the base and bundles projects
So to release a "consumer product" we update the launchpad/bundles
project with all the bundles we want to include and prepare the
releases
of the launchpad/bundles, launchpad/app and launchpad/webapp projects.
I know this is kind of "weird" in the Apache World, but in essence
these
releases are not mainly targeted at developers and "manual builders"
but
at consumers, who just want to grab-and-run it.
WDYT ?
Regards
Felix
