Re: [discuss][samples] Ease of access

I think this is a good start for criteria of acceptance (or moving to attic). I'd add a README.md with the supported version of Sling and basic build and usage instructions. A user should be able to understand why they want to install the sample just from the README. It might be a good idea to

[discuss][samples] Ease of access

Hi, I think that our samples could do with a little more usability. They are fine as code samples, but sometimes fail short when trying them out: - missing configuration - usually loginAdmin whitelist - extra bundle dependencies - dependencies on SNAPSHOT/unreleased bundles I'm not making any

[samples] Moving some samples to attic

Hi, I did a quick pass over the existing samples. I think these samples should be relevant to our users, and they are a whole category of learning tools. I think some are not as useful as they were when first included I am not too familiar with all of them, so I could use others double- checking

[jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188700#comment-16188700 ] Robert Munteanu commented on SLING-7174: thanks! > Using MockSlingHttpServletRequest for In-Sling

[jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188675#comment-16188675 ] Justin Edelson commented on SLING-7174: --- that's just me forgetting to commit a file. Should be fixed

[site] Simplifying publishing process

Hi, I think we can simplify the site publishing setup and it should be enough to work only on the master branch. I see two possible options: 1) Set up a Jenkins job to rebuild the site and push automatically . This _should_ be possible based on [1] 2) Configure the maven-scm-publish-plugin to

[jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188656#comment-16188656 ] Robert Munteanu commented on SLING-7174: I think the changes lead to some tests failing - see

Re: [Site] Placeholders?

On Mon, Oct 2, 2017 at 5:10 PM, Robert Munteanu wrote: > ...By reading the discussion at [1] it seems that we have to implement > this ourselves in our templates - there is no placeholder support for > articles... Note that there's already a processContent method in the page

[jira] [Resolved] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-7174. --- Resolution: Fixed > Using MockSlingHttpServletRequest for In-Sling Rendering fails when used

[jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188487#comment-16188487 ] Justin Edelson commented on SLING-7174: --- Fixed in r1810562/r1810564 by properly implementing the

[jira] [Updated] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-7174: -- Fix Version/s: Sling Models Impl 1.4.6 Servlet Helpers 1.1.2 > Using

[jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188477#comment-16188477 ] Justin Edelson commented on SLING-7174: --- bq. If that Request / Response pair if for In-Sling

[jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188432#comment-16188432 ] Andreas Schaefer commented on SLING-7174: - If that Request / Response pair if for In-Sling

[jira] [Assigned] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson reassigned SLING-7174: - Assignee: Justin Edelson > Using MockSlingHttpServletRequest for In-Sling Rendering

[jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188425#comment-16188425 ] Justin Edelson commented on SLING-7174: --- bq. In my opinion Sling should provide a Request / Response

[jira] [Updated] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

[ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-7174: -- Component/s: (was: Servlets) Extensions > Using

Using MockSlingHttpServletRequest for in-Sling rendering causes issues with the Export Servlet

Hi When I use the MockSlingHttpServletRequest to render a page with the Export Servlet then I will get an Unsupported Operation Exception when the Export Servlet tries to obtain the Reader from the request. private void addScriptBindings(SlingScriptHelper scriptHelper, SlingHttpServletRequest

[jira] [Created] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet

Andreas Schaefer created SLING-7174: --- Summary: Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet Key: SLING-7174 URL: https://issues.apache.org/jira/browse/SLING-7174

Re: [Site] Placeholders?

Per https://github.com/jbake-org/jbake/issues/326, it looks like we may be able to do this when Pegdown is replaced. On Mon, Oct 2, 2017 at 11:10 AM Robert Munteanu wrote: > On Sat, 2017-09-30 at 12:03 +0200, Carsten Ziegeler wrote: > > Hi, > > > > with the migration of the

[jira] [Comment Edited] (SLING-7169) FullTextIndexingTest sometimes fails with a timeout

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188313#comment-16188313 ] Konrad Windszus edited comment on SLING-7169 at 10/2/17 3:24 PM: - In case

[jira] [Updated] (SLING-7169) FullTextIndexingTest sometimes fails with a timeout

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7169: --- Summary: FullTextIndexingTest sometimes fails with a timeout (was: FullTextIndexingTest

[jira] [Commented] (SLING-7169) FullTextIndexingTest sometimes fails timeout

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188313#comment-16188313 ] Konrad Windszus commented on SLING-7169: In case of failure something like this can be observed in

Re: [Site] Placeholders?

On Sat, 2017-09-30 at 12:03 +0200, Carsten Ziegeler wrote: > Hi, > > with the migration of the website, I'm wondering if we can have > placeholders in pages? > > For example, the version number of the latest Launchpad release, the > minimun java version to use, the minimum Maven version for

[jira] [Commented] (SLING-7152) Unclosed ResourceResolver in org.apache.sling.extensions.webconsolesecurityprovider.internal.SlingWebConsoleSecurityProvider2

[ https://issues.apache.org/jira/browse/SLING-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188225#comment-16188225 ] Carsten Ziegeler commented on SLING-7152: - [~asanso] Does it solve the problem? I'm a little bit

Re: [Site] Improving the main site

Hi, On Sat, 2017-09-30 at 12:09 +0200, Carsten Ziegeler wrote: > Hi, > > we discussed last week at the hackathon a little bit on how to > improve > our site. With the move to git and the new system it should be > easier. > > Looking at the main site, there is a lot of stuff there which we >

[jira] [Updated] (SLING-7169) FullTextIndexingTest sometimes fails timeout

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7169: --- Description: The test fails maybe 1 in 10 runs. I could reproduce this locally by running

[jira] [Updated] (SLING-7169) FullTextIndexingTest sometimes fails timeout

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7169: --- Labels: sling-IT (was: ) > FullTextIndexingTest sometimes fails timeout >

[jira] [Updated] (SLING-7169) FullTextIndexingTest sometimes fails timeout

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7169: --- Summary: FullTextIndexingTest sometimes fails timeout (was: FullTextIndexingTest fails after

[jira] [Commented] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188197#comment-16188197 ] Robert Munteanu commented on SLING-7169: Well, it seems that the test also sometimes fails with

[jira] [Assigned] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-7169: -- Assignee: (was: Konrad Windszus) > FullTextIndexingTest fails after upgrading to

[jira] [Commented] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188116#comment-16188116 ] Robert Munteanu commented on SLING-7169: Try something like {{for i in $(seq 1 20); do mvn -q

[jira] [Assigned] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-7169: -- Assignee: Konrad Windszus (was: Robert Munteanu) > FullTextIndexingTest fails after

[jira] [Updated] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7169: --- Attachment: SLING-7169-logs.tar.gz > FullTextIndexingTest fails after upgrading to

[jira] [Commented] (SLING-7152) Unclosed ResourceResolver in org.apache.sling.extensions.webconsolesecurityprovider.internal.SlingWebConsoleSecurityProvider2

[ https://issues.apache.org/jira/browse/SLING-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188115#comment-16188115 ] Antonio Sanso commented on SLING-7152: -- {code} Index:

Re: [website] FYI, removed feed.xml (was Re: Unrelated ordering changes...)

On Mon, Oct 2, 2017 at 9:14 AM Bertrand Delacretaz wrote: > Hi Justin, > > On Mon, Oct 2, 2017 at 2:15 PM, Justin Edelson > wrote: > > ...However, the time is wrong since it is in local time yet doesn't > include > > the timezone > > Thanks

Re: [SLING-7167] Adjust READMEs

On Mon, 2017-10-02 at 13:26 +0200, Oliver Lietz wrote: > hi all, > > do we want to use the artifactId or the name for the title in all > READMEs, > e.g. Apache Sling Auth Core vs Apache Sling Authentication Service > (we have > both uncommon ids and names)? > >

[website] FYI, removed feed.xml (was Re: Unrelated ordering changes...)

Hi Justin, On Mon, Oct 2, 2017 at 2:15 PM, Justin Edelson wrote: > ...However, the time is wrong since it is in local time yet doesn't include > the timezone Thanks for fixing this in feed.xml but after taking another look I have disabled that page for now, it was

[jira] [Created] (SLING-7173) Add JMX data for pipes

Nicolas Peltier created SLING-7173: -- Summary: Add JMX data for pipes Key: SLING-7173 URL: https://issues.apache.org/jira/browse/SLING-7173 Project: Sling Issue Type: Improvement

[jira] [Updated] (SLING-7166) Deprecate Commons Testing

[ https://issues.apache.org/jira/browse/SLING-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7166: --- Description: The module {{Commons Testing}} seems to be rather old and not too actively

[jira] [Updated] (SLING-7166) Deprecate Commons Testing

[ https://issues.apache.org/jira/browse/SLING-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7166: --- Description: The module {{Commons Testing}} seems to be rather old and not too actively

[jira] [Created] (SLING-7172) Change SlingQuery Pipe API

Nicolas Peltier created SLING-7172: -- Summary: Change SlingQuery Pipe API Key: SLING-7172 URL: https://issues.apache.org/jira/browse/SLING-7172 Project: Sling Issue Type: Improvement

[jira] [Created] (SLING-7171) Add Pipe Throttling capability

Nicolas Peltier created SLING-7171: -- Summary: Add Pipe Throttling capability Key: SLING-7171 URL: https://issues.apache.org/jira/browse/SLING-7171 Project: Sling Issue Type: Improvement

[jira] [Commented] (SLING-7170) Add PipeModel

[ https://issues.apache.org/jira/browse/SLING-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187986#comment-16187986 ] Nicolas Peltier commented on SLING-7170: cc [~bdelacretaz] > Add PipeModel > - > >

[jira] [Updated] (SLING-7166) Deprecate Commons Testing

[ https://issues.apache.org/jira/browse/SLING-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7166: --- Description: The module {{Commons Testing}} seems to be rather old and not too actively

[jira] [Created] (SLING-7170) Add PipeModel

Nicolas Peltier created SLING-7170: -- Summary: Add PipeModel Key: SLING-7170 URL: https://issues.apache.org/jira/browse/SLING-7170 Project: Sling Issue Type: Improvement

[jira] [Updated] (SLING-7166) Deprecate Commons Testing

[ https://issues.apache.org/jira/browse/SLING-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7166: --- Description: The module {{Commons Testing}} seems to be rather old and not too actively

[jira] [Commented] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187960#comment-16187960 ] Konrad Windszus commented on SLING-7169: I triggered a new build (unfortunately haven't saved the

Re: Unrelated ordering changes in JBake-generated site

On Mon, Oct 2, 2017 at 4:24 AM Bertrand Delacretaz wrote: > Hi, > > On Sun, Oct 1, 2017 at 2:40 PM, Justin Edelson > wrote: > > ...After updating the Sling Models documentation and running Maven, I > see that > > a number of extra files are

[jira] [Commented] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187918#comment-16187918 ] Konrad Windszus commented on SLING-7169: I currently fail to see the relation to commons.threads

[jira] [Assigned] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-7169: -- Assignee: Robert Munteanu (was: Konrad Windszus) > FullTextIndexingTest fails after

[jira] [Updated] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7169: --- Description: After upgrading the launchpad to commons.threads 3.2.10 the

[SLING-7167] Adjust READMEs

hi all, do we want to use the artifactId or the name for the title in all READMEs, e.g. Apache Sling Auth Core vs Apache Sling Authentication Service (we have both uncommon ids and names)? https://issues.apache.org/jira/browse/SLING-7167 Thanks, O.

[jira] [Updated] (SLING-7167) Adjust READMEs

[ https://issues.apache.org/jira/browse/SLING-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-7167: Description: * remove outdated information * switch from plain text to Markdown * add uniform

[jira] [Commented] (SLING-7142) Allow to pull a set of packages per request

[ https://issues.apache.org/jira/browse/SLING-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187840#comment-16187840 ] Tommaso Teofili commented on SLING-7142: thanks [~marett], it sounds like a possibly nice

[jira] [Created] (SLING-7169) FullTextIndexingTest fails after upgrading to commons.threads 3.2.10

Robert Munteanu created SLING-7169: -- Summary: FullTextIndexingTest fails after upgrading to commons.threads 3.2.10 Key: SLING-7169 URL: https://issues.apache.org/jira/browse/SLING-7169 Project:

[jira] [Commented] (SLING-7134) Composum does not work with Java 9

[ https://issues.apache.org/jira/browse/SLING-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187822#comment-16187822 ] Carsten Ziegeler commented on SLING-7134: - I briefly looked into the scripts resolver, right now

[jira] [Updated] (SLING-7168) Allow to implement custom distribution queue

[ https://issues.apache.org/jira/browse/SLING-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-7168: -- Fix Version/s: Content Distribution Core 0.2.10 > Allow to implement custom distribution queue

[jira] [Created] (SLING-7168) Allow to implement custom distribution queue

Timothee Maret created SLING-7168: - Summary: Allow to implement custom distribution queue Key: SLING-7168 URL: https://issues.apache.org/jira/browse/SLING-7168 Project: Sling Issue Type:

Re: Unrelated ordering changes in JBake-generated site

Hi, On Sun, Oct 1, 2017 at 2:40 PM, Justin Edelson wrote: > ...After updating the Sling Models documentation and running Maven, I see that > a number of extra files are modified, apparently just to reorder lists... The lists of pages in the sitemap and tags pages were

[jira] [Updated] (SLING-7167) Adjust READMEs

[ https://issues.apache.org/jira/browse/SLING-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-7167: Issue Type: Sub-task (was: Task) Parent: SLING-3987 > Adjust READMEs > -- > >

[jira] [Created] (SLING-7167) Adjust READMEs

Oliver Lietz created SLING-7167: --- Summary: Adjust READMEs Key: SLING-7167 URL: https://issues.apache.org/jira/browse/SLING-7167 Project: Sling Issue Type: Task Reporter: Oliver

[RESULT] [VOTE] Release Apache Sling Thread Support 3.2.10

Hi, The vote has passed with the following result: +1 (binding): Stefan Seifert, Carsten Ziegeler, Robert Munteanu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.

[jira] [Updated] (SLING-3987) Move from Subversion to Git

[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3987: Summary: Move from Subversion to Git (was: move from Subversion to Git) > Move from Subversion to