So what do people think?
Should we rather go with
[runMode name=jackrabbit]
[artifacts startLevel=1]
..artifacts for level 1
[artifacts startLevel=5]
..artifacts for level 5
[configurations]
..configurations
[settings]
.settings
or
[artifacts startLevel=1 runMode=jackrabbit]
Well, I don't have a strong preference either way - just playing the
devil's advocate a bit. I think there's a third option as well, making
the runMode a property of the config file, so all
configurations/artifacts in a config file would be automatically
assigned to the defined runMode - if any.
Hi Carsten,
I probably just struggle with the naming but I guess runModes should
provide similar capabilities as runmodes currently do (with the
config.runmode options and so on).
Therefore I wonder if it really reasonable to splitt runmodes or to better
have the second one and potentially assign
Hi
2014-10-01 12:57 GMT+02:00 Dominik Süß dominik.su...@gmail.com:
Hi Carsten,
I probably just struggle with the naming but I guess runModes should
provide similar capabilities as runmodes currently do (with the
config.runmode options and so on).
Yep, exactly
Therefore I wonder if it
On Tue, Sep 30, 2014 at 8:11 AM, Carsten Ziegeler cziege...@apache.org wrote:
What about Sling Provisioning Model (SPM) ?..
I like that name, +1
-Bertrand
Hi,
On Wed, Oct 1, 2014 at 12:44 PM, Carsten Ziegeler cziege...@apache.org wrote:
...
[artifacts startLevel=1 runMode=jackrabbit]
..artifacts for level 1
[configurations runMode=jackrabbit]
..configurations
I'd write this a bit differently to make it obvious that start level
and run
Hi,
2014-10-01 14:06 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org:
Hi,
On Wed, Oct 1, 2014 at 12:44 PM, Carsten Ziegeler cziege...@apache.org
wrote:
...
[artifacts startLevel=1 runMode=jackrabbit]
..artifacts for level 1
[configurations runMode=jackrabbit]
Hi,
On Tue, Sep 30, 2014 at 9:21 AM, Carsten Ziegeler cziege...@apache.org wrote:
I've thought a little bit more about the model and I came up with a
slightly different syntax...
https://svn.apache.org/repos/asf/sling/trunk/launchpad/slingstart/src/main/model/example.txt
...
Looks good to me,
Hi,
2014-10-01 14:22 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org:
I would require a header like
[sling.feature]
name=Example feature
description=Optional description
to make sure people at least think about what they put in there ;-)
Good point, agreed (I don't agree on
Hi,
On Wed, Oct 1, 2014 at 3:13 PM, Carsten Ziegeler cziege...@apache.org wrote:
2014-10-01 14:22 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org:
...Should have both local (to the feature) and global variables?...
Variables are currently local to a feature - do we need global variables?
2014-10-01 15:19 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org:
Hi,
On Wed, Oct 1, 2014 at 3:13 PM, Carsten Ziegeler cziege...@apache.org
wrote:
2014-10-01 14:22 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org:
...Should have both local (to the feature) and global
2014-09-29 23:12 GMT+02:00 Alexander Klimetschek aklim...@adobe.com:
On 29.09.2014, at 06:36, Carsten Ziegeler cziege...@apache.org wrote:
I'm fine with a structured text format that's not YAML, as long as
it's diff-friendly and allows for comments. The benefit is that we can
customize
Hi,
2014-09-29 15:36 GMT+02:00 Carsten Ziegeler cziege...@apache.org:
Hi Bertrand,
2014-09-29 14:42 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org:
Can we call this startup model BTW? It's more descriptive than
slingstart.
I'm fine with nearly any name, I just picked the first
I've thought a little bit more about the model and I came up with a
slightly different syntax. A file with examples can be found here:
https://svn.apache.org/repos/asf/sling/trunk/launchpad/slingstart/src/main/model/example.txt
The previous version messed up features and run modes and made them
Hi,
On Tue, Sep 30, 2014 at 10:21 AM, Carsten Ziegeler cziege...@apache.org wrote:
I've thought a little bit more about the model and I came up with a
slightly different syntax. A file with examples can be found here:
Hi Robert,
2014-09-30 17:22 GMT+02:00 Robert Munteanu romb...@apache.org:
I haven't looked very much in depth at this, but I like where this is
heading. A couple of questions/nitpicks:
1. Attaching additional information to artifacts currently looks like this
Hi Carsten,
On Sat, Sep 27, 2014 at 5:48 PM, Carsten Ziegeler cziege...@apache.org wrote:
...You can find the sample definition at:
http://svn.apache.org/repos/asf/sling/trunk/launchpad/slingstart/src/main/systems/
...
Thanks for this - as discussed last week at adaptTo I like the idea
very
Hi Bertrand,
2014-09-29 14:42 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org:
Can we call this startup model BTW? It's more descriptive than
slingstart.
I'm fine with nearly any name, I just picked the first thing running
through my brain...
While startup model is more descriptive,
On 29.09.2014, at 06:36, Carsten Ziegeler cziege...@apache.org wrote:
I'm fine with a structured text format that's not YAML, as long as
it's diff-friendly and allows for comments. The benefit is that we can
customize the syntax for our actual needs.
Yepp, exactly. Funnily, I found YAML to
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:
20 matches
Mail list logo