[
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
[
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
See https://builds.apache.org/job/sling-trunk-1.8/666/changes
[
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
See https://builds.apache.org/job/sling-trunk-1.6/2986/changes
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
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
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
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
[
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
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
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
[
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
[
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
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
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
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?
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
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
[
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
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
[
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
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:
[
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
[
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:
--
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
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
[
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
[
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
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,
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
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
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
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
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,
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
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;
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
38 matches
Mail list logo
