Am 27.01.15 um 17:09 schrieb Stefan Seifert:
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
[
https://issues.apache.org/jira/browse/SLING-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295162#comment-14295162
]
Carsten Ziegeler commented on SLING-4358:
-
The OSGi CPEG is currently of
[
https://issues.apache.org/jira/browse/SLING-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295167#comment-14295167
]
Radu Cotescu commented on SLING-4358:
-
In what release of the spec do we expect to
See https://builds.apache.org/job/sling-trunk-1.7/1380/changes
See https://builds.apache.org/job/sling-trunk-1.7/1381/changes
See https://builds.apache.org/job/sling-trunk-1.8/667/changes
[
https://issues.apache.org/jira/browse/SLING-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294895#comment-14294895
]
Radu Cotescu commented on SLING-913:
Wouldn't this still need a read operation to be
See https://builds.apache.org/job/sling-trunk-1.7/changes
Hi,
The vote has passed with the following result:
+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Egli
I will promote the artifacts to the central Maven repository and update this
sling site.
@any PMC member: please copy this release to the Sling dist directory.
stefan
Carsten Ziegeler created SLING-4361:
---
Summary: Improve handling of unregistering
ResourceProviderFactories
Key: SLING-4361
URL: https://issues.apache.org/jira/browse/SLING-4361
Project: Sling
Nicolas Peltier created SLING-4362:
--
Summary: [jcr mocks] Resource type not correctly loaded when using
jcr mock
Key: SLING-4362
URL: https://issues.apache.org/jira/browse/SLING-4362
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-4362:
---
Description:
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such
Am 27.01.15 um 17:33 schrieb Bertrand Delacretaz:
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 ;-)
We need a third *binding* vote, and it realyl would be nice if more
people would vote
+1
Sorry for the delay, been underwater lately.
On Jan 28, 2015, at 10:36 AM, Carsten Ziegeler cziege...@apache.org wrote:
Am 27.01.15 um 17:33 schrieb Bertrand Delacretaz:
On Tue, Jan 27, 2015 at 5:15 PM, Stefan Seifert sseif...@pro-vision.de
wrote:
one (binding) vote is missing...
See https://builds.apache.org/job/sling-trunk-1.6/2988/changes
Stefan Egli created SLING-4359:
--
Summary: LargeTopologyWithHubTest.testLargeTopologyWithHub test
failure
Key: SLING-4359
URL: https://issues.apache.org/jira/browse/SLING-4359
Project: Sling
Am 28.01.15 um 10:55 schrieb Stefan Seifert:
Hi,
The vote has passed with the following result:
+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Egli
I will promote the artifacts to the central Maven repository and update this
sling site.
@any PMC member: please copy this
See https://builds.apache.org/job/sling-trunk-1.7/1376/changes
[
https://issues.apache.org/jira/browse/SLING-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294941#comment-14294941
]
Carsten Ziegeler commented on SLING-4340:
-
[~justinedelson] What about a
[
https://issues.apache.org/jira/browse/SLING-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4360.
-
Resolution: Fixed
Solved as explained above
Mark ResourceResolver and
+1,
(verified md5/sha1)
Cheers,
Stefan
On 1/27/15 5:15 PM, Stefan Seifert sseif...@pro-vision.de wrote:
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
See https://builds.apache.org/job/sling-trunk-1.7/1378/changes
Am 28.01.15 um 11:24 schrieb Carsten Ziegeler:
Am 28.01.15 um 10:55 schrieb Stefan Seifert:
Hi,
The vote has passed with the following result:
+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Egli
I will promote the artifacts to the central Maven repository and update this
sling
Carsten Ziegeler created SLING-4360:
---
Summary: Mark ResourceResolver and ResourceResolverFactory as
invalid if factory is unregistered
Key: SLING-4360
URL: https://issues.apache.org/jira/browse/SLING-4360
Hi,
On Tue, Jan 27, 2015 at 6:33 PM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
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
On Wed, 2015-01-28 at 12:29 +, cziege...@apache.org wrote:
Author: cziegeler
Date: Wed Jan 28 12:29:44 2015
New Revision: 1655278
URL: http://svn.apache.org/r1655278
Log:
Clarify lifetime of resource and resource resolver objects.
Modified:
[
https://issues.apache.org/jira/browse/SLING-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295223#comment-14295223
]
David Bosschaert commented on SLING-4358:
-
It will be in Enterprise R6.
However,
[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4318:
---
Attachment: SLING-4318-test.patch
The attached SLING-4318-test.patch provides some
Hi,
For SLING-4318 Tomek's contribution uses the V selector that I
suggested so that foo.V.json lists the versions of the foo node.
Putting this servlet in our servlets.get bundle might interfere with
existing user servlets that use this selector.
How should we avoid this potential collision?
[
https://issues.apache.org/jira/browse/SLING-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295476#comment-14295476
]
Justin Edelson commented on SLING-4340:
---
[~cziegeler] I think this will work for my
See https://builds.apache.org/job/sling-trunk-1.8/changes
+1
On Jan 28, 2015, at 4:57 PM, Carsten Ziegeler cziege...@apache.org wrote:
Hi,
we solved three issue
https://issues.apache.org/jira/browse/SLING/fixforversion/12329309
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1178/
You can use this UNIX
See https://builds.apache.org/job/sling-trunk-1.7/changes
[
https://issues.apache.org/jira/browse/SLING-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295900#comment-14295900
]
Alexander Klimetschek commented on SLING-4344:
--
Hmm, while the fix might be
Hello Justin,
On Wed, Jan 28, 2015 at 8:14 PM, Justin Edelson jus...@justinedelson.com
wrote:
How about using ConfigurationPolicy.REQUIRE for this so that it needs
to be manually enabled? I suspect that's probably a good idea for this
feature anyway even if there was no potential collision.
Carsten Ziegeler created SLING-4363:
---
Summary: Unregistering a resource provider should also reregister
the resource resolver factory
Key: SLING-4363
URL: https://issues.apache.org/jira/browse/SLING-4363
Hi,
we solved three issue
https://issues.apache.org/jira/browse/SLING/fixforversion/12329309
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1178/
You can use this UNIX script to download the release and verify the
signatures:
Not sure what the above is supposed to mean:
The same applies in general to all objects returned by this
instance, especially for all instances
Good catch, thanks - I meant resources. Fixed now
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
[
https://issues.apache.org/jira/browse/SLING-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295235#comment-14295235
]
Nicolas Peltier commented on SLING-4362:
my guess here is content loader uses
[
https://issues.apache.org/jira/browse/SLING-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4363.
-
Resolution: Fixed
Fixed in rev 1655361
Unregistering a resource provider should also
[
https://issues.apache.org/jira/browse/SLING-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-4362:
---
Description:
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such
[
https://issues.apache.org/jira/browse/SLING-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4361.
-
Resolution: Fixed
I've refactored the handling in 1655358 to use a background thread for
See https://builds.apache.org/job/sling-oak-it-1.6/299/changes
+1
On Jan 28, 2015 4:57 PM, Carsten Ziegeler cziege...@apache.org wrote:
Hi,
we solved three issue
https://issues.apache.org/jira/browse/SLING/fixforversion/12329309
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1178/
You can use this UNIX script
See https://builds.apache.org/job/sling-trunk-1.7/1382/changes
See https://builds.apache.org/job/sling-trunk-1.6/2994/changes
+1
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
See https://builds.apache.org/job/sling-trunk-1.8/673/changes
Sandro Boehme created SLING-4364:
Summary: Integrate new JavaScript node type library
Key: SLING-4364
URL: https://issues.apache.org/jira/browse/SLING-4364
Project: Sling
Issue Type: New
Hi Bertrand,
thanks for your feedback, that sounds good!
If there are no objections I would commit it with SLING-4364 in the folder
/contrib/commons/js/nodetypes
with the Sling parent pom,
the ArtifactId org.apache.sling.commons.js.nodetypes
and the version 1.0.SNAPSHOT.
Does that fit in the
Hi
I think the capability here really says „this bundle implements Sightly
Language Spec 1.1“ And since this spec is outside of Sling at [1] and commonly
referred to as sightly.io I would think we should be using a namespace which
matches the Sightly Language Spec and is not implementation
Hi Sandro,
On Wed, Jan 28, 2015 at 5:37 PM, Sandro Boehme sandro.boe...@gmx.de wrote:
...If there are no objections I would commit it with SLING-4364 in the folder
/contrib/commons/js/nodetypes
with the Sling parent pom,
the ArtifactId org.apache.sling.commons.js.nodetypes
and the version
How about using ConfigurationPolicy.REQUIRE for this so that it needs
to be manually enabled? I suspect that's probably a good idea for this
feature anyway even if there was no potential collision.
Regards,
Justin
On Wed, Jan 28, 2015 at 12:33 PM, Bertrand Delacretaz
bdelacre...@apache.org
53 matches
Mail list logo
