[jira] [Resolved] (SLING-7715) PathPipe default autosave value should be false

[Nicolas Peltier (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Peltier resolved SLING-7715.

   Resolution: Fixed
 Assignee: Nicolas Peltier
Fix Version/s: pipes 3.0.0

> PathPipe default autosave value should be false
> ---
>
> Key: SLING-7715
> URL: https://issues.apache.org/jira/browse/SLING-7715
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: pipes 2.0.2
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Major
> Fix For: pipes 3.0.0
>
>
> default value for autosave right now is {{true}} which leads to very bad 
> default performances while they could be better, and require users to know 
> that setting. 
> Setting it to false by default will lead to pipe error where it will be 
> easier for the user to understand why it's failing and to set the parameter 
> to {{true}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7715) PathPipe default autosave value should be false

[Nicolas Peltier (JIRA)]

Nicolas Peltier created SLING-7715:
--

 Summary: PathPipe default autosave value should be false
 Key: SLING-7715
 URL: https://issues.apache.org/jira/browse/SLING-7715
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Affects Versions: pipes 2.0.2
Reporter: Nicolas Peltier


default value for autosave right now is {{true}} which leads to very bad 
default performances while they could be better, and require users to know that 
setting. 
Setting it to false by default will lead to pipe error where it will be easier 
for the user to understand why it's failing and to set the parameter to {{true}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSSION][API][PROPOSAL] Adding Stream generator to Sling API

[Daniel Klco]

On Thu, Jun 7, 2018 at 9:05 AM, Bertrand Delacretaz 
wrote:

> On Thu, Jun 7, 2018 at 3:00 PM, Jason E Bailey  wrote:
> > ...I really don't think creating a dedicated bundle that consists of a
> single class
> > is really appropriate
>
> That's not necessarily a problem, especially if it's meant to avoid
> touching our api bundle, which we're always quite reluctant to touch
> unless really needed.
>

I'm of the opinion that it could make sense to update the API to support
streams, but I think first, we should have a stand-alone option. A) this
will help evaluate the best approach for the eventual inclusion into the
Sling API. B) This will also allow developers using older versions of the
Sling API and underling implementations use Lamdba expressions immediately
instead of having to update their stack to support the newest API (which
often will not be possible for people running proprietary software such as
AEM).


>
> And I suppose your code will have more than that class, in total, so
> maybe you can (at least initially) put that utility class in your main
> bundle if you have one? If you do this you can quietly work on that in
> isolation, and once you have enough to demonstrate the whole thing we
> can discuss how to best organize it.
>

I'd think you'd need at least the ResourceStream, an adapter factory and
ideally the Predicates from your original project. Ideally, IMO this should
be a "quick start" to using Streams with Sling.


>
> > ...I've come to realize that I'm doing an extremely poor job at
> explaining
> > the vision behind this and/or communicating the overall benefits...
>
> We're all busy, so maybe we're not paying enough attention...don't despair
> ;-)
>

I for one am super excited for this. :-) Once the standalone bundle is
ready, it'd be great to provide a few examples of pre and post code using
the Resource Stream API.


>
> -Bertrand
>

[jira] [Commented] (SLING-7714) User/Groups vault packages are not getting created with wrong filters

[Ankit Aggarwal (JIRA)]

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

Ankit Aggarwal commented on SLING-7714:
---

[~marett], [~mpetria]

I have attached two patches [^CQ-4245994_2.patch][^CQ-4245994.patch] with minor 
differences but the resultant vault packages are different in each case when 
there are no properties filter configured. Both works fine when there are 
properties filter configured in "Apache Sling Distribution Packaging - Vault 
Package Builder Factory".

> User/Groups vault packages are not getting created with wrong filters
> -
>
> Key: SLING-7714
> URL: https://issues.apache.org/jira/browse/SLING-7714
> Project: Sling
>  Issue Type: Bug
>  Components: Content Distribution
>Affects Versions: Content Distribution Core 0.2.10
>Reporter: Ankit Aggarwal
>Priority: Major
> Attachments: CQ-4245994.patch, CQ-4245994_2.patch, 
> faulty-pkg-4503-1.0.zip, pkg-4503-additionnal.zip, pkg-4503-base.zip, 
> pre-SP2-1.0.zip
>
>
> After upgrading the customer stage instances (this is ManagedService), it has 
> been observed that the user synchronization si broken.
> After investigation, I observed that not only the user sync is broken but 
> possible the whole instance, as many "rep:policy" nodes have been removed.
>  
> h4. Steps to reproduce
>  # start a 3 instances (1 author, 2 publishers) setup on AEM 6.3
>  # enable the user synchronization following the documentation
>  # upgrade publishers to SP2, then author
>  # create a new user on pub1
>  
> Expected result:
> User is propagated/synchronized on pub2 without side-effect
>  
> Actual result:
> User is propagated/synchronized on pub2, but the following rep:policy nodes 
> are removed (maybe non exhaustive list):
>  * /rep:policy
>  * /home/rep:policy
>  * /home/users/rep:policy
>  
> I reproduce this issue and tested again the procedure, but I disabled the 
> sync agent on Author, so that I could retrieve the package being replicated 
> on the other publisher (pub2) to inspect its definition.
>  
> [faulty-pkg-4503-1.0.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594552/2594552_faulty-pkg-4503-1.0.zip]
>  is a raw package containing the "/var/sling/distribution" and 
> "/var/eventing/jobs/unassigned" of pub1 where I created the new user post-SP2 
> install, if you require more details.
>  
> [pkg-4503-base.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594549/2594549_pkg-4503-base.zip]
>  and 
> [pkg-4503-additionnal.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594550/2594550_pkg-4503-additionnal.zip]
>  are the actual packages that will be distributed by SCD, and installed on 
> pub2. I extracted them from 
> [faulty-pkg-4503-1.0.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594552/2594552_faulty-pkg-4503-1.0.zip]
>  from the following path 
> "faulty-pkg-4503-1.0.zip\jcr_root\var\sling\distribution\packages\socialpubsync-vlt\data\dstrpck-1528203802286-58c3aa28-a83a-4a74-a781-e48e5415a541\"
>  and "dstrpck-1528203802288-c6416288-9b4d-43cc-8967-c09215bd6a91" (they are 
> the "bin" file renamed).
>  
> Checking their _META-INF\vault\filter.xml,_ I think that the filter 
> definition is incorrect:
> {code:java}
> 
>   
> 
>   
>   
> 
>   
>   
> {code}
>  
> *The last entry with filter on "/" looks suspicious.*
>  
> On a pre-SP2 instance, I have the following which is correct:
> {code:java}
> 
>   
> 
>   
>   
> 
>   
> {code}
>  
> I assume that the ACL are merged and as the filter is pointing to "/" and the 
> package doesn't have any rep:policy for any nodes in the hierarchy, it is 
> removing the existing ones.
>  
> PS: I have some instances setup to share if needed.
> *Btw now that the issue is qualified I guess you only need to setup one 
> single publisher, enable usersync, and create a new user. This should trigger 
> the package creation containing the invalid filter definition.*



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7714) User/Groups vault packages are not getting created with wrong filters

[Ankit Aggarwal (JIRA)]

Ankit Aggarwal created SLING-7714:
-

 Summary: User/Groups vault packages are not getting created with 
wrong filters
 Key: SLING-7714
 URL: https://issues.apache.org/jira/browse/SLING-7714
 Project: Sling
  Issue Type: Bug
  Components: Content Distribution
Affects Versions: Content Distribution Core 0.2.10
Reporter: Ankit Aggarwal
 Attachments: CQ-4245994.patch, CQ-4245994_2.patch, 
faulty-pkg-4503-1.0.zip, pkg-4503-additionnal.zip, pkg-4503-base.zip, 
pre-SP2-1.0.zip

After upgrading the customer stage instances (this is ManagedService), it has 
been observed that the user synchronization si broken.

After investigation, I observed that not only the user sync is broken but 
possible the whole instance, as many "rep:policy" nodes have been removed.

 
h4. Steps to reproduce
 # start a 3 instances (1 author, 2 publishers) setup on AEM 6.3
 # enable the user synchronization following the documentation
 # upgrade publishers to SP2, then author
 # create a new user on pub1

 

Expected result:

User is propagated/synchronized on pub2 without side-effect

 

Actual result:

User is propagated/synchronized on pub2, but the following rep:policy nodes are 
removed (maybe non exhaustive list):
 * /rep:policy
 * /home/rep:policy
 * /home/users/rep:policy

 

I reproduce this issue and tested again the procedure, but I disabled the sync 
agent on Author, so that I could retrieve the package being replicated on the 
other publisher (pub2) to inspect its definition.

 

[faulty-pkg-4503-1.0.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594552/2594552_faulty-pkg-4503-1.0.zip]
 is a raw package containing the "/var/sling/distribution" and 
"/var/eventing/jobs/unassigned" of pub1 where I created the new user post-SP2 
install, if you require more details.

 

[pkg-4503-base.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594549/2594549_pkg-4503-base.zip]
 and 
[pkg-4503-additionnal.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594550/2594550_pkg-4503-additionnal.zip]
 are the actual packages that will be distributed by SCD, and installed on 
pub2. I extracted them from 
[faulty-pkg-4503-1.0.zip^!/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!^|https://issues.apache.org/secure/attachment/2594552/2594552_faulty-pkg-4503-1.0.zip]
 from the following path 
"faulty-pkg-4503-1.0.zip\jcr_root\var\sling\distribution\packages\socialpubsync-vlt\data\dstrpck-1528203802286-58c3aa28-a83a-4a74-a781-e48e5415a541\"
 and "dstrpck-1528203802288-c6416288-9b4d-43cc-8967-c09215bd6a91" (they are the 
"bin" file renamed).

 

Checking their _META-INF\vault\filter.xml,_ I think that the filter definition 
is incorrect:
{code:java}

  

  

  

  

  
{code}
 

*The last entry with filter on "/" looks suspicious.*

 

On a pre-SP2 instance, I have the following which is correct:
{code:java}

  

  

  

  
{code}
 

I assume that the ACL are merged and as the filter is pointing to "/" and the 
package doesn't have any rep:policy for any nodes in the hierarchy, it is 
removing the existing ones.

 

PS: I have some instances setup to share if needed.

*Btw now that the issue is qualified I guess you only need to setup one single 
publisher, enable usersync, and create a new user. This should trigger the 
package creation containing the invalid filter definition.*



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSSION][API][PROPOSAL] Adding Stream generator to Sling API

[Bertrand Delacretaz]

On Thu, Jun 7, 2018 at 3:00 PM, Jason E Bailey  wrote:
> ...I really don't think creating a dedicated bundle that consists of a single 
> class
> is really appropriate

That's not necessarily a problem, especially if it's meant to avoid
touching our api bundle, which we're always quite reluctant to touch
unless really needed.

And I suppose your code will have more than that class, in total, so
maybe you can (at least initially) put that utility class in your main
bundle if you have one? If you do this you can quietly work on that in
isolation, and once you have enough to demonstrate the whole thing we
can discuss how to best organize it.

> ...I've come to realize that I'm doing an extremely poor job at explaining
> the vision behind this and/or communicating the overall benefits...

We're all busy, so maybe we're not paying enough attention...don't despair ;-)

-Bertrand

Re: [DISCUSSION][API][PROPOSAL] Adding Stream generator to Sling API

[Jason E Bailey]

Or,  you know,  new Streamer(resource) :)

I really don't think creating a dedicated bundle that consists of a single 
class is really appropriate.  I've gone ahead and closed the pull request 
because I've come to realize that I'm doing an extremely poor job at explaining 
the vision behind this and/or communicating the overall benefits.

I'll focus instead on creating the other bundles that handle Predicate creation 
and maybe once those are in place I'll revisit where to put this utility.

- Jason

On Wed, Jun 6, 2018, at 4:59 PM, Bertrand Delacretaz wrote:
> On Wed, Jun 6, 2018 at 7:23 PM, Jörg Hoh  wrote:
> > ...Streamer stream = resource.adaptTo(Streamer.class);
> > could do the trick. Then you can have everything in a dedicated bundle and
> > there is no need to change any of the sling core APIs or bundles
> 
> +1
> 
> -Bertrand

[jira] [Commented] (SLING-7713) [HTL] Add support for data-sly-unwrap identifiers

[Radu Cotescu (JIRA)]

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

Radu Cotescu commented on SLING-7713:
-

Implemented in [commit 
9eefb61|https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler/commit/9eefb61].

> [HTL] Add support for data-sly-unwrap identifiers
> -
>
> Key: SLING-7713
> URL: https://issues.apache.org/jira/browse/SLING-7713
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
>
> According to [0], {{data-sly-unwrap}} will support identifiers starting with 
> version 1.4 of the HTL language specification.
> [0] - https://github.com/Adobe-Marketing-Cloud/htl-spec/issues/52



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7713) [HTL] Add support for data-sly-unwrap identifiers

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-7713:
---

 Summary: [HTL] Add support for data-sly-unwrap identifiers
 Key: SLING-7713
 URL: https://issues.apache.org/jira/browse/SLING-7713
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu


According to [0], {{data-sly-unwrap}} will support identifiers starting with 
version 1.4 of the HTL language specification.

[0] - https://github.com/Adobe-Marketing-Cloud/htl-spec/issues/52



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7712) slig-mock: make register Sling Models from classpath optionaly

[Andrey Bardashevsky (JIRA)]

Andrey Bardashevsky created SLING-7712:
--

 Summary: slig-mock: make register Sling Models from classpath 
optionaly
 Key: SLING-7712
 URL: https://issues.apache.org/jira/browse/SLING-7712
 Project: Sling
  Issue Type: Improvement
  Components: Testing
Affects Versions: Testing Sling Mock 2.2.18, Testing Sling Mock 1.9.12
Reporter: Andrey Bardashevsky


Registering all sling models from classpath leads to slow down tests 
dramatically.

Steps to reproduce:
 # Register several models.
 # In context.afterSetup() register several custom injetors that implements 
StaticInjectAnnotationProcessorFactory

Each injector registration leads to update every model (ModelAdapterFactory) 
that slow downs test dramatically, when you have 300+ models and 5-6 injectors 
that register in setup method before each test.

Workaround is to register injectors before models.

Please implement optional registration all sling models from classpath.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2

[Karl Pauls]

+1

regards,

Karl

On Thu, Jun 7, 2018 at 11:24 AM, Radu Cotescu  wrote:
> +1
> On 5 June 2018 at 16:28:43, dav...@apache.org (dav...@apache.org) wrote:
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert



-- 
Karl Pauls
karlpa...@gmail.com

[jira] [Commented] (SLING-7685) data-sly-resource throws RecursionTooDeepException when used with dynamic variables that are null / empty

[Radu Cotescu (JIRA)]

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

Radu Cotescu commented on SLING-7685:
-

[~sagarsane], can you validate this issue on Apache Sling? Your stack trace 
shows that the caller is 
{{com.adobe.cq.sightly.WCMScriptHelper.includeScript(WCMScriptHelper.java:227)}},
 hence I think this might be a bug in AEM.

> data-sly-resource throws RecursionTooDeepException when used with dynamic 
> variables that are null / empty
> -
>
> Key: SLING-7685
> URL: https://issues.apache.org/jira/browse/SLING-7685
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Reporter: Sagar Sane
>Priority: Major
>
> I am on AEM 6.3.1.2.
> If I use *data-sly-resource* w/ dynamic variable which is null or empty, I 
> get a *RecursionTooDeepException* runtime. The stack looks something like 
> this (redacting project specific stuff): 
> {code:java}
> 2018-05-26 20:18:33,335 *ERROR* [0:0:0:0:0:0:0:1 [1527380309473] GET 
> /content/ HTTP/1.1] 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught 
> SlingException
> org.apache.sling.scripting.sightly.SightlyException: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.request.RecursionTooDeepException: /content/
> at 
> 

[jira] [Assigned] (SLING-7685) data-sly-resource throws RecursionTooDeepException when used with dynamic variables that are null / empty

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-7685:
---

Assignee: Radu Cotescu

> data-sly-resource throws RecursionTooDeepException when used with dynamic 
> variables that are null / empty
> -
>
> Key: SLING-7685
> URL: https://issues.apache.org/jira/browse/SLING-7685
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Reporter: Sagar Sane
>Assignee: Radu Cotescu
>Priority: Major
>
> I am on AEM 6.3.1.2.
> If I use *data-sly-resource* w/ dynamic variable which is null or empty, I 
> get a *RecursionTooDeepException* runtime. The stack looks something like 
> this (redacting project specific stuff): 
> {code:java}
> 2018-05-26 20:18:33,335 *ERROR* [0:0:0:0:0:0:0:1 [1527380309473] GET 
> /content/ HTTP/1.1] 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught 
> SlingException
> org.apache.sling.scripting.sightly.SightlyException: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: 
> org.apache.sling.api.request.RecursionTooDeepException: /content/
> at 
> com.adobe.cq.sightly.WCMScriptHelper.includeScript(WCMScriptHelper.java:227)
> at 
> com.adobe.cq.sightly.internal.extensions.IncludeExtension.call(IncludeExtension.java:73)
> at 
> 

Re: [VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2

[Radu Cotescu]

+1
On 5 June 2018 at 16:28:43, dav...@apache.org (dav...@apache.org) wrote:

Please vote to approve this release: 

[ ] +1 Approve the release 
[ ] 0 Don't care 
[ ] -1 Don't release, because ... 

This majority vote is open for at least 72 hours. 

Best regards, 

David Bosschaert 

Re: [VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2

[Carsten Ziegeler]

+1


David Bosschaert wrote
> Hi all,
> 
> I'd like release the following components:
> 
> org.apache.sling.feature 0.1.2
> Issues resolved:
> https://issues.apache.org/jira/projects/SLING/versions/12343303
> 
> org.apache.sling.feature-io 0.1.2
> Issues resolved:
> https://issues.apache.org/jira/projects/SLING/versions/12343302
> 
> org.apache.sling.feature-analyser 0.1.2
> No issues resolved, but based on feature/feature-io 0.1.2
> 
> org.apache.sling.feature-modelconverter 0.1.2
> Issues resolved:
> https://issues.apache.org/jira/projects/SLING/versions/12343300
> 
> This release would also be needed in order to be able to do the next
> release of the slingstart-maven-plugin.
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1912
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-
> release.git;a=blob;f=check_staged_release.sh;hb=HEAD
> 
> Usage:
> sh check_staged_release.sh 1912 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
> This majority vote is open for at least 72 hours.
> 
> Best regards,
> 
> David Bosschaert
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2

[Robert Munteanu]

On Tue, 2018-06-05 at 15:28 +0100, dav...@apache.org wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2

[davidb]

Here's my +1

David

On 5 June 2018 at 15:28,  wrote:

> Hi all,
>
> I'd like release the following components:
>
> org.apache.sling.feature 0.1.2
> Issues resolved: https://issues.apache.org/jira/projects/
> SLING/versions/12343303
>
> org.apache.sling.feature-io 0.1.2
> Issues resolved: https://issues.apache.org/jira/projects/
> SLING/versions/12343302
>
> org.apache.sling.feature-analyser 0.1.2
> No issues resolved, but based on feature/feature-io 0.1.2
>
> org.apache.sling.feature-modelconverter 0.1.2
> Issues resolved: https://issues.apache.org/jira/projects/SLING/versions/
> 12343300
>
> This release would also be needed in order to be able to do the next
> release of the slingstart-maven-plugin.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1912
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.
> git;a=blob;f=check_staged_release.sh;hb=HEAD
>
> Usage:
> sh check_staged_release.sh 1912 /tmp/sling-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert
>

Re: Plan to release servlet annotations (https://issues.apache.org/jira/browse/SLING-7624)

[Robert Munteanu]

On Thu, 2018-06-07 at 08:36 +0200, Konrad Windszus wrote:
> Since the discussion around the servlet annotations in https://issues
> .apache.org/jira/browse/SLING-7624  owse/SLING-7624> settled a bit I would like to do a first release
> soon. Please raise your voice now if you have any concerns with the
> annotations how they are currently structured (https://github.com/apa
> che/sling-org-apache-sling-servlets-annotations  pache/sling-org-apache-sling-servlets-annotations>).
> I plan on starting the release vote next week, in parallel I will
> also extend the documentation at https://sling.apache.org/documentati
> on/the-sling-engine/servlets.html  tion/the-sling-engine/servlets.html> to document the new annotations
> and also give some hints on how to migrate from SCR annotations.

For the record, 'live' examples of the annotations are in the IT
project at

  https://github.com/apache/sling-org-apache-sling-servlets-annotations-it

Robert

[jira] [Updated] (SLING-7711) [JIRA] Access to assign tickets / sub-tasks

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-7711:
---
Component/s: Build and Source Control
 Issue Type: Task  (was: Improvement)

> [JIRA] Access to assign tickets / sub-tasks
> ---
>
> Key: SLING-7711
> URL: https://issues.apache.org/jira/browse/SLING-7711
> Project: Sling
>  Issue Type: Task
>  Components: Build and Source Control
>Reporter: Chris Millar
>Assignee: Robert Munteanu
>Priority: Major
>
> As a user of the issues website, I would like access to update issues and 
> assign tasks so that I can effectively manage tickets I make.
> Username: cmillar
> Email: cmil...@apache.org
> I believe [~radu.cotescu] has helped someone recently with this. Any help is 
> greatly appreciated!
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7711) [JIRA] Access to assign tickets / sub-tasks

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-7711.

Resolution: Fixed
  Assignee: Robert Munteanu

I added you to the Jira admin group, you should now be able to assign issues.

> [JIRA] Access to assign tickets / sub-tasks
> ---
>
> Key: SLING-7711
> URL: https://issues.apache.org/jira/browse/SLING-7711
> Project: Sling
>  Issue Type: Improvement
>Reporter: Chris Millar
>Assignee: Robert Munteanu
>Priority: Major
>
> As a user of the issues website, I would like access to update issues and 
> assign tasks so that I can effectively manage tickets I make.
> Username: cmillar
> Email: cmil...@apache.org
> I believe [~radu.cotescu] has helped someone recently with this. Any help is 
> greatly appreciated!
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Plan to release servlet annotations (https://issues.apache.org/jira/browse/SLING-7624)

[Konrad Windszus]

Since the discussion around the servlet annotations in 
https://issues.apache.org/jira/browse/SLING-7624 
 settled a bit I would like 
to do a first release soon. Please raise your voice now if you have any 
concerns with the annotations how they are currently structured 
(https://github.com/apache/sling-org-apache-sling-servlets-annotations 
).
I plan on starting the release vote next week, in parallel I will also extend 
the documentation at 
https://sling.apache.org/documentation/the-sling-engine/servlets.html 
 to 
document the new annotations and also give some hints on how to migrate from 
SCR annotations.

Thanks,
Konrad

[jira] [Commented] (SLING-7624) Add OSGi7 component property annotations for Servlet and Filter

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-7624:


The repos have been pushed meanwhile to 
https://github.com/apache/sling-org-apache-sling-servlets-annotations and 
https://github.com/apache/sling-org-apache-sling-servlets-annotations-it.

> Add OSGi7 component property annotations for Servlet and Filter
> ---
>
> Key: SLING-7624
> URL: https://issues.apache.org/jira/browse/SLING-7624
> Project: Sling
>  Issue Type: New Feature
>  Components: Servlets
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Previously there were annotations hosted at Felix for Sling Servlets/Filters 
> as custom Felix SCR annotations 
> (https://github.com/apache/felix/tree/trunk/tools/org.apache.felix.scr.annotations/src/main/java/org/apache/felix/scr/annotations/sling).
>  With OSGi R7 and DS 1.4 component property annotations are specified. Sling 
> should provide those annotations in a dedicated new artifact. Compare also 
> with FELIX-5396.
> Those are supported in the upcoming bnd 4.0 
> (https://github.com/bndtools/bnd/issues/2163).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7669) StartupManager overwrites the frameworkstartlevel property and there is no way to retrieve the intended target start level

[Andrei Dulvac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulvac resolved SLING-7669.
--
   Resolution: Fixed
Fix Version/s: Launchpad Base 2.6.26

> StartupManager overwrites the frameworkstartlevel property and there is no 
> way to retrieve the intended target start level
> --
>
> Key: SLING-7669
> URL: https://issues.apache.org/jira/browse/SLING-7669
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Reporter: Andrei Dulvac
>Assignee: Andrei Dulvac
>Priority: Major
> Fix For: Launchpad Base 2.6.26
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> In incremental mode, the {{StartupManager}} keeps the target startlevel in a 
> private field, but overwrites "org.osgi.framework.startlevel.beginning" (for 
> a reason), but leaves no other way to retrieve the "target start level" of 
> the application.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)