[jira] [Resolved] (SLING-4541) Provide an extensive test suite for the JCR content loader

2017-01-03 Thread Carsten Ziegeler (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-4541.
-
   Resolution: Won't Fix
Fix Version/s: (was: JCR ContentLoader 2.2.0)

> Provide an extensive test suite for the JCR content loader
> --
>
> Key: SLING-4541
> URL: https://issues.apache.org/jira/browse/SLING-4541
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR ContentLoader 2.1.10
>Reporter: Radu Cotescu
>Assignee: Petr Shypila
> Attachments: week-4-completed.patch, week-4_first_part.patch, 
> week2-part1-pathentry.patch, week2-part2-defaultcontentcreator.patch, 
> week2-part3-single-jcrmock-test.patch, week3.patch, week4-5.patch
>
>
> The JCR content loader is a sensible bundle. An extensive IT suite should be 
> written to make sure that code changes don't affect core functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling File System Resource 1.2.0

2017-01-03 Thread Daniel Klco 
+1

On Tue, Jan 3, 2017 at 4:15 AM, Carsten Ziegeler 
wrote:

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

[jira] [Resolved] (SLING-6432) Avoid path parameter parsing with paths containing a dot

2017-01-03 Thread Carsten Ziegeler (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-6432.
-
Resolution: Fixed

Fixed in rev 1777118

> Avoid path parameter parsing with paths containing a dot
> 
>
> Key: SLING-6432
> URL: https://issues.apache.org/jira/browse/SLING-6432
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.5.10
>
>
> Currently parameter parsing (PathParser) takes place if the path does neither 
> contain a dot nor a semi-colon. However, a path only contains a parameter if 
> there is a semi-colon, so we can reduce the check to just check for a 
> semi-colon and skip parsing regardless whether the path contains a dot or not.
> This is a minor optimization



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6432) Avoid path parameter parsing with paths containing a dot

2017-01-03 Thread Carsten Ziegeler (JIRA) 
Carsten Ziegeler created SLING-6432:
---

 Summary: Avoid path parameter parsing with paths containing a dot
 Key: SLING-6432
 URL: https://issues.apache.org/jira/browse/SLING-6432
 Project: Sling
  Issue Type: Improvement
  Components: ResourceResolver
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Resource Resolver 1.5.10


Currently parameter parsing (PathParser) takes place if the path does neither 
contain a dot nor a semi-colon. However, a path only contains a parameter if 
there is a semi-colon, so we can reduce the check to just check for a 
semi-colon and skip parsing regardless whether the path contains a dot or not.
This is a minor optimization



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6423) Allow for specifying ACL merge mode (ACHandling) in repoinit

2017-01-03 Thread Nitin Nizhawan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Nizhawan updated SLING-6423:
--
Attachment: SLING-6423_testcases.patch

patch containing test cases for merge and merge_preserve mode

> Allow for specifying ACL merge mode (ACHandling) in repoinit
> 
>
> Key: SLING-6423
> URL: https://issues.apache.org/jira/browse/SLING-6423
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING-6423_testcases.patch
>
>
> Repoinit by default just add new ACLs if they are not already present.
> By contract package manager provides various strategies for ACL merging
> Extend repoinit to allow specifying these strategies 
> https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/io/AccessControlHandling.html#MERGE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] sling pull request #194: SLING-6423, Allow for specifying ACL merge mode (AC...

2017-01-03 Thread nitin-nizhawan 
GitHub user nitin-nizhawan opened a pull request:

https://github.com/apache/sling/pull/194

SLING-6423, Allow for specifying ACL merge mode (ACHandling) in repoinit

 - test cases for merge and merge_preserve mode

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nitin-nizhawan/sling nitin-nizhawan/SLING-6423

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/194.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #194


commit 13837f09942f692a0c6d003d4fea9c48e522475a
Author: Nitin Nizhawan 
Date:   2017-01-03T10:48:08Z

SLING-6423, Allow for specifying ACL merge mode (ACHandling) in repoinit

 - test cases for merge and merge_preserve mode




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (SLING-6423) Allow for specifying ACL merge mode (ACHandling) in repoinit

2017-01-03 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794806#comment-15794806
 ] 

ASF GitHub Bot commented on SLING-6423:
---

GitHub user nitin-nizhawan opened a pull request:

https://github.com/apache/sling/pull/194

SLING-6423, Allow for specifying ACL merge mode (ACHandling) in repoinit

 - test cases for merge and merge_preserve mode

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nitin-nizhawan/sling nitin-nizhawan/SLING-6423

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/194.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #194


commit 13837f09942f692a0c6d003d4fea9c48e522475a
Author: Nitin Nizhawan 
Date:   2017-01-03T10:48:08Z

SLING-6423, Allow for specifying ACL merge mode (ACHandling) in repoinit

 - test cases for merge and merge_preserve mode




> Allow for specifying ACL merge mode (ACHandling) in repoinit
> 
>
> Key: SLING-6423
> URL: https://issues.apache.org/jira/browse/SLING-6423
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
>
> Repoinit by default just add new ACLs if they are not already present.
> By contract package manager provides various strategies for ACL merging
> Extend repoinit to allow specifying these strategies 
> https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/io/AccessControlHandling.html#MERGE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling File System Resource 1.2.0

2017-01-03 Thread Carsten Ziegeler 
+1

 

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

[VOTE] Release Apache Sling File System Resource 1.2.0

2017-01-03 Thread Carsten Ziegeler 
Hi,

We solved 3 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12328647

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1615/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1615 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org