Re: Sling Oak Restrictions - Release 1.0.0 now?

On Monday 01 August 2016 13:37:26 Robert Munteanu wrote: > Hi Georg, Hi, > On Sat, 2016-07-30 at 10:14 +0200, Georg Henzler wrote: > > Hi all, > > > > with SLING-5768/SLING-5891 fixed and the documentation in > > https://sling.apache.org/documentation/bundles/sling-oak-restrictions > > .html

Re: Sling Oak Restrictions - Release 1.0.0 now?

Hi Robert, thanks for merging SLING-6042. For your comment regarding the better location contrib/jcr I created SLING-6045 including a PR. So if everyone is happy with this version then, it would be great to have a first release! Regards Georg On 2016-08-01 12:37, Robert Munteanu wrote:

[jira] [Commented] (SLING-6045) Move oak-restrictions bundle to contrib/jcr, rename java package and GAV

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

[GitHub] sling pull request #169: SLING-6045 Moving module to contrib/jcr

GitHub user ghenzler opened a pull request: https://github.com/apache/sling/pull/169 SLING-6045 Moving module to contrib/jcr You can merge this pull request into a Git repository by running: $ git pull https://github.com/ghenzler/sling feature/SLING-6045-move-to-contrib-jcr

[jira] [Created] (SLING-6045) Move oak-restrictions bundle to contrib/jcr, rename java package and GAV

Georg Henzler created SLING-6045: Summary: Move oak-restrictions bundle to contrib/jcr, rename java package and GAV Key: SLING-6045 URL: https://issues.apache.org/jira/browse/SLING-6045 Project:

[jira] [Created] (SLING-6044) Conflicting LogManager and LogWriter if using the same logfile

Jörg Hoh created SLING-6044: --- Summary: Conflicting LogManager and LogWriter if using the same logfile Key: SLING-6044 URL: https://issues.apache.org/jira/browse/SLING-6044 Project: Sling Issue

[jira] [Commented] (SLING-6027) Support existing Chunked upload functionality in streaming mode.

[ https://issues.apache.org/jira/browse/SLING-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470863#comment-15470863 ] Ian Boston commented on SLING-6027: --- Nothing can be done to eliminate the IO from copying chunks into

[jira] [Updated] (SLING-6027) Support existing Chunked upload functionality in streaming mode.

[ https://issues.apache.org/jira/browse/SLING-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Boston updated SLING-6027: -- Fix Version/s: Servlets Post 2.3.14 > Support existing Chunked upload functionality in streaming mode.

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

> >> 2. paxexam integration tests do not run in the IDE (at least not in >> eclipse/junit runner - the problem seems to be that the pom information is >> not available for version lookup). this is only nice-to-have. > > Neither do I use Eclipse nor do I run ITs from my IDE, but I'm sure that >

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: > ...Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1517 ... +1 to release the artifacts listed below - checked signatures, builds and that the svn tags match. Although the

[jira] [Resolved] (SLING-6043) Switch from inline configurations to config files

[ https://issues.apache.org/jira/browse/SLING-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-6043. - Resolution: Fixed [r1759600|https://svn.apache.org/r1759600]

[jira] [Commented] (SLING-6017) Streaming Uploads detection of request parameters is wrong.

[ https://issues.apache.org/jira/browse/SLING-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470506#comment-15470506 ] Ian Boston commented on SLING-6017: --- Thanks for testing. I am still working on SLING-6027 (support for

[jira] [Assigned] (SLING-6027) Support existing Chunked upload functionality in streaming mode.

[ https://issues.apache.org/jira/browse/SLING-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Boston reassigned SLING-6027: - Assignee: Ian Boston > Support existing Chunked upload functionality in streaming mode. >

[jira] [Created] (SLING-6043) Switch from inline configurations to config files

Oliver Lietz created SLING-6043: --- Summary: Switch from inline configurations to config files Key: SLING-6043 URL: https://issues.apache.org/jira/browse/SLING-6043 Project: Sling Issue Type:

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

On Wednesday 07 September 2016 09:29:15 Andrei Dulvac wrote: > -- Forwarded message - > From: Stefan Seifert > Date: Tue, Sep 6, 2016 at 11:25 PM > Subject: http-based/teleporter unit tests vs. paxexam integraiton tests > (was: RE: flaky integration tests

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

On Tuesday 06 September 2016 21:25:45 Stefan Seifert wrote: > >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

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

-- Forwarded message - From: Stefan Seifert Date: Tue, Sep 6, 2016 at 11:25 PM Subject: http-based/teleporter unit tests vs. paxexam integraiton tests (was: RE: flaky integration tests with teleporte rule) To: dev@sling.apache.org

[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=15470128#comment-15470128 ] ASF GitHub Bot commented on SLING-6042: --- Github user asfgit closed the pull request at:

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

Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/168 --- 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-6042) Use sling:resourceTypesWithDescendants instead of sling:resourceTypesWithChildren

[ https://issues.apache.org/jira/browse/SLING-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6042. Resolution: Fixed Applied in https://svn.apache.org/r1759570, thanks! > Use

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

On Mon, 2016-09-05 at 16:59 +, Radu Cotescu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Commented] (SLING-6017) Streaming Uploads detection of request parameters is wrong.

[ https://issues.apache.org/jira/browse/SLING-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470074#comment-15470074 ] Satya Deep Maheshwari commented on SLING-6017: -- [~ianeboston], I verified that the fix works

[jira] [Comment Edited] (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=15470056#comment-15470056 ] Bertrand Delacretaz edited comment on SLING-5135 at 9/7/16 8:56 AM:

[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=15470056#comment-15470056 ] Bertrand Delacretaz commented on SLING-5135: bq. ...I suppose calls to

[jira] [Resolved] (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:all-tabpanel ] Bertrand Delacretaz resolved SLING-5356. Resolution: Fixed Makes sense, I agree with releasing this soon - marking this

[jira] [Updated] (SLING-5998) NewJobSender should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanish Bansal updated SLING-5998: - Attachment: diff_SLING-5998.txt > NewJobSender should move to new ResourceChangeListener API >

[jira] [Commented] (SLING-5998) NewJobSender should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469940#comment-15469940 ] Hanish Bansal commented on SLING-5998: -- Attaching a diff patch which fixes this issue