[jira] [Commented] (SLING-9773) Starter project does not build with the enforced minimum version of maven

[Konrad Windszus (Jira)]

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

Konrad Windszus commented on SLING-9773:


Indeed the plugin seems to require Maven 3.5.0. I opened 
https://github.com/bndtools/bnd/issues/4327 to get more clarity on this. Once I 
have feedback I will adjust the minimum Maven version for Sling Starter.

> Starter project does not build with the enforced minimum version of maven
> -
>
> Key: SLING-9773
> URL: https://issues.apache.org/jira/browse/SLING-9773
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Priority: Major
> Fix For: Starter 12
>
>
> The org-apache-sling-starter  project does not build with maven 3.3.9 which 
> is the current enforcer minimum version.
> The bnd-indexer-maven-plugin doesn't appear to work with maven 3.3.9 even 
> with the skip flag set to true.   It reports lots of nasty exceptions and 
> fails the build.
> I did some additional testing and it looks like maven version 3.5.0 is the 
> minimum version that seems to work.
> Do we need to enforce/change the minimum maven version required to build 
> sling to something newer than 3.3.9?



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

[jira] [Assigned] (SLING-9773) Starter project does not build with the enforced minimum version of maven

[Konrad Windszus (Jira)]

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

Konrad Windszus reassigned SLING-9773:
--

Assignee: Konrad Windszus

> Starter project does not build with the enforced minimum version of maven
> -
>
> Key: SLING-9773
> URL: https://issues.apache.org/jira/browse/SLING-9773
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Starter 12
>
>
> The org-apache-sling-starter  project does not build with maven 3.3.9 which 
> is the current enforcer minimum version.
> The bnd-indexer-maven-plugin doesn't appear to work with maven 3.3.9 even 
> with the skip flag set to true.   It reports lots of nasty exceptions and 
> fails the build.
> I did some additional testing and it looks like maven version 3.5.0 is the 
> minimum version that seems to work.
> Do we need to enforce/change the minimum maven version required to build 
> sling to something newer than 3.3.9?



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

[jira] [Resolved] (SLING-9774) The ValueMapUtil#merge behavior is different from the deprecated CompositeValueMap

[Eric Norman (Jira)]

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

Eric Norman resolved SLING-9774.

Resolution: Fixed

Fixed at: 
[https://github.com/apache/sling-org-apache-sling-api/commit/ebe211f16cc8d7ca6f1c61c9338674d8fcc99ad6]

Also added a new unit test to guard against future regressions.

> The ValueMapUtil#merge behavior is different from the deprecated 
> CompositeValueMap
> --
>
> Key: SLING-9774
> URL: https://issues.apache.org/jira/browse/SLING-9774
> Project: Sling
>  Issue Type: Bug
>Affects Versions: API 2.23.0
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: API 2.23.2
>
>
> CompositeValueMap has been marked as deprecated and the recommendation was to 
> replace those usages with ValueMapUtil#merge(ValueMap...)}
> Unfortunately it looks like implementation from ValueMapUtil#merge has 
> different behavior when it comes to handling of entries in the map where the 
> key is supplied but the value is null.
> My use case is that in a few places I have used the key=null behavior of 
> CompositeValueMap to hide entries in a wrapped ValueMap and those uses cases 
> don't work the same after switching to ValueMapUtil#merge(ValueMap...)}.
> To be compatible with the deprecated CompositeValueMap, the 
> MergingValueMap#get impl should not automatically filter entries whose value 
> is null.  Instead it should only filter when the value is null and the map 
> does not contain the key.   A null value doesn't always mean that the map 
> didn't have an entry for the key.



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

[jira] [Created] (SLING-9774) The ValueMapUtil#merge behavior is different from the deprecated CompositeValueMap

[Eric Norman (Jira)]

Eric Norman created SLING-9774:
--

 Summary: The ValueMapUtil#merge behavior is different from the 
deprecated CompositeValueMap
 Key: SLING-9774
 URL: https://issues.apache.org/jira/browse/SLING-9774
 Project: Sling
  Issue Type: Bug
Affects Versions: API 2.23.0
Reporter: Eric Norman
Assignee: Eric Norman
 Fix For: API 2.23.2


CompositeValueMap has been marked as deprecated and the recommendation was to 
replace those usages with ValueMapUtil#merge(ValueMap...)}

Unfortunately it looks like implementation from ValueMapUtil#merge has 
different behavior when it comes to handling of entries in the map where the 
key is supplied but the value is null.

My use case is that in a few places I have used the key=null behavior of 
CompositeValueMap to hide entries in a wrapped ValueMap and those uses cases 
don't work the same after switching to ValueMapUtil#merge(ValueMap...)}.

To be compatible with the deprecated CompositeValueMap, the MergingValueMap#get 
impl should not automatically filter entries whose value is null.  Instead it 
should only filter when the value is null and the map does not contain the key. 
  A null value doesn't always mean that the map didn't have an entry for the 
key.



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

Sling Model Persist

[Andreas Schaefer]

Hi

I am working on using JSon Schemas to create a dynamic Sling Model. For now on 
the frontend I am using JSonForms to display the content, edit and persist it.

It would be great to use the Dynamic Sling Model to persist the resource rather 
than having to use Post / Import. Ruben mention Sling Model Persist but I do 
not understand how to use it as there is no documentation nor a sample.

To obtain the data I use:

/.model.json

After editing the data it would be great if I could store it with a POST to an 
URL like this:

/.modelpersist.json

With the JSon Payload as request input stream.

As far as I can tell the Sling Model Persist still requires an additional 
endpoint like Servlet to persist the data.

Cheers - Andy

[jira] [Resolved] (SLING-8041) Inline kxml2 in the JCR Contentloader

[Eric Norman (Jira)]

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

Eric Norman resolved SLING-8041.

Resolution: Fixed

Marking this one as fixed as the work was already done

> Inline kxml2 in the JCR Contentloader
> -
>
> Key: SLING-8041
> URL: https://issues.apache.org/jira/browse/SLING-8041
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR ContentLoader 2.2.6
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: JCR ContentLoader 2.4.0
>
>
> It would be nice if we could inline the embedded kxml2 jar in the 
> contentloader to avoid extracting it into the framework cache.



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

[jira] [Commented] (SLING-9773) Starter project does not build with the enforced minimum version of maven

[Eric Norman (Jira)]

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

Eric Norman commented on SLING-9773:


[~kwin] Do you have any thoughts on this?

> Starter project does not build with the enforced minimum version of maven
> -
>
> Key: SLING-9773
> URL: https://issues.apache.org/jira/browse/SLING-9773
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Priority: Major
> Fix For: Starter 12
>
>
> The org-apache-sling-starter  project does not build with maven 3.3.9 which 
> is the current enforcer minimum version.
> The bnd-indexer-maven-plugin doesn't appear to work with maven 3.3.9 even 
> with the skip flag set to true.   It reports lots of nasty exceptions and 
> fails the build.
> I did some additional testing and it looks like maven version 3.5.0 is the 
> minimum version that seems to work.
> Do we need to enforce/change the minimum maven version required to build 
> sling to something newer than 3.3.9?



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

[jira] [Created] (SLING-9773) Starter project does not build with the enforced minimum version of maven

[Eric Norman (Jira)]

Eric Norman created SLING-9773:
--

 Summary: Starter project does not build with the enforced minimum 
version of maven
 Key: SLING-9773
 URL: https://issues.apache.org/jira/browse/SLING-9773
 Project: Sling
  Issue Type: Bug
Reporter: Eric Norman
 Fix For: Starter 12


The org-apache-sling-starter  project does not build with maven 3.3.9 which is 
the current enforcer minimum version.

The bnd-indexer-maven-plugin doesn't appear to work with maven 3.3.9 even with 
the skip flag set to true.   It reports lots of nasty exceptions and fails the 
build.


I did some additional testing and it looks like maven version 3.5.0 is the 
minimum version that seems to work.

Do we need to enforce/change the minimum maven version required to build sling 
to something newer than 3.3.9?



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

[jira] [Updated] (SLING-9771) Cleanup build warnings from bnd

[Eric Norman (Jira)]

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

Eric Norman updated SLING-9771:
---
Affects Version/s: Apache Sling Server Setup Tools 1.0.2

> Cleanup build warnings from bnd
> ---
>
> Key: SLING-9771
> URL: https://issues.apache.org/jira/browse/SLING-9771
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Apache Sling Server Setup Tools 1.0.2
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Server Setup Tools 1.0.4
>
>
> [INFO] --- bnd-maven-plugin:5.0.0:bnd-process (bnd-process) @ 
> org.apache.sling.testing.serversetup ---
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup.jarexec) that uses the default version 
> because no version is specified (1.0.2). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup.instance) that uses the default version 
> because no version is specified (1.0.2). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup) that uses the default version because 
> no version is specified (1.0.2). Remove duplicate package or add an explicit 
> version to it.



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

[jira] [Resolved] (SLING-9772) Cleanup build warnings from bnd

[Eric Norman (Jira)]

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

Eric Norman resolved SLING-9772.

Resolution: Fixed

Fixed at: 
https://github.com/apache/sling-org-apache-sling-testing-clients/commit/dfb790bf432a620b77c540357f1822c930234362

> Cleanup build warnings from bnd
> ---
>
> Key: SLING-9772
> URL: https://issues.apache.org/jira/browse/SLING-9772
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Apache Sling Testing Clients 2.0.4
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Testing Clients 2.0.6
>
>
> [INFO] --- bnd-maven-plugin:5.0.0:bnd-process (bnd-process) @ 
> org.apache.sling.testing.clients ---
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
> [0:0]: Invalid component name: Sling Testing Clients Query Servlet
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
> [0:0]: Unused Import-Package instructions: [org.apache.commons.exec.*]
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.clients.email) that uses the default version 
> because no version is specified (2.0.5). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.clients.indexing) that uses the default version 
> because no version is specified (2.0.5). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.clients.query) that uses the default version 
> because no version is specified (2.0.5). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.clients.query.servlet) that uses the default 
> version because no version is specified (2.0.5). Remove duplicate package or 
> add an explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.clients.util.config.impl) that uses the default 
> version because no version is specified (2.0.5). Remove duplicate package or 
> add an explicit version to it.
>  
>  



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

[jira] [Created] (SLING-9772) Cleanup build warnings from bnd

[Eric Norman (Jira)]

Eric Norman created SLING-9772:
--

 Summary: Cleanup build warnings from bnd
 Key: SLING-9772
 URL: https://issues.apache.org/jira/browse/SLING-9772
 Project: Sling
  Issue Type: Bug
Affects Versions: Apache Sling Testing Clients 2.0.4
Reporter: Eric Norman
Assignee: Eric Norman
 Fix For: Apache Sling Testing Clients 2.0.6


[INFO] --- bnd-maven-plugin:5.0.0:bnd-process (bnd-process) @ 
org.apache.sling.testing.clients ---
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
[0:0]: Invalid component name: Sling Testing Clients Query Servlet
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
[0:0]: Unused Import-Package instructions: [org.apache.commons.exec.*]
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.clients.email) that uses the default version because 
no version is specified (2.0.5). Remove duplicate package or add an explicit 
version to it.
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.clients.indexing) that uses the default version 
because no version is specified (2.0.5). Remove duplicate package or add an 
explicit version to it.
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.clients.query) that uses the default version because 
no version is specified (2.0.5). Remove duplicate package or add an explicit 
version to it.
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.clients.query.servlet) that uses the default version 
because no version is specified (2.0.5). Remove duplicate package or add an 
explicit version to it.
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-clients/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.clients.util.config.impl) that uses the default 
version because no version is specified (2.0.5). Remove duplicate package or 
add an explicit version to it.
 
 



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

[jira] [Updated] (SLING-9771) Cleanup build warnings from bnd

[Eric Norman (Jira)]

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

Eric Norman updated SLING-9771:
---
Fix Version/s: Apache Sling Server Setup Tools 1.0.4

> Cleanup build warnings from bnd
> ---
>
> Key: SLING-9771
> URL: https://issues.apache.org/jira/browse/SLING-9771
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Server Setup Tools 1.0.4
>
>
> [INFO] --- bnd-maven-plugin:5.0.0:bnd-process (bnd-process) @ 
> org.apache.sling.testing.serversetup ---
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup.jarexec) that uses the default version 
> because no version is specified (1.0.2). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup.instance) that uses the default version 
> because no version is specified (1.0.2). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup) that uses the default version because 
> no version is specified (1.0.2). Remove duplicate package or add an explicit 
> version to it.



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

[jira] [Resolved] (SLING-9771) Cleanup build warnings from bnd

[Eric Norman (Jira)]

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

Eric Norman resolved SLING-9771.

Resolution: Fixed

Fixed at: 
https://github.com/apache/sling-org-apache-sling-testing-serversetup/commit/e1866d6918e0fafafdfd2bba15fbfd360b0eaac9

> Cleanup build warnings from bnd
> ---
>
> Key: SLING-9771
> URL: https://issues.apache.org/jira/browse/SLING-9771
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
>
> [INFO] --- bnd-maven-plugin:5.0.0:bnd-process (bnd-process) @ 
> org.apache.sling.testing.serversetup ---
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup.jarexec) that uses the default version 
> because no version is specified (1.0.2). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup.instance) that uses the default version 
> because no version is specified (1.0.2). Remove duplicate package or add an 
> explicit version to it.
> [WARNING] 
> /home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
> [0:0]: Export-Package duplicate package name 
> (org.apache.sling.testing.serversetup) that uses the default version because 
> no version is specified (1.0.2). Remove duplicate package or add an explicit 
> version to it.



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

[jira] [Created] (SLING-9771) Cleanup build warnings from bnd

[Eric Norman (Jira)]

Eric Norman created SLING-9771:
--

 Summary: Cleanup build warnings from bnd
 Key: SLING-9771
 URL: https://issues.apache.org/jira/browse/SLING-9771
 Project: Sling
  Issue Type: Bug
Reporter: Eric Norman
Assignee: Eric Norman


[INFO] --- bnd-maven-plugin:5.0.0:bnd-process (bnd-process) @ 
org.apache.sling.testing.serversetup ---
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.serversetup.jarexec) that uses the default version 
because no version is specified (1.0.2). Remove duplicate package or add an 
explicit version to it.
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.serversetup.instance) that uses the default version 
because no version is specified (1.0.2). Remove duplicate package or add an 
explicit version to it.
[WARNING] 
/home/enorman/projects/sling.git/org-apache-sling-testing-serversetup/bnd.bnd 
[0:0]: Export-Package duplicate package name 
(org.apache.sling.testing.serversetup) that uses the default version because no 
version is specified (1.0.2). Remove duplicate package or add an explicit 
version to it.



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

[jira] [Closed] (SLING-9756) Update to Sling Bundle Parent 39

[Eric Norman (Jira)]

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

Eric Norman closed SLING-9756.
--

Completed with the 2.0.4 release.

> Update to Sling Bundle Parent 39
> 
>
> Key: SLING-9756
> URL: https://issues.apache.org/jira/browse/SLING-9756
> Project: Sling
>  Issue Type: Sub-task
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Testing Clients 2.0.4
>
>
> Update to Sling Bundle Parent 39 so it can be compiled with java 11



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

[jira] [Closed] (SLING-9765) Stabilize the SlingClientWaitExistsTest#testWaitExistsTimeout test

[Eric Norman (Jira)]

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

Eric Norman closed SLING-9765.
--

Completed with the 2.0.4 release.

> Stabilize the SlingClientWaitExistsTest#testWaitExistsTimeout test
> --
>
> Key: SLING-9765
> URL: https://issues.apache.org/jira/browse/SLING-9765
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Testing Clients 2.0.4
>
>
> On fast hardware, the SlingClientWaitExistsTest#testWaitExistsTimeout test 
> fails regularly because the waitExists check is able to complete all 40 of 
> the checks within 1 second so the timeout is not triggered.
> Fix by increasing the waitCount to a bigger number that won't complete within 
> 1 second.



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

[jira] [Closed] (SLING-9757) Add configurable connection timeout for SlingClient

[Eric Norman (Jira)]

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

Eric Norman closed SLING-9757.
--

Completed with the 2.0.4 release.

> Add configurable connection timeout for SlingClient
> ---
>
> Key: SLING-9757
> URL: https://issues.apache.org/jira/browse/SLING-9757
> Project: Sling
>  Issue Type: Improvement
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Testing Clients 2.0.4
>
>
> Occasionally during execution of test automation, the 
> SlingTestBase.waitForServerReady() call is getting stuck when the GET request 
> to check if the server is ready doesn't return a response in a timely manner.
> To avoid these bad requests hanging indefinitely, it should be possible to 
> configure a connection timeout.
> Add handling of a new "sling.client.connection.timeout.seconds" system 
> property so the user can supply the connection timeout duration in seconds.



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

[jira] [Closed] (SLING-9760) Query parameters are not handled in the server.ready.path parsing

[Eric Norman (Jira)]

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

Eric Norman closed SLING-9760.
--

Completed with the 1.0.2 release

> Query parameters are not handled in the server.ready.path parsing
> -
>
> Key: SLING-9760
> URL: https://issues.apache.org/jira/browse/SLING-9760
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Server Setup Tools 1.0.2
>
>
> If the server ready path contains parameters, like a heath check address, the 
> query parameters were not passed along in the GET request:
>  
> For example, this should work:
> /system/health?tags=bundlesformat=json:All 51 
> bundles are content loaded
>  



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

[jira] [Closed] (SLING-9764) Support regex pattern matching of the content for the server.ready.path checks

[Eric Norman (Jira)]

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

Eric Norman closed SLING-9764.
--

Completed with the 1.0.2 release

> Support regex pattern matching of the content for the server.ready.path checks
> --
>
> Key: SLING-9764
> URL: https://issues.apache.org/jira/browse/SLING-9764
> Project: Sling
>  Issue Type: Improvement
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Server Setup Tools 1.0.2
>
>
> Check for a third segment in the property value and if the value is "regexp" 
> then use the get#checkContentRegexp api instead of the 
> get#checkContentContains api to check if the content contains the value.
> For example if you want to use the heath check path to determine if all 
> required services are available but you don't want to hard code the number of 
> required services, you could use something like this to check for the 
> expected pattern: 
>  
> {code:java}
> /system/health?tags=systemaliveformat=json:All \d+ 
> required services are available:regexp{code}
>  



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

[jira] [Closed] (SLING-9759) convert the bundle install and start timeout system property values to milliseconds

[Eric Norman (Jira)]

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

Eric Norman closed SLING-9759.
--

Completed with the 1.0.2 release

> convert the bundle install and start timeout system property values to 
> milliseconds
> ---
>
> Key: SLING-9759
> URL: https://issues.apache.org/jira/browse/SLING-9759
> Project: Sling
>  Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Server Setup Tools 1.0.2
>
>
> BundlesInstaller#waitBundlesInstalled and BundlesInstaller#startAllBundles 
> expect the timeout duration to be in milliseconds
> However, SlingTestBase#installAdditionalBundles is readying the 
> BUNDLE_INSTALL_TIMEOUT_SECONDS and START_BUNDLES_TIMEOUT_SECONDS system 
> properties and not converting the duration from seconds to milliseconds



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

[jira] [Closed] (SLING-9758) Update to Sling Bundle Parent 39

[Eric Norman (Jira)]

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

Eric Norman closed SLING-9758.
--

Completed with the 1.0.2 release

> Update to Sling Bundle Parent 39
> 
>
> Key: SLING-9758
> URL: https://issues.apache.org/jira/browse/SLING-9758
> Project: Sling
>  Issue Type: Sub-task
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Apache Sling Server Setup Tools 1.0.2
>
>
> Update to Sling Bundle Parent 39 so it can be compiled with java 11



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

[RESULT] [VOTE] Release Apache Sling Server Setup Tools 1.0.2, Apache Sling Testing Clients 2.0.4

[Eric Norman]

Hi,

The vote has passed with the following result :

+1 (binding): Eric Norman, Daniel Klco, Robert Munteanu
+1 (non binding): Andreas Schaefer

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

Re: [VOTE] Release Apache Sling Pipes 4.0.0

[davidb]

+1

David

On Saturday, 26 September 2020, Carsten Ziegeler 
wrote:

> +1
>
> Carsten
>
> Am 25.09.2020 um 23:49 schrieb Nicolas Peltier:
>
>> Hi,
>>
>> We solved 14 issues in this release:
>> https://issues.apache.org/jira/projects/SLING/versions/12344958
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-2344/
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.
>> git;a=blob;f=check_staged_release.sh;hb=HEAD
>>
>> Usage:
>> sh check_staged_release.sh 2344 /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,
>> Nicolas Peltier
>>
>>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

Re: [VOTE] Release Apache Sling Scripting Core 2.3.4

[Karl Pauls]

+1

regards,

Karl

On Saturday, September 26, 2020, Georg Henzler  wrote:

> +1
>
> -Georg
>
> On 2020-09-25 20:14, Radu Cotescu wrote:
>
>> Hi,
>>
>> We solved 3 issues in this release:
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348630
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-2340/
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.
>> git;a=blob;f=check_staged_release.sh;hb=HEAD
>>
>> Usage:
>> sh check_staged_release.sh 2340 /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,
>> Radu Cotescu
>>
>

-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Scripting HTL Compiler 1.2.8-1.4.0, Apache Sling Scripting HTL Java Compiler 1.2.2-1.4.0, Apache Sling Scripting HTL Engine 1.4.4-1.4.0, Apache Sling Scripting HTL Runt

[Karl Pauls]

+1

regards,

Karl

On Saturday, September 26, 2020, Georg Henzler  wrote:

> +1
>
> -Georg
>
> On 2020-09-25 20:32, Radu Cotescu wrote:
>
>> Hi,
>>
>> We solved 6 issues in these releases:
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348731
>> 
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348730
>> 
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348726
>> 
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348719
>> 
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348751
>> 
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348732
>> 
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12348677
>> 
>>
>> Staging repositories:
>> https://repository.apache.org/content/repositories/orgapachesling-2341
>> 
>> https://repository.apache.org/content/repositories/orgapachesling-2342
>> 
>> https://repository.apache.org/content/repositories/orgapachesling-2343
>> 
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.
>> git;a=blob;f=check_staged_release.sh;hb=HEAD
>>
>> Usage:
>> sh check_staged_release.sh 2341 /tmp/sling-staging
>> sh check_staged_release.sh 2342 /tmp/sling-staging
>> sh check_staged_release.sh 2343 /tmp/sling-staging
>>
>> Running the tests from Apache Sling Scripting HTL Testing 1.0.24-1.4.0
>> requires Apache Sling Scripting Core 2.3.4, currently under release as
>> well.
>>
>> 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,
>> Radu Cotescu
>>
>

-- 
Karl Pauls
karlpa...@gmail.com