[jira] [Commented] (SLING-6923) Update JSPC plugin to support java 1.8
[ https://issues.apache.org/jira/browse/SLING-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030492#comment-16030492 ] Tobias Bocanegra commented on SLING-6923: - I try to provide a patch... > Update JSPC plugin to support java 1.8 > -- > > Key: SLING-6923 > URL: https://issues.apache.org/jira/browse/SLING-6923 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: Maven JSPC Plugin 2.0.8 >Reporter: Tobias Bocanegra > > The current 2.0.8 version of the JSPC plugin only supports java version 1.6. > task: > - update code of JSPC plugin to also support 1.7 and 1.8 > - use latest org.apache.sling.scripting.jsp:2.3.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6923) Update JSPC plugin to support java 1.8
Tobias Bocanegra created SLING-6923: --- Summary: Update JSPC plugin to support java 1.8 Key: SLING-6923 URL: https://issues.apache.org/jira/browse/SLING-6923 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.8 Reporter: Tobias Bocanegra The current 2.0.8 version of the JSPC plugin only supports java version 1.6. task: - update code of JSPC plugin to also support 1.7 and 1.8 - use latest org.apache.sling.scripting.jsp:2.3.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6895) Remove commons.json from Content Distribution Kryo Serializer
[ https://issues.apache.org/jira/browse/SLING-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6895. --- Resolution: Fixed Done in r1796954. > Remove commons.json from Content Distribution Kryo Serializer > - > > Key: SLING-6895 > URL: https://issues.apache.org/jira/browse/SLING-6895 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6895) Remove commons.json from Content Distribution Kryo Serializer
[ https://issues.apache.org/jira/browse/SLING-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6895: - Assignee: Karl Pauls > Remove commons.json from Content Distribution Kryo Serializer > - > > Key: SLING-6895 > URL: https://issues.apache.org/jira/browse/SLING-6895 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6894) Remove commons.json from Content Distribution Avro Serializer
[ https://issues.apache.org/jira/browse/SLING-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6894. --- Resolution: Fixed Done in r1796953. > Remove commons.json from Content Distribution Avro Serializer > - > > Key: SLING-6894 > URL: https://issues.apache.org/jira/browse/SLING-6894 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6894) Remove commons.json from Content Distribution Avro Serializer
[ https://issues.apache.org/jira/browse/SLING-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6894: - Assignee: Karl Pauls > Remove commons.json from Content Distribution Avro Serializer > - > > Key: SLING-6894 > URL: https://issues.apache.org/jira/browse/SLING-6894 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6893) Remove commons.json from Content Distribution Integration Tests
[ https://issues.apache.org/jira/browse/SLING-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6893. --- Resolution: Fixed Done in r1796952. > Remove commons.json from Content Distribution Integration Tests > --- > > Key: SLING-6893 > URL: https://issues.apache.org/jira/browse/SLING-6893 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution Integration Tests >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6893) Remove commons.json from Content Distribution Integration Tests
[ https://issues.apache.org/jira/browse/SLING-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6893: - Assignee: Karl Pauls > Remove commons.json from Content Distribution Integration Tests > --- > > Key: SLING-6893 > URL: https://issues.apache.org/jira/browse/SLING-6893 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution Integration Tests >Reporter: Karl Pauls >Assignee: Karl Pauls > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6892) Remove commons.json from Content Distribution Core
[ https://issues.apache.org/jira/browse/SLING-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6892. --- Resolution: Fixed Done in r1796951. > Remove commons.json from Content Distribution Core > -- > > Key: SLING-6892 > URL: https://issues.apache.org/jira/browse/SLING-6892 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Affects Versions: Content Distribution Core 0.2.6 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Content Distribution Core 0.2.8 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6892) Remove commons.json from Content Distribution Core
[ https://issues.apache.org/jira/browse/SLING-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6892: - Assignee: Karl Pauls > Remove commons.json from Content Distribution Core > -- > > Key: SLING-6892 > URL: https://issues.apache.org/jira/browse/SLING-6892 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Affects Versions: Content Distribution Core 0.2.6 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Content Distribution Core 0.2.8 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6905) Remove commons.json from testing http clients
[ https://issues.apache.org/jira/browse/SLING-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6905: - Assignee: Karl Pauls > Remove commons.json from testing http clients > - > > Key: SLING-6905 > URL: https://issues.apache.org/jira/browse/SLING-6905 > Project: Sling > Issue Type: Sub-task > Components: Apache Sling Testing Clients >Affects Versions: Apache Sling Testing Clients 1.0.1 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: Apache Sling Testing Clients 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6889) Retire commons.json to the attic
[ https://issues.apache.org/jira/browse/SLING-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030114#comment-16030114 ] Karl Pauls commented on SLING-6889: --- I called for a vote on this on the dev list. > Retire commons.json to the attic > > > Key: SLING-6889 > URL: https://issues.apache.org/jira/browse/SLING-6889 > Project: Sling > Issue Type: Sub-task >Reporter: Karl Pauls >Assignee: Karl Pauls > > When we are done using it in the trunk we should retire commons.json to the > attic (as we can't release it anymore anyways). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6891) Retire xss.compat to the attic
[ https://issues.apache.org/jira/browse/SLING-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030112#comment-16030112 ] Karl Pauls commented on SLING-6891: --- I called for a vote on this on the dev list. > Retire xss.compat to the attic > -- > > Key: SLING-6891 > URL: https://issues.apache.org/jira/browse/SLING-6891 > Project: Sling > Issue Type: Sub-task > Components: XSS Protection API >Affects Versions: XSS Protection API Compat 1.1.0 >Reporter: Karl Pauls >Assignee: Karl Pauls > > We should probably retire the xss.compat bundle to the attic as we can't > release it anymore anyhow. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
RE: [VOTE] Retire o.a.s.xss.compat module to the Sling Attic
+1
[jira] [Updated] (SLING-6889) Retire commons.json to the attic
[ https://issues.apache.org/jira/browse/SLING-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-6889: -- Description: When we are done using it in the trunk we should retire commons.json to the attic (as we can't release it anymore anyways). was: When we are done using it in the trunk we should retire commons.json to the attic (as we can't release it anymore anyways). I'll call for a vote on the dev list when the rest of SLING-6887 is done. > Retire commons.json to the attic > > > Key: SLING-6889 > URL: https://issues.apache.org/jira/browse/SLING-6889 > Project: Sling > Issue Type: Sub-task >Reporter: Karl Pauls >Assignee: Karl Pauls > > When we are done using it in the trunk we should retire commons.json to the > attic (as we can't release it anymore anyways). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
RE: [VOTE] Retire o.a.s.commons.json module to the Sling Attic
+1
[jira] [Assigned] (SLING-6891) Retire xss.compat to the attic
[ https://issues.apache.org/jira/browse/SLING-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6891: - Assignee: Karl Pauls > Retire xss.compat to the attic > -- > > Key: SLING-6891 > URL: https://issues.apache.org/jira/browse/SLING-6891 > Project: Sling > Issue Type: Sub-task > Components: XSS Protection API >Affects Versions: XSS Protection API Compat 1.1.0 >Reporter: Karl Pauls >Assignee: Karl Pauls > > We should probably retire the xss.compat bundle to the attic as we can't > release it anymore anyhow. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[VOTE] Retire o.a.s.xss.compat module to the Sling Attic
Hi, I'd like to retire our bundles/extensions/xss.compat module by moving it under https://svn.apache.org/repos/asf/sling/attic/ As that module is there only to support the old api using commons.json we can't release any new versions of it anyways, so we might as well retire it now. Please vote to accept this retirement, this majority vote is open for at least 72 hours. Here's my +1. regards, Karl -- Karl Pauls karlpa...@gmail.com
[VOTE] Retire o.a.s.commons.json module to the Sling Attic
Hi, I'd like to retire our bundles/commons/json module by moving it under https://svn.apache.org/repos/asf/sling/attic/ As should be clear by now, we can't release any new versions of it anyways, so we might as well retire it now. Please vote to accept this retirement, this majority vote is open for at least 72 hours. Here's my +1. regards, Karl -- Karl Pauls karlpa...@gmail.com
[jira] [Resolved] (SLING-6888) Remove commons.json and org.json excludes
[ https://issues.apache.org/jira/browse/SLING-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6888. --- Resolution: Fixed I removed the excludes. > Remove commons.json and org.json excludes > - > > Key: SLING-6888 > URL: https://issues.apache.org/jira/browse/SLING-6888 > Project: Sling > Issue Type: Sub-task >Reporter: Karl Pauls >Assignee: Karl Pauls > > In a couple of places we have now unnecessary excludes that can be removed > when we stopped using commons.json/org.json. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6890) Remove usage of o.a.jackrabbit.commons.json from i18n
[ https://issues.apache.org/jira/browse/SLING-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6890. --- Resolution: Invalid [~alexander.klimetschek] - Ha! You are correct. I mistakingly assumed that commons.json from jackrabbit was yet another instance of org.json. Turns out it isn't. Nice, that helps. Thanks - I'll close this one as invalid. > Remove usage of o.a.jackrabbit.commons.json from i18n > - > > Key: SLING-6890 > URL: https://issues.apache.org/jira/browse/SLING-6890 > Project: Sling > Issue Type: Sub-task > Components: i18n >Affects Versions: i18n 2.5.8 >Reporter: Karl Pauls > Fix For: i18n 2.5.10 > > > It looks like i18n is using some org.json this time from > o.a.jackrabbit.commons.json. We'll have to replace that too I would guess. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (SLING-6890) Remove usage of o.a.jackrabbit.commons.json from i18n
[ https://issues.apache.org/jira/browse/SLING-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-6890. - > Remove usage of o.a.jackrabbit.commons.json from i18n > - > > Key: SLING-6890 > URL: https://issues.apache.org/jira/browse/SLING-6890 > Project: Sling > Issue Type: Sub-task > Components: i18n >Affects Versions: i18n 2.5.8 >Reporter: Karl Pauls > Fix For: i18n 2.5.10 > > > It looks like i18n is using some org.json this time from > o.a.jackrabbit.commons.json. We'll have to replace that too I would guess. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6890) Remove usage of o.a.jackrabbit.commons.json from i18n
[ https://issues.apache.org/jira/browse/SLING-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030046#comment-16030046 ] Alexander Klimetschek commented on SLING-6890: -- Where did you saw it? The code itself has no direct import of {{org.json}}. > Remove usage of o.a.jackrabbit.commons.json from i18n > - > > Key: SLING-6890 > URL: https://issues.apache.org/jira/browse/SLING-6890 > Project: Sling > Issue Type: Sub-task > Components: i18n >Affects Versions: i18n 2.5.8 >Reporter: Karl Pauls > Fix For: i18n 2.5.10 > > > It looks like i18n is using some org.json this time from > o.a.jackrabbit.commons.json. We'll have to replace that too I would guess. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6921) Slingbucks2: HTL Rewrite
[ https://issues.apache.org/jira/browse/SLING-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1602#comment-1602 ] Stefan Seifert commented on SLING-6921: --- bq. For the time being that plugin must be downloaded... it's on maven central since yesterday! http://repo1.maven.org/maven2/io/wcm/maven/plugins/wcmio-content-package-maven-plugin/1.5.0/ > Slingbucks2: HTL Rewrite > > > Key: SLING-6921 > URL: https://issues.apache.org/jira/browse/SLING-6921 > Project: Sling > Issue Type: Improvement > Components: Samples >Reporter: Andreas Schaefer > Labels: Slingbucks > > Create a PR: https://github.com/apache/sling/pull/236 for Headwire's > Slingucks2 rewrite using HTL, System User and JCR Content Package using the > brand new WCMIO Content Package Plugin 1.5.0. > For the time being that plugin must be downloaded from > https://github.com/wcm-io/wcm-io-tooling/releases/tag/wcmio-content-package-maven-plugin-1.5.0 > and installed locally. > Then the package ui.apps.user must be installed once before the rest with the > profile 'autoInstallUserPackage' in order to install the Service User used to > copy the order from the public to the private branch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6922) New Sling Archetypes for Content Packages
Andreas Schaefer created SLING-6922: --- Summary: New Sling Archetypes for Content Packages Key: SLING-6922 URL: https://issues.apache.org/jira/browse/SLING-6922 Project: Sling Issue Type: Improvement Components: Tooling Reporter: Andreas Schaefer Created a PR for two new Sling Archetypes: https://github.com/apache/sling/pull/237 Both Archetypes are creating a project using Content Packages. The 'project' provides the traditional core / ui.apps where core is embedded into the ui.apps package. The 'project-all' is creating a wrapper 'all' content package that contains both the core bundle and the ui.apps package. The generated projects require WCMIO Content Package Plugin 1.5.0 which needs to be download and installed locally first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] sling pull request #237: Feature/sling project archetypes
GitHub user schaefa opened a pull request: https://github.com/apache/sling/pull/237 Feature/sling project archetypes Created two archetypes with a service core and a content package ui.apps. The 'project' is deployed through the ui.apps module whereas the 'project-all' is using a wrapper content package which contains the core and ui.apps. Both archetypes come with shadow folders both for the core and ui.apps with example code. The code is generated in a way that it can be easily copied over to the active module but if not needed it can be deleted w/o any side effects. You can merge this pull request into a Git repository by running: $ git pull https://github.com/headwirecom/sling feature/sling-project-archetypes Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/237.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #237 commit 8247f6cb2a809eb9777848d4e6fce9588333b2f9 Author: Andreas SchaeferDate: 2017-04-05T15:44:26Z Added Sling Maven Project (core / ui.apps) and All Project (core / ui.apps / all) Archetypes Signed-off-by: Andreas Schaefer commit d90da240f7fe695485c8e82d9c2cdd8a4381eaa3 Author: Andreas Schaefer Date: 2017-05-01T17:11:46Z Adjusted the Maven Bundle Plugin version and enforced Maven 3.1.0 Signed-off-by: Andreas Schaefer commit 9be68e91820ae28159072b80b18dc2ddc671e42b Author: Andreas Schaefer Date: 2017-05-01T17:59:46Z Extracted all Plugin Versions and updated to the latest Signed-off-by: Andreas Schaefer commit a43e4867ace1ed28ae1854df47bc09710d2f50f4 Author: Andreas Schaefer Date: 2017-05-11T00:30:45Z Migrated our Archetypes to using the WCMIO maven plugins and remove Adobe Repo and Plugins Signed-off-by: Andreas Schaefer commit bc6847ef5927a4d0f535c1979ff721c6091778d5 Author: Andreas Schaefer Date: 2017-05-30T18:15:46Z Merge branch 'trunk' into feature/sling-project-archetypes commit 044a2fca6bd13d41efafceba541e1cb5dade710b Author: Andreas Schaefer Date: 2017-05-30T18:20:14Z Upgraded to official WCMIO release, added the integration script and updated the Readme files Signed-off-by: Andreas Schaefer --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (SLING-6921) Slingbucks2: HTL Rewrite
Andreas Schaefer created SLING-6921: --- Summary: Slingbucks2: HTL Rewrite Key: SLING-6921 URL: https://issues.apache.org/jira/browse/SLING-6921 Project: Sling Issue Type: Improvement Components: Samples Reporter: Andreas Schaefer Create a PR: https://github.com/apache/sling/pull/236 for Headwire's Slingucks2 rewrite using HTL, System User and JCR Content Package using the brand new WCMIO Content Package Plugin 1.5.0. For the time being that plugin must be downloaded from https://github.com/wcm-io/wcm-io-tooling/releases/tag/wcmio-content-package-maven-plugin-1.5.0 and installed locally. Then the package ui.apps.user must be installed once before the rest with the profile 'autoInstallUserPackage' in order to install the Service User used to copy the order from the public to the private branch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] sling pull request #236: Feature/slingbucks2
GitHub user schaefa opened a pull request: https://github.com/apache/sling/pull/236 Feature/slingbucks2 Rewrite of the Slingbucks sample with HTL, service user and JCR Content Package using the new WCMIO Content Package Plugin (1.5.0). For the time being the WCMIO Content Package must be download from https://github.com/wcm-io/wcm-io-tooling/releases/tag/wcmio-content-package-maven-plugin-1.5.0 and installed locally until the plugin is available on Maven Central. You can merge this pull request into a Git repository by running: $ git pull https://github.com/headwirecom/sling feature/slingbucks2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/236.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #236 commit ef73791a2ae67c52f1e0b3fd4fa47e7ac4c64ada Author: Andreas SchaeferDate: 2017-04-01T18:28:01Z Added Slingbuck 2 Sample Slingbucks 2 is a rewrite of Slingbucks using HTL / Sling Model instead of ESP and a JCR Content Package instead of a Bundle Content for easier IDE Tooling. It also has the apps and content folder named differntly to make it easier for the readers to know when we are refereing to /apps and when to /content. Signed-off-by: Andreas Schaefer commit 7355c86c69780958429496af10afe5672af9e339 Author: Andreas Schaefer Date: 2017-04-07T22:57:57Z Fixed an issue with the instlalation of the Core and added the System User for the Session Signed-off-by: Andreas Schaefer commit a2b3233b52cf26e19519758e7cea73edbbe69b9d Author: Andreas Schaefer Date: 2017-04-24T18:16:02Z Adjusted the Slingbucks2 Sample to work without any Adobe Maven Plugins Signed-off-by: Andreas Schaefer commit 7211873a3ab537297939a45296affb4dc51c12a9 Author: Andreas Schaefer Date: 2017-05-10T23:09:38Z Updated the Slingbucks 2 Sample to use WCMIO content packager and removed Adobe repo and plugins Signed-off-by: Andreas Schaefer commit 0d82374571521dceec16771e88d90ce8aafd6ca4 Author: Andreas Schaefer Date: 2017-05-30T16:44:49Z Updated to WCMIO Content Package Plugin 1.5.0 Signed-off-by: Andreas Schaefer commit c82cb571d2c6c622d24cfc9f49ea3bf051075da8 Author: Andreas Schaefer Date: 2017-05-30T16:45:40Z Merge branch 'trunk' into feature/slingbucks2 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [VOTE] Release Apache Sling JCR Content Parser 1.2.2, JCR ContentLoader 2.2.4, File System Resource Provider 2.1.4, File System Resource Provider 1.4.4, Maven Sling Plugin 2.3.0
On Tue, 2017-05-30 at 08:58 +, Stefan Seifert wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part
Re: [VOTE] Release Apache Sling JCR Content Parser 1.2.2, JCR ContentLoader 2.2.4, File System Resource Provider 2.1.4, File System Resource Provider 1.4.4, Maven Sling Plugin 2.3.0
+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
RE: [VOTE] Release Apache Sling JCR Content Parser 1.2.2, JCR ContentLoader 2.2.4, File System Resource Provider 2.1.4, File System Resource Provider 1.4.4, Maven Sling Plugin 2.3.0
+1
[VOTE] Release Apache Sling JCR Content Parser 1.2.2, JCR ContentLoader 2.2.4, File System Resource Provider 2.1.4, File System Resource Provider 1.4.4, Maven Sling Plugin 2.3.0
Hi, Apache Sling JCR Content Parser 1.2.2 (3 issues) https://issues.apache.org/jira/browse/SLING/fixforversion/12340620 Apache Sling JCR ContentLoader 2.2.4 (1 issue) https://issues.apache.org/jira/browse/SLING/fixforversion/12340616 Apache Sling File System Resource Provider 2.1.4 (1 issue) https://issues.apache.org/jira/browse/SLING/fixforversion/12340621 Apache Sling File System Resource Provider 1.4.4 (1 issue) https://issues.apache.org/jira/browse/SLING/fixforversion/12340622 Apache Sling Maven Sling Plugin 2.3.0 (2 issues) https://issues.apache.org/jira/browse/SLING/fixforversion/12340623 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1736/ 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 1736 /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
[jira] [Commented] (SLING-6905) Remove commons.json from testing http clients
[ https://issues.apache.org/jira/browse/SLING-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029171#comment-16029171 ] ASF GitHub Bot commented on SLING-6905: --- Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/235 > Remove commons.json from testing http clients > - > > Key: SLING-6905 > URL: https://issues.apache.org/jira/browse/SLING-6905 > Project: Sling > Issue Type: Sub-task > Components: Apache Sling Testing Clients >Affects Versions: Apache Sling Testing Clients 1.0.1 >Reporter: Karl Pauls > Fix For: Apache Sling Testing Clients 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] sling pull request #235: SLING-6905
Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/235 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (SLING-6905) Remove commons.json from testing http clients
[ https://issues.apache.org/jira/browse/SLING-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-6905. --- Resolution: Fixed Great - Thanks a lot! I applied your patch in r1796802. > Remove commons.json from testing http clients > - > > Key: SLING-6905 > URL: https://issues.apache.org/jira/browse/SLING-6905 > Project: Sling > Issue Type: Sub-task > Components: Apache Sling Testing Clients >Affects Versions: Apache Sling Testing Clients 1.0.1 >Reporter: Karl Pauls > Fix For: Apache Sling Testing Clients 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6905) Remove commons.json from testing http clients
[ https://issues.apache.org/jira/browse/SLING-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028851#comment-16028851 ] Valentin Olteanu commented on SLING-6905: - The attached patch replaces commons.json with jackson. I think that's the safest option, since jackson is already exposed in the API, so changing it to javax.json would impact the users. > Remove commons.json from testing http clients > - > > Key: SLING-6905 > URL: https://issues.apache.org/jira/browse/SLING-6905 > Project: Sling > Issue Type: Sub-task > Components: Apache Sling Testing Clients >Affects Versions: Apache Sling Testing Clients 1.0.1 >Reporter: Karl Pauls > Fix For: Apache Sling Testing Clients 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6905) Remove commons.json from testing http clients
[ https://issues.apache.org/jira/browse/SLING-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028845#comment-16028845 ] ASF GitHub Bot commented on SLING-6905: --- GitHub user volteanu opened a pull request: https://github.com/apache/sling/pull/235 SLING-6905 You can merge this pull request into a Git repository by running: $ git pull https://github.com/volteanu/sling SLING-6905 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/235.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #235 commit b2316b76b0bfedb376a9b061b518f9cbeb9bea6f Author: volteanuDate: 2017-05-30T08:30:46Z SLING-6905: Remove commons.json from testing http clients > Remove commons.json from testing http clients > - > > Key: SLING-6905 > URL: https://issues.apache.org/jira/browse/SLING-6905 > Project: Sling > Issue Type: Sub-task > Components: Apache Sling Testing Clients >Affects Versions: Apache Sling Testing Clients 1.0.1 >Reporter: Karl Pauls > Fix For: Apache Sling Testing Clients 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] sling pull request #235: SLING-6905
GitHub user volteanu opened a pull request: https://github.com/apache/sling/pull/235 SLING-6905 You can merge this pull request into a Git repository by running: $ git pull https://github.com/volteanu/sling SLING-6905 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/235.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #235 commit b2316b76b0bfedb376a9b061b518f9cbeb9bea6f Author: volteanuDate: 2017-05-30T08:30:46Z SLING-6905: Remove commons.json from testing http clients --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (SLING-3535) reduce duplicated code in content loader
[ https://issues.apache.org/jira/browse/SLING-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-3535: -- Fix Version/s: (was: JCR ContentLoader 2.2.4) JCR ContentLoader 2.2.6 > reduce duplicated code in content loader > > > Key: SLING-3535 > URL: https://issues.apache.org/jira/browse/SLING-3535 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: JCR ContentLoader 2.2.6 > > > e.g. {{DefaultContentImporter}} and {{Loader}} can share more code in > {{BaseImportLoader}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-3619: -- Fix Version/s: (was: JCR ContentLoader 2.2.4) JCR ContentLoader 2.2.6 > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR ContentLoader 2.2.6 > > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-3533) improve error handling and logging in content loader
[ https://issues.apache.org/jira/browse/SLING-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-3533: -- Fix Version/s: (was: JCR ContentLoader 2.2.4) JCR ContentLoader 2.2.6 > improve error handling and logging in content loader > > > Key: SLING-3533 > URL: https://issues.apache.org/jira/browse/SLING-3533 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: JCR ContentLoader 2.2.6 > > > handle errors more appropriate and use proper log levels -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-3534) separate node name and content type in content loader
[ https://issues.apache.org/jira/browse/SLING-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-3534. --- Resolution: Fixed Fix Version/s: (was: JCR ContentLoader 2.2.4) JCR ContentLoader 2.2.0 according to comments above this was already solved in version 2.2.0 > separate node name and content type in content loader > - > > Key: SLING-3534 > URL: https://issues.apache.org/jira/browse/SLING-3534 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: JCR ContentLoader 2.2.0 > > > extend API (node name and content type are currently taken from file name) -- This message was sent by Atlassian JIRA (v6.3.15#6346)