Re: [VOTE] Release Apache Sling Slingstart Maven Plugin 1.3.6

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

[VOTE] Release Apache Sling Slingstart Maven Plugin 1.3.6

Hi, we solved one issues https://issues.apache.org/jira/browse/SLING-4970 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1322/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_

[jira] [Commented] (SLING-4979) commons.testing.util.RepositoryUtil should allow to instantiate a SlingRepository where loginService is supported

[ https://issues.apache.org/jira/browse/SLING-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723480#comment-14723480 ] Robert Munteanu commented on SLING-4979: Maybe you can use the Sling/JCR mocks ins

Re: double slash in WebDAV URL -> default workspace, was that by design?

Am 31.08.15 um 16:16 schrieb Konrad Windszus: > But this is not what the test case in > https://issues.apache.org/jira/browse/SLING-4976 > validates. > It now validates /dav//… (which should be fine and is > fine) > But /dav// but in fact the //

Re: double slash in WebDAV URL -> default workspace, was that by design?

But this is not what the test case in https://issues.apache.org/jira/browse/SLING-4976 validates. It now validates /dav//… (which should be fine and is fine) But /dav// On 31 Aug 2015, at 11:49, Carsten Ziegeler wrote: > > Am 31.08.15 um 11:42

[jira] [Resolved] (SLING-4980) Improve locking in the SightlyJavaCompilerService

[ https://issues.apache.org/jira/browse/SLING-4980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4980. - Resolution: Fixed Fixed in [r1700251|https://svn.apache.org/viewvc?view=revision&revision=1700251

[jira] [Created] (SLING-4980) Improve locking in the SightlyJavaCompilerService

Radu Cotescu created SLING-4980: --- Summary: Improve locking in the SightlyJavaCompilerService Key: SLING-4980 URL: https://issues.apache.org/jira/browse/SLING-4980 Project: Sling Issue Type: Bug

[jira] [Created] (SLING-4979) commons.testing.util.RepositoryUtil should allow to instantiate a SlingRepository where loginService is supported

Tommaso Teofili created SLING-4979: -- Summary: commons.testing.util.RepositoryUtil should allow to instantiate a SlingRepository where loginService is supported Key: SLING-4979 URL: https://issues.apache.org/jira/

[jira] [Closed] (SLING-4973) Add Content Disposition Excluded Paths

[ https://issues.apache.org/jira/browse/SLING-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso closed SLING-4973. > Add Content Disposition Excluded Paths > -- > > Ke

[RESULT][VOTE] Release Apache Sling Security 1.0.14

The vote is successful with three binding +1 votes regards antonio

Re: [VOTE] Release Apache Sling Security 1.0.14

+1 On Fri, Aug 28, 2015 at 6:53 AM Antonio Sanso wrote: > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING-4973< > https://issues.apache.org/jira/browse/SLING/fixforversion/12331968/> > > Staging repository: > https://repository.apache.org/content/reposito

[jira] [Created] (SLING-4978) VersionParameterTest integration test fails

Bertrand Delacretaz created SLING-4978: -- Summary: VersionParameterTest integration test fails Key: SLING-4978 URL: https://issues.apache.org/jira/browse/SLING-4978 Project: Sling Issue T

[jira] [Resolved] (SLING-4977) Optimise the SightlyJavaCompilerService to provide objects faster

[ https://issues.apache.org/jira/browse/SLING-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4977. - Resolution: Fixed Fixed in [r1700229|https://svn.apache.org/viewvc?view=revision&revision=1700229

[jira] [Created] (SLING-4977) Optimise the SightlyJavaCompilerService to provide objects faster

Radu Cotescu created SLING-4977: --- Summary: Optimise the SightlyJavaCompilerService to provide objects faster Key: SLING-4977 URL: https://issues.apache.org/jira/browse/SLING-4977 Project: Sling

[jira] [Closed] (SLING-4974) Observation support is using a stale resource resolver if resource resolver factory is restarted

[ https://issues.apache.org/jira/browse/SLING-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-4974. --- > Observation support is using a stale resource resolver if resource resolver > factory is restar

[jira] [Closed] (SLING-4972) Debug log output of OakResourceListener is not usable

[ https://issues.apache.org/jira/browse/SLING-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-4972. --- > Debug log output of OakResourceListener is not usable >

[VOTE RESULT] Release Apache Sling JCR Resource 2.5.6

The vote is successful with three binding +1 votes Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

Re: double slash in WebDAV URL -> default workspace, was that by design?

Am 31.08.15 um 11:42 schrieb Konrad Windszus: > If I understood Carsten correctly the double slash should be accepted by the > implementation. So IMHO the old behaviour described in SLING-4976 is the > correct one (i.e. falling back to the default workspace). No :) What I meant is that usually ur

Re: double slash in WebDAV URL -> default workspace, was that by design?

If I understood Carsten correctly the double slash should be accepted by the implementation. So IMHO the old behaviour described in SLING-4976 is the correct one (i.e. falling back to the default workspace). > On 31 Aug 2015, at 11:37, Bertrand Delacretaz wrote: > > Hi, > > On Mon, Aug 31, 201

Re: double slash in WebDAV URL -> default workspace, was that by design?

Hi, On Mon, Aug 31, 2015 at 8:05 AM, Carsten Ziegeler wrote: > ...If I'm not mistaken, most > servers handle a double slash as a single slash, so whatever changed in > the implementation seems to be now according to what everyone else is doing... Yeah that sounds right - I have added a test at S

[jira] [Resolved] (SLING-4976) Clarify handling of empty JCR workspace name in WebDAV URLs

[ https://issues.apache.org/jira/browse/SLING-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-4976. Resolution: Fixed I have added a new WebDavDoubleSlashTest that demonstrates the dif

[jira] [Created] (SLING-4976) Clarify handling of empty JCR workspace name in WebDAV URLs

Bertrand Delacretaz created SLING-4976: -- Summary: Clarify handling of empty JCR workspace name in WebDAV URLs Key: SLING-4976 URL: https://issues.apache.org/jira/browse/SLING-4976 Project: Sling

Re: [VOTE] Release Apache Sling Launchpad Base 5.2.0-2.6.4

+1 On Aug 31, 2015, at 7:41 AM, Carsten Ziegeler wrote: > Hi, > > we solved five issues > https://issues.apache.org/jira/browse/SLING/fixforversion/12332943 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1321/ > > You can use this UNIX script to do

Re: [VOTE] Release Apache Sling Security 1.0.14

anyone :) ? On Aug 28, 2015, at 12:53 PM, Antonio Sanso wrote: > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING-4973 > > Staging repository: > https://repository.apache.org/content/rep

Re: [VOTE] Release Apache Sling Launchpad Base 5.2.0-2.6.4

On Mon, 2015-08-31 at 07:41 +0200, Carsten Ziegeler wrote: > Please vote to approve this release: +1 Robert