[jira] [Commented] (SLING-3528) Add ability to configure OSGi components from crank files

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990677#comment-13990677 ] 

Bertrand Delacretaz commented on SLING-3528:
--------------------------------------------

I think the current String format for commands is too limitative, and it shows here as the configuration format is not very flexible.

In http://svn.apache.org/r1592750 I have introduced a new CrankstartCommandLine interface that is meant to introduce a simple parser to handle structures like this in the crankstart file:

{code}
# comment
command_verb optional qualifier which can be several words
  property = a string (a line which is indented defines a property)
  another.property[] = [ some, array, of, strings ]
another.verb which starts a new command as it's not indented 
{code}

There's no parser yet but if you want you can try implementing one, that takes a Reader and provides an Iterator<CrankstartCommandLine> by parsing according to the above example. I'm not planning to work on this in the next few days, will get back to it next week.

> Add ability to configure OSGi components from crank files
> ---------------------------------------------------------
>
>                 Key: SLING-3528
>                 URL: https://issues.apache.org/jira/browse/SLING-3528
>             Project: Sling
>          Issue Type: New Feature
>            Reporter: Artyom Stetsenko
>              Labels: crankstart, osgi-config
>         Attachments: crankstart-config.patch, crankstart-config.patch
>
>
> Users should be able to specify OSGi configs inside .crank.txt files.



--
This message was sent by Atlassian JIRA
(v6.2#6252)