Maybe I try to explain the basics of my idea again :)
Right now, we have the launchpad which is configured in many different
files, it's maven based and produces a runnable jar and a web application.
My primary goal is to have the possibility to define a single file
containing all the information.
The second goal is to split this description into different functional
parts, and the final result is aggregated by this.
And then, this description can be used by various tooling - so we can still
built a maven plugin on top of it that produces our launchpad. But we can
also build crankstart on top of it. But the same description file can be
used.
I hope this brief summary makes more sense :)
Now, in this sense, the model should be complete to get a runnable
installation. Therefore variables which are fed by environment variables
are not part of it. Of course you could simply specify such a variable in
the model, crankstart would work but the launchpad plugin would create
something unusable as actual values would be missing.
I'm also not sure, if explicit variables, like ENV:{mongodb.url} is the way
to go - this limits the control to very specific parts - namely only those
where such a variable is used. However, if no value is specified there is
no default value and if you want to override a different configuration
settings, you can't.
But I think that's an additional topic we should discuss. I would like to
talk about the first one first :)
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
