[jira] [Commented] (SLING-6849) Impersonation for group of users
[
https://issues.apache.org/jira/browse/SLING-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034238#comment-16034238
]
Tomasz Wagner commented on SLING-6849:
--
Any update or plans for such improvement?
> Impersonation for group of users
>
>
> Key: SLING-6849
> URL: https://issues.apache.org/jira/browse/SLING-6849
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
>Reporter: Krzysztof Watral
> Labels: impersonation
>
> Currently we have two possibilities (which I know) to impersonate some
> account as a different user:
> # First solution can be implemented in the following way:
> {code:java}
> Map authenticationInfo = Maps.newHashMap();
> authenticationInfo.put(ResourceResolverFactory.USER_IMPERSONATION, userId);
> resourceResolver =
> resourceResolverFactory.getServiceResourceResolver(authenticationInfo);
> {code}
> it works, but adds a lot of effort for Administrators, they have to define
> each user in list of possible impersonators (unfortunately this approach
> doesn't support groups).
> # Second approach is to get user session using
> SlingRepository.impersonateFroService:
> {code:java}
> slingRepository.impersonateFromService(null, credentials, null);
> {code}
> Unfortunately, this requires to pass userId and password, that is usually
> impossible to get from programmatical point of view.
> To make life easier, it would be nice if one of the following suggestion
> would be implemented:
> - slingRepository.impersonateFromService(null, credentials, null); could
> start accepting credentials without password
> - impersonators could be configured for group of users
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SLING-6925) Make JSPC plugin useful to validation and analysis
[
https://issues.apache.org/jira/browse/SLING-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034234#comment-16034234
]
Carsten Ziegeler commented on SLING-6925:
-
Thanks for the patch [~tripod]. However I can't apply
https://patch-diff.githubusercontent.com/raw/apache/sling/pull/240.patch as it
also contains the already applied patch for SLING-6923
> Make JSPC plugin useful to validation and analysis
> --
>
> Key: SLING-6925
> URL: https://issues.apache.org/jira/browse/SLING-6925
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Affects Versions: Maven JSPC Plugin 2.0.8
>Reporter: Tobias Bocanegra
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Maven JSPC Plugin 2.0.10
>
>
> the JSPs plugin is very useful to validate the JSPs before they get packaged
> into the artifact. --but the deployment unit might not need to class files
> but there is currently no way to disable their attachment--. further it might
> be valuable to know which dependencies in the project are really used by the
> JSPs. this helps developers to optimize the runtime dependencies of their
> code.
> suggest:
> - --add new flag: {{attachClasses}} (default true)--
> - analyze the java packages of the class path used to compile the JSPs and
> report which dependencies are not used.
> - add new flag: {{reportUnusedDependencies}} (default true)
> - add new flag: {{dumpClassPathUsage}} (default false)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SLING-6926) JCR WebDAV: avoid embedding code from Jackrabbit
[ https://issues.apache.org/jira/browse/SLING-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034196#comment-16034196 ] Carsten Ziegeler commented on SLING-6926: - [~reschke] I don't know enough about what this module actually does and why it's done in this way. I suggest you look at what it does and which extension points it would need from jackrabbit to do its job > JCR WebDAV: avoid embedding code from Jackrabbit > > > Key: SLING-6926 > URL: https://issues.apache.org/jira/browse/SLING-6926 > Project: Sling > Issue Type: Task > Components: JCR >Affects Versions: JCR Webdav 2.3.8 >Reporter: Julian Reschke > > The WebDAV bundle currently *embeds* code from Jackrabbit. This causes all > kinds of problems, such as: > - components getting out of sync when Jackrabbit is upgraded but this bundle > is not > - some of the embedded code has dependencies on jcr-commons, which is not > embedded > It would be ...awesome... if we could avoid all the embedding. Can we > identify a set of changes needed in Jackrabbit that would allow us to get rid > of the embedding? > cc: [~cziegeler] [~edivad] [~fmeschbe] [~baedke] [~anchela] > (a similar task should be applied to the davex bundle once we have dealt with > his one) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6925) Make JSPC plugin useful to validation and analysys
[
https://issues.apache.org/jira/browse/SLING-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034151#comment-16034151
]
ASF GitHub Bot commented on SLING-6925:
---
GitHub user tripodsan opened a pull request:
https://github.com/apache/sling/pull/240
SLING-6925 Make JSPC plugin useful to validation and analysis
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tripodsan/sling SLING-6925
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/240.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 #240
commit 2d9904470ff97b6bc6caa9675f1c5d66fdebab7b
Author: Tobias Bocanegra
Date: 2017-05-31T09:18:50Z
SLING-6923 Update JSPC plugin to support java 1.8
commit 82be08f6e2ee296bbe8235f93f3eecfd2c91da19
Author: Tobias Bocanegra
Date: 2017-06-01T01:32:57Z
SLING-6923 Update JSPC plugin to support java 1.8
- only log classpath in debug mode
commit d126865840d85ffef758aa624aac79041a5cc31e
Author: Tobias Bocanegra
Date: 2017-06-01T02:37:43Z
SLING-6923 Update JSPC plugin to support java 1.8
- add deprecation reason
commit 13daf647d67b1489f2fa07d82e0621e427682f7c
Author: Tobias Bocanegra
Date: 2017-06-01T05:47:50Z
SLING-6925 Make JSPC plugin useful to validation and analysys
commit 3e71b98d4bf4c2a6320e4bd59c806ad5b3604420
Author: Tobias Bocanegra
Date: 2017-06-02T05:12:29Z
Merge branch 'trunk' into SLING-6923
commit 05a702813d46b36fff92b086880a0eed2a5a2afa
Author: Tobias Bocanegra
Date: 2017-06-02T05:12:56Z
Merge branch 'SLING-6923' into SLING-6925
> Make JSPC plugin useful to validation and analysys
> --
>
> Key: SLING-6925
> URL: https://issues.apache.org/jira/browse/SLING-6925
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Affects Versions: Maven JSPC Plugin 2.0.8
>Reporter: Tobias Bocanegra
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Maven JSPC Plugin 2.0.10
>
>
> the JSPs plugin is very useful to validate the JSPs before they get packaged
> into the artifact. --but the deployment unit might not need to class files
> but there is currently no way to disable their attachment--. further it might
> be valuable to know which dependencies in the project are really used by the
> JSPs. this helps developers to optimize the runtime dependencies of their
> code.
> suggest:
> - --add new flag: {{attachClasses}} (default true)--
> - analyze the java packages of the class path used to compile the JSPs and
> report which dependencies are not used.
> - add new flag: {{reportUnusedDependencies}} (default true)
> - add new flag: {{dumpClassPathUsage}} (default false)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SLING-6925) Make JSPC plugin useful to validation and analysis
[
https://issues.apache.org/jira/browse/SLING-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated SLING-6925:
Summary: Make JSPC plugin useful to validation and analysis (was: Make
JSPC plugin useful to validation and analysys)
> Make JSPC plugin useful to validation and analysis
> --
>
> Key: SLING-6925
> URL: https://issues.apache.org/jira/browse/SLING-6925
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Affects Versions: Maven JSPC Plugin 2.0.8
>Reporter: Tobias Bocanegra
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Maven JSPC Plugin 2.0.10
>
>
> the JSPs plugin is very useful to validate the JSPs before they get packaged
> into the artifact. --but the deployment unit might not need to class files
> but there is currently no way to disable their attachment--. further it might
> be valuable to know which dependencies in the project are really used by the
> JSPs. this helps developers to optimize the runtime dependencies of their
> code.
> suggest:
> - --add new flag: {{attachClasses}} (default true)--
> - analyze the java packages of the class path used to compile the JSPs and
> report which dependencies are not used.
> - add new flag: {{reportUnusedDependencies}} (default true)
> - add new flag: {{dumpClassPathUsage}} (default false)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] sling pull request #240: SLING-6925 Make JSPC plugin useful to validation an...
GitHub user tripodsan opened a pull request: https://github.com/apache/sling/pull/240 SLING-6925 Make JSPC plugin useful to validation and analysis You can merge this pull request into a Git repository by running: $ git pull https://github.com/tripodsan/sling SLING-6925 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/240.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 #240 commit 2d9904470ff97b6bc6caa9675f1c5d66fdebab7b Author: Tobias Bocanegra Date: 2017-05-31T09:18:50Z SLING-6923 Update JSPC plugin to support java 1.8 commit 82be08f6e2ee296bbe8235f93f3eecfd2c91da19 Author: Tobias Bocanegra Date: 2017-06-01T01:32:57Z SLING-6923 Update JSPC plugin to support java 1.8 - only log classpath in debug mode commit d126865840d85ffef758aa624aac79041a5cc31e Author: Tobias Bocanegra Date: 2017-06-01T02:37:43Z SLING-6923 Update JSPC plugin to support java 1.8 - add deprecation reason commit 13daf647d67b1489f2fa07d82e0621e427682f7c Author: Tobias Bocanegra Date: 2017-06-01T05:47:50Z SLING-6925 Make JSPC plugin useful to validation and analysys commit 3e71b98d4bf4c2a6320e4bd59c806ad5b3604420 Author: Tobias Bocanegra Date: 2017-06-02T05:12:29Z Merge branch 'trunk' into SLING-6923 commit 05a702813d46b36fff92b086880a0eed2a5a2afa Author: Tobias Bocanegra Date: 2017-06-02T05:12:56Z Merge branch 'SLING-6923' into SLING-6925 --- 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-6923) Update JSPC plugin to support java 1.8
[ https://issues.apache.org/jira/browse/SLING-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034150#comment-16034150 ] ASF GitHub Bot commented on SLING-6923: --- Github user tripodsan closed the pull request at: https://github.com/apache/sling/pull/238 > Update JSPC plugin to support java 1.8 > -- > > Key: SLING-6923 > URL: https://issues.apache.org/jira/browse/SLING-6923 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: Maven JSPC Plugin 2.0.8 >Reporter: Tobias Bocanegra >Assignee: Carsten Ziegeler > Fix For: Maven JSPC Plugin 2.0.10 > > > The current 2.0.8 version of the JSPC plugin only supports java version 1.6. > task: > - update code of JSPC plugin to also support 1.7 and 1.8 > - use latest org.apache.sling.scripting.jsp:2.3.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] sling pull request #238: SLING-6923 Update JSPC plugin to support java 1.8
Github user tripodsan closed the pull request at: https://github.com/apache/sling/pull/238 --- 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] [Resolved] (SLING-6923) Update JSPC plugin to support java 1.8
[ https://issues.apache.org/jira/browse/SLING-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra resolved SLING-6923. - Resolution: Fixed perfect, thanks. I will provide a PR for SLING-6925 shortly > Update JSPC plugin to support java 1.8 > -- > > Key: SLING-6923 > URL: https://issues.apache.org/jira/browse/SLING-6923 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: Maven JSPC Plugin 2.0.8 >Reporter: Tobias Bocanegra >Assignee: Carsten Ziegeler > Fix For: Maven JSPC Plugin 2.0.10 > > > The current 2.0.8 version of the JSPC plugin only supports java version 1.6. > task: > - update code of JSPC plugin to also support 1.7 and 1.8 > - use latest org.apache.sling.scripting.jsp:2.3.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6925) Make JSPC plugin useful to validation and analysys
[
https://issues.apache.org/jira/browse/SLING-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-6925:
---
Assignee: Carsten Ziegeler
> Make JSPC plugin useful to validation and analysys
> --
>
> Key: SLING-6925
> URL: https://issues.apache.org/jira/browse/SLING-6925
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Affects Versions: Maven JSPC Plugin 2.0.8
>Reporter: Tobias Bocanegra
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Maven JSPC Plugin 2.0.10
>
>
> the JSPs plugin is very useful to validate the JSPs before they get packaged
> into the artifact. --but the deployment unit might not need to class files
> but there is currently no way to disable their attachment--. further it might
> be valuable to know which dependencies in the project are really used by the
> JSPs. this helps developers to optimize the runtime dependencies of their
> code.
> suggest:
> - --add new flag: {{attachClasses}} (default true)--
> - analyze the java packages of the class path used to compile the JSPs and
> report which dependencies are not used.
> - add new flag: {{reportUnusedDependencies}} (default true)
> - add new flag: {{dumpClassPathUsage}} (default false)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SLING-6925) Make JSPC plugin useful to validation and analysys
[
https://issues.apache.org/jira/browse/SLING-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-6925:
Fix Version/s: Maven JSPC Plugin 2.0.10
> Make JSPC plugin useful to validation and analysys
> --
>
> Key: SLING-6925
> URL: https://issues.apache.org/jira/browse/SLING-6925
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Affects Versions: Maven JSPC Plugin 2.0.8
>Reporter: Tobias Bocanegra
>Priority: Minor
> Fix For: Maven JSPC Plugin 2.0.10
>
>
> the JSPs plugin is very useful to validate the JSPs before they get packaged
> into the artifact. --but the deployment unit might not need to class files
> but there is currently no way to disable their attachment--. further it might
> be valuable to know which dependencies in the project are really used by the
> JSPs. this helps developers to optimize the runtime dependencies of their
> code.
> suggest:
> - --add new flag: {{attachClasses}} (default true)--
> - analyze the java packages of the class path used to compile the JSPs and
> report which dependencies are not used.
> - add new flag: {{reportUnusedDependencies}} (default true)
> - add new flag: {{dumpClassPathUsage}} (default false)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SLING-6923) Update JSPC plugin to support java 1.8
[ https://issues.apache.org/jira/browse/SLING-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6923: Fix Version/s: Maven JSPC Plugin 2.0.10 > Update JSPC plugin to support java 1.8 > -- > > Key: SLING-6923 > URL: https://issues.apache.org/jira/browse/SLING-6923 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: Maven JSPC Plugin 2.0.8 >Reporter: Tobias Bocanegra >Assignee: Carsten Ziegeler > Fix For: Maven JSPC Plugin 2.0.10 > > > The current 2.0.8 version of the JSPC plugin only supports java version 1.6. > task: > - update code of JSPC plugin to also support 1.7 and 1.8 > - use latest org.apache.sling.scripting.jsp:2.3.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6923) Update JSPC plugin to support java 1.8
[ https://issues.apache.org/jira/browse/SLING-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034123#comment-16034123 ] Carsten Ziegeler commented on SLING-6923: - Thanks for your patch [~tripod]. I've applied it in rev 1797317 together with an update of the parent pom and an update to servlet 3.1, which is the base for Sling. WDYT? > Update JSPC plugin to support java 1.8 > -- > > Key: SLING-6923 > URL: https://issues.apache.org/jira/browse/SLING-6923 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: Maven JSPC Plugin 2.0.8 >Reporter: Tobias Bocanegra >Assignee: Carsten Ziegeler > Fix For: Maven JSPC Plugin 2.0.10 > > > The current 2.0.8 version of the JSPC plugin only supports java version 1.6. > task: > - update code of JSPC plugin to also support 1.7 and 1.8 > - use latest org.apache.sling.scripting.jsp:2.3.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6923) Update JSPC plugin to support java 1.8
[ https://issues.apache.org/jira/browse/SLING-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-6923: --- Assignee: Carsten Ziegeler > Update JSPC plugin to support java 1.8 > -- > > Key: SLING-6923 > URL: https://issues.apache.org/jira/browse/SLING-6923 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: Maven JSPC Plugin 2.0.8 >Reporter: Tobias Bocanegra >Assignee: Carsten Ziegeler > > The current 2.0.8 version of the JSPC plugin only supports java version 1.6. > task: > - update code of JSPC plugin to also support 1.7 and 1.8 > - use latest org.apache.sling.scripting.jsp:2.3.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-6932) [javadoc] Document transient nature of ResourceResolver operations
[ https://issues.apache.org/jira/browse/SLING-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6932: - Description: All ResourceResolver resource operations (create, delete, move, copy) are transient, one always has to call commit() to save the transaction. This isn't documented in the current [ResourceResolver javadoc|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java]. A general paragraph in the class level javadoc on the overall transactional behavior, plus a sentence on each modifying operation such as "It is necessary to call commit() to persist these changes." would help. Furthermore, with changes across multiple resource providers (such as a move), these are multiple transactions, but there is no two phase commit or the like - the first failure will stop committing transactions, and already committed transactions are not rolled back. (Based on reading [this code|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/helper/ResourceResolverControl.java#L419-L423]). Should be documented as well. Discussed here: http://sling.markmail.org/thread/vrnjgqgf3djvwscv was: All ResourceResolver resource operations (create, delete, move, copy) are transient, one always has to call commit() to save the transaction. This isn't documented in the current [ResourceResolver javadoc|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java]. A general paragraph in the class level javadoc on the overall transactional behavior, plus a sentence on each modifying operation such as "It is necessary to call commit() to persist these changes." would help. Furthermore, with changes across multiple resource providers (such as a move), these are multiple transactions, but there is no two phase commit or the like - the first failure will stop committing transactions, and already committed transactions are not rolled back. (Based on reading [this code|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/helper/ResourceResolverControl.java#L419-L423]). Should be clarified as well. Discussed here: http://sling.markmail.org/thread/vrnjgqgf3djvwscv > [javadoc] Document transient nature of ResourceResolver operations > -- > > Key: SLING-6932 > URL: https://issues.apache.org/jira/browse/SLING-6932 > Project: Sling > Issue Type: Improvement > Components: API >Reporter: Alexander Klimetschek > > All ResourceResolver resource operations (create, delete, move, copy) are > transient, one always has to call commit() to save the transaction. > This isn't documented in the current [ResourceResolver > javadoc|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java]. > A general paragraph in the class level javadoc on the overall transactional > behavior, plus a sentence on each modifying operation such as "It is > necessary to call commit() to persist these changes." would help. > Furthermore, with changes across multiple resource providers (such as a > move), these are multiple transactions, but there is no two phase commit or > the like - the first failure will stop committing transactions, and already > committed transactions are not rolled back. (Based on reading [this > code|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/helper/ResourceResolverControl.java#L419-L423]). > Should be documented as well. > Discussed here: http://sling.markmail.org/thread/vrnjgqgf3djvwscv -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: [API] ResourceResolver.copy/move() transient or not?
Thanks. I created https://issues.apache.org/jira/browse/SLING-6932 for the javadoc change. Also noted that the multi-phase commit behaviour (across providers) should probably be documented as well. Cheers, Alex > On 31.05.2017, at 22:27, Carsten Ziegeler wrote: > > Hi, > > all resource operations are transient, you always have to call commit. > But I guess we need to work on the javadocs a little bit to make this clear. > > Sling 9 is not released yet, but we're pretty close. Once it's there the > javadoc will be there as well. > > Carsten > > Alexander Klimetschek wrote >> BTW, there is no published javadoc for sling 9, the latest is sling 8 [3], >> which does not include the copy/move methods, albeit they are 2 years old >> [4]. >> >> [3] >> https://sling.apache.org/apidocs/sling8/org/apache/sling/api/resource/ResourceResolver.html >> [4] >> https://github.com/apache/sling/commit/6653209154a464f45fa63634af869408d6b84619 >> >> Cheers, >> Alex >> >>> On 31.05.2017, at 17:34, Alexander Klimetschek >>> wrote: >>> >>> Hi everyone, >>> >>> the javadocs of ResourceResolver.copy/move() [1] aren't very clear whether >>> these methods immediately persist the change, or if the change is transient >>> and it's necessary to call commit(). >>> >>> The implementation of the JCR resource provider uses Session.move() which >>> is transient. >>> >>> When copy and move works across different providers, I wonder if transient >>> is still supposed to work. It seems, but would be good to clarify this. >>> >>> In fact, no other modifying method mentions commit(), nor does the class >>> level javadoc. >>> >>> [1] >>> https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java#L727-L781 >>> [2] >>> https://github.com/apache/sling/blob/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrResourceProvider.java#L554 >>> >>> Cheers, >>> Alex >> >> > > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
[jira] [Created] (SLING-6932) [javadoc] Document transient nature of ResourceResolver operations
Alexander Klimetschek created SLING-6932: Summary: [javadoc] Document transient nature of ResourceResolver operations Key: SLING-6932 URL: https://issues.apache.org/jira/browse/SLING-6932 Project: Sling Issue Type: Improvement Components: API Reporter: Alexander Klimetschek All ResourceResolver resource operations (create, delete, move, copy) are transient, one always has to call commit() to save the transaction. This isn't documented in the current [ResourceResolver javadoc|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java]. A general paragraph in the class level javadoc on the overall transactional behavior, plus a sentence on each modifying operation such as "It is necessary to call commit() to persist these changes." would help. Furthermore, with changes across multiple resource providers (such as a move), these are multiple transactions, but there is no two phase commit or the like - the first failure will stop committing transactions, and already committed transactions are not rolled back. (Based on reading [this code|https://github.com/apache/sling/blob/96c4134f770c83a665170ec9fad1f8d49832e650/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/helper/ResourceResolverControl.java#L419-L423]). Should be clarified as well. Discussed here: http://sling.markmail.org/thread/vrnjgqgf3djvwscv -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6931) Remove commons.json from valiation/core
Karl Pauls created SLING-6931: - Summary: Remove commons.json from valiation/core Key: SLING-6931 URL: https://issues.apache.org/jira/browse/SLING-6931 Project: Sling Issue Type: Sub-task Reporter: Karl Pauls -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6930) Remove commons.json from ./contrib/extensions/cassandra
Karl Pauls created SLING-6930: - Summary: Remove commons.json from ./contrib/extensions/cassandra Key: SLING-6930 URL: https://issues.apache.org/jira/browse/SLING-6930 Project: Sling Issue Type: Sub-task Reporter: Karl Pauls -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6929) Remove commons.json from ./contrib/launchpad/testing
Karl Pauls created SLING-6929: - Summary: Remove commons.json from ./contrib/launchpad/testing Key: SLING-6929 URL: https://issues.apache.org/jira/browse/SLING-6929 Project: Sling Issue Type: Sub-task Reporter: Karl Pauls -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (SLING-6910) Remove commons.json from crankstart
[ https://issues.apache.org/jira/browse/SLING-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reopened SLING-6910: --- Still some dependency on the artifact. > Remove commons.json from crankstart > --- > > Key: SLING-6910 > URL: https://issues.apache.org/jira/browse/SLING-6910 > Project: Sling > Issue Type: Sub-task > Components: Crankstart >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Crankstart Launcher 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (SLING-6893) Remove commons.json from Content Distribution Integration Tests
[ https://issues.apache.org/jira/browse/SLING-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reopened SLING-6893: --- Looks like i overlooked some cases. > Remove commons.json from Content Distribution Integration Tests > --- > > Key: SLING-6893 > URL: https://issues.apache.org/jira/browse/SLING-6893 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution Integration Tests >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6914) Remove commons.json from bundles/extensions/validation/examples
[ https://issues.apache.org/jira/browse/SLING-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6914. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797284. > Remove commons.json from bundles/extensions/validation/examples > --- > > Key: SLING-6914 > URL: https://issues.apache.org/jira/browse/SLING-6914 > Project: Sling > Issue Type: Sub-task >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6913) Remove commons.json from validation/test-services
[ https://issues.apache.org/jira/browse/SLING-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6913. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797279. > Remove commons.json from validation/test-services > - > > Key: SLING-6913 > URL: https://issues.apache.org/jira/browse/SLING-6913 > Project: Sling > Issue Type: Sub-task > Components: Validation >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6912) Remove commons.json from bundles/extensions/models/integration-tests/
[ https://issues.apache.org/jira/browse/SLING-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6912. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797272. > Remove commons.json from bundles/extensions/models/integration-tests/ > - > > Key: SLING-6912 > URL: https://issues.apache.org/jira/browse/SLING-6912 > Project: Sling > Issue Type: Sub-task >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Release Sling 9?
As an update - we are now SNAPSHOT-free in the launchpad/builder project. We still have a release under vote so I'm going to get that in and plan to start the release vote for the Launchpad 9 release on Wednesday. If anything speaks for delaying the release, please let me know. Thanks, Robert
[jira] [Resolved] (SLING-6911) Remove commons.json from ./contrib/commons/mom/jobs/it
[ https://issues.apache.org/jira/browse/SLING-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6911. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797268. > Remove commons.json from ./contrib/commons/mom/jobs/it > -- > > Key: SLING-6911 > URL: https://issues.apache.org/jira/browse/SLING-6911 > Project: Sling > Issue Type: Sub-task > Components: Commons >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6910) Remove commons.json from crankstart
[ https://issues.apache.org/jira/browse/SLING-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6910. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797264. > Remove commons.json from crankstart > --- > > Key: SLING-6910 > URL: https://issues.apache.org/jira/browse/SLING-6910 > Project: Sling > Issue Type: Sub-task > Components: Crankstart >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Crankstart Launcher 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6909) Remove commons.json from samples/mail-archive/stats
[ https://issues.apache.org/jira/browse/SLING-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6909. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797261. > Remove commons.json from samples/mail-archive/stats > --- > > Key: SLING-6909 > URL: https://issues.apache.org/jira/browse/SLING-6909 > Project: Sling > Issue Type: Sub-task > Components: Samples >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6908) Remove commons.json from Tooling Support Source
[ https://issues.apache.org/jira/browse/SLING-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6908. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797259. > Remove commons.json from Tooling Support Source > --- > > Key: SLING-6908 > URL: https://issues.apache.org/jira/browse/SLING-6908 > Project: Sling > Issue Type: Sub-task > Components: Tooling >Affects Versions: Tooling Support Source 1.0.2 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Tooling Support Source 1.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6907) Remove commons.json from Tooling Support Install
[ https://issues.apache.org/jira/browse/SLING-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6907. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797257. > Remove commons.json from Tooling Support Install > > > Key: SLING-6907 > URL: https://issues.apache.org/jira/browse/SLING-6907 > Project: Sling > Issue Type: Sub-task > Components: Tooling >Affects Versions: Tooling Support Install 1.0.2 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Tooling Support Install 1.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-6928) Remove servlets.compat and commons.json vom launchpad.testing*
[ https://issues.apache.org/jira/browse/SLING-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-6928: -- Summary: Remove servlets.compat and commons.json vom launchpad.testing* (was: Remove servlets.compat vom launchpad.testing*) > Remove servlets.compat and commons.json vom launchpad.testing* > -- > > Key: SLING-6928 > URL: https://issues.apache.org/jira/browse/SLING-6928 > Project: Sling > Issue Type: Sub-task > Components: Launchpad >Reporter: Karl Pauls > > We retired servlets.compat but it is still used in the launchpad.testing and > launchpad.testing-war via the test-bundles. For some reason certain tests > will fail without it. > As far as I can tell, the servlets.compat is the only reason at this point > that we still need the commons.json bundle in the test-bundles. > Due to the fact that we retired servlets.compat, are about to retire > commons.json, and can't release anything with commons.json anyways. We should > figure out what is going on and find a way to remove the dependency on the > servlets.compat bundle in the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6928) Remove servlets.compat vom launchpad.testing*
Karl Pauls created SLING-6928: - Summary: Remove servlets.compat vom launchpad.testing* Key: SLING-6928 URL: https://issues.apache.org/jira/browse/SLING-6928 Project: Sling Issue Type: Sub-task Components: Launchpad Reporter: Karl Pauls We retired servlets.compat but it is still used in the launchpad.testing and launchpad.testing-war via the test-bundles. For some reason certain tests will fail without it. As far as I can tell, the servlets.compat is the only reason at this point that we still need the commons.json bundle in the test-bundles. Due to the fact that we retired servlets.compat, are about to retire commons.json, and can't release anything with commons.json anyways. We should figure out what is going on and find a way to remove the dependency on the servlets.compat bundle in the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6904) Remove commons.json from launchpad integrationtests
[ https://issues.apache.org/jira/browse/SLING-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033533#comment-16033533 ] Karl Pauls commented on SLING-6904: --- Added a missing file in r1797250. > Remove commons.json from launchpad integrationtests > --- > > Key: SLING-6904 > URL: https://issues.apache.org/jira/browse/SLING-6904 > Project: Sling > Issue Type: Sub-task > Components: Launchpad >Affects Versions: Launchpad Integration Tests 1.0.0 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Launchpad Integration Tests 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6904) Remove commons.json from launchpad integrationtests
[ https://issues.apache.org/jira/browse/SLING-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6904. --- Resolution: Fixed Done in r1797248. > Remove commons.json from launchpad integrationtests > --- > > Key: SLING-6904 > URL: https://issues.apache.org/jira/browse/SLING-6904 > Project: Sling > Issue Type: Sub-task > Components: Launchpad >Affects Versions: Launchpad Integration Tests 1.0.0 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Launchpad Integration Tests 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6906) Remove commons.json from testing junit remote
[ https://issues.apache.org/jira/browse/SLING-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6906. --- Resolution: Fixed Added tick escaped json handling in r1797247. > Remove commons.json from testing junit remote > - > > Key: SLING-6906 > URL: https://issues.apache.org/jira/browse/SLING-6906 > Project: Sling > Issue Type: Sub-task > Components: Testing >Affects Versions: JUnit Remote Tests Runners 1.0.10 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: JUnit Remote Test Runners 1.0.12 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (SLING-6906) Remove commons.json from testing junit remote
[ https://issues.apache.org/jira/browse/SLING-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reopened SLING-6906: --- > Remove commons.json from testing junit remote > - > > Key: SLING-6906 > URL: https://issues.apache.org/jira/browse/SLING-6906 > Project: Sling > Issue Type: Sub-task > Components: Testing >Affects Versions: JUnit Remote Tests Runners 1.0.10 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: JUnit Remote Test Runners 1.0.12 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6927) Fix testing.junit.core JsonRenderer
[ https://issues.apache.org/jira/browse/SLING-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6927. --- Resolution: Fixed Done in r1797245. > Fix testing.junit.core JsonRenderer > --- > > Key: SLING-6927 > URL: https://issues.apache.org/jira/browse/SLING-6927 > Project: Sling > Issue Type: Sub-task > Components: JUnit Core >Affects Versions: JUnit Core 1.0.24 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: JUnit Core 1.0.26 > > > The JsonRenderer in Junit Core is broken. It needs a flush to send out the > json correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6927) Fix testing.junit.core JsonRenderer
Karl Pauls created SLING-6927: - Summary: Fix testing.junit.core JsonRenderer Key: SLING-6927 URL: https://issues.apache.org/jira/browse/SLING-6927 Project: Sling Issue Type: Sub-task Components: JUnit Core Affects Versions: JUnit Core 1.0.24 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: JUnit Core 1.0.26 The JsonRenderer in Junit Core is broken. It needs a flush to send out the json correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6904) Remove commons.json from launchpad integrationtests
[ https://issues.apache.org/jira/browse/SLING-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6904: - Assignee: Karl Pauls > Remove commons.json from launchpad integrationtests > --- > > Key: SLING-6904 > URL: https://issues.apache.org/jira/browse/SLING-6904 > Project: Sling > Issue Type: Sub-task > Components: Launchpad >Affects Versions: Launchpad Integration Tests 1.0.0 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Launchpad Integration Tests 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[RESULT] [VOTE] Release Apache Sling SLF4J Implementation (Logback) 5.0.2
Hi, The vote has passed with the following result : +1 (binding): Carsten Ziegeler, Chetan Mehrotra, Stefan Egli, Robert Munteanu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.
[jira] [Commented] (SLING-6926) JCR WebDAV: avoid embedding code from Jackrabbit
[ https://issues.apache.org/jira/browse/SLING-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033208#comment-16033208 ] Julian Reschke commented on SLING-6926: --- ...the key question being: is there something we can change in Jackrabbit so embedding can be avoided? > JCR WebDAV: avoid embedding code from Jackrabbit > > > Key: SLING-6926 > URL: https://issues.apache.org/jira/browse/SLING-6926 > Project: Sling > Issue Type: Task > Components: JCR >Affects Versions: JCR Webdav 2.3.8 >Reporter: Julian Reschke > > The WebDAV bundle currently *embeds* code from Jackrabbit. This causes all > kinds of problems, such as: > - components getting out of sync when Jackrabbit is upgraded but this bundle > is not > - some of the embedded code has dependencies on jcr-commons, which is not > embedded > It would be ...awesome... if we could avoid all the embedding. Can we > identify a set of changes needed in Jackrabbit that would allow us to get rid > of the embedding? > cc: [~cziegeler] [~edivad] [~fmeschbe] [~baedke] [~anchela] > (a similar task should be applied to the davex bundle once we have dealt with > his one) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (SLING-6926) JCR WebDAV: avoid embedding code from Jackrabbit
[
https://issues.apache.org/jira/browse/SLING-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033170#comment-16033170
]
Carsten Ziegeler edited comment on SLING-6926 at 6/1/17 3:56 PM:
-
I see these packages are needed by the bundle atm:
{noformat}
org.apache.jackrabbit.server {version=[1.0,2)}
org.apache.jackrabbit.server.io{version=[2.14,2.15)}
org.apache.jackrabbit.util {version=[2.4,3)}
org.apache.jackrabbit.webdav {version=[1.0,2)}
org.apache.jackrabbit.webdav.io{version=[1.0,2)}
org.apache.jackrabbit.webdav.jcr
org.apache.jackrabbit.webdav.property {version=[1.0,2)}
org.apache.jackrabbit.webdav.simple
org.apache.jackrabbit.webdav.util {version=[1.0,2)}
org.apache.jackrabbit.webdav.xml {version=[1.1,2)}
{noformat}
was (Author: cziegeler):
I see these packages are needed by the bundle atm:
org.apache.jackrabbit.server {version=[1.0,2)}
org.apache.jackrabbit.server.io{version=[2.14,2.15)}
org.apache.jackrabbit.util {version=[2.4,3)}
org.apache.jackrabbit.webdav {version=[1.0,2)}
org.apache.jackrabbit.webdav.io{version=[1.0,2)}
org.apache.jackrabbit.webdav.jcr
org.apache.jackrabbit.webdav.property {version=[1.0,2)}
org.apache.jackrabbit.webdav.simple
org.apache.jackrabbit.webdav.util {version=[1.0,2)}
org.apache.jackrabbit.webdav.xml {version=[1.1,2)}
> JCR WebDAV: avoid embedding code from Jackrabbit
>
>
> Key: SLING-6926
> URL: https://issues.apache.org/jira/browse/SLING-6926
> Project: Sling
> Issue Type: Task
> Components: JCR
>Affects Versions: JCR Webdav 2.3.8
>Reporter: Julian Reschke
>
> The WebDAV bundle currently *embeds* code from Jackrabbit. This causes all
> kinds of problems, such as:
> - components getting out of sync when Jackrabbit is upgraded but this bundle
> is not
> - some of the embedded code has dependencies on jcr-commons, which is not
> embedded
> It would be ...awesome... if we could avoid all the embedding. Can we
> identify a set of changes needed in Jackrabbit that would allow us to get rid
> of the embedding?
> cc: [~cziegeler] [~edivad] [~fmeschbe] [~baedke] [~anchela]
> (a similar task should be applied to the davex bundle once we have dealt with
> his one)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SLING-6926) JCR WebDAV: avoid embedding code from Jackrabbit
[
https://issues.apache.org/jira/browse/SLING-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033170#comment-16033170
]
Carsten Ziegeler commented on SLING-6926:
-
I see these packages are needed by the bundle atm:
org.apache.jackrabbit.server {version=[1.0,2)}
org.apache.jackrabbit.server.io{version=[2.14,2.15)}
org.apache.jackrabbit.util {version=[2.4,3)}
org.apache.jackrabbit.webdav {version=[1.0,2)}
org.apache.jackrabbit.webdav.io{version=[1.0,2)}
org.apache.jackrabbit.webdav.jcr
org.apache.jackrabbit.webdav.property {version=[1.0,2)}
org.apache.jackrabbit.webdav.simple
org.apache.jackrabbit.webdav.util {version=[1.0,2)}
org.apache.jackrabbit.webdav.xml {version=[1.1,2)}
> JCR WebDAV: avoid embedding code from Jackrabbit
>
>
> Key: SLING-6926
> URL: https://issues.apache.org/jira/browse/SLING-6926
> Project: Sling
> Issue Type: Task
> Components: JCR
>Affects Versions: JCR Webdav 2.3.8
>Reporter: Julian Reschke
>
> The WebDAV bundle currently *embeds* code from Jackrabbit. This causes all
> kinds of problems, such as:
> - components getting out of sync when Jackrabbit is upgraded but this bundle
> is not
> - some of the embedded code has dependencies on jcr-commons, which is not
> embedded
> It would be ...awesome... if we could avoid all the embedding. Can we
> identify a set of changes needed in Jackrabbit that would allow us to get rid
> of the embedding?
> cc: [~cziegeler] [~edivad] [~fmeschbe] [~baedke] [~anchela]
> (a similar task should be applied to the davex bundle once we have dealt with
> his one)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SLING-6926) JCR WebDAV: avoid embedding code from Jackrabbit
Julian Reschke created SLING-6926: - Summary: JCR WebDAV: avoid embedding code from Jackrabbit Key: SLING-6926 URL: https://issues.apache.org/jira/browse/SLING-6926 Project: Sling Issue Type: Task Components: JCR Affects Versions: JCR Webdav 2.3.8 Reporter: Julian Reschke The WebDAV bundle currently *embeds* code from Jackrabbit. This causes all kinds of problems, such as: - components getting out of sync when Jackrabbit is upgraded but this bundle is not - some of the embedded code has dependencies on jcr-commons, which is not embedded It would be ...awesome... if we could avoid all the embedding. Can we identify a set of changes needed in Jackrabbit that would allow us to get rid of the embedding? cc: [~cziegeler] [~edivad] [~fmeschbe] [~baedke] [~anchela] (a similar task should be applied to the davex bundle once we have dealt with his one) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
composum upload does not update jcr:lastModified for files and images
Hello, I have posted this issue on the composum issue tracker [0], but not sure where is the right place so I'm posting it here as well. I'm using the latest sling-launchpad org.apache.sling.launchpad-9-20170531.170627-12089.jar with composum browser. I use the browser to create a |nt:file| image |content/hello.png|. I can preview the image. After that I upload a new image by double clicking on the jcr:data and using the upload dialog there. Using the preview button on |jcr:content| node, I can see the new image. Using preview on the |hello.png| file shows the old version. Also, viewing the image on the public link displayes the old image as well [1] One workaround is to manually change the |jcr:lastModified| property of the 'jcr:content' node. That way, the image is updated. The same thing happens with file updates as well. Editing a file via the composum web interface does not change the contents in the public link, unless you update the jcr:lastModified proeprty. [0] https://github.com/ist-dresden/composum/issues/84 [1] http://localhost:8080/content/hello.png signature.asc Description: OpenPGP digital signature
unable to edit resources in Webdav mount via Nautilus
Hello, I'm using the latest sling-launchpad 9 snapshot version org.apache.sling.launchpad-9-20170531.170627-12089.jar in a local application. I mounted the JCR repository as a Webdav filesystem in Nautilus. I authenticated in Nautilus with dav://admin@localhost:8080/ and admin password. I can add resources and copy files into Sling/JCR repo and I can also replace content, but I can't rename, edit files or move them around. Is this a limitation/bug in Sling/JCR a configuration issue with Sling JCR or shoul I check the webdav client (Nautilus)? Thanks, signature.asc Description: OpenPGP digital signature
[jira] [Resolved] (SLING-6903) Remove commons.json from launchpad test-services
[ https://issues.apache.org/jira/browse/SLING-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6903. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797220. > Remove commons.json from launchpad test-services > > > Key: SLING-6903 > URL: https://issues.apache.org/jira/browse/SLING-6903 > Project: Sling > Issue Type: Sub-task > Components: Launchpad >Affects Versions: Launchpad Test Services 2.0.6 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Launchpad Test Services 2.0.12 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6906) Remove commons.json from testing junit remote
[ https://issues.apache.org/jira/browse/SLING-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6906. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797216. > Remove commons.json from testing junit remote > - > > Key: SLING-6906 > URL: https://issues.apache.org/jira/browse/SLING-6906 > Project: Sling > Issue Type: Sub-task > Components: Testing >Affects Versions: JUnit Remote Tests Runners 1.0.10 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: JUnit Remote Test Runners 1.0.12 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6902) Remove commons.json from Apache Sling Script Console
[ https://issues.apache.org/jira/browse/SLING-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6902. --- Resolution: Fixed Assignee: Karl Pauls Done in r1797143. > Remove commons.json from Apache Sling Script Console > > > Key: SLING-6902 > URL: https://issues.apache.org/jira/browse/SLING-6902 > Project: Sling > Issue Type: Sub-task > Components: Scripting >Affects Versions: Scripting Console 1.0.0 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Scripting Console 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
