[jira] [Resolved] (SLING-6920) Maven Sling Plugin: Optional activate json tick parse support for validate goal

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-6920.
---
Resolution: Fixed

Completed: At revision: 1796677  


> Maven Sling Plugin: Optional activate json tick parse support for validate 
> goal
> ---
>
> Key: SLING-6920
> URL: https://issues.apache.org/jira/browse/SLING-6920
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions: Maven Sling Plugin 2.2.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: Maven Sling Plugin 2.3.0
>
>
> the support for parsing tick quotes in JSON should be disabled by default, 
> and enabled only if a maven plugin parameter is set to true explicitly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6920) Maven Sling Plugin: Optional activate json tick parse support for validate goal

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6920:
-

 Summary: Maven Sling Plugin: Optional activate json tick parse 
support for validate goal
 Key: SLING-6920
 URL: https://issues.apache.org/jira/browse/SLING-6920
 Project: Sling
  Issue Type: Improvement
  Components: Maven Plugins and Archetypes
Affects Versions: Maven Sling Plugin 2.2.2
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: Maven Sling Plugin 2.3.0


the support for parsing tick quotes in JSON should be disabled by default, and 
enabled only if a maven plugin parameter is set to true explicitly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6919) JCR Content Parser: Do no enable JSON tick parsing by default

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-6919.
---
Resolution: Fixed

Completed: At revision: 1796676  


> JCR Content Parser: Do no enable JSON tick parsing by default
> -
>
> Key: SLING-6919
> URL: https://issues.apache.org/jira/browse/SLING-6919
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Content Parser 1.2.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: JCR Content Parser 1.2.2
>
>
> the JSON tick quote parse support should be disabled by default.
> it can be enabled via JsonParserFeature enumset.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6919) JCR Content Parser: Do no enable JSON tick parsing by default

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6919:
-

 Summary: JCR Content Parser: Do no enable JSON tick parsing by 
default
 Key: SLING-6919
 URL: https://issues.apache.org/jira/browse/SLING-6919
 Project: Sling
  Issue Type: Improvement
  Components: JCR
Affects Versions: JCR Content Parser 1.2.0
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Priority: Minor
 Fix For: JCR Content Parser 1.2.2


the JSON tick quote parse support should be disabled by default.
it can be enabled via JsonParserFeature enumset.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6918) FSResource: Update to latest JCR ContentParser

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-6918.
---
Resolution: Fixed

rev. 1796612  (2.x)
rev. 1796027  (1.x)

updated to jcr content parser 1.2.2

> FSResource: Update to latest JCR ContentParser
> --
>
> Key: SLING-6918
> URL: https://issues.apache.org/jira/browse/SLING-6918
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: File System Resource Provider 1.4.2, File System 
> Resource Provider 2.1.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Resource Provider 1.4.4, File System 
> Resource Provider 2.1.4
>
>
> JCR content parser 1.2.0 was buggy concering the JSON preprocessing when tick 
> parsing was activated - we should update to latest version.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6918) FSResource: Update to latest JCR ContentParser

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6918:
-

 Summary: FSResource: Update to latest JCR ContentParser
 Key: SLING-6918
 URL: https://issues.apache.org/jira/browse/SLING-6918
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Affects Versions: File System Resource Provider 2.1.2, File System Resource 
Provider 1.4.2
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: File System Resource Provider 1.4.4, File System Resource 
Provider 2.1.4


JCR content parser 1.2.0 was buggy concering the JSON preprocessing when tick 
parsing was activated - we should update to latest version.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6917) Maven Sling Plugin: Deploy fsresource bundles on fsmount goal if required

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-6917.
---
Resolution: Fixed

Completed: At revision: 1796657  


> Maven Sling Plugin: Deploy fsresource bundles on fsmount goal if required
> -
>
> Key: SLING-6917
> URL: https://issues.apache.org/jira/browse/SLING-6917
> Project: Sling
>  Issue Type: New Feature
>  Components: Maven Plugins and Archetypes
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: Maven Sling Plugin 2.3.0
>
>
> currently only OSGi configuration is created on the "fsmount" goal. if the 
> fsresource bundle is not installed this has no effect. on freshly-installed 
> instances this bundles is often not present.
> * the goal "fsmount" should automatically deploy the bundles if it is not 
> deployed already (configurable, activated by default).
> * the minimum version of fsresource bundle can be configured via plugin 
> property - if the bundle is not deployed or too old this version is deployed 
> to the instance



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6917) Maven Sling Plugin: Deploy fsresource bundles on fsmount goal if required

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6917:
-

 Summary: Maven Sling Plugin: Deploy fsresource bundles on fsmount 
goal if required
 Key: SLING-6917
 URL: https://issues.apache.org/jira/browse/SLING-6917
 Project: Sling
  Issue Type: New Feature
  Components: Maven Plugins and Archetypes
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: Maven Sling Plugin 2.3.0


currently only OSGi configuration is created on the "fsmount" goal. if the 
fsresource bundle is not installed this has no effect. on freshly-installed 
instances this bundles is often not present.

* the goal "fsmount" should automatically deploy the bundles if it is not 
deployed already (configurable, activated by default).
* the minimum version of fsresource bundle can be configured via plugin 
property - if the bundle is not deployed or too old this version is deployed to 
the instance



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6905) Remove commons.json from testing http clients

[Karl Pauls (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028468#comment-16028468
 ] 

Karl Pauls commented on SLING-6905:
---

Hi [~volteanu], strictly speaking, this is only about org.json and derived code 
(i.e., commons.json). In general, we are trying to use the 
o.a.felix.util.json.JSONWriter embedded where a bundle is only writing out 
simple json and javax.json otherwise. Towards that end, we created a new 
o.a.s.commons.johnzon bundle that provides javax.json.

In other words, it depends. We can keep the jackson code and we might even 
replace the org.json/commons.json usage with jackson if that makes sense but if 
it is not too much effort it might be nicer to switch to javax.json - just to 
get the number of json impls we use down. 

At any rate, a patch would be great!

> 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] [Resolved] (SLING-6916) JCR Content Parser: Tick parsing fails when string contains escaped escaped character

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-6916.
---
Resolution: Fixed

Completed: At revision: 1796649  


> JCR Content Parser: Tick parsing fails when string contains escaped escaped 
> character
> -
>
> Key: SLING-6916
> URL: https://issues.apache.org/jira/browse/SLING-6916
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Content Parser 1.2.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: JCR Content Parser 1.2.2
>
>
> when a JSON string with tickt parsing contains "\\" (escaped backslash) this 
> is replaced with "\" which leads to invalid JSON.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6916) JCR Content Parser: Tick parsing fails when string contains escaped escaped character

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6916:
-

 Summary: JCR Content Parser: Tick parsing fails when string 
contains escaped escaped character
 Key: SLING-6916
 URL: https://issues.apache.org/jira/browse/SLING-6916
 Project: Sling
  Issue Type: Bug
  Components: JCR
Affects Versions: JCR Content Parser 1.2.0
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: JCR Content Parser 1.2.2


when a JSON string with tickt parsing contains "\\" (escaped backslash) this is 
replaced with "\" which leads to invalid JSON.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6905) Remove commons.json from testing http clients

[Valentin Olteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028448#comment-16028448
 ] 

Valentin Olteanu commented on SLING-6905:
-

[~karlpauls], sling testing clients are using both {{commons.json}} and 
{{org.codehaus.jackson}}. Is this issue related to {{commons.json}} only, or is 
it also about removing {{org.codehaus.jackson}}?

BTW, I can provide a patch for it, if you need help.

> 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)

Re: [VOTE] Release Apache Sling SLF4J Implementation (Logback) 5.0.2

[Carsten Ziegeler]

+1

 

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling SLF4J Implementation (Logback) 5.0.2

[Chetan Mehrotra]

+1
Chetan Mehrotra


On Mon, May 29, 2017 at 3:50 PM, Robert Munteanu  wrote:
> Hi,
>
> We solved 2 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12338587
>
> There are still some outstanding issues:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12340651
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1733
>
> 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 1733 /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.

Re: [VOTE] Release Apache Sling SLF4J Implementation (Logback) 5.0.2

[Stefan Egli]

+1

Cheers,
Stefan

On 29/05/17 12:20, "Robert Munteanu"  wrote:

>Hi,
>
>We solved 2 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12338587
>
>There are still some outstanding issues:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12340651
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1733
>
>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 1733 /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.

[jira] [Resolved] (SLING-6915) JCR Content Parser: Tick parsing fails when comment contains tick character

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-6915.
---
Resolution: Fixed

Completed: At revision: 1796611  


> JCR Content Parser: Tick parsing fails when comment contains tick character
> ---
>
> Key: SLING-6915
> URL: https://issues.apache.org/jira/browse/SLING-6915
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Content Parser 1.2.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: JCR Content Parser 1.2.2
>
>
> when both non-standard JSON options (support comments, support tick symbols 
> in JSON) are activated parsing may fail when the comment text contains a tick.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Sling SLF4J Implementation (Logback) 5.0.2

[Robert Munteanu]

On Mon, 2017-05-29 at 13:20 +0300, Robert Munteanu wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

[VOTE] Release Apache Sling SLF4J Implementation (Logback) 5.0.2

[Robert Munteanu]

Hi,

We solved 2 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12338587

There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING/fixforversion/12340651

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1733

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 1733 /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.

[jira] [Created] (SLING-6915) JCR Content Parser: Tick parsing fails when comment contains tick character

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6915:
-

 Summary: JCR Content Parser: Tick parsing fails when comment 
contains tick character
 Key: SLING-6915
 URL: https://issues.apache.org/jira/browse/SLING-6915
 Project: Sling
  Issue Type: Bug
  Components: JCR
Affects Versions: JCR Content Parser 1.2.0
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: JCR Content Parser 1.2.2


when both non-standard JSON options (support comments, support tick symbols in 
JSON) are activated parsing may fail when the comment text contains a tick.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6044) Conflicting LogManager and LogWriter if using the same logfile

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-6044:
---
Fix Version/s: (was: Commons Log 5.0.2)
   Commons Log 5.0.4

> Conflicting LogManager and LogWriter if using the same logfile
> --
>
> Key: SLING-6044
> URL: https://issues.apache.org/jira/browse/SLING-6044
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons Log 4.0.2
>Reporter: Jörg Hoh
>Assignee: Chetan Mehrotra
> Fix For: Commons Log 5.0.4
>
> Attachments: SLING-6044-multiple-loggers-writers.jpg
>
>
> When you have a logmanager and a logwriter pointing to the same file, you get 
> an exception like this:
> {panel}
> 07.09.2016 17:33:31.126 *ERROR* [] CM Configuration Updater (Update: 
> pid=org.apache.sling.commons.log.LogManager) org.apache.felix.configadmin 
> Service [org.apache.felix.cm.ConfigurationAdmin,9, 
> [org.osgi.service.cm.ConfigurationAdmin]] 
> [org.osgi.service.cm.ManagedService, id=10, 
> bundle=7/slinginstall:c:\java\IBM\LibertyProfile\usr\servers\aem-1\sling\_\launchpad\startup\1\org.apache.sling.commons.log-4.0.0.jar]:
>  Updating property org.apache.sling.commons.log.file of configuration 
> org.apache.sling.commons.log.LogManager caused a problem: LogFile 
> C:\java\IBM\LibertyProfile\usr\servers\aem-1\aemlogs\logs\error.log already 
> configured by configuration 
> org.apache.sling.commons.log.LogManager.factory.writer.8402a603-bdef-4404-9ff1-0e0f592578af
>  (org.osgi.service.cm.ConfigurationException: 
> org.apache.sling.commons.log.file : LogFile 
> C:\java\IBM\LibertyProfile\usr\servers\aem-1\aemlogs\logs\error.log already 
> configured by configuration 
> org.apache.sling.commons.log.LogManager.factory.writer.8402a603-bdef-4404-9ff1-0e0f592578af)
>  
> org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.file 
> : LogFile C:\java\IBM\LibertyProfile\usr\servers\aem-1\aemlogs\logs\error.log 
> already configured by configuration 
> org.apache.sling.commons.log.LogManager.factory.writer.8402a603-bdef-4404-9ff1-0e0f592578af
>  
>         at 
> org.apache.sling.commons.log.logback.internal.config.GlobalConfigurator.updated(GlobalConfigurator.java:32)
>         at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:148)
>  
>         at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:81)
>  
>         at 
> org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1744)
>  
>         at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103) 
>         at java.lang.Thread.run(Thread.java:744) 
> Caused by: 
> org.apache.sling.commons.log.logback.internal.config.ConfigurationException: 
>         at 
> org.apache.sling.commons.log.logback.internal.LogConfigManager.updateLogWriter(LogConfigManager.java:398)
>  
>         at 
> org.apache.sling.commons.log.logback.internal.LogConfigManager.updateGlobalConfiguration(LogConfigManager.java:327)
>  
>         at 
> org.apache.sling.commons.log.logback.internal.config.GlobalConfigurator.updated(GlobalConfigurator.java:30)
>  
>         ... 5 common frames omitted
> {panel}
> Obviously the Logmanager internally provides a Logwriter, so these conflict. 
> This should be documented.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6577) StringIndexOutOfBoundsException in Sling Log Web Console when creating new logger with absolute file name

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-6577:
---
Fix Version/s: (was: Commons Log 5.0.2)
   Commons Log 5.0.4

> StringIndexOutOfBoundsException in Sling Log Web Console when creating new 
> logger with absolute file name
> -
>
> Key: SLING-6577
> URL: https://issues.apache.org/jira/browse/SLING-6577
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Log 5.0.0
>Reporter: Konrad Windszus
> Fix For: Commons Log 5.0.4
>
>
> After adding a new logger via the web console exposed at 
> {{/system/console/slinglog}} with an absolute filename (one starting with 
> "/"), the following exception is thrown 
> {code}
> 28.02.2017 16:47:31.300 *ERROR* [qtp455076072-280] 
> org.apache.felix.http.jetty Exception while processing request to 
> /system/console/slinglog (java.lang.StringIndexOutOfBoundsException: String 
> index out of range: -42)
> java.lang.StringIndexOutOfBoundsException: String index out of range: -42
>   at java.lang.String.substring(String.java:1931)
>   at 
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.getPath(SlingLogPanel.java:791)
>   at 
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.appendOsgiConfiguredLoggerData(SlingLogPanel.java:221)
>   at 
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.render(SlingLogPanel.java:110)
>   at 
> org.apache.sling.commons.log.webconsole.internal.LogWebConsolePlugin.renderContent(LogWebConsolePlugin.java:79)
>   at 
> org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
> {code}
> This is related to the exception being mentioned in SLING-6482.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6914) Remove commons.json from bundles/extensions/validation/examples

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6914:
-

 Summary: Remove commons.json from 
bundles/extensions/validation/examples
 Key: SLING-6914
 URL: https://issues.apache.org/jira/browse/SLING-6914
 Project: Sling
  Issue Type: Sub-task
Reporter: Karl Pauls






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6913) Remove commons.json from validation/test-services

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6913:
-

 Summary: Remove commons.json from validation/test-services
 Key: SLING-6913
 URL: https://issues.apache.org/jira/browse/SLING-6913
 Project: Sling
  Issue Type: Sub-task
  Components: Validation
Reporter: Karl Pauls






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6912) Remove commons.json from bundles/extensions/models/integration-tests/

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6912:
-

 Summary: Remove commons.json from 
bundles/extensions/models/integration-tests/
 Key: SLING-6912
 URL: https://issues.apache.org/jira/browse/SLING-6912
 Project: Sling
  Issue Type: Sub-task
Reporter: Karl Pauls






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6911) Remove commons.json from ./contrib/commons/mom/jobs/it

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6911:
-

 Summary: Remove commons.json from ./contrib/commons/mom/jobs/it
 Key: SLING-6911
 URL: https://issues.apache.org/jira/browse/SLING-6911
 Project: Sling
  Issue Type: Sub-task
  Components: Commons
Reporter: Karl Pauls






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6909) Remove commons.json from samples/mail-archive/stats

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6909:
-

 Summary: Remove commons.json from samples/mail-archive/stats
 Key: SLING-6909
 URL: https://issues.apache.org/jira/browse/SLING-6909
 Project: Sling
  Issue Type: Sub-task
  Components: Samples
Reporter: Karl Pauls






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6908) Remove commons.json from Tooling Support Source

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6908:
-

 Summary: Remove commons.json from Tooling Support Source
 Key: SLING-6908
 URL: https://issues.apache.org/jira/browse/SLING-6908
 Project: Sling
  Issue Type: Sub-task
  Components: Tooling
Affects Versions: Tooling Support Source 1.0.2
Reporter: Karl Pauls
 Fix For: Tooling Support Source 1.0.4






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6907) Remove commons.json from Tooling Support Install

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated SLING-6907:
--
Summary: Remove commons.json from Tooling Support Install  (was: Remove 
commons.json from )

> Remove commons.json from Tooling Support Install
> 
>
> Key: SLING-6907
> URL: https://issues.apache.org/jira/browse/SLING-6907
> Project: Sling
>  Issue Type: Sub-task
>  Components: Tooling
>Affects Versions: Tooling Support Install 1.0.2
>Reporter: Karl Pauls
> Fix For: Tooling Support Install 1.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6907) Remove commons.json from

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6907:
-

 Summary: Remove commons.json from 
 Key: SLING-6907
 URL: https://issues.apache.org/jira/browse/SLING-6907
 Project: Sling
  Issue Type: Sub-task
  Components: Tooling
Affects Versions: Tooling Support Install 1.0.2
Reporter: Karl Pauls
 Fix For: Tooling Support Install 1.0.4






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6906) Remove commons.json from testing junit remote

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6906:
-

 Summary: Remove commons.json from testing junit remote
 Key: SLING-6906
 URL: https://issues.apache.org/jira/browse/SLING-6906
 Project: Sling
  Issue Type: Sub-task
  Components: Testing
Affects Versions: JUnit Remote Tests Runners 1.0.10
Reporter: Karl Pauls
 Fix For: JUnit Remote Test Runners 1.0.12






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6905) Remove commons.json from testing http clients

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6905:
-

 Summary: 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] [Created] (SLING-6904) Remove commons.json from launchpad integrationtests

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6904:
-

 Summary: Remove commons.json from launchpad integrationtests
 Key: SLING-6904
 URL: https://issues.apache.org/jira/browse/SLING-6904
 Project: Sling
  Issue Type: Sub-task
  Components: Launchpad
Affects Versions: Launchpad Integration Tests 1.0.0
Reporter: Karl Pauls
 Fix For: Launchpad Integration Tests 1.0.2






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6903) Remove commons.json from launchpad test-services

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6903:
-

 Summary: Remove commons.json from launchpad test-services
 Key: SLING-6903
 URL: https://issues.apache.org/jira/browse/SLING-6903
 Project: Sling
  Issue Type: Sub-task
  Components: Launchpad
Affects Versions: Launchpad Test Services 2.0.6
Reporter: Karl Pauls
 Fix For: Launchpad Test Services 2.0.12






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6902) Remove commons.json from Apache Sling Script Console

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6902:
-

 Summary: Remove commons.json from Apache Sling Script Console
 Key: SLING-6902
 URL: https://issues.apache.org/jira/browse/SLING-6902
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Affects Versions: Scripting Console 1.0.0
Reporter: Karl Pauls
 Fix For: Scripting Console 1.0.2






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6901) Remove commons.json from jsNodeTypes

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6901:
-

 Summary: Remove commons.json from jsNodeTypes
 Key: SLING-6901
 URL: https://issues.apache.org/jira/browse/SLING-6901
 Project: Sling
  Issue Type: Sub-task
Reporter: Karl Pauls






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6900) Remove commons.json from Log Tracer

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6900:
-

 Summary: Remove commons.json from Log Tracer
 Key: SLING-6900
 URL: https://issues.apache.org/jira/browse/SLING-6900
 Project: Sling
  Issue Type: Sub-task
Affects Versions: Log Tracer 1.0.2
Reporter: Karl Pauls
 Fix For: Log Tracer 1.0.4






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6899) Remove commons.json from Sling Pipes

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6899:
-

 Summary: Remove commons.json from Sling Pipes
 Key: SLING-6899
 URL: https://issues.apache.org/jira/browse/SLING-6899
 Project: Sling
  Issue Type: Sub-task
Affects Versions: Pipes 0.0.10
Reporter: Karl Pauls
 Fix For: Pipes 0.0.12






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6898) Remove commons.json from Resource Inventory

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6898:
-

 Summary: Remove commons.json from Resource Inventory
 Key: SLING-6898
 URL: https://issues.apache.org/jira/browse/SLING-6898
 Project: Sling
  Issue Type: Sub-task
Affects Versions: Resource Inventory 1.0.6
Reporter: Karl Pauls
 Fix For: Resource Inventory 1.0.8






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6897) Remove commons.json from Log Tail Implementation

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6897:
-

 Summary: Remove commons.json from Log Tail Implementation
 Key: SLING-6897
 URL: https://issues.apache.org/jira/browse/SLING-6897
 Project: Sling
  Issue Type: Sub-task
Reporter: Karl Pauls






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6896) Remove commons.json from HAPI

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6896:
-

 Summary: Remove commons.json from HAPI
 Key: SLING-6896
 URL: https://issues.apache.org/jira/browse/SLING-6896
 Project: Sling
  Issue Type: Sub-task
  Components: HApi
Affects Versions: HApi 1.0.2
Reporter: Karl Pauls
 Fix For: HApi 2.0.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6894) Remove commons.json from Content Distribution Avro Serializer

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6894:
-

 Summary: 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






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6895) Remove commons.json from Content Distribution Kryo Serializer

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6895:
-

 Summary: 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






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6893) Remove commons.json from Content Distribution Integration Tests

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6893:
-

 Summary: 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






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6892) Remove commons.json from Content Distribution Core

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6892:
-

 Summary: 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
 Fix For: Content Distribution Core 0.2.8






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6891) Retire xss.compat to the attic

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6891:
-

 Summary: 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


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)

[RESULT][VOTE] Release Apache Sling Launchpad Content 2.0.12

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Carsten Ziegeler, Karl Pauls, Stefan Egli, Stefan
Seifert, Robert Munteanu
+1 (non binding): Chris Millar

I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.

[jira] [Commented] (SLING-6888) Remove commons.json and org.json excludes

[Karl Pauls (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028114#comment-16028114
 ] 

Karl Pauls commented on SLING-6888:
---

List of places where we still ref commons.json:

./bundles/extensions/discovery/base/
./bundles/extensions/discovery/impl/
./bundles/extensions/discovery/oak/
./bundles/jcr/contentloader/

> 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] [Created] (SLING-6890) Remove usage of o.a.jackrabbit.commons.json from i18n

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6890:
-

 Summary: 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] [Created] (SLING-6889) Retire commons.json to the attic

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6889:
-

 Summary: 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).

I'll call for a vote on the dev list when the rest of SLING-6887 is done.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6880) CAConfig Mock Plugin: Add helper methods for writing configurations

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6880.
-

> CAConfig Mock Plugin: Add helper methods for writing configurations
> ---
>
> Key: SLING-6880
> URL: https://issues.apache.org/jira/browse/SLING-6880
> Project: Sling
>  Issue Type: New Feature
>  Components: Testing
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>  Labels: mocks
> Fix For: Context-Aware Configuration Mock Plugin 1.3.0
>
>
> add methods for writing configuration and configuration collections:
> * {{MockContextAwareConfig.writeConfiguration}}
> * {{MockContextAwareConfig.writeConfigurationCollection}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6882) CAConfig Impl: Display context paths and config refs in web console

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6882.
-

> CAConfig Impl: Display context paths and config refs in web console
> ---
>
> Key: SLING-6882
> URL: https://issues.apache.org/jira/browse/SLING-6882
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Context-Aware Configuration Impl 1.4.2
>
>
> for debugging purpose it is usefull to list all context paths and the 
> associated config references for a given content resource in the web console 
> plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6881) CAConfig Mock Plugin: Register configuration classes via package name

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6881.
-

> CAConfig Mock Plugin: Register configuration classes via package name
> -
>
> Key: SLING-6881
> URL: https://issues.apache.org/jira/browse/SLING-6881
> Project: Sling
>  Issue Type: New Feature
>  Components: Testing
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>  Labels: mocks
> Fix For: Context-Aware Configuration Mock Plugin 1.3.0
>
>
> add methods for registring configuration classes in the current project via 
> their package name:
> * {{MockContextAwareConfig.registerAnnotationPackages}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6883) CAConfig: Respect service ranking in ordering context path/config ref proposals

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6883.
-

> CAConfig: Respect service ranking in ordering context path/config ref 
> proposals
> ---
>
> Key: SLING-6883
> URL: https://issues.apache.org/jira/browse/SLING-6883
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>  Labels: contextaware-config
> Fix For: Context-Aware Configuration SPI 1.3.2, Context-Aware 
> Configuration Impl 1.4.2
>
>
> when multiple context path strategies are registered with provide different 
> config refs for the same context paths, their proposals should be sorted 
> descending by service ranking, so the order can be controlled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[RESULT] [VOTE] Release Apache Sling Context-Aware Configuration SPI 1.3.2, Context-Aware Configuration Impl 1.4.2, Context-Aware Configuration Mock Plugin 1.3.0

[Stefan Seifert]

Hi,

The vote has passed with the following result :

+1 (binding): Stefan Seifert, Carsten Ziegeler, Karl Pauls

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

stefan

[jira] [Created] (SLING-6888) Remove commons.json and org.json excludes

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6888:
-

 Summary: 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] [Created] (SLING-6887) Remove commons.json and org.json from trunk

[Karl Pauls (JIRA)]

Karl Pauls created SLING-6887:
-

 Summary: Remove commons.json and org.json from trunk
 Key: SLING-6887
 URL: https://issues.apache.org/jira/browse/SLING-6887
 Project: Sling
  Issue Type: Improvement
Reporter: Karl Pauls
Assignee: Karl Pauls


Following-up on SLING-6679 where we removed all usage of commons.json and 
org.json from launchpad relevant bundles we still have some work to do to 
remove commons.json and org.json from all of trunk. 

This is the umbrella issue for getting this done. I'll create sub-issues for 
the affected bundles and will resolve this issue when they are 
commons.json/org.json free and released. 

When this issue is closed we shouldn't have references to commons.json/org.json 
in trunk anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json in launchpad relevant bundles

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated SLING-6679:
--
Summary: Replace usage of org.apache.sling.commons.json.* and org.json in 
launchpad relevant bundles  (was: Replace usage of 
org.apache.sling.commons.json.* and org.json)

> Replace usage of org.apache.sling.commons.json.* and org.json in launchpad 
> relevant bundles
> ---
>
> Key: SLING-6679
> URL: https://issues.apache.org/jira/browse/SLING-6679
> Project: Sling
>  Issue Type: Improvement
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>  Labels: Sling-9-ReleaseNotes
>
> Following the deprecation of org.apache.sling.commons.json (SLING-6536) we 
> need to replace its usage everywhere else (at least if we want to be able to 
> release other modules that depend on it). 
> This is the umbrella issue for getting this done. The idea is to create 
> sub-issues with patches for individual components, review the patches, and 
> when all are done: close this issue. 
> General discussions and problems should go to this issue and specific ones on 
> the sub-issue in question.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json in launchpad relevant bundles

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls closed SLING-6679.
-

> Replace usage of org.apache.sling.commons.json.* and org.json in launchpad 
> relevant bundles
> ---
>
> Key: SLING-6679
> URL: https://issues.apache.org/jira/browse/SLING-6679
> Project: Sling
>  Issue Type: Improvement
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>  Labels: Sling-9-ReleaseNotes
>
> Following the deprecation of org.apache.sling.commons.json (SLING-6536) we 
> need to replace its usage everywhere else (at least if we want to be able to 
> release other modules that depend on it). 
> This is the umbrella issue for getting this done. The idea is to create 
> sub-issues with patches for individual components, review the patches, and 
> when all are done: close this issue. 
> General discussions and problems should go to this issue and specific ones on 
> the sub-issue in question.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6686) Replace commons.json usage in org.apache.sling.servlets.compat (or retire that module)

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls closed SLING-6686.
-

> Replace commons.json usage in org.apache.sling.servlets.compat (or retire 
> that module)
> --
>
> Key: SLING-6686
> URL: https://issues.apache.org/jira/browse/SLING-6686
> Project: Sling
>  Issue Type: Sub-task
>  Components: Servlets
>Affects Versions: Servlets Compat 1.0.0
>Reporter: Karl Pauls
>Assignee: Bertrand Delacretaz
>
> Not sure we have to update this one?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6713) Remove commons.json and org.json from launchpad

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls closed SLING-6713.
-

> Remove commons.json and org.json from launchpad
> ---
>
> Key: SLING-6713
> URL: https://issues.apache.org/jira/browse/SLING-6713
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>  Labels: Sling-9-ReleaseNotes
> Attachments: SLING-6713.patch
>
>
> We need to remove commons.json from the launchpad provisioning, add the 
> commons.johnzon bundle, and update all bundles after we switched them to 
> johnzon. 
> Furthermore, we need to make sure it still works :-)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6857) Include latest version of the Felix framework in the Launchpad

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls closed SLING-6857.
-

> Include latest version of the Felix framework in the Launchpad
> --
>
> Key: SLING-6857
> URL: https://issues.apache.org/jira/browse/SLING-6857
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Karl Pauls
> Fix For: Launchpad Base 2.6.18
>
>
> Update to the upcomming Felix framework 5.6.4.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6871) JsonReader should allow tick as well as double quotes on import.

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls closed SLING-6871.
-

> JsonReader should allow tick as well as double quotes on import.
> 
>
> Key: SLING-6871
> URL: https://issues.apache.org/jira/browse/SLING-6871
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR ContentLoader 2.2.0
>Reporter: Karl Pauls
>Assignee: Karl Pauls
> Fix For: JCR ContentLoader 2.2.2
>
>
> I think we have to relax the json parsing at least for the contentloader 
> import case. It's just to likely that people will use ticks instead of double 
> quotes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6870) ImportOperation is created to late

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls closed SLING-6870.
-

> ImportOperation is created to late
> --
>
> Key: SLING-6870
> URL: https://issues.apache.org/jira/browse/SLING-6870
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Post 2.3.18
>Reporter: Karl Pauls
>Assignee: Karl Pauls
> Fix For: Servlets Post 2.3.20
>
>
> The latest jcr dependency removal makes it so that the ImportOperation is 
> created in the @activate. That is too late, because the dependencies get set 
> before the @activate which causes the ImportOperation to have missing 
> dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Sling JCR Resource 3.0.2

[Stefan Egli]

+1

Cheers,
Stefan

On 28/05/17 16:22, "Carsten Ziegeler"  wrote:

>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] [Closed] (SLING-6877) FSResource: Allow to adapt to Node from FileResource

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6877.
-

> FSResource: Allow to adapt to Node from FileResource
> 
>
> Key: SLING-6877
> URL: https://issues.apache.org/jira/browse/SLING-6877
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: File System Resource Provider 1.4.0, File System 
> Resource Provider 2.1.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Resource Provider 1.4.2, File System 
> Resource Provider 2.1.2
>
>
> since SLING-6829 FileResource has precedence over FileContentResource. for 
> files and folders with node descriptor files adapting to a JCR node should 
> still be supported.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6875) maven-sling-plugin: Support tick as well as double quote when validating JSON files

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6875.
-

> maven-sling-plugin: Support tick as well as double quote when validating JSON 
> files
> ---
>
> Key: SLING-6875
> URL: https://issues.apache.org/jira/browse/SLING-6875
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: Maven Sling Plugin 2.2.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: Maven Sling Plugin 2.2.2
>
>
> apply SLING-6872 to validation goal in maven-sling-plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6869) fsresource: Avoid NPE when content fragment file contains invalid JSON

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6869.
-

> fsresource: Avoid NPE when content fragment file contains invalid JSON
> --
>
> Key: SLING-6869
> URL: https://issues.apache.org/jira/browse/SLING-6869
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: File System Resource Provider 1.4.0, File System 
> Resource Provider 2.1.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: File System Resource Provider 1.4.2, File System 
> Resource Provider 2.1.2
>
>
> a NPE in 
> {{org.apache.sling.fsprovider.internal.mapper.ContentFile#getContent()}} my 
> be thrown when the underlying JSON content fragment file contains invalid 
> JSON that leads to a parsing error.
> this should be handled gently (an warning to the log is already written).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6873) FSResource: Support tick as well as double quote when parsing JSON files

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6873.
-

> FSResource: Support tick as well as double quote when parsing JSON files
> 
>
> Key: SLING-6873
> URL: https://issues.apache.org/jira/browse/SLING-6873
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: File System Resource Provider 1.4.0, File System 
> Resource Provider 2.1.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Resource Provider 1.4.2, File System 
> Resource Provider 2.1.2
>
>
> apply SLING-6872 to file system resource provider.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SLING-6872) JCR Content Parser: Support tick as well as double quote when parsing JSON files

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-6872.
-

> JCR Content Parser: Support tick as well as double quote when parsing JSON 
> files
> 
>
> Key: SLING-6872
> URL: https://issues.apache.org/jira/browse/SLING-6872
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Affects Versions: JCR Content Parser 1.1.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: JCR Content Parser 1.2.0
>
>
> currently the content parser supports JSON files only in "strict format", 
> plus the support for comments in JSON files.
> we should also support ticks for quoting names and string values, as in 
> SLING-6871 for the content loader.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[RESULT] [VOTE] Release Apache Sling JCR Content Parser 1.2.0, File System Resource Provider 2.1.2, File System Resource Provider 1.4.2, Maven Sling Plugin 2.2.2

[Stefan Seifert]

Hi,

The vote has passed with the following result :

+1 (binding): Stefan Seifert, Carsten Ziegeler, Karl Pauls

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

stefan

Re: [VOTE] Release Apache Sling JCR Resource 3.0.2

[Robert Munteanu]

On Sun, 2017-05-28 at 16:22 +0200, Carsten Ziegeler wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: sling 9 very large - reducing the size?

[Bertrand Delacretaz]

On Mon, May 22, 2017 at 1:16 PM, Ioan Eugen Stan  wrote:
> ...All I have to do is figure
> out if I need tika or not

I *think* Tika includes libraries for many different formats, so if
you don't need some of those formats it should be possible to create a
smaller Tika jar.

-Bertrand

Re: feedback + missing karaf feature for sling with RDBDocumentStore?

[Bertrand Delacretaz]

Hi,

On Sun, May 21, 2017 at 1:35 PM, Oliver Lietz  wrote:
> ...A sample feature using RDBDocumentStore is planned though...

As usual, contributions of such things are welcome, so Ioan if you
create such a feature for your own purposes feel free to suggest it as
a Sling sample contribution.

-Bertrand