[jira] [Commented] (SLING-6025) Context-Aware Config: Provide configuration parameter metadata

[ https://issues.apache.org/jira/browse/SLING-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469114#comment-15469114 ] Carsten Ziegeler commented on SLING-6025: - Ok, so the resource/performance problems could be

[jira] [Commented] (SLING-6025) Context-Aware Config: Provide configuration parameter metadata

[ https://issues.apache.org/jira/browse/SLING-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468685#comment-15468685 ] Stefan Seifert commented on SLING-6025: --- bq. However I think we should move the heavy work to the

[jira] [Commented] (SLING-5768) Introduce sling:resourceTypes as extension to Oak permission system

[ https://issues.apache.org/jira/browse/SLING-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468638#comment-15468638 ] ASF GitHub Bot commented on SLING-5768: --- Github user ghenzler closed the pull request at:

[jira] [Commented] (SLING-6042) Use sling:resourceTypesWithDescendants instead of sling:resourceTypesWithChildren

[ https://issues.apache.org/jira/browse/SLING-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468639#comment-15468639 ] ASF GitHub Bot commented on SLING-6042: --- GitHub user ghenzler opened a pull request:

[GitHub] sling pull request #168: SLING-6042 using sling:resourceTypesWithDescendants...

GitHub user ghenzler opened a pull request: https://github.com/apache/sling/pull/168 SLING-6042 using sling:resourceTypesWithDescendants instead of sling:resourceTypesWithChildren now You can merge this pull request into a Git repository by running: $ git pull

[GitHub] sling pull request #163: SLING-5768 using sling:resourceTypesWithDescendants...

Github user ghenzler closed the pull request at: https://github.com/apache/sling/pull/163 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (SLING-5768) Introduce sling:resourceTypes as extension to Oak permission system

[ https://issues.apache.org/jira/browse/SLING-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468624#comment-15468624 ] Georg Henzler commented on SLING-5768: -- Created follow up ticket for PR: SLING-6042 > Introduce

[jira] [Created] (SLING-6042) Use sling:resourceTypesWithDescendants instead of sling:resourceTypesWithChildren

Georg Henzler created SLING-6042: Summary: Use sling:resourceTypesWithDescendants instead of sling:resourceTypesWithChildren Key: SLING-6042 URL: https://issues.apache.org/jira/browse/SLING-6042

http-based/teleporter unit tests vs. paxexam integraiton tests (was: RE: flaky integration tests with teleporte rule)

>To be honest, I see only 2, maybe 3 cases where managing tests over HTTP >makes >sense: > >1. you do not want to start your (fat and slow) application under test from >the tests itself >2. you need a different runner than PaxExam (runners and rules are gone in >JUnit 5) >3. reuse of tests like

[jira] [Commented] (SLING-5356) New ResourceBuilder module - fluent API to create content structures

[ https://issues.apache.org/jira/browse/SLING-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468587#comment-15468587 ] Stefan Seifert commented on SLING-5356: --- [~bdelacretaz] is there any important open on this ticket -

[GitHub] sling pull request #167: SLING-6040 Add ResourceBuilder Support to sling-moc...

Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/167 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6040. --- Resolution: Fixed Completed: At revision: 1759511 sling-mock 1.x und sling-mock 2.x um

[jira] [Commented] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468562#comment-15468562 ] ASF GitHub Bot commented on SLING-6040: --- Github user asfgit closed the pull request at:

[jira] [Updated] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6040: -- Fix Version/s: Testing Sling Mock 1.7.2 > Add ResourceBuilder Support to sling-mock >

[jira] [Commented] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468526#comment-15468526 ] Stefan Seifert commented on SLING-6040: --- Completed: At revision: 1759507 split up resourcebuilder

[jira] [Commented] (SLING-6039) ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory

[ https://issues.apache.org/jira/browse/SLING-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468447#comment-15468447 ] ASF GitHub Bot commented on SLING-6039: --- Github user asfgit closed the pull request at:

[GitHub] sling pull request #166: SLING-6039 ResourceBuilder: Split up ResourceBuilde...

Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/166 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (SLING-6039) ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory

[ https://issues.apache.org/jira/browse/SLING-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6039. --- Resolution: Fixed Completed: At revision: 1759501 applied patch Completed: At revision:

[jira] [Commented] (SLING-6031) Teleporter.getService() should wait for required services

[ https://issues.apache.org/jira/browse/SLING-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468404#comment-15468404 ] ASF GitHub Bot commented on SLING-6031: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (SLING-6036) ResourceBuilder: Reusing ResourceBuilder instances

[ https://issues.apache.org/jira/browse/SLING-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6036. --- Resolution: Fixed > ResourceBuilder: Reusing ResourceBuilder instances >

[jira] [Resolved] (SLING-6031) Teleporter.getService() should wait for required services

[ https://issues.apache.org/jira/browse/SLING-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6031. --- Resolution: Fixed Completed: At revision: 1759492 update junit.core/junit.teleporter (with

[GitHub] sling pull request #164: SLING-6031 Teleporter.getService() should wait for ...

Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/164 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (SLING-6037) sling pipes additionnal bindings should be configurable as resources

[ https://issues.apache.org/jira/browse/SLING-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-6037. Resolution: Not A Problem basically this feature already exists with additionalBindings

Re: What's wrong with Sightly?

It was a response to a third party's legal demand, not a marketing fail. A change to the name used by the software is suggested, not just a change of the language name. In fact, the language name would not normally be an issue. Roy > On Sep 6, 2016, at 6:39 AM, Oliver Lietz

[jira] [Commented] (SLING-6036) ResourceBuilder: Reusing ResourceBuilder instances

[ https://issues.apache.org/jira/browse/SLING-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467623#comment-15467623 ] Bertrand Delacretaz commented on SLING-6036: Looks great, thanks! > ResourceBuilder: Reusing

[jira] [Commented] (SLING-6031) Teleporter.getService() should wait for required services

[ https://issues.apache.org/jira/browse/SLING-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467630#comment-15467630 ] Bertrand Delacretaz commented on SLING-6031: Looks great, thanks! I would just add a constant

[jira] [Resolved] (SLING-6041) Avoid embedding httpasyncclient dependency in SCD core

[ https://issues.apache.org/jira/browse/SLING-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-6041. Resolution: Fixed fixed in r1759441. > Avoid embedding httpasyncclient dependency in SCD

[jira] [Created] (SLING-6041) Avoid embedding httpasyncclient dependency in SCD core

Tommaso Teofili created SLING-6041: -- Summary: Avoid embedding httpasyncclient dependency in SCD core Key: SLING-6041 URL: https://issues.apache.org/jira/browse/SLING-6041 Project: Sling

[jira] [Commented] (SLING-6039) ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory

[ https://issues.apache.org/jira/browse/SLING-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467620#comment-15467620 ] Bertrand Delacretaz commented on SLING-6039: +1, obviously, thanks! > ResourceBuilder: Split

[jira] [Commented] (SLING-6025) Context-Aware Config: Provide configuration parameter metadata

[ https://issues.apache.org/jira/browse/SLING-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467600#comment-15467600 ] Carsten Ziegeler commented on SLING-6025: - Thanks for testing this [~sseif...@pro-vision.de]

Re: What's wrong with Sightly?

Done in https://svn.apache.org/r1759438 On Tue, 6 Sep 2016 at 16:22 Radu Cotescu wrote: > There's one redirect that we need to put in place: > > > https://sling.apache.org/documentation/bundles/scripting/scripting-sightly.html > --> >

Re: What's wrong with Sightly?

There's one redirect that we need to put in place: https://sling.apache.org/documentation/bundles/scripting/scripting-sightly.html --> https://sling.apache.org/documentation/bundles/scripting/scripting-htl.html I'll also revert the changes to the Sling Launchpad 8 and Sling IDE Tooling 1.1

Re: What's wrong with Sightly?

On Tue, Sep 6, 2016 at 3:53 PM, Oliver Lietz wrote: > On Tuesday 06 September 2016 13:50:21 Radu Cotescu wrote: >> On Tue, 6 Sep 2016 at 15:40 Oliver Lietz wrote: >> > We now have a break between names and modules/packages and a bunch of dead >> >

Re: September Board Report

Thanks, I submitted it. Carsten > On Mon, 2016-09-05 at 07:55 -0700, Carsten Ziegeler wrote: >> Hi, >> >> I've prepared the September board report here: >> >> https://cwiki.apache.org/confluence/display/SLING/Status+Report+Septe >> mber+2016 >> >> Please review, adjust, comment >> > > Looks

Re: flaky integration tests with teleporte rule

On Friday 02 September 2016 10:32:38 Stefan Seifert wrote: > i've used the teleporter rules in the integration tests for the > context-aware configs: > https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/contextawar > e-config/integration-tests > > on my machines they run smooth on a

Re: What's wrong with Sightly?

On Tuesday 06 September 2016 13:50:21 Radu Cotescu wrote: > On Tue, 6 Sep 2016 at 15:40 Oliver Lietz wrote: > > We now have a break between names and modules/packages and a bunch of dead > > links. > > Which dead links are you referring to? The ones we don't control:

Re: What's wrong with Sightly?

On Tue, 6 Sep 2016 at 15:40 Oliver Lietz wrote: > > We now have a break between names and modules/packages and a bunch of dead > links. > > Which dead links are you referring to? > @Radu, can you please revert the changes in Sling Launchpad 8 and Sling IDE > Tooling 1.1

Re: What's wrong with Sightly?

On Tuesday 06 September 2016 00:03:22 Justin Edelson wrote: > Simply put - because Adobe changed the language name. Since Adobe defines > the specification and Sling just contains the implementation, it makes > sense for the implementation to have the same name as the specification. > Otherwise,

[jira] [Assigned] (SLING-5991) [SCD] Evaluate avoiding to buffer the whole packages before streaming

[ https://issues.apache.org/jira/browse/SLING-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili reassigned SLING-5991: -- Assignee: Tommaso Teofili > [SCD] Evaluate avoiding to buffer the whole packages

[jira] [Commented] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467385#comment-15467385 ] Carsten Ziegeler commented on SLING-6040: - [~sseif...@pro-vision.de] Please ignore my comment

[jira] [Updated] (SLING-5994) Move from EventHandler to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanish Bansal updated SLING-5994: - Summary: Move from EventHandler to new ResourceChangeListener API (was: Move from Deprecated

Re: What's wrong with Sightly?

Hi, Everything's already there - I've just published the update. :) Cheers, Radu On Tue, 6 Sep 2016 at 13:37 Bertrand Delacretaz wrote: > On Tue, Sep 6, 2016 at 11:32 AM, Stefan Seifert > wrote: > > ...perhaps we should also add an addition

Re: What's wrong with Sightly?

On Tue, Sep 6, 2016 at 11:32 AM, Stefan Seifert wrote: > ...perhaps we should also add an addition like "formerly known as Sightly, > renamed in August 2016" etc., > so people do not get confused esp. as slightly still occurs in all technical > names on this page... +1,

[jira] [Resolved] (SLING-5818) make sling pipe writer a persistent configuration

[ https://issues.apache.org/jira/browse/SLING-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5818. Resolution: Fixed Fix Version/s: Pipes 1.0.0 Applied in

[jira] [Assigned] (SLING-5818) make sling pipe writer a persistent configuration

[ https://issues.apache.org/jira/browse/SLING-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-5818: -- Assignee: Robert Munteanu > make sling pipe writer a persistent configuration >

[jira] [Resolved] (SLING-6032) Not sling pipe

[ https://issues.apache.org/jira/browse/SLING-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6032. Resolution: Fixed Applied in https://svn.apache.org/r1759409, thanks for your contribution!

[jira] [Assigned] (SLING-6032) Not sling pipe

[ https://issues.apache.org/jira/browse/SLING-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-6032: -- Assignee: Robert Munteanu > Not sling pipe > -- > > Key:

[jira] [Updated] (SLING-6032) Not sling pipe

[ https://issues.apache.org/jira/browse/SLING-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6032: --- Fix Version/s: Pipes 1.0.0 > Not sling pipe > -- > > Key:

[jira] [Commented] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467144#comment-15467144 ] Stefan Seifert commented on SLING-6040: --- here is a proposal:

[jira] [Commented] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467139#comment-15467139 ] ASF GitHub Bot commented on SLING-6040: --- GitHub user stefanseifert opened a pull request:

[GitHub] sling pull request #167: SLING-6040 Add ResourceBuilder Support to sling-moc...

GitHub user stefanseifert opened a pull request: https://github.com/apache/sling/pull/167 SLING-6040 Add ResourceBuilder Support to sling-mock depends on PR #166 You can merge this pull request into a Git repository by running: $ git pull https://github.com/stefanseifert/sling

[jira] [Commented] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467116#comment-15467116 ] Stefan Seifert commented on SLING-6040: --- it's just one more dependency (to the very long list of

[jira] [Commented] (SLING-6040) Add ResourceBuilder Support to sling-mock

[ https://issues.apache.org/jira/browse/SLING-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467111#comment-15467111 ] Carsten Ziegeler commented on SLING-6040: - I'm fine with this as long as I can use the current

[jira] [Created] (SLING-6040) Add ResourceBuilder Support to sling-mock

Stefan Seifert created SLING-6040: - Summary: Add ResourceBuilder Support to sling-mock Key: SLING-6040 URL: https://issues.apache.org/jira/browse/SLING-6040 Project: Sling Issue Type: New

[jira] [Commented] (SLING-6039) ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory

[ https://issues.apache.org/jira/browse/SLING-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467015#comment-15467015 ] Stefan Seifert commented on SLING-6039: --- the change would be quite simple, here is a proposal:

[jira] [Commented] (SLING-6039) ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory

[ https://issues.apache.org/jira/browse/SLING-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467012#comment-15467012 ] ASF GitHub Bot commented on SLING-6039: --- GitHub user stefanseifert opened a pull request:

[GitHub] sling pull request #166: SLING-6039 ResourceBuilder: Split up ResourceBuilde...

GitHub user stefanseifert opened a pull request: https://github.com/apache/sling/pull/166 SLING-6039 ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (SLING-6039) ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory

Stefan Seifert created SLING-6039: - Summary: ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory Key: SLING-6039 URL: https://issues.apache.org/jira/browse/SLING-6039 Project: Sling

[jira] [Commented] (SLING-5135) Whitelist legit usages of loginAdministrative and administrative ResourceResolver

[ https://issues.apache.org/jira/browse/SLING-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467001#comment-15467001 ] Antonio Sanso commented on SLING-5135: -- bq. LoginAdminWhitelistImpl has a whitelist.bypass

[jira] [Commented] (SLING-5135) Whitelist legit usages of loginAdministrative and administrative ResourceResolver

[ https://issues.apache.org/jira/browse/SLING-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466994#comment-15466994 ] Bertrand Delacretaz commented on SLING-5135: You're right that this might break some things in

RE: What's wrong with Sightly?

>We have >https://sling.apache.org/documentation/bundles/scripting/scripting-htl.html >which >documents most of the available bundles (except for the two new compilers - >I'll add them soon). perhaps we should also add an addition like "formerly known as Sightly, renamed in August 2016" etc.,

[jira] [Commented] (SLING-6025) Context-Aware Config: Provide configuration parameter metadata

[ https://issues.apache.org/jira/browse/SLING-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466944#comment-15466944 ] Stefan Seifert commented on SLING-6025: --- i played around with porting it to metatype and encountered

Re: Build failed in Jenkins: sling-tooling-trunk-1.7 #262

Thanks for this - fixed in https://svn.apache.org/viewvc/sling/trunk/tooling/maven/pom.xml?r1=1759381=1759380=1759381 . On Tue, 6 Sep 2016 at 10:31 Robert Munteanu wrote: > Looks like this is broken by the Sightly → HTL rename. > > Robert > > > On Mon, 2016-09-05 at 16:12

Re: [VOTE] Release Apache Sling Scripting HTL Compiler 1.0.0, Apache Sling Scripting HTL Java Compiler 1.0.0, Apache Sling Scripting HTL Engine 1.0.20, Apache Sling Scripting HTL JS Use Provider 1.0.1

Hi, I've just replied in the other thread - there are no backwards compatibility issues introduced by the rename as this was mostly cosmetic: I've only changed projects' names and descriptions. None of the tests were changed for these releases. Thanks, Radu On Tue, 6 Sep 2016 at 09:41 Bertrand

Re: What's wrong with Sightly?

Hi, We have https://sling.apache.org/documentation/bundles/scripting/scripting-htl.html which documents most of the available bundles (except for the two new compilers - I'll add them soon). The rename is mostly cosmetic - the bundles names and API are the same. I've only changed the projects'

Re: Build failed in Jenkins: sling-tooling-trunk-1.7 #262

Looks like this is broken by the Sightly → HTL rename. Robert On Mon, 2016-09-05 at 16:12 +, Apache Jenkins Server wrote: > See s> > > Changes: > > [radu] releng: updated dependencies > > [radu] [maven-release-plugin]

Re: September Board Report

On Mon, 2016-09-05 at 07:55 -0700, Carsten Ziegeler wrote: > Hi, > > I've prepared the September board report here: > > https://cwiki.apache.org/confluence/display/SLING/Status+Report+Septe > mber+2016 > > Please review, adjust, comment >  Looks good to me, thanks. Robert

Re: [VOTE] Release Apache Sling Scripting HTL Compiler 1.0.0, Apache Sling Scripting HTL Java Compiler 1.0.0, Apache Sling Scripting HTL Engine 1.0.20, Apache Sling Scripting HTL JS Use Provider 1.0.1

Hi, On Mon, Sep 5, 2016 at 6:59 PM, Radu Cotescu wrote: > ...1. the modularisation of the Sightly engine - now renamed to HTL... Before voting on this release I have concerns about the name change and related backwards compatibility issues, added my thoughts in the "What's

Re: What's wrong with Sightly?

Hi, On Tue, Sep 6, 2016 at 2:03 AM, Justin Edelson wrote: > ...Since Adobe defines the specification and Sling just contains the > implementation, > it makes sense for the implementation to have the same name as the > specification... I'm not opposed to renaming but