Hi, 2014-10-01 14:06 GMT+02:00 Bertrand Delacretaz <[email protected]>:
> Hi, > > On Wed, Oct 1, 2014 at 12:44 PM, Carsten Ziegeler <[email protected]> > 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 mode apply only to the current section: > > [artifacts] > startLevel:1 > runModes:jackrabbit,author > ... > > [configurations] > startLevel:2 > (will use runModes:<blank>) > > And require, while parsing, those statements to be at the beginning of > the section, before any artifacts. > > It's a bit more typing but things are then obvious, and one can always > use ${variables} for lists of run modes for example. > > But it complicates the parser, as it would need special casing to check for the startLevel: and runModes: key words and personally I think having all the info on one line is a little bit nicer. Its already obvious that startLevel and runMode only apply to the current section as they are part of the section definition. [artifacts runMode=jackrabbit] [configurations] in contrast to [artifacts] runModes:jackrabbit [configurations] If you think about having a lot listed under artifacts, it's easy to miss that the first line is actually not an artifact but an attribute of the section. Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
