You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jörg Hoh (JIRA)" <ji...@apache.org> on 2018/09/21 09:15:00 UTC
[jira] [Updated] (SLING-7942) RepoInit: language should not require
newlines
[ https://issues.apache.org/jira/browse/SLING-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jörg Hoh updated SLING-7942:
----------------------------
Description:
At the moment the repoinit used to define the scriptlets requires newlines. While this doesn't matter when dealing with full-blown models, it gets cumbersome when you just want to create an instance of the RepositoryInitializerFactory configuration to perform a single action (e.g. setting an ACL on a path for a certain user).
When I add such a configuration and set the scripts property to ```set ACL on /var allow jcr:read for anonymous end``` the parser throws this exception:
{noformat}
...
Caused by: org.apache.sling.repoinit.parser.impl.ParseException: Encountered " "allow" "allow "" at line 1, column 29.
Was expecting:
"\n" ...
{noformat}
I can possibly find out how I can get this newline character in there, but it's getting cumbersome to work with.
It would be much better if the EOL tokens are optional. Don't know if that's possible though.
was:
At the moment the repoinit used to define the scriptlets requires newlines. While this doesn't matter when dealing with full-blown models, it gets cumbersome when you just want to create an instance of the RepositoryInitializerFactory configuration to perform a single action (e.g. setting an ACL on a path for a certain user).
When I add such a configuration and set the scripts property to ```set ACL on /var allow jcr:read for anonymous end``` the parser throws this exception:
{noformat}
...
Caused by: org.apache.sling.repoinit.parser.impl.ParseException: Encountered " "allow" "allow "" at line 1, column 29.
Was expecting:
"\n" ...
{noformat}
I can possibly find out how I can get this newline character in there (and btw: defining the EOL token as "\n" is veeery problematic, there are other platforms than unix!), but it's getting cumbersome to work with.
It would be much better if the EOL tokens are optional. Don't know if that's possible though.
> RepoInit: language should not require newlines
> ----------------------------------------------
>
> Key: SLING-7942
> URL: https://issues.apache.org/jira/browse/SLING-7942
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
> Affects Versions: Repoinit Parser 1.2.2
> Reporter: Jörg Hoh
> Priority: Major
>
> At the moment the repoinit used to define the scriptlets requires newlines. While this doesn't matter when dealing with full-blown models, it gets cumbersome when you just want to create an instance of the RepositoryInitializerFactory configuration to perform a single action (e.g. setting an ACL on a path for a certain user).
> When I add such a configuration and set the scripts property to ```set ACL on /var allow jcr:read for anonymous end``` the parser throws this exception:
> {noformat}
> ...
> Caused by: org.apache.sling.repoinit.parser.impl.ParseException: Encountered " "allow" "allow "" at line 1, column 29.
> Was expecting:
> "\n" ...
> {noformat}
> I can possibly find out how I can get this newline character in there, but it's getting cumbersome to work with.
> It would be much better if the EOL tokens are optional. Don't know if that's possible though.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)