Re: [RESULT][VOTE] Apache Sling Launchpad Base 5.6.4-2.6.18
Time to call the vote on the Apache Sling Launchpad Base 5.6.4-2.6.18 release. * +1 votes from Carsten Ziegeler, Robert Munteanu, Stefan Seifert, and Karl Pauls. * No other votes. The vote is successful. I will make the release artifacts available as soon as possible.
Re: [RESULT] [VOTE] Apache Sling Servlet Post 2.3.20
Time to call the vote on the Apache Sling Servlet Post 2.3.20 release. * +1 votes from Carsten Ziegeler, Stefan Egli, Stefan Seifert, Antonio Sanso, and Karl Pauls. * No other votes. The vote is successful. I will make the release artifacts available as soon as possible.
Re: [RESULT][VOTE] Apache Sling JCR Contentloader 2.2.2
Time to call the vote on the Apache Sling JCR Contentloader 2.2.2 release. * +1 votes from Stefan Egli, Stefan Seifert, Carsten Ziegeler, and Karl Pauls. * No other votes. The vote is successful. I will make the release artifacts available as soon as possible.
Re: [VOTE] Apache Sling Launchpad Base 5.6.4-2.6.18
+1 regards, Karl On Fri, May 26, 2017 at 9:18 AM, Stefan Seifertwrote: > +1 > -- Karl Pauls karlpa...@gmail.com
Re: [VOTE] Apache Sling Servlet Post 2.3.20
+1 regards, Karl On Wed, May 24, 2017 at 6:33 AM, Antonio Sansowrote: > +1 > On May 23, 2017, at 3:05 PM, Karl Pauls wrote: > >> I would like to call a vote on the following release, >> >> Apache Sling Servlet Post 2.3.20 >> >> We solved 1 issues in this release: >> https://issues.apache.org/jira/browse/SLING/fixforversion/12340584 >> >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachesling-1727/ >> >> 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 1727 /tmp/sling-staging >> >> Please vote to approve this release: >> >> [ ] +1 Approve the release >> [ ] 0 Don't care >> [ ] -1 Don't release, because ... > -- Karl Pauls karlpa...@gmail.com
Re: [VOTE] Apache Sling JCR Contentloader 2.2.2
+1 regards, Karl On Wed, May 24, 2017 at 8:01 AM, Carsten Ziegelerwrote: > +1 > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org -- Karl Pauls karlpa...@gmail.com
Re: [VOTE] Release Apache Sling JCR Resource 3.0.2
+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[VOTE] Release Apache Sling JCR Resource 3.0.2
Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12340481 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1732 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 1732 /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. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Updated] (SLING-4752) New resource query API
[ https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-4752: Fix Version/s: (was: JCR Resource 3.0.2) JCR Resource 3.0.4 > New resource query API > -- > > Key: SLING-4752 > URL: https://issues.apache.org/jira/browse/SLING-4752 > Project: Sling > Issue Type: Improvement > Components: API, JCR, ResourceResolver >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: JCR Resource 3.0.4, API 2.16.4, Resource Resolver 1.5.26 > > Attachments: api-patch.txt, resourceresolver-patch.txt > > > Discussion thread: > http://mail-archives.apache.org/mod_mbox/sling-dev/201505.mbox/%3C555983F6.7020100%40apache.org%3E > Starting mail: > The current resource query api has several problems: > - it's using the JCR spec to define a query > - it's not clear which queries are supported by providers > - queries are string based > - implementing queries in a resource provider is way too hard as this > would require to implement the complete jcr query api. > I've created a draft for a new, object based API at [1]. The main idea > is to use a builder pattern to create Query objects. This are immutable > and have a unique identifier. The QueryManager service can be used to > execute a query in the context of a resource resolver. The manager > delegates the query to the providers. As each Query object has this > identifier, implementations can use this to cache the parsing of the query. > In addition to the query object you can pass in query instructions to > specify a limit or range for the query. > Obviously this is a reduced set compared to the full fledged jcr search > api, however it should be suitable for the majority of use cases. > [1] > https://svn.apache.org/repos/asf/sling/whiteboard/cziegeler/api-v3/src/main/java/org/apache/sling/api/resource/query/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6886) JcrListenerBaseConfig sets external flag incorrectly
[ https://issues.apache.org/jira/browse/SLING-6886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6886. - Resolution: Fixed Assignee: Carsten Ziegeler Thanks for your patch. It's applied in rev 1796496 > JcrListenerBaseConfig sets external flag incorrectly > > > Key: SLING-6886 > URL: https://issues.apache.org/jira/browse/SLING-6886 > Project: Sling > Issue Type: Bug > Components: JCR >Affects Versions: JCR Resource 2.9.2 >Reporter: Varun Nagpal >Assignee: Carsten Ziegeler > Fix For: JCR Resource 3.0.2 > > Attachments: SLING-6886.patch > > > o.a.s.j.r.i.JcrListenerBaseConfig.java sets the NoExternal flag incorrectly. > See > http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/JcrListenerBaseConfig.java?view=markup#l125 > This impacts JcrResourceListener and OsgiObservationBridge which does not > convert JCR observation events to OSGi events which are not local to the > Sling instance. -- This message was sent by Atlassian JIRA (v6.3.15#6346)