Hi,
i've updated the model implementation based on various discussions from
last week. I'm using it together with a new maven plugin to create the
launchpad webapp and standalone.
You can find the sample definition at:
http://svn.apache.org/repos/asf/sling/trunk/launchpad/slingstart/src/main/systems/
I think it's now time to get serious and go into the fun discussions:
naming and format. After looking into the various YAML implementations I
decided against using one of those and wrote a simple text parser which
supports a simpler but slightly compacter syntax (the parser is not 100%
finished, but once we decided on the exact language I'll do this).
It seems we agree all on using a text based format, you'll find in the
above sample how it currently looks like.
Basic building blocks are:
- variables - these can be used throughout all files with ${variableName},
e.g in configuration values, to define an artifact or a framework setting.
- features - a feature can be combined with run modes, has start levels,
framework settings and configurations
- start levels have the artifacts
The artifacts for the various start levels must not necessarily be bundles.
Artifacts can have metadata which allows us to store things like a hash or
a signature.
WDYT?
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
