[jira] [Updated] (SLING-7650) Update SCR, ConfigAdmin and Http to R7 implementations
[ https://issues.apache.org/jira/browse/SLING-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7650: --- Labels: Sling-11-ReleaseNotes (was: ) > Update SCR, ConfigAdmin and Http to R7 implementations > -- > > Key: SLING-7650 > URL: https://issues.apache.org/jira/browse/SLING-7650 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Labels: Sling-11-ReleaseNotes > Fix For: Starter 11 > > > The R7 implementations are released: > Apache Felix ConfigAdmin 1.9.0 > Apache Felix SCR 2.1.0 > Apache Felix Http Jetty 4.0.0 > Apache Felix Http Bridge 4.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SLING-7652) Define explicit execution ids to make it easier to overwrite
Konrad Windszus created SLING-7652:
--
Summary: Define explicit execution ids to make it easier to
overwrite
Key: SLING-7652
URL: https://issues.apache.org/jira/browse/SLING-7652
Project: Sling
Issue Type: Improvement
Components: General
Affects Versions: Parent 33
Reporter: Konrad Windszus
Fix For: Parent 34
Maven plugin executions defined without an id get the id {{default}}. We should
rather given an explicit id to make it easier to either overwrite/extend the
existing execution within a child pom.xml or define a dedicated separate one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SLING-7575) Define common instructions for bnd-maven-plugin
[
https://issues.apache.org/jira/browse/SLING-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7575:
---
Description:
Once [https://github.com/bndtools/bnd/issues/2265] is fixed and released in
{{bnd-maven-plugin}} 4.0 we should upgrade to that version and make sure to
define all the instructions common to all Sling bundles in the parameter
{{bnd}} of the parent. Those instructions should include
# Bundle-Category: sling
# Bundle-Description: ${project.description}
# Bundle-DocURL: https://sling.apache.org|https://sling.apache.org/
# Bundle-License: Apache License, Version 2.0
# Bundle-Vendor: The Apache Software Foundation
# -exportcontents: ${removeall;${packages;VERSIONED};${packages;CONDITIONAL}},
this is to by default export all versioned packages, except for the ones which
are conditionally included, compare with
[https://github.com/bndtools/bnd/issues/2131]
# -snapshot: ${tstamp;MMddHHmmssSS} (compare with
[https://www.mail-archive.com/dev@sling.apache.org/msg76177.html])
was:
Once [https://github.com/bndtools/bnd/issues/2265] is fixed and released in
{{bnd-maven-plugin}} 4.0 we should upgrade to that version and make sure to
define all the instructions common to all Sling bundles in the parameter
{{bnd}} of the parent. Those instructions should include
# Bundle-Category: sling
# Bundle-Description: ${project.description}
# Bundle-DocURL: https://sling.apache.org|https://sling.apache.org/
# Bundle-License: Apache License, Version 2.0
# Bundle-Vendor: The Apache Software Foundation
# -exportcontents: ${packages;VERSIONED}, this is to by default export all
versioned packages, compare with [https://github.com/bndtools/bnd/issues/2131]
# -snapshot: ${tstamp;MMddHHmmssSS} (compare with
[https://www.mail-archive.com/dev@sling.apache.org/msg76177.html])
> Define common instructions for bnd-maven-plugin
> ---
>
> Key: SLING-7575
> URL: https://issues.apache.org/jira/browse/SLING-7575
> Project: Sling
> Issue Type: Improvement
> Components: General
>Affects Versions: Parent 33
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Parent 34
>
>
> Once [https://github.com/bndtools/bnd/issues/2265] is fixed and released in
> {{bnd-maven-plugin}} 4.0 we should upgrade to that version and make sure to
> define all the instructions common to all Sling bundles in the parameter
> {{bnd}} of the parent. Those instructions should include
> # Bundle-Category: sling
> # Bundle-Description: ${project.description}
> # Bundle-DocURL: https://sling.apache.org|https://sling.apache.org/
> # Bundle-License: Apache License, Version 2.0
> # Bundle-Vendor: The Apache Software Foundation
> # -exportcontents:
> ${removeall;${packages;VERSIONED};${packages;CONDITIONAL}}, this is to by
> default export all versioned packages, except for the ones which are
> conditionally included, compare with
> [https://github.com/bndtools/bnd/issues/2131]
> # -snapshot: ${tstamp;MMddHHmmssSS} (compare with
> [https://www.mail-archive.com/dev@sling.apache.org/msg76177.html])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Teleporter: deploy a test bundle, then use it from the client(!) side, afterwards undeploy it
Hi, since in general I very much like to keep related things together in most of the cases want to execute the IT in the same Maven module where the actual implementation is. Therefore, teleporter rules are very handy, because they transparently create bundles only for the IT purpose and execute them remotely. But sometimes I want to cover in the IT also the request starting on the client side, e.g. to check if a certain servlet/script is correctly deployed. How can I combine these two approaches to have a special servlet only necessary for the IT (not part of the actual code) transparently deployed as dedicated test bundle and call that then from my test with an http client? These are the steps which would be necessary: 1. create and deploy the test bundle containing my servlet with the teleporter 2. execute the IT leveraging an HTTP client to send a request to the previously deployed servlet 3. uninstall the test bundle Any ideas how to accomplish that with either the existing teleporter rules or a small extension of them? Thanks, Konrad
Re: [VOTE] Release Apache Sling JCR Content Parser version 1.2.6 and Apache Sling Query version 4.0.2
Dan - The keys are correct in the sling.asc file now - Jason On Thu, May 3, 2018, at 6:11 PM, Daniel Klco wrote: > Hm, I'm getting GPG errors... > > > CHECK SIGNATURES AND > DIGESTS > > /tmp/sling-staging/1897/org/apache/sling/index.html.tmp > gpg: > md5 : > sha1 : > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/ > index.html.tmp > gpg: > md5 : > sha1 : > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/maven- > metadata.xml > gpg: > md5 : GOOD (a7706a7ee9d876d2976f09e1123b8e38) > sha1 : GOOD (2d2809a468153b50241a7f6a7ca6ff778eddc4e8) > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > org.apache.sling.query-4.0.2.jar > gpg: BAD > md5 : GOOD (dbf90e3cc8126a0f3d2eb130750e7679) > sha1 : GOOD (0801831664d3cdb6f8b9bdcd6c33ff6121407c6b) > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > org.apache.sling.query-4.0.2-source-release.zip > gpg: BAD > md5 : GOOD (1912ba15ed14460bf36cadaa3479a83a) > sha1 : GOOD (ab4f6fa29e343ebe7cc06ef8a2ce396db8db513b) > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > index.html.tmp > gpg: > md5 : > sha1 : > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > org.apache.sling.query-4.0.2.pom > gpg: BAD > md5 : GOOD (6340e9ba5a72a2d0be69a4cc4894fe84) > sha1 : GOOD (a3d72fde160150f0851384e78612bf0e3c29a6e9) > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > org.apache.sling.query-4.0.2-sources.jar > gpg: BAD > md5 : GOOD (4b2b9b8271b17ba1569aebe155e71148) > sha1 : GOOD (87af5dbb7ffac9a77be636c3500bb8fa7d73a531) > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > org.apache.sling.query-4.0.2-javadoc.jar > gpg: BAD > md5 : GOOD (72a03851ed3905aa9a16cfbbfc09f4b9) > sha1 : GOOD (d5f0df25da04558bd12be4e35e418027d399a1d5) > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/index.html.tmp > gpg: > md5 : > sha1 : > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/maven-metadata.xml > gpg: > md5 : GOOD (4f5dceaa2143378ffa3d5ac4b6f960b8) > sha1 : GOOD (379bddfb27a6f484e50adc59580515eb9f10f242) > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/1.2.6/ > org.apache.sling.jcr.contentparser-1.2.6-source-release.zip > gpg: BAD > md5 : GOOD (f7710e1cc9226fcd8e89bae8ceffc0be) > sha1 : GOOD (c7fca8fcea6270f3978ef73e949b77f7ab880532) > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/1.2.6/ > org.apache.sling.jcr.contentparser-1.2.6.pom > gpg: BAD > md5 : GOOD (8622e1fd6354bfe1329b85c4647903db) > sha1 : GOOD (75e6332dd48f4f1a60277d91d269dec801de7cee) > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/1.2.6/ > org.apache.sling.jcr.contentparser-1.2.6-sources.jar > gpg: BAD > md5 : GOOD (8be56140dee0a39ada2cc986529cdb7c) > sha1 : GOOD (89c5baf0774e8ae9a1e0d233528b5313a3bea585) > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/1.2.6/ > org.apache.sling.jcr.contentparser-1.2.6-javadoc.jar > gpg: BAD > md5 : GOOD (8d7f8da5789431b1dacc3aff3b5f39ca) > sha1 : GOOD (33e02c0e0955185c7c3c5fa59cbbdf0208d20f6c) > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/1.2.6/index.html.tmp > gpg: > md5 : > sha1 : > /tmp/sling-staging/1897/org/apache/sling/ > org.apache.sling.jcr.contentparser/1.2.6/ > org.apache.sling.jcr.contentparser-1.2.6.jar > gpg: BAD > md5 : GOOD (54eb0fe6df701cb9f7a5973a56984720) > sha1 : GOOD (a9a241ee413b578b214d212e552826b2afb7d512) > > > Anyone else having issues? not sure if it's something about my setup. I > just re-imported the sling keys from > https://people.apache.org/keys/group/sling.asc and still got the same issue. > > Regards, > Dan > > On Thu, May 3, 2018 at 7:25 AM, Radu Cotescu wrote: > > > +1 (only checked signatures) > > > > > On 2 May 2018, at 17:30, Jason E Bailey wrote: > > > > > > Please vote to approve this release: > > > > > > [ ] +1 Approve the release > > > [ ] 0 Don't care > > > [ ] -1 Don't release, because ... > > > >
Re: [VOTE] Release Apache Sling JCR Content Parser version 1.2.6 and Apache Sling Query version 4.0.2
Looks good to me +1 On Sat, May 5, 2018 at 1:21 PM, Jason E Bailey wrote: > Dan - The keys are correct in the sling.asc file now > > - Jason > > On Thu, May 3, 2018, at 6:11 PM, Daniel Klco wrote: > > Hm, I'm getting GPG errors... > > > > > > > CHECK SIGNATURES AND > > DIGESTS > > > > > /tmp/sling-staging/1897/org/apache/sling/index.html.tmp > > gpg: > > md5 : > > sha1 : > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/ > > index.html.tmp > > gpg: > > md5 : > > sha1 : > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/maven- > > metadata.xml > > gpg: > > md5 : GOOD (a7706a7ee9d876d2976f09e1123b8e38) > > sha1 : GOOD (2d2809a468153b50241a7f6a7ca6ff778eddc4e8) > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > > org.apache.sling.query-4.0.2.jar > > gpg: BAD > > md5 : GOOD (dbf90e3cc8126a0f3d2eb130750e7679) > > sha1 : GOOD (0801831664d3cdb6f8b9bdcd6c33ff6121407c6b) > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > > org.apache.sling.query-4.0.2-source-release.zip > > gpg: BAD > > md5 : GOOD (1912ba15ed14460bf36cadaa3479a83a) > > sha1 : GOOD (ab4f6fa29e343ebe7cc06ef8a2ce396db8db513b) > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > > index.html.tmp > > gpg: > > md5 : > > sha1 : > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > > org.apache.sling.query-4.0.2.pom > > gpg: BAD > > md5 : GOOD (6340e9ba5a72a2d0be69a4cc4894fe84) > > sha1 : GOOD (a3d72fde160150f0851384e78612bf0e3c29a6e9) > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > > org.apache.sling.query-4.0.2-sources.jar > > gpg: BAD > > md5 : GOOD (4b2b9b8271b17ba1569aebe155e71148) > > sha1 : GOOD (87af5dbb7ffac9a77be636c3500bb8fa7d73a531) > > /tmp/sling-staging/1897/org/apache/sling/org.apache.sling.query/4.0.2/ > > org.apache.sling.query-4.0.2-javadoc.jar > > gpg: BAD > > md5 : GOOD (72a03851ed3905aa9a16cfbbfc09f4b9) > > sha1 : GOOD (d5f0df25da04558bd12be4e35e418027d399a1d5) > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/index.html.tmp > > gpg: > > md5 : > > sha1 : > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/maven-metadata.xml > > gpg: > > md5 : GOOD (4f5dceaa2143378ffa3d5ac4b6f960b8) > > sha1 : GOOD (379bddfb27a6f484e50adc59580515eb9f10f242) > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/1.2.6/ > > org.apache.sling.jcr.contentparser-1.2.6-source-release.zip > > gpg: BAD > > md5 : GOOD (f7710e1cc9226fcd8e89bae8ceffc0be) > > sha1 : GOOD (c7fca8fcea6270f3978ef73e949b77f7ab880532) > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/1.2.6/ > > org.apache.sling.jcr.contentparser-1.2.6.pom > > gpg: BAD > > md5 : GOOD (8622e1fd6354bfe1329b85c4647903db) > > sha1 : GOOD (75e6332dd48f4f1a60277d91d269dec801de7cee) > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/1.2.6/ > > org.apache.sling.jcr.contentparser-1.2.6-sources.jar > > gpg: BAD > > md5 : GOOD (8be56140dee0a39ada2cc986529cdb7c) > > sha1 : GOOD (89c5baf0774e8ae9a1e0d233528b5313a3bea585) > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/1.2.6/ > > org.apache.sling.jcr.contentparser-1.2.6-javadoc.jar > > gpg: BAD > > md5 : GOOD (8d7f8da5789431b1dacc3aff3b5f39ca) > > sha1 : GOOD (33e02c0e0955185c7c3c5fa59cbbdf0208d20f6c) > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/1.2.6/index.html.tmp > > gpg: > > md5 : > > sha1 : > > /tmp/sling-staging/1897/org/apache/sling/ > > org.apache.sling.jcr.contentparser/1.2.6/ > > org.apache.sling.jcr.contentparser-1.2.6.jar > > gpg: BAD > > md5 : GOOD (54eb0fe6df701cb9f7a5973a56984720) > > sha1 : GOOD (a9a241ee413b578b214d212e552826b2afb7d512) > > > > > > > Anyone else having issues? not sure if it's something about my setup. I > > just re-imported the sling keys from > > https://people.apache.org/keys/group/sling.asc and still got the same > issue. > > > > Regards, > > Dan > > > > On Thu, May 3, 2018 at 7:25 AM, Radu Cotescu wrote: > > > > > +1 (only checked signatures) > > > > > > > On 2 May 2018, at 17:30, Jason E Bailey > wrote: > > > > > > > > Please vote to approve this release: > > > > > > > > [ ] +1 Approve the release > > > > [ ] 0 Don't care > > > > [ ] -1 Don't release, because ... > > > > > > >
[jira] [Resolved] (SLING-7628) Event support depends on Discovery Commons
[
https://issues.apache.org/jira/browse/SLING-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-7628.
-
Resolution: Fixed
Fix Version/s: Event 4.2.12
> Event support depends on Discovery Commons
> --
>
> Key: SLING-7628
> URL: https://issues.apache.org/jira/browse/SLING-7628
> Project: Sling
> Issue Type: Bug
> Components: Event
>Affects Versions: Event 4.0.2
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Critical
> Fix For: Event 4.2.12
>
>
> SLING-5560 added a dependency on Discovery Commons
> ({{InitDelayingTopologyEventListener}}) which means Event support is no
> longer useable in (Discovery) standalone setups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [VOTE] Release Apache Sling JCR Content Parser version 1.2.6 and Apache Sling Query version 4.0.2
+1 David On 2 May 2018 at 16:30, Jason E Bailey wrote: > Hi, > > This combines two releases > > We solved 2 issues in this release of JCR Content Parser: > https://issues.apache.org/jira/projects/SLING/versions/12341009 > > We solved 3 issues in this release of Sling Query: > https://issues.apache.org/jira/projects/SLING/versions/12341713 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1897/ > > You can use this UNIX script to download the release and verify the > signatures: > https://gitbox.apache.org/repos/asf?p=sling-tooling- > release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > Usage: > sh check_staged_release.sh 1897 /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. > > - Jason > > -- > Jason >
[VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.0
Hi all, I'd like to make the very first release of the following components: org.apache.sling.feature 0.1.0 org.apache.sling.feature-io 0.1.0 org.apache.sling.feature-analyser 0.1.0 org.apache.sling.feature-modelconverter 0.1.0 As this is the very first release of these components, they are versioned at 0.1.0. For more information on these components, see: https://github.com/apache/sling-org-apache-sling-feature/blob/master/readme.md Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1899/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 1899 /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. Best regards, David Bosschaert
[jira] [Commented] (SLING-7651) POST to / creates nodes instead of setting properties
[
https://issues.apache.org/jira/browse/SLING-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464884#comment-16464884
]
Dan Klco commented on SLING-7651:
-
Thanks and sorry for causing the digging [~bdelacretaz]! I think the original
thought was to have the default URL be the Sling Starter page, but I'm not sure
why the mapping was required considering there was already a redirect. Changes
look good +1
> POST to / creates nodes instead of setting properties
> -
>
> Key: SLING-7651
> URL: https://issues.apache.org/jira/browse/SLING-7651
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Affects Versions: Servlets Post 2.3.24
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Major
>
> The changes that I had to make to {{PostToRootTest}} [1] indicate that the
> POST behavior has changed since sling10, at least on /.
> With sling10 this request sets a property {{x=y }}on the root node, while
> with the current trunk it creates a node under the root.
> {code:java}
> curl -u admin:admin -Fx=y http://localhost:8080/
> {code}
> It looks like the culprit is {{resource}} being null in
> {{AbstractCreateOperation.processCreate}}, in this code:
> {code:java}
> final String path = response.getPath();
> final Resource resource = resolver.getResource(path);
> {code}
> I'll investigate further - and the changes to {{PostToRootTest}} should be
> reverted once this is fixed.
> [1]
> [https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/3750eb05dc038544ba155d91de8991114077ac0c]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SLING-7640) Package pipe
[ https://issues.apache.org/jira/browse/SLING-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-7640. Resolution: Fixed Assignee: Nicolas Peltier Fix Version/s: pipes 2.1.0 only filter collection mode for now (most useful) > Package pipe > > > Key: SLING-7640 > URL: https://issues.apache.org/jira/browse/SLING-7640 > Project: Sling > Issue Type: Improvement > Components: Extensions >Affects Versions: pipes 2.0.2 >Reporter: Nicolas Peltier >Assignee: Nicolas Peltier >Priority: Major > Fix For: pipes 2.1.0 > > > à la Authorizable pipe, both reader & writer, ability to read apache > filevault package filters, or write some. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-7639) Enhance error message when additional script has errors
[
https://issues.apache.org/jira/browse/SLING-7639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7639:
---
Summary: Enhance error message when additional script has errors (was:
Enhance error message when additional script has erros)
> Enhance error message when additional script has errors
> ---
>
> Key: SLING-7639
> URL: https://issues.apache.org/jira/browse/SLING-7639
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: pipes 2.0.2
>Reporter: Nicolas Peltier
>Priority: Minor
>
> {{org.apache.sling.pipes.PipeBindings unable to execute ..blah.js}} is pretty
> useless...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SLING-7639) Enhance error message when additional script has errors
[
https://issues.apache.org/jira/browse/SLING-7639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier resolved SLING-7639.
Resolution: Fixed
Assignee: Nicolas Peltier
Fix Version/s: pipes 2.1.0
> Enhance error message when additional script has errors
> ---
>
> Key: SLING-7639
> URL: https://issues.apache.org/jira/browse/SLING-7639
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: pipes 2.0.2
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Minor
> Fix For: pipes 2.1.0
>
>
> {{org.apache.sling.pipes.PipeBindings unable to execute ..blah.js}} is pretty
> useless...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (SLING-7614) write pipe should allow expression in node names
[ https://issues.apache.org/jira/browse/SLING-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier reassigned SLING-7614: -- Assignee: Nicolas Peltier > write pipe should allow expression in node names > > > Key: SLING-7614 > URL: https://issues.apache.org/jira/browse/SLING-7614 > Project: Sling > Issue Type: Improvement > Components: Extensions >Affects Versions: pipes 2.0.2 >Reporter: Nicolas Peltier >Assignee: Nicolas Peltier >Priority: Major > Fix For: pipes 2.1.0 > > > when writing a structure, configuration should allow expressions in node names -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-7614) write pipe should allow expression in node names
[ https://issues.apache.org/jira/browse/SLING-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-7614. Resolution: Fixed > write pipe should allow expression in node names > > > Key: SLING-7614 > URL: https://issues.apache.org/jira/browse/SLING-7614 > Project: Sling > Issue Type: Improvement > Components: Extensions >Affects Versions: pipes 2.0.2 >Reporter: Nicolas Peltier >Assignee: Nicolas Peltier >Priority: Major > Fix For: pipes 2.1.0 > > > when writing a structure, configuration should allow expressions in node names -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[RESULT] [VOTE] Release Apache Sling JCR Content Parser version 1.2.6 and Apache Sling Query version 4.0.2
Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Robert Munteanu, Radu Cotescu, Dan Klco, David Bosschaert +1 (non binding): N/A I will promote the artifacts to the central Maven repository and update the news page. Can a PMC member please copy this release to the Sling dist directory. Thanks - Jason
[jira] [Closed] (SLING-7590) Content Loaders not respecting time zone for Dates
[ https://issues.apache.org/jira/browse/SLING-7590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason E Bailey closed SLING-7590. - > Content Loaders not respecting time zone for Dates > -- > > Key: SLING-7590 > URL: https://issues.apache.org/jira/browse/SLING-7590 > Project: Sling > Issue Type: Improvement >Reporter: Jason E Bailey >Assignee: Jason E Bailey >Priority: Major > Fix For: JCR ContentLoader 2.2.6, JCR Content Parser 1.2.6 > > Time Spent: 20m > Remaining Estimate: 0h > > When importing content, the JCR supports the setting of the time zone for a > jcr Date. However we currently have several processes that fail to set the > time zone correctly. > org.apache.sling.jcr.contentparser.impl.ParserHelper > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > org.apache.sling.servlets.post.impl.helper.DateParser > Take a String based time representation that includes a time offset and > convert it to Date that looses that information, before conversion to a > Calendar object. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-7185) Content Parser: Support for ISO-8601
[ https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason E Bailey closed SLING-7185. - > Content Parser: Support for ISO-8601 > > > Key: SLING-7185 > URL: https://issues.apache.org/jira/browse/SLING-7185 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Content Parser 1.2.4 >Reporter: Jason E Bailey >Assignee: Stefan Seifert >Priority: Minor > Fix For: JCR Content Parser 1.2.6 > > > The class org.apache.sling.jcr.contentparser.impl.ParserHelper defines the > Json format for a date to a defined value of ECMA_DATE_FORMAT. > Please support ISO-8601 as a date format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-7524) Sling Query - unique function does not not remove all duplicates
[ https://issues.apache.org/jira/browse/SLING-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason E Bailey closed SLING-7524. - > Sling Query - unique function does not not remove all duplicates > > > Key: SLING-7524 > URL: https://issues.apache.org/jira/browse/SLING-7524 > Project: Sling > Issue Type: Improvement > Components: Sling Query >Reporter: Jason E Bailey >Assignee: Jason E Bailey >Priority: Major > Fix For: Sling Query 4.0.2 > > > the function for unique does not match the contract a unique function usually > provides including JQuery, rather it's providing a sequential deduplicator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-7520) Sling Query - shortened URL goes to non apache site
[ https://issues.apache.org/jira/browse/SLING-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason E Bailey closed SLING-7520. - > Sling Query - shortened URL goes to non apache site > --- > > Key: SLING-7520 > URL: https://issues.apache.org/jira/browse/SLING-7520 > Project: Sling > Issue Type: Improvement > Components: Sling Query >Reporter: Jason E Bailey >Assignee: Jason E Bailey >Priority: Trivial > Fix For: Sling Query 4.0.2 > > > Warning is generated out of Sling Query which contains a shortened url that > links to the previous site before it was merged. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-7540) Sling Query - Iterator improvements
[ https://issues.apache.org/jira/browse/SLING-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason E Bailey closed SLING-7540. - > Sling Query - Iterator improvements > --- > > Key: SLING-7540 > URL: https://issues.apache.org/jira/browse/SLING-7540 > Project: Sling > Issue Type: Improvement > Components: Sling Query >Reporter: Jason E Bailey >Assignee: Jason E Bailey >Priority: Major > Fix For: Sling Query 4.0.2 > > > Cover some minor improvements to Iterators, specifically > AlternativeIterator - prevent iterator from continuing with iteration after > item to be returned has been discovered. > LastIterator - current design predetermines end item. Removes that and makes > it more "lazy" > SuppIterator - removes recursion -- This message was sent by Atlassian JIRA (v7.6.3#76005)
RE: [RESULT] [VOTE] Release Apache Sling JCR Content Parser version 1.2.6 and Apache Sling Query version 4.0.2
>Can a PMC member please copy this release to the Sling dist directory. done stefan
