[jira] [Updated] (SLING-10369) org.apache.sling.starter dependencies out of date

2021-05-10 Thread Ruben Reusser (Jira)


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

Ruben Reusser updated SLING-10369:
--
Description: 
please accept PR [1] to update the dependencies of the sling starter

the following dependencies were outdated:
{code:java}
[INFO]   org.apache.sling:org.apache.sling.api ... 2.23.0 -> 2.23.4
[INFO]   org.apache.sling:org.apache.sling.serviceusermapper ... 1.5.2 -> 1.5.4
[INFO]   org.apache.felix:org.apache.felix.configadmin ... 1.9.20 -> 1.9.22
[INFO]   org.apache.felix:org.apache.felix.http.jetty .. 4.1.6 -> 
4.1.8{code}
 [1] [https://github.com/apache/sling-org-apache-sling-starter/pull/21] 

  was:
please accept PR [1] to update the dependencies of the sling starter

the following dependencies were outdated:
{code:java}
[INFO] org.apache.sling:org.apache.sling.auth.core ... 1.5.0 -> 1.5.2
[INFO] org.apache.sling:org.apache.sling.engine .. 2.7.2 -> 2.7.4
[INFO] org.apache.sling:org.apache.sling.repoinit.parser . 1.6.6 -> 1.6.8
[INFO] org.apache.sling:org.apache.sling.resourceresolver  1.7.2 -> 1.7.4
[INFO] org.apache.sling:org.apache.sling.xss  2.2.8 -> 2.2.12
[INFO] com.composum.nodes:composum-nodes-commons . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-console . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-jslibs .. 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-pckgmgr . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-usermgr . 2.3.0 -> 2.6.1
[INFO] org.apache.felix:org.apache.felix.http.jetty .. 4.1.4 -> 4.1.6
[INFO] org.apache.felix:org.apache.felix.scr ... 2.1.24 -> 2.1.26
[INFO] org.apache.felix:org.apache.felix.utils . 1.11.6 -> 
1.11.8{code}
also had to move org.apache.sling.commons.metrics and 
io.dropwizard.metrics:metrics-core from start-level 15 to start-level 5 to be 
able to build the project due to
{code:java}
[ERROR] org.apache.sling:org.apache.sling.auth.core:1.5.2: is importing 
package(s) org.apache.sling.commons.metrics in start level 5 but no bundle is 
exporting these for that start level.
[ERROR] Analyser detected errors on feature 
'org.apache.sling:org.apache.sling.starter:slingosgifeature:nosample_base:12-SNAPSHOT'.
 See log output for error messages.{code}
 [1] https://github.com/apache/sling-org-apache-sling-starter/pull/19


> org.apache.sling.starter dependencies out of date
> -
>
> Key: SLING-10369
> URL: https://issues.apache.org/jira/browse/SLING-10369
> Project: Sling
>  Issue Type: Improvement
>  Components: Starter
>Reporter: Ruben Reusser
>Assignee: Bertrand Delacretaz
>Priority: Critical
>
> please accept PR [1] to update the dependencies of the sling starter
> the following dependencies were outdated:
> {code:java}
> [INFO]   org.apache.sling:org.apache.sling.api ... 2.23.0 -> 
> 2.23.4
> [INFO]   org.apache.sling:org.apache.sling.serviceusermapper ... 1.5.2 -> 
> 1.5.4
> [INFO]   org.apache.felix:org.apache.felix.configadmin ... 1.9.20 -> 
> 1.9.22
> [INFO]   org.apache.felix:org.apache.felix.http.jetty .. 4.1.6 -> 
> 4.1.8{code}
>  [1] [https://github.com/apache/sling-org-apache-sling-starter/pull/21] 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (SLING-10369) org.apache.sling.starter dependencies out of date

2021-05-10 Thread Ruben Reusser (Jira)
Ruben Reusser created SLING-10369:
-

 Summary: org.apache.sling.starter dependencies out of date
 Key: SLING-10369
 URL: https://issues.apache.org/jira/browse/SLING-10369
 Project: Sling
  Issue Type: Improvement
  Components: Starter
Reporter: Ruben Reusser
Assignee: Bertrand Delacretaz


please accept PR [1] to update the dependencies of the sling starter

the following dependencies were outdated:
{code:java}
[INFO] org.apache.sling:org.apache.sling.auth.core ... 1.5.0 -> 1.5.2
[INFO] org.apache.sling:org.apache.sling.engine .. 2.7.2 -> 2.7.4
[INFO] org.apache.sling:org.apache.sling.repoinit.parser . 1.6.6 -> 1.6.8
[INFO] org.apache.sling:org.apache.sling.resourceresolver  1.7.2 -> 1.7.4
[INFO] org.apache.sling:org.apache.sling.xss  2.2.8 -> 2.2.12
[INFO] com.composum.nodes:composum-nodes-commons . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-console . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-jslibs .. 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-pckgmgr . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-usermgr . 2.3.0 -> 2.6.1
[INFO] org.apache.felix:org.apache.felix.http.jetty .. 4.1.4 -> 4.1.6
[INFO] org.apache.felix:org.apache.felix.scr ... 2.1.24 -> 2.1.26
[INFO] org.apache.felix:org.apache.felix.utils . 1.11.6 -> 
1.11.8{code}
also had to move org.apache.sling.commons.metrics and 
io.dropwizard.metrics:metrics-core from start-level 15 to start-level 5 to be 
able to build the project due to
{code:java}
[ERROR] org.apache.sling:org.apache.sling.auth.core:1.5.2: is importing 
package(s) org.apache.sling.commons.metrics in start level 5 but no bundle is 
exporting these for that start level.
[ERROR] Analyser detected errors on feature 
'org.apache.sling:org.apache.sling.starter:slingosgifeature:nosample_base:12-SNAPSHOT'.
 See log output for error messages.{code}
 [1] https://github.com/apache/sling-org-apache-sling-starter/pull/19



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (SLING-10347) org.apache.sling.starter dependencies out of date

2021-05-03 Thread Ruben Reusser (Jira)
Ruben Reusser created SLING-10347:
-

 Summary: org.apache.sling.starter dependencies out of date
 Key: SLING-10347
 URL: https://issues.apache.org/jira/browse/SLING-10347
 Project: Sling
  Issue Type: Improvement
  Components: Starter
Reporter: Ruben Reusser


please accept PR [1] to update the dependencies of the sling starter

the following dependencies were outdated:
{code:java}
[INFO] org.apache.sling:org.apache.sling.auth.core ... 1.5.0 -> 1.5.2
[INFO] org.apache.sling:org.apache.sling.engine .. 2.7.2 -> 2.7.4
[INFO] org.apache.sling:org.apache.sling.repoinit.parser . 1.6.6 -> 1.6.8
[INFO] org.apache.sling:org.apache.sling.resourceresolver  1.7.2 -> 1.7.4
[INFO] org.apache.sling:org.apache.sling.xss  2.2.8 -> 2.2.12
[INFO] com.composum.nodes:composum-nodes-commons . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-console . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-jslibs .. 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-pckgmgr . 2.3.0 -> 2.6.1
[INFO] com.composum.nodes:composum-nodes-usermgr . 2.3.0 -> 2.6.1
[INFO] org.apache.felix:org.apache.felix.http.jetty .. 4.1.4 -> 4.1.6
[INFO] org.apache.felix:org.apache.felix.scr ... 2.1.24 -> 2.1.26
[INFO] org.apache.felix:org.apache.felix.utils . 1.11.6 -> 
1.11.8{code}
also had to move org.apache.sling.commons.metrics and 
io.dropwizard.metrics:metrics-core from start-level 15 to start-level 5 to be 
able to build the project due to
{code:java}
[ERROR] org.apache.sling:org.apache.sling.auth.core:1.5.2: is importing 
package(s) org.apache.sling.commons.metrics in start level 5 but no bundle is 
exporting these for that start level.
[ERROR] Analyser detected errors on feature 
'org.apache.sling:org.apache.sling.starter:slingosgifeature:nosample_base:12-SNAPSHOT'.
 See log output for error messages.{code}
 [1]https://github.com/apache/sling-org-apache-sling-starter/pull/19



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (SLING-10143) bundles referenced in sling starter are out of date

2021-02-17 Thread Ruben Reusser (Jira)


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

Ruben Reusser commented on SLING-10143:
---

PR created at [https://github.com/apache/sling-org-apache-sling-starter/pull/18]

I did however notice a shutdown issue with the new starter in the 
org.apache.sling.discovery.oak module - not sure if that is an issue or not 
(start sling, hit ctrl-c to stop sling, get the error) - the issue is not 
present in master: 
{code:java}
ERROR : bundle org.apache.sling.discovery.oak:1.2.30 
(148)[org.apache.sling.discovery.oak.OakDiscoveryService(232)] : The 
updatedPropertyProvider method has thrown an exceptionERROR : bundle 
org.apache.sling.discovery.oak:1.2.30 
(148)[org.apache.sling.discovery.oak.OakDiscoveryService(232)] : The 
updatedPropertyProvider method has thrown an 
exceptionjava.lang.IllegalArgumentException: Can't create child on a synthetic 
root at 
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:979)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:666)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:603)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:571)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:654)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:603)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:571)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:654)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:603)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:571)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResourceInternal(ResourceUtil.java:654)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:603)
 at 
org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:571){code}

> bundles referenced in sling starter are out of date
> ---
>
> Key: SLING-10143
> URL: https://issues.apache.org/jira/browse/SLING-10143
> Project: Sling
>  Issue Type: Improvement
>  Components: Starter
>Reporter: Ruben Reusser
>Priority: Major
> Fix For: Starter 12
>
> Attachments: 
> 0001-updated-3rd-party-dependencies-of-sling-starter.patch, 
> 0002-javax.activation-dependency-needed-to-be-increased.patch, 
> 0003-updated-to-latest-sling-bundles-added-missing-felix-.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Would be nice to make sure the sling starter uses the latest bundles - 
> according to 
> {code:java}
> mvn versions:display-dependency-updates{code}
> the sling starter is a bit out of date with the dependencies
> {code:java}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO]   com.composum.nodes:composum-nodes-commons . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-console . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-jslibs .. 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-pckgmgr . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-usermgr . 2.1.1 -> 
> 2.3.0
> [INFO]   com.fasterxml.jackson.core:jackson-annotations .. 2.11.1 -> 
> 2.12.1
> [INFO]   com.fasterxml.jackson.core:jackson-core . 2.11.1 -> 
> 2.12.1
> [INFO]   com.fasterxml.jackson.core:jackson-databind . 2.11.1 -> 
> 2.12.1
> [INFO]   com.google.guava:guava .. 15.0 -> 
> 30.1-jre
> [INFO]   com.h2database:h2-mvstore . 1.4.194 -> 
> 1.4.200
> [INFO]   commons-codec:commons-codec . 1.14 -> 
> 1.15
> [INFO]   commons-collections:commons-collections  3.2.2 -> 
> 20040616
> [INFO]   commons-io:commons-io ... 2.6 -> 
> 2.8.0
> [INFO]   io.dropwizard.metrics:metrics-core . 3.2.6 -> 
> 4.2.0-beta.1
> [INFO]   org.antlr:antlr4-runtime .. 4.7.2 -> 
> 4.9.1
> [INFO]   org.apache.commons:commons-lang3 . 3.9 -> 
> 3.11
> [INFO]   org.apache.felix:org.apache.felix.configadmin ... 1.9.16 -> 
> 1.9.20
> [INFO]   org.apache.felix:org.apache.felix.eventadmin .. 1.5.0 -> 
> 1.6.2
> [INFO]   org.apache.felix:org.apache.felix.http.jetty . 4.0.18 -> 
> 4.1.4
> [INFO]   org.apache.felix:org.apache.felix.metatype  1.2.2 -> 
> 1.2.4
> [INFO]   org.apache.felix:org.apache.felix.scr ... 

[jira] [Commented] (SLING-10143) bundles referenced in sling starter are out of date

2021-02-15 Thread Ruben Reusser (Jira)


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

Ruben Reusser commented on SLING-10143:
---

patch files to bring dependencies up to latest versions attached to this issue

out of date dependencies are now greatly reduced, however, hard to say if this 
introduces new issues. 
{code:java}
[INFO] artifact org.apache.felix:org.apache.felix.cm.json: checking for updates 
from central
[INFO] The following dependencies in Dependencies have newer versions:
[INFO]   com.google.guava:guava .. 15.0 -> 30.1-jre
[INFO]   commons-collections:commons-collections  3.2.2 -> 20040616
[INFO]   io.dropwizard.metrics:metrics-core . 3.2.6 -> 4.2.0-beta.1
[INFO]   org.apache.tika:tika-core  1.24 -> 2.0.0-ALPHA
[INFO]   org.apache.tika:tika-parsers . 1.24 -> 2.0.0-ALPHA
[INFO]   org.jvnet.staxex:stax-ex .. 1.7.6 -> 2.0.0
[INFO]   org.slf4j:jcl-over-slf4j .. 1.7.30 -> 2.0.0-alpha1
[INFO]   org.slf4j:log4j-over-slf4j  1.7.30 -> 2.0.0-alpha1
[INFO]   org.slf4j:slf4j-api ... 1.7.30 -> 2.0.0-alpha1

{code}

> bundles referenced in sling starter are out of date
> ---
>
> Key: SLING-10143
> URL: https://issues.apache.org/jira/browse/SLING-10143
> Project: Sling
>  Issue Type: Improvement
>  Components: Starter
>Reporter: Ruben Reusser
>Priority: Major
> Fix For: Starter 12
>
> Attachments: 
> 0001-updated-3rd-party-dependencies-of-sling-starter.patch, 
> 0002-javax.activation-dependency-needed-to-be-increased.patch, 
> 0003-updated-to-latest-sling-bundles-added-missing-felix-.patch
>
>
> Would be nice to make sure the sling starter uses the latest bundles - 
> according to 
> {code:java}
> mvn versions:display-dependency-updates{code}
> the sling starter is a bit out of date with the dependencies
> {code:java}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO]   com.composum.nodes:composum-nodes-commons . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-console . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-jslibs .. 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-pckgmgr . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-usermgr . 2.1.1 -> 
> 2.3.0
> [INFO]   com.fasterxml.jackson.core:jackson-annotations .. 2.11.1 -> 
> 2.12.1
> [INFO]   com.fasterxml.jackson.core:jackson-core . 2.11.1 -> 
> 2.12.1
> [INFO]   com.fasterxml.jackson.core:jackson-databind . 2.11.1 -> 
> 2.12.1
> [INFO]   com.google.guava:guava .. 15.0 -> 
> 30.1-jre
> [INFO]   com.h2database:h2-mvstore . 1.4.194 -> 
> 1.4.200
> [INFO]   commons-codec:commons-codec . 1.14 -> 
> 1.15
> [INFO]   commons-collections:commons-collections  3.2.2 -> 
> 20040616
> [INFO]   commons-io:commons-io ... 2.6 -> 
> 2.8.0
> [INFO]   io.dropwizard.metrics:metrics-core . 3.2.6 -> 
> 4.2.0-beta.1
> [INFO]   org.antlr:antlr4-runtime .. 4.7.2 -> 
> 4.9.1
> [INFO]   org.apache.commons:commons-lang3 . 3.9 -> 
> 3.11
> [INFO]   org.apache.felix:org.apache.felix.configadmin ... 1.9.16 -> 
> 1.9.20
> [INFO]   org.apache.felix:org.apache.felix.eventadmin .. 1.5.0 -> 
> 1.6.2
> [INFO]   org.apache.felix:org.apache.felix.http.jetty . 4.0.18 -> 
> 4.1.4
> [INFO]   org.apache.felix:org.apache.felix.metatype  1.2.2 -> 
> 1.2.4
> [INFO]   org.apache.felix:org.apache.felix.scr ... 2.1.20 -> 
> 2.1.24
> [INFO]   org.apache.felix:org.apache.felix.utils . 1.11.2 -> 
> 1.11.6
> [INFO]   org.apache.felix:org.apache.felix.webconsole .. 4.5.0 -> 
> 4.6.0
> [INFO]   org.apache.geronimo.specs:geronimo-annotation_1.3_spec  1.1 -> 
> 1.3
> [INFO]   org.apache.geronimo.specs:geronimo-atinject_1.0_spec .. 1.1 -> 
> 1.2
> [INFO]   org.apache.httpcomponents:httpclient  4.5.10 -> 
> 4.5.13
> [INFO]   org.apache.httpcomponents:httpclient-osgi ... 4.5.10 -> 
> 4.5.13
> [INFO]   org.apache.httpcomponents:httpcore-osgi . 4.4.12 -> 
> 4.4.14
> [INFO]   org.apache.jackrabbit:jackrabbit-data ... 2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-jcr-commons  2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-jcr-rmi  2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-spi  2.20.0 -> 
> 2.21.5
> 

[jira] [Updated] (SLING-10143) bundles referenced in sling starter are out of date

2021-02-15 Thread Ruben Reusser (Jira)


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

Ruben Reusser updated SLING-10143:
--
Attachment: 0001-updated-3rd-party-dependencies-of-sling-starter.patch
0002-javax.activation-dependency-needed-to-be-increased.patch
0003-updated-to-latest-sling-bundles-added-missing-felix-.patch

> bundles referenced in sling starter are out of date
> ---
>
> Key: SLING-10143
> URL: https://issues.apache.org/jira/browse/SLING-10143
> Project: Sling
>  Issue Type: Improvement
>  Components: Starter
>Reporter: Ruben Reusser
>Priority: Major
> Fix For: Starter 12
>
> Attachments: 
> 0001-updated-3rd-party-dependencies-of-sling-starter.patch, 
> 0002-javax.activation-dependency-needed-to-be-increased.patch, 
> 0003-updated-to-latest-sling-bundles-added-missing-felix-.patch
>
>
> Would be nice to make sure the sling starter uses the latest bundles - 
> according to 
> {code:java}
> mvn versions:display-dependency-updates{code}
> the sling starter is a bit out of date with the dependencies
> {code:java}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO]   com.composum.nodes:composum-nodes-commons . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-console . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-jslibs .. 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-pckgmgr . 2.1.1 -> 
> 2.3.0
> [INFO]   com.composum.nodes:composum-nodes-usermgr . 2.1.1 -> 
> 2.3.0
> [INFO]   com.fasterxml.jackson.core:jackson-annotations .. 2.11.1 -> 
> 2.12.1
> [INFO]   com.fasterxml.jackson.core:jackson-core . 2.11.1 -> 
> 2.12.1
> [INFO]   com.fasterxml.jackson.core:jackson-databind . 2.11.1 -> 
> 2.12.1
> [INFO]   com.google.guava:guava .. 15.0 -> 
> 30.1-jre
> [INFO]   com.h2database:h2-mvstore . 1.4.194 -> 
> 1.4.200
> [INFO]   commons-codec:commons-codec . 1.14 -> 
> 1.15
> [INFO]   commons-collections:commons-collections  3.2.2 -> 
> 20040616
> [INFO]   commons-io:commons-io ... 2.6 -> 
> 2.8.0
> [INFO]   io.dropwizard.metrics:metrics-core . 3.2.6 -> 
> 4.2.0-beta.1
> [INFO]   org.antlr:antlr4-runtime .. 4.7.2 -> 
> 4.9.1
> [INFO]   org.apache.commons:commons-lang3 . 3.9 -> 
> 3.11
> [INFO]   org.apache.felix:org.apache.felix.configadmin ... 1.9.16 -> 
> 1.9.20
> [INFO]   org.apache.felix:org.apache.felix.eventadmin .. 1.5.0 -> 
> 1.6.2
> [INFO]   org.apache.felix:org.apache.felix.http.jetty . 4.0.18 -> 
> 4.1.4
> [INFO]   org.apache.felix:org.apache.felix.metatype  1.2.2 -> 
> 1.2.4
> [INFO]   org.apache.felix:org.apache.felix.scr ... 2.1.20 -> 
> 2.1.24
> [INFO]   org.apache.felix:org.apache.felix.utils . 1.11.2 -> 
> 1.11.6
> [INFO]   org.apache.felix:org.apache.felix.webconsole .. 4.5.0 -> 
> 4.6.0
> [INFO]   org.apache.geronimo.specs:geronimo-annotation_1.3_spec  1.1 -> 
> 1.3
> [INFO]   org.apache.geronimo.specs:geronimo-atinject_1.0_spec .. 1.1 -> 
> 1.2
> [INFO]   org.apache.httpcomponents:httpclient  4.5.10 -> 
> 4.5.13
> [INFO]   org.apache.httpcomponents:httpclient-osgi ... 4.5.10 -> 
> 4.5.13
> [INFO]   org.apache.httpcomponents:httpcore-osgi . 4.4.12 -> 
> 4.4.14
> [INFO]   org.apache.jackrabbit:jackrabbit-data ... 2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-jcr-commons  2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-jcr-rmi  2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-spi  2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-spi-commons  2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:jackrabbit-webdav . 2.20.0 -> 
> 2.21.5
> [INFO]   org.apache.jackrabbit:oak-api ... 1.32.0 -> 
> 1.38.0
> [INFO]   org.apache.jackrabbit:oak-authorization-principalbased ...
> [INFO] 1.32.0 -> 
> 1.38.0
> [INFO]   org.apache.jackrabbit:oak-blob .. 1.32.0 -> 
> 1.38.0
> [INFO]   org.apache.jackrabbit:oak-blob-plugins .. 1.32.0 -> 
> 1.38.0
> [INFO]   org.apache.jackrabbit:oak-commons ... 1.32.0 -> 
> 1.38.0
> [INFO]   org.apache.jackrabbit:oak-core .. 1.32.0 -> 
> 1.38.0
> [INFO]   org.apache.jackrabbit:oak-core-spi .. 1.32.0 -> 
> 1.38.0
> [INFO]   org.apache.jackrabbit:oak-jackrabbit-api  

[jira] [Created] (SLING-10143) bundles referenced in sling starter are out of date

2021-02-15 Thread Ruben Reusser (Jira)
Ruben Reusser created SLING-10143:
-

 Summary: bundles referenced in sling starter are out of date
 Key: SLING-10143
 URL: https://issues.apache.org/jira/browse/SLING-10143
 Project: Sling
  Issue Type: Improvement
  Components: Starter
Reporter: Ruben Reusser
 Fix For: Starter 12


Would be nice to make sure the sling starter uses the latest bundles - 
according to 
{code:java}
mvn versions:display-dependency-updates{code}
the sling starter is a bit out of date with the dependencies
{code:java}
[INFO] The following dependencies in Dependencies have newer versions:
[INFO]   com.composum.nodes:composum-nodes-commons . 2.1.1 -> 2.3.0
[INFO]   com.composum.nodes:composum-nodes-console . 2.1.1 -> 2.3.0
[INFO]   com.composum.nodes:composum-nodes-jslibs .. 2.1.1 -> 2.3.0
[INFO]   com.composum.nodes:composum-nodes-pckgmgr . 2.1.1 -> 2.3.0
[INFO]   com.composum.nodes:composum-nodes-usermgr . 2.1.1 -> 2.3.0
[INFO]   com.fasterxml.jackson.core:jackson-annotations .. 2.11.1 -> 2.12.1
[INFO]   com.fasterxml.jackson.core:jackson-core . 2.11.1 -> 2.12.1
[INFO]   com.fasterxml.jackson.core:jackson-databind . 2.11.1 -> 2.12.1
[INFO]   com.google.guava:guava .. 15.0 -> 30.1-jre
[INFO]   com.h2database:h2-mvstore . 1.4.194 -> 1.4.200
[INFO]   commons-codec:commons-codec . 1.14 -> 1.15
[INFO]   commons-collections:commons-collections  3.2.2 -> 20040616
[INFO]   commons-io:commons-io ... 2.6 -> 2.8.0
[INFO]   io.dropwizard.metrics:metrics-core . 3.2.6 -> 4.2.0-beta.1
[INFO]   org.antlr:antlr4-runtime .. 4.7.2 -> 4.9.1
[INFO]   org.apache.commons:commons-lang3 . 3.9 -> 3.11
[INFO]   org.apache.felix:org.apache.felix.configadmin ... 1.9.16 -> 1.9.20
[INFO]   org.apache.felix:org.apache.felix.eventadmin .. 1.5.0 -> 1.6.2
[INFO]   org.apache.felix:org.apache.felix.http.jetty . 4.0.18 -> 4.1.4
[INFO]   org.apache.felix:org.apache.felix.metatype  1.2.2 -> 1.2.4
[INFO]   org.apache.felix:org.apache.felix.scr ... 2.1.20 -> 2.1.24
[INFO]   org.apache.felix:org.apache.felix.utils . 1.11.2 -> 1.11.6
[INFO]   org.apache.felix:org.apache.felix.webconsole .. 4.5.0 -> 4.6.0
[INFO]   org.apache.geronimo.specs:geronimo-annotation_1.3_spec  1.1 -> 1.3
[INFO]   org.apache.geronimo.specs:geronimo-atinject_1.0_spec .. 1.1 -> 1.2
[INFO]   org.apache.httpcomponents:httpclient  4.5.10 -> 4.5.13
[INFO]   org.apache.httpcomponents:httpclient-osgi ... 4.5.10 -> 4.5.13
[INFO]   org.apache.httpcomponents:httpcore-osgi . 4.4.12 -> 4.4.14
[INFO]   org.apache.jackrabbit:jackrabbit-data ... 2.20.0 -> 2.21.5
[INFO]   org.apache.jackrabbit:jackrabbit-jcr-commons  2.20.0 -> 2.21.5
[INFO]   org.apache.jackrabbit:jackrabbit-jcr-rmi  2.20.0 -> 2.21.5
[INFO]   org.apache.jackrabbit:jackrabbit-spi  2.20.0 -> 2.21.5
[INFO]   org.apache.jackrabbit:jackrabbit-spi-commons  2.20.0 -> 2.21.5
[INFO]   org.apache.jackrabbit:jackrabbit-webdav . 2.20.0 -> 2.21.5
[INFO]   org.apache.jackrabbit:oak-api ... 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-authorization-principalbased ...
[INFO] 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-blob .. 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-blob-plugins .. 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-commons ... 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-core .. 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-core-spi .. 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-jackrabbit-api  1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-jcr ... 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-lucene  1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-query-spi . 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-security-spi .. 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-segment-tar ... 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-store-composite ... 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-store-document  1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit:oak-store-spi . 1.32.0 -> 1.38.0
[INFO]   org.apache.jackrabbit.vault:org.apache.jackrabbit.vault ...
[INFO]   3.4.6 -> 3.4.8
[INFO]   org.apache.pdfbox:fontbox ... 2.0.17 -> 

[jira] [Created] (SLING-8747) establish @apachesling npmjs organization

2019-09-27 Thread Ruben Reusser (Jira)
Ruben Reusser created SLING-8747:


 Summary: establish @apachesling npmjs organization
 Key: SLING-8747
 URL: https://issues.apache.org/jira/browse/SLING-8747
 Project: Sling
  Issue Type: Improvement
  Components: CI
Reporter: Ruben Reusser


now that the donation for the slingpackager has been accepted we need to create 
a common apachesling organization on npmjs and start setting up a ci/cd flow to 
release the slingpackager

https://issues.apache.org/jira/browse/SLING-8584



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (SLING-8655) Add an Annotation to Sling Model to mark a property to be Externalized

2019-08-27 Thread Ruben Reusser (Jira)


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

Ruben Reusser commented on SLING-8655:
--

[~vladb] [~sseifert] [~radu.cotescu] we are mostly looking to externalize for 
an SPA use case - it looks like [~vladb]'s suggestion would work well for that 
- Does it still make sense to add the suggested ExternalizedSerializer to Sling 
as this is probably a use case most client side rendered web apps/sites will 
face at one point?

> Add an Annotation to Sling Model to mark a property to be Externalized
> --
>
> Key: SLING-8655
> URL: https://issues.apache.org/jira/browse/SLING-8655
> Project: Sling
>  Issue Type: New Feature
>  Components: Sling Models
>Affects Versions: Sling Models API 1.3.8
>Reporter: Andreas Schaefer
>Assignee: Andreas Schaefer
>Priority: Major
> Fix For: Sling Models API 1.3.10
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> For Peregrine CMS we use Sling Models to obtain data in JSon format to be 
> rendered on the client side. This means that the returned content is not 
> externalized aka paths are not mapped to the external view.
> Sling Model should have an Annotation (@ExternalizedPath) that marks a 
> property to be externalized when loaded.
> In order to be flexible the Externalized Path Injector should be pluggable so 
> that customers can add their custom Externalized Path Providers if they 
> choose to do so. By default there is a provider that uses the Resource 
> Resolver's map() function.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Issue Comment Deleted] (SLING-7768) Add String Interpolation support to /etc/map

2019-07-26 Thread Ruben Reusser (JIRA)


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

Ruben Reusser updated SLING-7768:
-
Comment: was deleted

(was: so when this was done there was a bigger discussion about making this 
more generic and hence this never made it into sling itself as it's only 
supporting etc/map. 

A more generic solution to this problem could be achieved with sling pipes (a 
config structure somewhere in the repository that is copied over to the final 
location with sling pipes and while doing so it should be able to pickup and 
inject the environment variables))

> Add String Interpolation support to /etc/map
> 
>
> Key: SLING-7768
> URL: https://issues.apache.org/jira/browse/SLING-7768
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
> Environment: Sling 11-SNAPSHOT, JDK 1.8
>Reporter: Andreas Schaefer
>Priority: Major
> Attachments: Screenshot 2018-07-06 11.41.58.png, Screenshot 
> 2018-07-06 11.42.41.png, Screenshot 2018-07-06 11.43.34.png
>
>
> Having worked on migrations of a Sling derivate Ruben & I ran into issues 
> where the /etc/map would map to production instead of testing environment.
>  Many big customer have extensive /etc/maps and also many different 
> environments like dev, qa, staging, prod etc.
>  It would be great to have a tool where for example items like the host name 
> or external links in /etc/map could be configured outside so that just one 
> entry has to adjusted rather than creating a full copy of the /etc/map tree.
>   
>  Example:
>   
>  /etc/map/http/phv.fq.host.name.8080
>   
>  Placeholder provides:
>  DEV: phv.fq.host.name=localhost
>  QA: phv.fq.host.name=qa.author.acme.com
>  STAGING: 
> phv.fq.host.name=[staging.author.acme.com|http://staging.author.acme.com/]
>  PROD: phv.fq.host.name=[acme.com|http://acme.com/]
>   
>  At runtime these are the resolved values:
>  DEV: http/localhost.8080
>  QA: http/qa.author.acme.com.8080
>  STAGING: http/[staging.author.acme.com|http://staging.author.acme.com/].8080
>  PROD: http/[acme.com|http://acme.com/].8080
>   
>  Not only does that make it easier and faster to create new test environments 
> but it also cuts down on the chance of copy-n-paste errors.
>   
>  I have a working POC with an PlaceholderProvider OSGi service and an 
> enhanced MapEntries that resolved any placeholders if found.
>   
>  Attached are 3 screenshots:
>  1. OSGi Placeholder Provider Configuration
>  2. /etc/map (Composum)
>  3. Result of [http://andreass.local:8080/] call



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (SLING-7768) Add String Interpolation support to /etc/map

2019-07-26 Thread Ruben Reusser (JIRA)


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

Ruben Reusser commented on SLING-7768:
--

so when this was done there was a bigger discussion about making this more 
generic and hence this never made it into sling itself as it's only supporting 
etc/map. 

A more generic solution to this problem could be achieved with sling pipes (a 
config structure somewhere in the repository that is copied over to the final 
location with sling pipes and while doing so it should be able to pickup and 
inject the environment variables)

> Add String Interpolation support to /etc/map
> 
>
> Key: SLING-7768
> URL: https://issues.apache.org/jira/browse/SLING-7768
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
> Environment: Sling 11-SNAPSHOT, JDK 1.8
>Reporter: Andreas Schaefer
>Priority: Major
> Attachments: Screenshot 2018-07-06 11.41.58.png, Screenshot 
> 2018-07-06 11.42.41.png, Screenshot 2018-07-06 11.43.34.png
>
>
> Having worked on migrations of a Sling derivate Ruben & I ran into issues 
> where the /etc/map would map to production instead of testing environment.
>  Many big customer have extensive /etc/maps and also many different 
> environments like dev, qa, staging, prod etc.
>  It would be great to have a tool where for example items like the host name 
> or external links in /etc/map could be configured outside so that just one 
> entry has to adjusted rather than creating a full copy of the /etc/map tree.
>   
>  Example:
>   
>  /etc/map/http/phv.fq.host.name.8080
>   
>  Placeholder provides:
>  DEV: phv.fq.host.name=localhost
>  QA: phv.fq.host.name=qa.author.acme.com
>  STAGING: 
> phv.fq.host.name=[staging.author.acme.com|http://staging.author.acme.com/]
>  PROD: phv.fq.host.name=[acme.com|http://acme.com/]
>   
>  At runtime these are the resolved values:
>  DEV: http/localhost.8080
>  QA: http/qa.author.acme.com.8080
>  STAGING: http/[staging.author.acme.com|http://staging.author.acme.com/].8080
>  PROD: http/[acme.com|http://acme.com/].8080
>   
>  Not only does that make it easier and faster to create new test environments 
> but it also cuts down on the chance of copy-n-paste errors.
>   
>  I have a working POC with an PlaceholderProvider OSGi service and an 
> enhanced MapEntries that resolved any placeholders if found.
>   
>  Attached are 3 screenshots:
>  1. OSGi Placeholder Provider Configuration
>  2. /etc/map (Composum)
>  3. Result of [http://andreass.local:8080/] call



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (SLING-8278) improve chrome audit score

2019-02-19 Thread Ruben Reusser (JIRA)


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

Ruben Reusser commented on SLING-8278:
--

https://issues.apache.org/jira/browse/SLING-8283 is needed to get the best 
practices score up 

> improve chrome audit score
> --
>
> Key: SLING-8278
> URL: https://issues.apache.org/jira/browse/SLING-8278
> Project: Sling
>  Issue Type: Improvement
>  Components: Starter
>Reporter: Ruben Reusser
>Priority: Trivial
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> google chrome audit currently lists a set of accessibility and seo problems 
> with the sling starter content. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SLING-8283) httpGet in system/sling.js uses depricated main thread blocking code

2019-02-19 Thread Ruben Reusser (JIRA)


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

Ruben Reusser commented on SLING-8283:
--

https://github.com/apache/sling-org-apache-sling-servlets-post/pull/4

> httpGet in system/sling.js uses depricated main thread blocking code
> 
>
> Key: SLING-8283
> URL: https://issues.apache.org/jira/browse/SLING-8283
> Project: Sling
>  Issue Type: Improvement
>  Components: Best practices
>Reporter: Ruben Reusser
>Priority: Major
>
> the sling starter homepage throws the following error in the browser console.
> sling.js:75 [Deprecation] Synchronous XMLHttpRequest on the main thread is 
> deprecated because of its detrimental effects to the end user's experience. 
> For more help, check 
> [https://xhr.spec.whatwg.org/.|https://xhr.spec.whatwg.org/]
> As the error mentions this is due to the fact that sling is using main thread 
> blocking calls in /system/sling.js - this is generally not recommended 
> anymore as it blocks the ability for a user to interact with the browser
> The problem can easily be solved by using callbacks instead of main thread 
> blocking code. 
> by altering Sling.httpGet to support callbacks this change can be made 
> gradually over time without a break in backwards compatibility
>  
> {code:java}
> /**
>  * HTTP GET XHR Helper
>  * @param {String} url The URL
>  * @param {Function} optional second parameter for async version of the 
> method.
>  *The callback will get the XHR object, method returns immediately
>  * @return the XHR object, use .responseText for the data
>  * @type String
>  */
> Sling.httpGet = function(url, callback) {
> var httpcon = Sling.getXHR();
> if (httpcon) {
> if(callback) {
> httpcon.onload = function() { callback(this); };
> httpcon.open('GET', url);
> httpcon.send(null);
> } else {
> httpcon.open('GET', url, false);
> httpcon.send(null);
> return httpcon;
> }
> } else {
> return null;
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SLING-8283) httpGet in system/sling.js uses depricated main thread blocking code

2019-02-19 Thread Ruben Reusser (JIRA)
Ruben Reusser created SLING-8283:


 Summary: httpGet in system/sling.js uses depricated main thread 
blocking code
 Key: SLING-8283
 URL: https://issues.apache.org/jira/browse/SLING-8283
 Project: Sling
  Issue Type: Improvement
  Components: Best practices
Reporter: Ruben Reusser


the sling starter homepage throws the following error in the browser console.

sling.js:75 [Deprecation] Synchronous XMLHttpRequest on the main thread is 
deprecated because of its detrimental effects to the end user's experience. For 
more help, check [https://xhr.spec.whatwg.org/.|https://xhr.spec.whatwg.org/]

As the error mentions this is due to the fact that sling is using main thread 
blocking calls in /system/sling.js - this is generally not recommended anymore 
as it blocks the ability for a user to interact with the browser

The problem can easily be solved by using callbacks instead of main thread 
blocking code. 

by altering Sling.httpGet to support callbacks this change can be made 
gradually over time without a break in backwards compatibility

 
{code:java}
/**
 * HTTP GET XHR Helper
 * @param {String} url The URL
 * @param {Function} optional second parameter for async version of the method.
 *The callback will get the XHR object, method returns immediately
 * @return the XHR object, use .responseText for the data
 * @type String
 */
Sling.httpGet = function(url, callback) {
var httpcon = Sling.getXHR();
if (httpcon) {
if(callback) {
httpcon.onload = function() { callback(this); };
httpcon.open('GET', url);
httpcon.send(null);
} else {
httpcon.open('GET', url, false);
httpcon.send(null);
return httpcon;
}
} else {
return null;
}
}
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SLING-8278) improve chrome audit score

2019-02-18 Thread Ruben Reusser (JIRA)
Ruben Reusser created SLING-8278:


 Summary: improve chrome audit score
 Key: SLING-8278
 URL: https://issues.apache.org/jira/browse/SLING-8278
 Project: Sling
  Issue Type: Improvement
  Components: Starter
Reporter: Ruben Reusser


google chrome audit currently lists a set of accessibility and seo problems 
with the sling starter content. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SLING-7058) the stop command line option does not seem to work

2017-08-17 Thread Ruben Reusser (JIRA)

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

Ruben Reusser commented on SLING-7058:
--

it seems this issue is due to the logic in 
https://github.com/apache/sling/blob/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/app/Main.java
 as it only initializes the ControlListener if the command start is passed to 
sling. This may of course be intentional

> the stop command line option does not seem to work
> --
>
> Key: SLING-7058
> URL: https://issues.apache.org/jira/browse/SLING-7058
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Reporter: Ruben Reusser
>Priority: Minor
>
> as per 
> https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html#command-line-options
>  a user should be able to stop a running sling instance by calling
> {code:java}
> java -jar sling-9.jar stop
> {code}
> Sling is supposed to write a file at startup with the chosen control port and 
> the secret key at 
> `$\{sling.home}/conf/controlport`
> I do not see that file created nor does the above command work to stop a 
> running sling instance. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (SLING-7058) the stop command line option does not seem to work

2017-08-17 Thread Ruben Reusser (JIRA)
Ruben Reusser created SLING-7058:


 Summary: the stop command line option does not seem to work
 Key: SLING-7058
 URL: https://issues.apache.org/jira/browse/SLING-7058
 Project: Sling
  Issue Type: Bug
  Components: Launchpad
Reporter: Ruben Reusser
Priority: Minor


as per 
https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html#command-line-options
 a user should be able to stop a running sling instance by calling

{code:java}
java -jar sling-9.jar stop
{code}

Sling is supposed to write a file at startup with the chosen control port and 
the secret key at 
`$\{sling.home}/conf/controlport`

I do not see that file created nor does the above command work to stop a 
running sling instance. 




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)