[jira] [Assigned] (SLING-4205) Clarify the licensing of resourceeditor images, fonts etc.
[ https://issues.apache.org/jira/browse/SLING-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-4205: -- Assignee: Sandro Boehme (was: Bertrand Delacretaz) [~sandro] I've given you the committer role for sling in jira, and assigned this issue to you. Clarify the licensing of resourceeditor images, fonts etc. -- Key: SLING-4205 URL: https://issues.apache.org/jira/browse/SLING-4205 Project: Sling Issue Type: Task Components: Extensions Reporter: Bertrand Delacretaz Assignee: Sandro Boehme Priority: Minor Fix For: Resource Editor 1.0.2 Attachments: AddNodeDialogPatch-alu.gif.txt, AddNodeDialogPatch-src-stainless_steel.xcf.txt As per SLING-4169 some of the images, fonts and maybe other resources used by the resource-editor module need clarification or replacement to make sure we can be release them under the Apache License. This issue is meant to keep track of which files are already ok and which ones need modifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4105) Content Navigator should not read all the jcr_root when initialized
[
https://issues.apache.org/jira/browse/SLING-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294218#comment-14294218
]
Robert Munteanu commented on SLING-4105:
Optimised parsing in
https://svn.apache.org/viewvc?view=revisionrevision=r1655167 . The complete
jcr_root is still read unconditionally, but responsiveness is much better.
Content Navigator should not read all the jcr_root when initialized
---
Key: SLING-4105
URL: https://issues.apache.org/jira/browse/SLING-4105
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.4
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.6
Currently the {{JcrContentContentProvider}} eagery initialises the data for
all of the resources placed under the content sync root. This has a negative
effect on the responsiveness of Eclipse, especially since this is all done on
the UI thread.
Two scenarios are especially bad:
- startup with large project open
- switching branches for a large project
This can lock up the UI thread for 20-30 seconds or more. We should be able
to lazily load the data only for the displayed resources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.8 #666
See https://builds.apache.org/job/sling-trunk-1.8/666/changes
[jira] [Updated] (SLING-4261) WriteableResourcesProxyTest.runWriteableResourcesTest test failure
[
https://issues.apache.org/jira/browse/SLING-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-4261:
---
Description:
{noformat}java.lang.AssertionError: POST request to
http://localhost:35847/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.WriteableResourcesTest.json:
expecting status 200 expected:200 but was:404
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at
org.apache.sling.testing.tools.http.RequestExecutor.assertStatus(RequestExecutor.java:155)
at
org.apache.sling.junit.remote.httpclient.RemoteTestHttpClient.runTests(RemoteTestHttpClient.java:134)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.runTests(ServerSideTestClient.java:76)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:100)
at
org.apache.sling.launchpad.webapp.integrationtest.WriteableResourcesProxyTest.runWriteableResourcesTest(WriteableResourcesProxyTest.java:26)
{noformat}
Recorded failures:
* [sling-trunk-1.7 build
1255|https://builds.apache.org/job/sling-trunk-1.7/1255/]
* [sling-trunk-1.8 build
610|https://builds.apache.org/job/sling-trunk-1.8/610/] at revision 1651385
* [sling-trunk-1.8 build
666|https://builds.apache.org/job/sling-trunk-1.8/666/] at revision 1655167
was:
{noformat}java.lang.AssertionError: POST request to
http://localhost:35847/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.WriteableResourcesTest.json:
expecting status 200 expected:200 but was:404
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at
org.apache.sling.testing.tools.http.RequestExecutor.assertStatus(RequestExecutor.java:155)
at
org.apache.sling.junit.remote.httpclient.RemoteTestHttpClient.runTests(RemoteTestHttpClient.java:134)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.runTests(ServerSideTestClient.java:76)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:100)
at
org.apache.sling.launchpad.webapp.integrationtest.WriteableResourcesProxyTest.runWriteableResourcesTest(WriteableResourcesProxyTest.java:26)
{noformat}
Recorded failures:
* [sling-trunk-1.7 build
1255|https://builds.apache.org/job/sling-trunk-1.7/1255/]
* [sling-trunk-1.8 build
610|https://builds.apache.org/job/sling-trunk-1.8/610/] at revision 1651385
WriteableResourcesProxyTest.runWriteableResourcesTest test failure
--
Key: SLING-4261
URL: https://issues.apache.org/jira/browse/SLING-4261
Project: Sling
Issue Type: Bug
Components: Testing
Reporter: Robert Munteanu
Labels: sling-IT
{noformat}java.lang.AssertionError: POST request to
http://localhost:35847/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.WriteableResourcesTest.json:
expecting status 200 expected:200 but was:404
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at
org.apache.sling.testing.tools.http.RequestExecutor.assertStatus(RequestExecutor.java:155)
at
org.apache.sling.junit.remote.httpclient.RemoteTestHttpClient.runTests(RemoteTestHttpClient.java:134)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.runTests(ServerSideTestClient.java:76)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:100)
at
org.apache.sling.launchpad.webapp.integrationtest.WriteableResourcesProxyTest.runWriteableResourcesTest(WriteableResourcesProxyTest.java:26)
{noformat}
Recorded failures:
* [sling-trunk-1.7 build
1255|https://builds.apache.org/job/sling-trunk-1.7/1255/]
* [sling-trunk-1.8 build
610|https://builds.apache.org/job/sling-trunk-1.8/610/] at revision 1651385
* [sling-trunk-1.8 build
666|https://builds.apache.org/job/sling-trunk-1.8/666/] at revision 1655167
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.6 #2986
See https://builds.apache.org/job/sling-trunk-1.6/2986/changes
Re: Jenkins build became unstable: sling-trunk-1.6 #2986
On Wed, Jan 28, 2015 at 1:22 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/sling-trunk-1.6/2986/changes Failed tests are org.apache.sling.discovery.impl.cluster.ClusterTest.testConnectorSwitching4139 org.apache.sling.discovery.impl.cluster.ClusterTest.testClusterView org.apache.sling.discovery.impl.cluster.ClusterTest.testStableClusterId org.apache.sling.discovery.impl.cluster.ClusterTest.testPropertyProviders org.apache.sling.discovery.impl.cluster.ClusterTest.testStaleInstanceIn3Clusters4139 org.apache.sling.discovery.impl.cluster.ClusterTest.testLeaderDesc org.apache.sling.discovery.impl.cluster.ClusterTest.testAdditionalInstance org.apache.sling.discovery.impl.cluster.ClusterTest.testDuplicateInstanceIn2Clusters4139 org.apache.sling.discovery.impl.cluster.ClusterTest.testDuplicateInstance3726 org.apache.sling.discovery.impl.cluster.ClusterTest.testLeaderAsc org.apache.sling.discovery.impl.cluster.ClusterTest.testStaleAnnouncementsVisibleToClusterPeers4139 org.apache.sling.discovery.impl.topology.LargeTopologyWithHubTest.testLargeTopologyWithHub Stefan, any thoughts? Robert
[jira] [Created] (SLING-4356) Implement support for 'data-sly-repeat'
Radu Cotescu created SLING-4356:
---
Summary: Implement support for 'data-sly-repeat'
Key: SLING-4356
URL: https://issues.apache.org/jira/browse/SLING-4356
Project: Sling
Issue Type: Sub-task
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
Version 1.1 of the Sightly language specification defines a new block element -
{{data-sly-repeat}} [0].
[0] -
https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md#227-repeat
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4353) Update the Sightly implementation to comply with version 1.1 of the language specification
Radu Cotescu created SLING-4353:
---
Summary: Update the Sightly implementation to comply with version
1.1 of the language specification
Key: SLING-4353
URL: https://issues.apache.org/jira/browse/SLING-4353
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
The Sightly language specification \[0\] has been updated to version 1.1,
therefore the implementation from {{org.apache.sling.scripting.sightly}} should
be updated.
\[0\] -
https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4354) Update the behaviour of the 'join' option
Radu Cotescu created SLING-4354:
---
Summary: Update the behaviour of the 'join' option
Key: SLING-4354
URL: https://issues.apache.org/jira/browse/SLING-4354
Project: Sling
Issue Type: Sub-task
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
The implementation of the {{join}} option should be updated to support
expressions that evaluate to a string, according to the specification update
from \[0\].
\[0\] -
https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md#124-array-join
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4205) Clarify the licensing of resourceeditor images, fonts etc.
[ https://issues.apache.org/jira/browse/SLING-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14293658#comment-14293658 ] Sandro Boehme commented on SLING-4205: -- Thanks [~bdelacretaz]! Clarify the licensing of resourceeditor images, fonts etc. -- Key: SLING-4205 URL: https://issues.apache.org/jira/browse/SLING-4205 Project: Sling Issue Type: Task Components: Extensions Reporter: Bertrand Delacretaz Assignee: Sandro Boehme Priority: Minor Fix For: Resource Editor 1.0.2 Attachments: AddNodeDialogPatch-alu.gif.txt, AddNodeDialogPatch-src-stainless_steel.xcf.txt As per SLING-4169 some of the images, fonts and maybe other resources used by the resource-editor module need clarification or replacement to make sure we can be release them under the Apache License. This issue is meant to keep track of which files are already ok and which ones need modifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4355) Implement support for the 'sly' HTML tag
Radu Cotescu created SLING-4355:
---
Summary: Implement support for the 'sly' HTML tag
Key: SLING-4355
URL: https://issues.apache.org/jira/browse/SLING-4355
Project: Sling
Issue Type: Sub-task
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
Version 1.1 of the Sightly language specification defines a special HTML tag -
{{sly}} - that acts similarly to {{data-sly-unwrap}} \[0\].
\[0\] -
https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md#31-sly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Jenkins build became unstable: sling-trunk-1.8 #666
Semi-random failure, already tracked in https://issues.apache.org/jira/browse/SLING-4261 On Wed, Jan 28, 2015 at 12:25 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/sling-trunk-1.8/666/changes
[jira] [Commented] (SLING-4261) WriteableResourcesProxyTest.runWriteableResourcesTest test failure
[
https://issues.apache.org/jira/browse/SLING-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294808#comment-14294808
]
Bertrand Delacretaz commented on SLING-4261:
404 on that URL seems to indicate that either the JUnit servlet is not ready
yet, or that the server-side WriteableResourcesTest is not found.
Looking at the output at
https://builds.apache.org/job/sling-trunk-1.8/666/console this is the first
test that runs, so I suspect it runs too early - the launchpad plugin that
starts Sling thinks it's ready for testing but it's not.
I'll try to add more readiness conditions to the set added for SLING-3235.
WriteableResourcesProxyTest.runWriteableResourcesTest test failure
--
Key: SLING-4261
URL: https://issues.apache.org/jira/browse/SLING-4261
Project: Sling
Issue Type: Bug
Components: Testing
Reporter: Robert Munteanu
Labels: sling-IT
{noformat}java.lang.AssertionError: POST request to
http://localhost:35847/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.WriteableResourcesTest.json:
expecting status 200 expected:200 but was:404
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at
org.apache.sling.testing.tools.http.RequestExecutor.assertStatus(RequestExecutor.java:155)
at
org.apache.sling.junit.remote.httpclient.RemoteTestHttpClient.runTests(RemoteTestHttpClient.java:134)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.runTests(ServerSideTestClient.java:76)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:100)
at
org.apache.sling.launchpad.webapp.integrationtest.WriteableResourcesProxyTest.runWriteableResourcesTest(WriteableResourcesProxyTest.java:26)
{noformat}
Recorded failures:
* [sling-trunk-1.7 build
1255|https://builds.apache.org/job/sling-trunk-1.7/1255/]
* [sling-trunk-1.8 build
610|https://builds.apache.org/job/sling-trunk-1.8/610/] at revision 1651385
* [sling-trunk-1.8 build
666|https://builds.apache.org/job/sling-trunk-1.8/666/] at revision 1655167
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SLING-4261) WriteableResourcesProxyTest.runWriteableResourcesTest test failure
[
https://issues.apache.org/jira/browse/SLING-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-4261.
Resolution: Fixed
Assignee: Bertrand Delacretaz
http://svn.apache.org/r1655231 should fix this, marking this fixed, we'll
reopen if it's not.
WriteableResourcesProxyTest.runWriteableResourcesTest test failure
--
Key: SLING-4261
URL: https://issues.apache.org/jira/browse/SLING-4261
Project: Sling
Issue Type: Bug
Components: Testing
Reporter: Robert Munteanu
Assignee: Bertrand Delacretaz
Labels: sling-IT
{noformat}java.lang.AssertionError: POST request to
http://localhost:35847/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.WriteableResourcesTest.json:
expecting status 200 expected:200 but was:404
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at
org.apache.sling.testing.tools.http.RequestExecutor.assertStatus(RequestExecutor.java:155)
at
org.apache.sling.junit.remote.httpclient.RemoteTestHttpClient.runTests(RemoteTestHttpClient.java:134)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.runTests(ServerSideTestClient.java:76)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:100)
at
org.apache.sling.launchpad.webapp.integrationtest.WriteableResourcesProxyTest.runWriteableResourcesTest(WriteableResourcesProxyTest.java:26)
{noformat}
Recorded failures:
* [sling-trunk-1.7 build
1255|https://builds.apache.org/job/sling-trunk-1.7/1255/]
* [sling-trunk-1.8 build
610|https://builds.apache.org/job/sling-trunk-1.8/610/] at revision 1651385
* [sling-trunk-1.8 build
666|https://builds.apache.org/job/sling-trunk-1.8/666/] at revision 1655167
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Jenkins build became unstable: sling-trunk-1.6 #2986
It looks like the test-repository could not be created correctly (see stacktrace below) I've restarted another build on jenkins and will monitor and analyze further today. Cheers, Stefan -- Caused by: javax.jcr.ItemNotFoundException: failed to build path of 7eda2c79-8574-4fa2-8c28-d7091c065d51: cafebabe-cafe-babe-cafe-babecafebabe has no child entry for 7eda2c79-8574-4fa2-8c28-d7091c065d51 at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerI mpl.java:291) at org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarc hyManager.java:199) at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerI mpl.java:280) at org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarc hyManager.java:199) at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerI mpl.java:280) at org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarc hyManager.java:199) at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerI mpl.java:280) at org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarc hyManager.java:199) at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerI mpl.java:280) at org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarc hyManager.java:199) at org.apache.jackrabbit.core.HierarchyManagerImpl.getPath(HierarchyManagerImp l.java:395) at org.apache.jackrabbit.core.CachingHierarchyManager.getPath(CachingHierarchy Manager.java:233) at org.apache.jackrabbit.core.ItemImpl.getPrimaryPath(ItemImpl.java:188) at org.apache.jackrabbit.core.NodeImpl.getPrimaryPath(NodeImpl.java:2745) at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:379) at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:376) at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:2 00) at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91) at org.apache.jackrabbit.core.ItemImpl.getPath(ItemImpl.java:376) at org.apache.sling.discovery.impl.setup.MockedResourceResolver$1.next(MockedR esourceResolver.java:171) On 1/28/15 12:26 AM, Robert Munteanu romb...@apache.org wrote: On Wed, Jan 28, 2015 at 1:22 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/sling-trunk-1.6/2986/changes Failed tests are org.apache.sling.discovery.impl.cluster.ClusterTest.testConnectorSwitching 4139 org.apache.sling.discovery.impl.cluster.ClusterTest.testClusterView org.apache.sling.discovery.impl.cluster.ClusterTest.testStableClusterId org.apache.sling.discovery.impl.cluster.ClusterTest.testPropertyProviders org.apache.sling.discovery.impl.cluster.ClusterTest.testStaleInstanceIn3Cl usters4139 org.apache.sling.discovery.impl.cluster.ClusterTest.testLeaderDesc org.apache.sling.discovery.impl.cluster.ClusterTest.testAdditionalInstance org.apache.sling.discovery.impl.cluster.ClusterTest.testDuplicateInstanceI n2Clusters4139 org.apache.sling.discovery.impl.cluster.ClusterTest.testDuplicateInstance3 726 org.apache.sling.discovery.impl.cluster.ClusterTest.testLeaderAsc org.apache.sling.discovery.impl.cluster.ClusterTest.testStaleAnnouncements VisibleToClusterPeers4139 org.apache.sling.discovery.impl.topology.LargeTopologyWithHubTest.testLarg eTopologyWithHub Stefan, any thoughts? Robert
RE: [RT] Sling Resource Providers for NoSQL databases - MongoDB, Couchbase
yes, this is a good point. have to think about it. on the first sight it feels a bit heavyweight for my usecase: in an osgi-microservice scenario without JCR/oak, and currently without sling engine but with some sling subprojects including launchpad i want to use sling distributed events and job processing and discovery. but the current implementations need to store some small parts of data in a shared repository, for which couchbase would suit well because it's used already by the microservices. but this is of course a very special usecase. stefan -Original Message- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Tuesday, January 27, 2015 5:38 PM To: dev Subject: Re: [RT] Sling Resource Providers for NoSQL databases - MongoDB, Couchbase Hi, On Tue, Jan 27, 2015 at 5:09 PM, Stefan Seifert sseif...@pro-vision.de wrote: ...we currently evaluate to integrate a Couchbase NoSQL database [1] into a sling resource tree... As mentioned in a different thread about DynamoDB, it might be interesting to consider writing a Couchbase backend for Oak instead. The advantages are inheriting Oak's indexing and other useful JCR features, and maybe that helps with the other issues that you mention, transient space etc. It's probably a bit more complicated, IIUC the current recommended way is to implement an Oak DocumentStore, but that should be checked with the Oak team. -Bertrand
Re: Use Provide-Capability for the org.apache.sling.scripting.sightly bundle
Hi Bertrand, I also had a look at the other thread but I think that for the Sightly bundle we should aim to offer a vendor independent capability name, in case somebody else would like to provide the same capability from a bundle not related to Apache Sling. Would this be too far-fetched? Thanks, Radu On Tue, Jan 27, 2015 at 6:39 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jan 27, 2015 at 5:35 PM, Radu Cotescu r...@apache.org wrote: ...Should the value of this header be different?... I saw SLING-4358 fly by and just started a thread here about defining a Sling standard for those values. -Bertrand
Re: [RT] Sling Resource Providers for NoSQL databases - MongoDB, Couchbase
On Tue, Jan 27, 2015 at 5:49 PM, Stefan Seifert sseif...@pro-vision.de wrote: ...this is of course a very special usecase Ok, if a Sling ResourceProvider is sufficient it's probably simpler to write than an Oak backend. -Bertrand
Re: Use Provide-Capability for the org.apache.sling.scripting.sightly bundle
Hi, On Tue, Jan 27, 2015 at 5:53 PM, Radu Cotescu r...@apache.org wrote: ...I think that for the Sightly bundle we should aim to offer a vendor independent capability name,... Why not - we can just mention that io.sightly is used for Sightly modules, in our specification of Sling capability names. As long as our naming is consistent I'm fine with it. -Bertrand
[jira] [Updated] (SLING-4357) Update Sightly IT
[ https://issues.apache.org/jira/browse/SLING-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4357: Attachment: SLING-4357.patch Attached patch ([^SLING-4357.patch]): * updated testing modules to use io.sightly.tck 1.1.0 which provides tests for Sightly 1.1 * added linting validation for JSON files that define initial content Update Sightly IT - Key: SLING-4357 URL: https://issues.apache.org/jira/browse/SLING-4357 Project: Sling Issue Type: Sub-task Components: Scripting Reporter: Radu Cotescu Fix For: Scripting Sightly Engine 1.0.0 Attachments: SLING-4357.patch The IT for Sightly should be updated to test conformance with version 1.1 of the language specification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [PROPOSAL] JSNodeTypes contribution :: IP clearance needed?
Hello again, while I think the JSNodeTypes contribution is useful I would also like to have it in Sling to not need an OBR to install the Resource Editor. Now that I'm a Committer in the meantime and I have written the JSNodeTypes library solely on my own the question is if the IP clearance process is still needed. What do you think? Best, Sandro Am 18.12.14 um 14:02 schrieb Bertrand Delacretaz: Hi Sandro, On Thu, Dec 11, 2014 at 4:25 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Here you find a demo of the full API and all background information: http://www.jcrbrowser.org/sling/libs/jsnodetypes/content/documentation.html I think it's interesting, I support accepting this donation as it is used in your editor. Thanks for this! Note that we'd need to go via the IP clearance process as we did for the editor. -Bertrand
[jira] [Resolved] (SLING-4290) Fix wrong cardinalities in agent factories
[ https://issues.apache.org/jira/browse/SLING-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-4290. Resolution: Fixed Fix wrong cardinalities in agent factories -- Key: SLING-4290 URL: https://issues.apache.org/jira/browse/SLING-4290 Project: Sling Issue Type: Bug Components: Distribution Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: Content Distribution 0.1.0 The agent factories have some multivalued properties, however their cardinality has been set to -1 which only works with vectors, while they are used e.g. as String arrays causing them only to contain one value, which causes the SyncDistributionAgentFactory to always have one importer and one exporter which is clearly an issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4357) Update Sightly IT
Radu Cotescu created SLING-4357: --- Summary: Update Sightly IT Key: SLING-4357 URL: https://issues.apache.org/jira/browse/SLING-4357 Project: Sling Issue Type: Sub-task Components: Scripting Reporter: Radu Cotescu Fix For: Scripting Sightly Engine 1.0.0 The IT for Sightly should be updated to test conformance with version 1.1 of the language specification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4356) Implement support for 'data-sly-repeat'
[
https://issues.apache.org/jira/browse/SLING-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-4356:
Attachment: SLING-4356.patch
Attached patch [^SLING-4356.patch]:
* implement support for {{data-sly-repeat}}
Implement support for 'data-sly-repeat'
---
Key: SLING-4356
URL: https://issues.apache.org/jira/browse/SLING-4356
Project: Sling
Issue Type: Sub-task
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
Attachments: SLING-4356.patch
Version 1.1 of the Sightly language specification defines a new block element
- {{data-sly-repeat}} [0].
[0] -
https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md#227-repeat
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SLING-4357) Update Sightly IT
[ https://issues.apache.org/jira/browse/SLING-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14293701#comment-14293701 ] Radu Cotescu edited comment on SLING-4357 at 1/27/15 3:48 PM: -- Attached patch [^SLING-4357.patch]: * updated testing modules to use io.sightly.tck 1.1.0 which provides tests for Sightly 1.1 * added linting validation for JSON files that define initial content was (Author: radu.cotescu): Attached patch ([^SLING-4357.patch]): * updated testing modules to use io.sightly.tck 1.1.0 which provides tests for Sightly 1.1 * added linting validation for JSON files that define initial content Update Sightly IT - Key: SLING-4357 URL: https://issues.apache.org/jira/browse/SLING-4357 Project: Sling Issue Type: Sub-task Components: Scripting Reporter: Radu Cotescu Fix For: Scripting Sightly Engine 1.0.0 Attachments: SLING-4357.patch The IT for Sightly should be updated to test conformance with version 1.1 of the language specification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4358) Add the 'Provide-Capability' OSGi header to the org.apache.sling.scripting.sightly bundle
Radu Cotescu created SLING-4358:
---
Summary: Add the 'Provide-Capability' OSGi header to the
org.apache.sling.scripting.sightly bundle
Key: SLING-4358
URL: https://issues.apache.org/jira/browse/SLING-4358
Project: Sling
Issue Type: Sub-task
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
The OSGi {{Provide-Capability}} \[0\] header should be added to the
{{org.apache.sling.scripting.sightly}} bundle to easily identify what version
of the Sightly specification \[1\] the bundle implements.
\[0\] - http://wiki.osgi.org/wiki/Provide-Capability
\[1\] - https://github.com/Adobe-Marketing-Cloud/sightly-spec/releases
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[RT] Sling Resource Providers for NoSQL databases - MongoDB, Couchbase
we currently evaluate to integrate a Couchbase NoSQL database [1] into a sling resource tree. as a starting point i had a deeper look on the MongoDB resource provider [2], because the concept is quite similar. some thoughts on this: 1. what is the status of the mongodb provider? is someone using it already in production? looking at the code it seems to be not threadsafe concerning the CRUD handling with non-synchronized hash maps. 2. how to map resource URLs to NoSQL: the mongodb provider has a syntax like: root_path/collection/custom_path where root_path and the mongodb database name is configurable via OSGi (multiple entry points possible), collection has to match with an existing collection in mongodb and the remaining path is mapped to a property in a document in the collection. i wonder if this is the best solution, the collection path part seems too restrictive to me (fails if the collection does not exist). i would favor specifying both root_path and collection via osgi allowing entry points with an unconstrained tree hierarchy below. couchbase for example does not have such a collection concept, it has only bucket which is comparable to the mongodb database. 3. the resource provider mixes up the in-memory CRUD handling with keeping maps of changed/deleted resources, and the mapping to the NoSQL structure. if these two aspects would be separated the former could be reused for all NoSQL databases and the latter is responsible only for the flat list resource-to-document mapping and will be different for each NoSQL database. bonus: the thread-safety of the CRUD handling has to be implemented only once, not once for each resource provider. additional logic like type mapping values to strings, generic value map implementations, automatic tree creation etc. could be shared between all NoSQL providers. 4. an open point is whether to support binary data as well, or to leave it out in the first phase. storing binary data may be problematic for some NoSQL databases, requiring a separate storage concept for this. the mongodb resource provider currently does not support binary data. 5. there were plans to create a SOLR sling resource provider [3][4], which goes roughly in the same direction; but it seems it had no outcome. WDYT? stefan [1] http://www.couchbase.com [2] https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/mongodb [3] https://issues.apache.org/jira/browse/SLING-2795 [4] http://apache-sling.73963.n3.nabble.com/GSoC-2013-Apache-Solr-backend-for-Apache-Sling-tt4023347.html
[jira] [Updated] (SLING-4354) Update the behaviour of the 'join' option
[
https://issues.apache.org/jira/browse/SLING-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-4354:
Attachment: SLING-4354.patch
Attached patch [^SLING-4354.patch]:
* allow {{join}} to work for expressions that evaluate to a string
Update the behaviour of the 'join' option
-
Key: SLING-4354
URL: https://issues.apache.org/jira/browse/SLING-4354
Project: Sling
Issue Type: Sub-task
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
Attachments: SLING-4354.patch
The implementation of the {{join}} option should be updated to support
expressions that evaluate to a string, according to the specification update
from \[0\].
\[0\] -
https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md#124-array-join
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4355) Implement support for the 'sly' HTML tag
[
https://issues.apache.org/jira/browse/SLING-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-4355:
Attachment: SLING-4355.patch
Attached patch [^SLING-4355.patch]:
* implemented support for the {{sly}} special tag in concordance with
{{data-sly-unwrap}}
Implement support for the 'sly' HTML tag
Key: SLING-4355
URL: https://issues.apache.org/jira/browse/SLING-4355
Project: Sling
Issue Type: Sub-task
Components: Scripting
Reporter: Radu Cotescu
Fix For: Scripting Sightly Engine 1.0.0
Attachments: SLING-4355.patch
Version 1.1 of the Sightly language specification defines a special HTML tag
- {{sly}} - that acts similarly to {{data-sly-unwrap}} \[0\].
\[0\] -
https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md#31-sly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
RE: [VOTE] Release Apache Sling Testing JCR Mock 1.1.2, ResourceResolver Mock 1.1.2, Sling Mock 1.1.2, Sling Mock Jackrabbit 0.1.2
one (binding) vote is missing... stefan -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Thursday, January 22, 2015 10:11 PM To: dev@sling.apache.org Subject: [VOTE] Release Apache Sling Testing JCR Mock 1.1.2, ResourceResolver Mock 1.1.2, Sling Mock 1.1.2, Sling Mock Jackrabbit 0.1.2 Hi, We solved 2 issues in JCR Mock 1.1.2: https://issues.apache.org/jira/browse/SLING/fixforversion/12329091 We solved 2 issues in ResourceResolver Mock 1.1.2: https://issues.apache.org/jira/browse/SLING/fixforversion/12329092 We solved 3 issues in Sling Mock 1.1.2: https://issues.apache.org/jira/browse/SLING/fixforversion/12329089 We solved 2 issues in Sling Mock Jackrabbit 0.1.2: https://issues.apache.org/jira/browse/SLING/fixforversion/12328858 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1175/ 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 1175 /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. stefan
SLING-4358 - provide/require capability, should we define a standard for capability names?
Hi, By analogy with http://www.osgi.org/Specifications/ReferenceNamespaces, should we agree on a prefix such as org.apache.sling.capability.MMM for our capability names, where MMM is the module name like sightly? -Bertrand
Re: [VOTE] Release Apache Sling Testing JCR Mock 1.1.2, ResourceResolver Mock 1.1.2, Sling Mock 1.1.2, Sling Mock Jackrabbit 0.1.2
On Tue, Jan 27, 2015 at 5:15 PM, Stefan Seifert sseif...@pro-vision.de wrote: one (binding) vote is missing... it's fine for you to vote as well ;-) -Bertrand
Re: [RT] Sling Resource Providers for NoSQL databases - MongoDB, Couchbase
Hi, On Tue, Jan 27, 2015 at 5:09 PM, Stefan Seifert sseif...@pro-vision.de wrote: ...we currently evaluate to integrate a Couchbase NoSQL database [1] into a sling resource tree... As mentioned in a different thread about DynamoDB, it might be interesting to consider writing a Couchbase backend for Oak instead. The advantages are inheriting Oak's indexing and other useful JCR features, and maybe that helps with the other issues that you mention, transient space etc. It's probably a bit more complicated, IIUC the current recommended way is to implement an Oak DocumentStore, but that should be checked with the Oak team. -Bertrand
Re: Use Provide-Capability for the org.apache.sling.scripting.sightly bundle
On Tue, Jan 27, 2015 at 5:35 PM, Radu Cotescu r...@apache.org wrote: ...Should the value of this header be different?... I saw SLING-4358 fly by and just started a thread here about defining a Sling standard for those values. -Bertrand
Re: [PROPOSAL] JSNodeTypes contribution :: IP clearance needed?
Hi Sandro, On Tue, Jan 27, 2015 at 4:51 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Now that I'm a Committer in the meantime and I have written the JSNodeTypes library solely on my own the question is if the IP clearance process is still needed IMO it's not needed in this case, committing code that you wrote yourself is covered by your iCLA. I suggest that you wait 24 hours for possible objections, and if there's none go ahead and commit. -Bertrand
Re: [VOTE] Release Apache Sling Testing JCR Mock 1.1.2, ResourceResolver Mock 1.1.2, Sling Mock 1.1.2, Sling Mock Jackrabbit 0.1.2
On Tue, Jan 27, 2015 at 5:33 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jan 27, 2015 at 5:15 PM, Stefan Seifert sseif...@pro-vision.de wrote: one (binding) vote is missing... it's fine for you to vote as well ;-) Ah no sorry, you're not on the PMC...I might have time tomorrow morning, but hopefully someone will beat me to it. -Bertrand
Use Provide-Capability for the org.apache.sling.scripting.sightly bundle
Hi, Given the recent update [0] of the Sightly language specification I'm tempted to use the Provide-Capability OSGi header [1] for the org.apache.sling.scripting.sightly bundle to provide information about which specification version is actually implemented: Provide-Capability: io.sightly; version=1.1 Do you think this would be a good idea? Should the value of this header be different? Thanks, Radu [0] - https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md [1] - http://wiki.osgi.org/wiki/Provide-Capability
[RT] Ideas for a multi-tenant and multi-module content model
Hi, I've been thinking a lot about a content model that would help Sling applications be naturally friendly to multi-tenancy and to continuous deployment where multiple versions of modules need to coexist. I have now written those thoughts down at https://cwiki.apache.org/confluence/display/SLING/Ideas+for+a+multi-tenant+and+multi-module+content+model Feedback is welcome but please keep in mind that this is mostly just thinking outloud at this point. Credit goes to Dominik Suess for the assemblies idea, it looks like this intermediate routing layer might help make sense of complex multi-T and multi-M systems. -Bertrand
