[jira] [Resolved] (SLING-6769) scripting.sightly.js.provider 1.0.21.SNAPSHOT fails to start

[ https://issues.apache.org/jira/browse/SLING-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6769. Resolution: Fixed Assignee: Oliver Lietz Great, thanks [~olli] . For the record, the

[jira] [Commented] (SLING-6273) Document SLING-5135 - whitelist of legit login admin uses

[ https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956445#comment-15956445 ] Konrad Windszus commented on SLING-6273: [~jsedding] Would you be able to extend

[jira] [Created] (SLING-6772) Provide default mapping for service users

Carsten Ziegeler created SLING-6772: --- Summary: Provide default mapping for service users Key: SLING-6772 URL: https://issues.apache.org/jira/browse/SLING-6772 Project: Sling Issue Type:

[RT] Unifying site documentation with per-module README.md files?

Hi, I like the fact that we have a consistent documentation section in our site. I also like the README.md, it's very much 'in-your-face' for developers and also for users browsing via Github. I was thinking for some time whether we can unify them by storing the canonical information in Github

Re: [RT] Unifying site documentation with per-module README.md files?

Let me quickly list the advantages/disadvantages of having a bundle documentation in the readme.md from my point of view: Advantages: - It allows a PR to contain documentation together with the actual script changes - The documentation could be versioned as well - Easy to find Disadvantages -

Releasing test bundles

For ITs we sometimes leverage dedicated test bundles (which should only be deployed for the purpose of running the IT). Those test bundles are usually not released (i.e. stay at 1.0.0-SNAPSHOT). But with PaxExam or even with the slingstart-maven-plugin it is now easily possible to have ITs in

[jira] [Commented] (SLING-6662) Move DefaultValidationFailure and DefaultValidationResult out of package org.apache.sling.validation.spi

[ https://issues.apache.org/jira/browse/SLING-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956844#comment-15956844 ] Konrad Windszus commented on SLING-6662: bq. We don't have a strict naming pattern and I guess

[jira] [Commented] (SLING-6273) Document SLING-5135 - whitelist of legit login admin uses

[ https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956988#comment-15956988 ] Konrad Windszus commented on SLING-6273: Thanks, did some more polishing in

[jira] [Updated] (SLING-6763) Remove org.apache.sling.commons.json depdency from esx engine

[ https://issues.apache.org/jira/browse/SLING-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senol Tas updated SLING-6763: - Description: remove org.apache.sling.commons.json dependency from esx engine and replace with native

[jira] [Resolved] (SLING-6273) Document SLING-5135 - whitelist of legit login admin uses

[ https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6273. --- Resolution: Fixed Documentation committed in [r1790285|https://svn.apache.org/r1790285].

[jira] [Comment Edited] (SLING-6273) Document SLING-5135 - whitelist of legit login admin uses

[ https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956988#comment-15956988 ] Konrad Windszus edited comment on SLING-6273 at 4/5/17 3:04 PM: Thanks,

[jira] [Updated] (SLING-6772) Provide default mapping for service users

[ https://issues.apache.org/jira/browse/SLING-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6772: Description: As discussed in [1] we should aim at making Sling configurationless again. One

Re: [VOTE] Release Apache Sling Validation version 1.0.0

Stefan Seifert wrote > +1 > > one finding: org.apache.sling.validation.test-services has a dependency to > org.apache.sling.commons.json (because the last released > org.apache.sling.servlets.post still requires it). not sure if this is a > blocker - it's only a test service not to be indented

Re: [VOTE] Release Apache Sling Validation version 1.0.0

+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

RE: [VOTE] Release Apache Sling Validation version 1.0.0

+1 one finding: org.apache.sling.validation.test-services has a dependency to org.apache.sling.commons.json (because the last released org.apache.sling.servlets.post still requires it). not sure if this is a blocker - it's only a test service not to be indented to be used outside sling.

[jira] [Commented] (SLING-6273) Document SLING-5135 - whitelist of legit login admin uses

[ https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957039#comment-15957039 ] Julian Sedding commented on SLING-6273: --- Great! Thanks for your changes, they look good. > Document

[VOTE] Release Apache Sling Validation version 1.0.0

Hi, This is first release of Apache Sling Validation, namely of the modules validation.api, validation.core and validation.test-services. We solved quite some issues in this first release: https://issues.apache.org/jira/browse/SLING/fixforversion/12328980 There are two outstanding issues:

[jira] [Commented] (SLING-6740) HTL Blog Sample

[ https://issues.apache.org/jira/browse/SLING-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957514#comment-15957514 ] Chris Millar commented on SLING-6740: - [~radu.cotescu] I've updated my pull request to bring the

Re: Releasing test bundles

On Wednesday 05 April 2017 11:56:56 Konrad Windszus wrote: > For ITs we sometimes leverage dedicated test bundles (which should only be > deployed for the purpose of running the IT). Those test bundles are usually > not released (i.e. stay at 1.0.0-SNAPSHOT). But with PaxExam or even with > the

[jira] [Commented] (SLING-6662) Move DefaultValidationFailure and DefaultValidationResult out of package org.apache.sling.validation.spi

[ https://issues.apache.org/jira/browse/SLING-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956702#comment-15956702 ] Oliver Lietz commented on SLING-6662: - We don't have a strict naming pattern and I guess having _SPI_

Re: Releasing test bundles

On Wed, 2017-04-05 at 13:12 +0200, Oliver Lietz wrote: > On Wednesday 05 April 2017 11:56:56 Konrad Windszus wrote: > > For ITs we sometimes leverage dedicated test bundles (which should > > only be > > deployed for the purpose of running the IT). Those test bundles are > > usually > > not

Re: Releasing test bundles

On Wed, 2017-04-05 at 11:56 +0200, Konrad Windszus wrote: > For ITs we sometimes leverage dedicated test bundles (which should > only be deployed for the purpose of running the IT). Those test > bundles are usually not released (i.e. stay at 1.0.0-SNAPSHOT). But > with PaxExam or even with the

Re: Releasing test bundles

On Wed, Apr 5, 2017 at 11:56 AM, Konrad Windszus wrote: > ...2. Release the test-services as well?.. +1, I've been doing this for a few modules already and I agree to make it a general rule. -Bertrand