[jira] [Updated] (SLING-2917) parent node descriptor (ROOT) gets installed twice

[ https://issues.apache.org/jira/browse/SLING-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2917: Fix Version/s: JCR ContentLoader 2.1.8 parent node descriptor (ROOT) gets installed twice

[jira] [Resolved] (SLING-2917) parent node descriptor (ROOT) gets installed twice

[ https://issues.apache.org/jira/browse/SLING-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-2917. - Resolution: Fixed parent node descriptor (ROOT) gets installed twice

Re: [VOTE] Release Apache Sling discovery.impl 1.0.8

Hi, We'd need one more binding vote here. Thanks, Stefan On 4/22/14 12:19 PM, Stefan Egli e...@adobe.com wrote: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326702 Staging repository:

[jira] [Created] (SLING-3521) Merged resource is not available if parent folder is unreadable

Carsten Ziegeler created SLING-3521: --- Summary: Merged resource is not available if parent folder is unreadable Key: SLING-3521 URL: https://issues.apache.org/jira/browse/SLING-3521 Project: Sling

[jira] [Commented] (SLING-3428) vanity paths might be shadowed by url mappings

[ https://issues.apache.org/jira/browse/SLING-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982900#comment-13982900 ] Antonio Sanso commented on SLING-3428: -- added test in rev. 1590589 vanity paths

[jira] [Resolved] (SLING-3428) vanity paths might be shadowed by url mappings

[ https://issues.apache.org/jira/browse/SLING-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso resolved SLING-3428. -- Resolution: Fixed Fix Version/s: Resource Resolver 1.1.2 fixed in rev. 1590592 vanity

[jira] [Assigned] (SLING-3428) vanity paths might be shadowed by url mappings

[ https://issues.apache.org/jira/browse/SLING-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso reassigned SLING-3428: Assignee: Antonio Sanso vanity paths might be shadowed by url mappings

[jira] [Assigned] (SLING-3505) Improve handling of updates to mapping (alias, vanity path)

[ https://issues.apache.org/jira/browse/SLING-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso reassigned SLING-3505: Assignee: Antonio Sanso Improve handling of updates to mapping (alias, vanity path)

[jira] [Created] (SLING-3522) NPE on startup in ChangeStateTask.getSortKey

Philipp Marx created SLING-3522: --- Summary: NPE on startup in ChangeStateTask.getSortKey Key: SLING-3522 URL: https://issues.apache.org/jira/browse/SLING-3522 Project: Sling Issue Type: Bug

[jira] [Assigned] (SLING-3522) NPE on startup in ChangeStateTask.getSortKey

[ https://issues.apache.org/jira/browse/SLING-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3522: --- Assignee: Carsten Ziegeler NPE on startup in ChangeStateTask.getSortKey

[jira] [Updated] (SLING-3522) NPE on startup in ChangeStateTask.getSortKey

[ https://issues.apache.org/jira/browse/SLING-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3522: Affects Version/s: (was: Installer Configuration Factory 1.0.10)

[jira] [Commented] (SLING-3522) NPE on startup in ChangeStateTask.getSortKey

[ https://issues.apache.org/jira/browse/SLING-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983008#comment-13983008 ] Carsten Ziegeler commented on SLING-3522: - I think the methods of the

[jira] [Updated] (SLING-3522) NPE on startup in ChangeStateTask.getSortKey

[ https://issues.apache.org/jira/browse/SLING-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3522: Fix Version/s: Installer Core 3.5.2 NPE on startup in ChangeStateTask.getSortKey

[jira] [Created] (SLING-3523) ResourceResolverImpl.mangleNamespace and unmangleNamespaces behave differently

Konrad Windszus created SLING-3523: -- Summary: ResourceResolverImpl.mangleNamespace and unmangleNamespaces behave differently Key: SLING-3523 URL: https://issues.apache.org/jira/browse/SLING-3523

[jira] [Commented] (SLING-3522) NPE on startup in ChangeStateTask.getSortKey

[ https://issues.apache.org/jira/browse/SLING-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983025#comment-13983025 ] Carsten Ziegeler commented on SLING-3522: - I've committed a first simple potential

[jira] [Commented] (SLING-3474) Concurrent modification exception in installer

[ https://issues.apache.org/jira/browse/SLING-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983041#comment-13983041 ] Carsten Ziegeler commented on SLING-3474: - Actually the underlying problem is the

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing #2108

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2108/

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2108

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2108/

Jenkins build is still unstable: sling-trunk-1.6 #2108

See https://builds.apache.org/job/sling-trunk-1.6/changes

Jenkins build is still unstable: sling-trunk-1.7 #479

See https://builds.apache.org/job/sling-trunk-1.7/changes

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #479

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/479/

Re: [VOTE] Release Apache Sling discovery.impl 1.0.8

+1 Ian On 28 April 2014 08:59, Stefan Egli e...@adobe.com wrote: Hi, We'd need one more binding vote here. Thanks, Stefan On 4/22/14 12:19 PM, Stefan Egli e...@adobe.com wrote: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326702

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #480

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/480/

Jenkins build is still unstable: sling-trunk-1.7 #480

See https://builds.apache.org/job/sling-trunk-1.7/changes

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2109

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2109/

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2109

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2109/

[jira] [Assigned] (SLING-3114) DefaultContentImporter should guard against a closed InputStream on system view imports

[ https://issues.apache.org/jira/browse/SLING-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-3114: --- Assignee: Oliver Lietz DefaultContentImporter should guard against a closed InputStream on

Jenkins build is still unstable: sling-trunk-1.6 #2109

See https://builds.apache.org/job/sling-trunk-1.6/changes

Re: ResourceResolver.clone(null) sharing same JCR session?

I wanted to get some opinions on this first. Created https://issues.apache.org/jira/browse/SLING-3524 Cheers, Alex On 27.04.2014, at 04:43, Carsten Ziegeler cziege...@apache.org wrote: Well, I'm just stating the docs, feel free to open an issue to get this changed. Thanks Carsten

[jira] [Created] (SLING-3524) ResourceResolver.clone(null) should not share the same JCR session

Alexander Klimetschek created SLING-3524: Summary: ResourceResolver.clone(null) should not share the same JCR session Key: SLING-3524 URL: https://issues.apache.org/jira/browse/SLING-3524

Re: ResourceResolver.clone(null) sharing same JCR session?

On 25.04.2014, at 12:43, Alexander Klimetschek aklim...@adobe.com wrote: Which is A LOT of boilerplate given there already is a clone() method. It is not so much if using the USER_IMPERSONATION Using USER_IMPERSONATION like this final ResourceResolver clonedResolver =

[jira] [Commented] (SLING-3524) ResourceResolver.clone(null) should not share the same JCR session

[ https://issues.apache.org/jira/browse/SLING-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13983889#comment-13983889 ] Alexander Klimetschek commented on SLING-3524: -- Note that use of