[jira] [Commented] (SLING-5932) Move Web Console Plugin to separate bundle

[ https://issues.apache.org/jira/browse/SLING-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15590900#comment-15590900 ] Carsten Ziegeler commented on SLING-5932: - Lgtm, thanks [~chetanm] > Move Web Console Plugin to

Re: sling attic / cleanup

Hello, I'm still working on the Sitebuilder [1] and the resource editor and need the js module for that. Please keep it. Thanks! Sandro 2) We scheduled contrib/jcr/js for removal, but it's indirectly referenced from contrib/explorers/resourceeditor. So we either keep both or move both to

[jira] [Resolved] (SLING-6173) HTL compiled scripts need to set the SlingBindings as request attributes on eval

[ https://issues.apache.org/jira/browse/SLING-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-6173. - Resolution: Fixed Fixed in [r1765682|https://svn.apache.org/r1765682]. > HTL compiled scripts

[jira] [Updated] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[ https://issues.apache.org/jira/browse/SLING-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6175: --- Description: With the configurator being added in SLING-3100 there is always WTP natures and

[jira] [Updated] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[ https://issues.apache.org/jira/browse/SLING-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6175: --- Description: With the configurator being added in SLING-3100 there is always WTP natures and

[jira] [Commented] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[ https://issues.apache.org/jira/browse/SLING-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589038#comment-15589038 ] Georg Henzler commented on SLING-6175: -- [~rombert], you stated bq. {{M2E_USE_WTP_PROJECT_SETUP}} -

[jira] [Updated] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[ https://issues.apache.org/jira/browse/SLING-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6175: --- Description: With the configurator being added in SLING-3100 there is always WTP natures and

[jira] [Commented] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[ https://issues.apache.org/jira/browse/SLING-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589031#comment-15589031 ] Konrad Windszus commented on SLING-6175: [~rombert] You basically argued in

[jira] [Updated] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[ https://issues.apache.org/jira/browse/SLING-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6175: --- Component/s: IDE > Sling IDE: Don't configure WTP natures by default for content-package

[jira] [Created] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

Konrad Windszus created SLING-6175: -- Summary: Sling IDE: Don't configure WTP natures by default for content-package projects Key: SLING-6175 URL: https://issues.apache.org/jira/browse/SLING-6175

[jira] [Resolved] (SLING-5014) Installer blacklist, to avoid reinstalling older bundles

[ https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5014. - Resolution: Fixed Assignee: Carsten Ziegeler Thanks for your patch [~dsuess] I've

[jira] [Resolved] (SLING-6103) crankstart-launcher ITs fail when executed in isolation (on Jenkins)

[ https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-6103. Resolution: Fixed With this the {{sling-contrib-crankstart-launcher}} 1.7 and 1.8

[jira] [Commented] (SLING-6062) Make it simple to run Jenkins jobs locally

[ https://issues.apache.org/jira/browse/SLING-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588816#comment-15588816 ] Bertrand Delacretaz commented on SLING-6062: I've found a Docker image that makes it easy to

[jira] [Commented] (SLING-6103) crankstart-launcher ITs fail when executed in isolation (on Jenkins)

[ https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588786#comment-15588786 ] Robert Munteanu commented on SLING-6103: Change looks good, thanks! And yes, quite fun :-) >

[jira] [Commented] (SLING-6103) crankstart-launcher ITs fail when executed in isolation (on Jenkins)

[ https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588779#comment-15588779 ] Bertrand Delacretaz commented on SLING-6103: Ok, I've implemented an {{extraGoalsParams}}

Re: [VOTE] Release Apache Sling Servlets Resolver 2.4.6

+1 On Wed, Oct 19, 2016 at 6:27 AM, Robert Munteanu wrote: > On Wed, 2016-10-19 at 12:23 +0200, Carsten Ziegeler wrote: > > sh check_staged_release.sh 1546 /tmp/sling-staging > > +1 > > Robert

[jira] [Commented] (SLING-6103) crankstart-launcher ITs fail when executed in isolation (on Jenkins)

[ https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588633#comment-15588633 ] Robert Munteanu commented on SLING-6103: We can do this in two ways: 1) add a 'goals' setting,

[jira] [Commented] (SLING-6103) crankstart-launcher ITs fail when executed in isolation (on Jenkins)

[ https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588624#comment-15588624 ] Bertrand Delacretaz commented on SLING-6103: The build passed now at

Re: [VOTE] Release Apache Sling Servlets Resolver 2.4.6

On Wed, 2016-10-19 at 12:23 +0200, Carsten Ziegeler wrote: > sh check_staged_release.sh 1546 /tmp/sling-staging +1 Robert signature.asc Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Servlets Resolver 2.4.6

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

[VOTE] Release Apache Sling Servlets Resolver 2.4.6

Hi, We solved 2 issues for these releases: https://issues.apache.org/jira/browse/SLING/fixforversion/12337881 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1546 You can use this UNIX script to download the releases and verify the signatures:

[jira] [Resolved] (SLING-6006) SlingServletResolver should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6006. - Resolution: Fixed Thanks for your patch [~krachi...@gmail.com] It's applied >

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6174: Description: We recently switched back to use a jcr listener (SLING-6138) unfortunately,

[jira] [Resolved] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6056. - Resolution: Fixed The implementation is done Created SLING-6174 for tracking the glob

[jira] [Created] (SLING-6174) Use Jackrabbit/Oak globbing support

Carsten Ziegeler created SLING-6174: --- Summary: Use Jackrabbit/Oak globbing support Key: SLING-6174 URL: https://issues.apache.org/jira/browse/SLING-6174 Project: Sling Issue Type:

[jira] [Commented] (SLING-5014) Installer blacklist, to avoid reinstalling older bundles

[ https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588191#comment-15588191 ] Dominik Süß commented on SLING-5014: Pullrequest has been updated based on feedback by [~cziegeler] -

[jira] [Assigned] (SLING-6006) SlingServletResolver should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-6006: --- Assignee: Carsten Ziegeler > SlingServletResolver should move to new

[jira] [Updated] (SLING-6006) SlingServletResolver should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rachit Kumar updated SLING-6006: Attachment: patch.txt Hi [~cziegeler] Please review the patch. Thanks, Rachit >

[jira] [Commented] (SLING-6171) Unable to set up ACLs for the 'everyone' principal

[ https://issues.apache.org/jira/browse/SLING-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588095#comment-15588095 ] Robert Munteanu commented on SLING-6171: I'm not sure why it fails. I know that in Jackrabbit and

[jira] [Commented] (SLING-6171) Unable to set up ACLs for the 'everyone' principal

[ https://issues.apache.org/jira/browse/SLING-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588087#comment-15588087 ] Bertrand Delacretaz commented on SLING-6171: In this case the failing code at [1] just does

[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=15588073#comment-15588073 ] Robert Munteanu commented on SLING-5135: That sounds good to me. > Whitelist legit usages of

[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=15588070#comment-15588070 ] Bertrand Delacretaz commented on SLING-5135: bq. it would be useful to have a configuration

[jira] [Commented] (SLING-3987) move from Subversion to Git

[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588037#comment-15588037 ] Bertrand Delacretaz commented on SLING-3987: Cloudstack has useful docs and scripts about

[jira] [Created] (SLING-6173) HTL compiled scripts need to set the SlingBindings as request attributes on eval

Radu Cotescu created SLING-6173: --- Summary: HTL compiled scripts need to set the SlingBindings as request attributes on eval Key: SLING-6173 URL: https://issues.apache.org/jira/browse/SLING-6173

[jira] [Commented] (SLING-5014) Installer blacklist, to avoid reinstalling older bundles

[ https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587906#comment-15587906 ] Dominik Süß commented on SLING-5014: [~cziegeler] - I was checking the various options before - the