Re: [VOTE] Release Apache Sling Testing Clients version 2.0.8

2020-11-10 Thread Eric Norman
+1

On Tue, Nov 10, 2020 at 6:02 AM Andrei Dulvac  wrote:

> Hi, We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12349274  Staging
> repository:
> https://repository.apache.org/content/repositories/orgapachesling-2372/
> 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 2372 /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.
>


Can we Un-deprecate SlingAnnotationsTestRunner ?

2020-11-10 Thread Cris Rockwell
Hi Sling Dev

SlingAnnotationsTestRunner is one of my favorite ways to test because it make 
my life simpler when doing Test Driven Development in Sling. Using this tool I 
have had fewer setup and dependency problems because it runs in the instance I 
develop and deploy to. SlingAnnotationsTestRunner can run JUnit tests in any of 
my various Sling instances (local, staging and production), which is super 
handy when diagnosing and troubleshooting remote server problems. QA, Ops, 
Admins and developers can easily run the JUnit tests after updates and restarts 
using the web-based user interface.

Unfortunately SlingAnnotationsTestRunner was marked as deprecated in 2015 
stating "TeleporterRule is a much simpler way of executing”  That maybe true in 
your experience, but TeleporterRule does not provide me the same value. IMO 
project developers should have a choice whether to use 
SlingAnnotationsTestRunner or TeleporterRule for their project. For some 
TeleporterRule may be better indeed. For me, SlingAnnotationsTestRunner is 
perfect when I’m trying to develop projects in Sling. 
SlingAnnotationsTestRunner Junit tests do not increase Maven build speed, and 
the UI allows me to run all the tests or just the ones I want. 

In summary, could I please volunteer to keep SlingAnnotationsTestRunner.java 
alive, supported and not deprecated?

Regards
Cris 

https://github.com/apache/sling-org-apache-sling-junit-core/blob/master/src/main/java/org/apache/sling/junit/annotations/SlingAnnotationsTestRunner.java



Re: Two "adapter annotations" module, deprecate the old one?

2020-11-10 Thread Bertrand Delacretaz
Hi,

I have implemented the below plan, the update to
https://sling.apache.org/downloads.cgi is not live yet.

-Bertrand

On Tue, Nov 10, 2020 at 1:24 PM Bertrand Delacretaz
 wrote:
> ...So I suggest:
>
> 1) Renaming the adapter-annotations-1.0.0 section to "Adapter
> Annotations (JSON)" at https://sling.apache.org/downloads.cgi and
> changing the name in its source code (pom and README), including a
> link to the new module
>
> 2) Releasing the new module as "Adapter Annotations 2.0.0"
>
> 3) Mentioning both modules and their difference using the new names at
> https://github.com/apache/sling-org-apache-sling-adapter-annotations
>
> I think that's a reasonable plan, or is anything missing? ...


[jira] [Commented] (SLING-9890) Document the new adapter-annotations module

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz commented on SLING-9890:


The docs should mention both this 
https://github.com/apache/sling-org-apache-sling-adapter-annotations module and 
the older https://github.com/apache/sling-adapter-annotations one and explain 
the difference between them.

> Document the new adapter-annotations module
> ---
>
> Key: SLING-9890
> URL: https://issues.apache.org/jira/browse/SLING-9890
> Project: Sling
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: Adapter Annotations 2.0.0
>Reporter: Bertrand Delacretaz
>Assignee: Henry Kuijpers
>Priority: Major
> Fix For: Adapter Annotations 2.0.2
>
>
> The new 
> [https://github.com/apache/sling-org-apache-sling-adapter-annotations] module 
> needs to be documented at 
> [https://sling.apache.org/documentation/the-sling-engine/adapters.html]
> That page can either briefly mention the module and point to its README for 
> more info, or include the full documentation.
> I'm assigning this ticket to [~Henry Kuijpers] who volunteered in SLING-2938



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


Re: [VOTE] Release Apache Sling Settings 1.4.2

2020-11-10 Thread Eric Norman
+1

On Sat, Nov 7, 2020 at 4:05 AM Oliver Lietz  wrote:

> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12348652
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-2370
>
> 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 2370 /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,
> O.
>
>
>
>
>


[jira] [Commented] (SLING-2938) AdapterMethods annotation and adapter proxy service

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz commented on SLING-2938:


I have now started the release vote for Sling Adapter Annotations 2.0.0 and 
renamed the older module with a "(JSON)" suffix for clarity, in the pom and 
README at [https://github.com/apache/sling-adapter-annotations] and at 
https://sling.apache.org/downloads.cgi

> AdapterMethods annotation and adapter proxy service
> ---
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter 2.1.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Adapter Annotations 2.0.0
>
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've 
> been working on an @AdapterMethod annotation that makes it easier to create 
> Sling adapters, as in
>   @Component
>   @Service
>   public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
>   }
> As this requires changes to the sling.api bundle, I'll commit to my 
> whiteboard first, for review



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


[VOTE] Release Sling Adapter Annotations 2.0.0

2020-11-10 Thread Bertrand Delacretaz
Hi,

This is a new module, at
https://github.com/apache/sling-org-apache-sling-adapter-annotations

...not to be confused with the older
https://github.com/apache/sling-adapter-annotations module, which I
have renamed with a (JSON) suffix for clarity.

There are still some outstanding issues:
https://issues.apache.org/jira/projects/SLING/versions/12349370

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

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

Here's my +1.

-Bertrand


[jira] [Updated] (SLING-9890) Document the new adapter-annotations module

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz updated SLING-9890:
---
Affects Version/s: (was: Adapter Annotations (JSON) 1.0.0)
   Adapter Annotations 2.0.0

> Document the new adapter-annotations module
> ---
>
> Key: SLING-9890
> URL: https://issues.apache.org/jira/browse/SLING-9890
> Project: Sling
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: Adapter Annotations 2.0.0
>Reporter: Bertrand Delacretaz
>Assignee: Henry Kuijpers
>Priority: Major
>
> The new 
> [https://github.com/apache/sling-org-apache-sling-adapter-annotations] module 
> needs to be documented at 
> [https://sling.apache.org/documentation/the-sling-engine/adapters.html]
> That page can either briefly mention the module and point to its README for 
> more info, or include the full documentation.
> I'm assigning this ticket to [~Henry Kuijpers] who volunteered in SLING-2938



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


[jira] [Updated] (SLING-9892) adapter-annotations integration tests sometimes fail

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz updated SLING-9892:
---
Affects Version/s: (was: Adapter Annotations (JSON) 1.0.0)
   Adapter Annotations 2.0.0

> adapter-annotations integration tests sometimes fail
> 
>
> Key: SLING-9892
> URL: https://issues.apache.org/jira/browse/SLING-9892
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter Annotations 2.0.0
>Reporter: Bertrand Delacretaz
>Priority: Minor
> Fix For: Adapter Annotations 2.0.2
>
>
> I have marked two such failing builds at 
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-adapter-annotations/job/master/]
>  as "keep forever", the error is apparently always
> {code}
> [INFO] [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time 
> elapsed: 11.235 s <<< FAILURE! - in 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT
> [INFO] [ERROR] org.apache.sling.adapter.annotations.AdapterRegistrationIT  
> Time elapsed: 11.21 s  <<< ERROR!
> [INFO] java.lang.RuntimeException: Could not read content from response
> [INFO]at 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
> [INFO] Caused by: org.apache.http.MalformedChunkCodingException: CRLF 
> expected at end of chunk
> [INFO]at 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
> [INFO] 
> {code}



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


[jira] [Updated] (SLING-9890) Document the new adapter-annotations module

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz updated SLING-9890:
---
Fix Version/s: Adapter Annotations 2.0.2

> Document the new adapter-annotations module
> ---
>
> Key: SLING-9890
> URL: https://issues.apache.org/jira/browse/SLING-9890
> Project: Sling
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: Adapter Annotations 2.0.0
>Reporter: Bertrand Delacretaz
>Assignee: Henry Kuijpers
>Priority: Major
> Fix For: Adapter Annotations 2.0.2
>
>
> The new 
> [https://github.com/apache/sling-org-apache-sling-adapter-annotations] module 
> needs to be documented at 
> [https://sling.apache.org/documentation/the-sling-engine/adapters.html]
> That page can either briefly mention the module and point to its README for 
> more info, or include the full documentation.
> I'm assigning this ticket to [~Henry Kuijpers] who volunteered in SLING-2938



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


[jira] [Updated] (SLING-9892) adapter-annotations integration tests sometimes fail

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz updated SLING-9892:
---
Fix Version/s: Adapter Annotations 2.0.2

> adapter-annotations integration tests sometimes fail
> 
>
> Key: SLING-9892
> URL: https://issues.apache.org/jira/browse/SLING-9892
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter Annotations (JSON) 1.0.0
>Reporter: Bertrand Delacretaz
>Priority: Minor
> Fix For: Adapter Annotations 2.0.2
>
>
> I have marked two such failing builds at 
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-adapter-annotations/job/master/]
>  as "keep forever", the error is apparently always
> {code}
> [INFO] [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time 
> elapsed: 11.235 s <<< FAILURE! - in 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT
> [INFO] [ERROR] org.apache.sling.adapter.annotations.AdapterRegistrationIT  
> Time elapsed: 11.21 s  <<< ERROR!
> [INFO] java.lang.RuntimeException: Could not read content from response
> [INFO]at 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
> [INFO] Caused by: org.apache.http.MalformedChunkCodingException: CRLF 
> expected at end of chunk
> [INFO]at 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
> [INFO] 
> {code}



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


[jira] [Updated] (SLING-2938) AdapterMethods annotation and adapter proxy service

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz updated SLING-2938:
---
Fix Version/s: Adapter Annotations 2.0.0

> AdapterMethods annotation and adapter proxy service
> ---
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter 2.1.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Adapter Annotations 2.0.0
>
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've 
> been working on an @AdapterMethod annotation that makes it easier to create 
> Sling adapters, as in
>   @Component
>   @Service
>   public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
>   }
> As this requires changes to the sling.api bundle, I'll commit to my 
> whiteboard first, for review



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


Re: [roundtable] Code coverage

2020-11-10 Thread Radu Cotescu
Hi Konrad,

Sorry for getting back so late - I was off for two weeks.

> On 24 Oct 2020, at 17:09, Konrad Windszus  wrote:
> 
> Hi Radu,
> I am wondering why we need to still generate reports for both unit and 
> integration test separately in 
> https://github.com/apache/sling-parent/blob/3e7b3edb7411440b6a5dcd4836da2c45f4cc7166/sling-parent/pom.xml#L509
>  
> .
> IMHO just generating the report after merging the exec files should be enough.

We *don’t* need to generate reports for both, but it could be useful in some 
setups to see how a project’s code is covered. Feel free to change the 
configuration if it takes too much time on the projects you’re working on.

> WDYT?
> Konrad
> 

Cheers,
Radu

[GitHub] [sling-org-apache-sling-feature-cpconverter] sonarcloud[bot] commented on pull request #34: SLING-9894 - setting explicit dependency from embedded to non-contain…

2020-11-10 Thread GitBox


sonarcloud[bot] commented on pull request #34:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/34#issuecomment-724848326


   Kudos, SonarCloud Quality Gate passed!
   
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=BUG)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=BUG)
 [0 
Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=BUG)
  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=VULNERABILITY)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=VULNERABILITY)
 [0 
Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=VULNERABILITY)
 (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter
 uest=34=false=SECURITY_HOTSPOT) [0 Security 
Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=SECURITY_HOTSPOT)
 to review)  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=CODE_SMELL)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=CODE_SMELL)
 [4 Code 
Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=34=false=CODE_SMELL)
   
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=34=new_coverage=list)
 [94.4% 
Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=34=new_coverage=list)
  
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=34=new_duplicated_lines_density=list)
 [0.0% 
Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=34=new_duplicated_lines_density=list)
   
The version of Java (1.8.0_252) you 
have used to run this analysis is deprecated and we will stop accepting it 
accepting it soon.Please update to at least Java 11.
   Read more [here](https://sonarcloud.io/documentation/upcoming/)
   
   
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] DominikSuess opened a new pull request #34: SLING-9894 - setting explicit dependency from embedded to non-contain…

2020-11-10 Thread GitBox


DominikSuess opened a new pull request #34:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/34


   …er parent to ensure same install order as in osgi installer (implicit 
ordering)



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Created] (SLING-9894) CP Converter not defining explicit dependency of embedded package on parent

2020-11-10 Thread Jira
Dominik Süß created SLING-9894:
--

 Summary: CP Converter not defining explicit dependency of embedded 
package on parent
 Key: SLING-9894
 URL: https://issues.apache.org/jira/browse/SLING-9894
 Project: Sling
  Issue Type: Bug
  Components: Content-Package to Feature Model Converter
Affects Versions: Content-Package to Feature Model Converter 1.0.16
Reporter: Dominik Süß


An embedded package of a non-container package (/libs/xy/install) when 
installed via OSGI installer will always be installed after the parent package 
even when there is no explicit dependency. The converter misses to convert this 
implicit dependency into an explict dependency which can cause the order to 
differ and therefore cause oversights of ordering issues. To align this 
packages need to set up an explicit dependency to a parent package unless this 
is a container package which would be treated as non-existing and therefore 
removed.



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


[GitHub] [sling-org-apache-sling-feature-cpconverter] rombert commented on pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


rombert commented on pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#issuecomment-724815672


   @kwin - we settled on a 'squash, rebase and merge' approach which is not 
possible with the GitHub UI, see the "Merging pull requests from contributors" 
section in 
https://cwiki.apache.org/confluence/display/SLING/Using+Git+with+Sling .



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] kwin commented on pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


kwin commented on pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#issuecomment-724813809


   @rombert Why not using 
https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squash-and-merge-your-pull-request-commits?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] rombert commented on pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


rombert commented on pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#issuecomment-724797688


   @DominikSuess  - can you please force-push a single commit with all the 
changes? I will then merge



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Updated] (SLING-9881) CPConverter dropping type information on sling:OsgiConfig nodes

2020-11-10 Thread A. J. David Bosschaert (Jira)


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

A. J. David Bosschaert updated SLING-9881:
--
Fix Version/s: Content-Package to Feature Model Converter 1.1.2

> CPConverter dropping type information on sling:OsgiConfig nodes
> ---
>
> Key: SLING-9881
> URL: https://issues.apache.org/jira/browse/SLING-9881
> Project: Sling
>  Issue Type: Bug
>  Components: Content-Package to Feature Model Converter
>Affects Versions: Content-Package to Feature Model Converter 1.0.16
>Reporter: Dominik Süß
>Priority: Critical
> Fix For: Content-Package to Feature Model Converter 1.1.2
>
>
> The implementation of the converter for sling:OsgiConfig nodes 
> (XmlConfigurationEntryHandler) currently ignores the type of the properties 
> and transforms everything into Strings (as DocViewProperty returns values as 
> String representations with separate type property).
> This leads to broken configurations in case of the use of those config nodes 
> with typed properties.



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


[jira] [Updated] (SLING-9881) CPConverter dropping type information on sling:OsgiConfig nodes

2020-11-10 Thread A. J. David Bosschaert (Jira)


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

A. J. David Bosschaert updated SLING-9881:
--
Fix Version/s: (was: Content-Package to Feature Model Converter 1.1.2)
   Content-Package to Feature Model Converter 1.1.0

> CPConverter dropping type information on sling:OsgiConfig nodes
> ---
>
> Key: SLING-9881
> URL: https://issues.apache.org/jira/browse/SLING-9881
> Project: Sling
>  Issue Type: Bug
>  Components: Content-Package to Feature Model Converter
>Affects Versions: Content-Package to Feature Model Converter 1.0.16
>Reporter: Dominik Süß
>Priority: Critical
> Fix For: Content-Package to Feature Model Converter 1.1.0
>
>
> The implementation of the converter for sling:OsgiConfig nodes 
> (XmlConfigurationEntryHandler) currently ignores the type of the properties 
> and transforms everything into Strings (as DocViewProperty returns values as 
> String representations with separate type property).
> This leads to broken configurations in case of the use of those config nodes 
> with typed properties.



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


[jira] [Updated] (SLING-9692) Add support for principal-based access control entries

2020-11-10 Thread A. J. David Bosschaert (Jira)


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

A. J. David Bosschaert updated SLING-9692:
--
Fix Version/s: (was: Content-Package to Feature Model Converter 1.1.0)
   Content-Package to Feature Model Converter 1.1.2

> Add support for principal-based access control entries
> --
>
> Key: SLING-9692
> URL: https://issues.apache.org/jira/browse/SLING-9692
> Project: Sling
>  Issue Type: Improvement
>  Components: Content-Package to Feature Model Converter
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.2
>
>
> When passed a content package that contains principal-based access control 
> entries, the converter ignores them. It should instead generate the proper 
> repoinit statements.



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


[jira] [Resolved] (SLING-9891) Content Package to Feature Model converter does not work on Windows

2020-11-10 Thread A. J. David Bosschaert (Jira)


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

A. J. David Bosschaert resolved SLING-9891.
---
Resolution: Fixed

> Content Package to Feature Model converter does not work on Windows
> ---
>
> Key: SLING-9891
> URL: https://issues.apache.org/jira/browse/SLING-9891
> Project: Sling
>  Issue Type: Bug
>  Components: Content-Package to Feature Model Converter
>Affects Versions: Content-Package to Feature Model Converter 1.0.16
>Reporter: A. J. David Bosschaert
>Assignee: A. J. David Bosschaert
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.0
>
>
> Run `mvn install` in the project on Windows and you'll see.
> There are 2 main problems:
>  * The {{java.nio.Path}} implementation chosen to represent Repository paths, 
> does not accept all valid repository paths when run with the Windows 
> implementation.
>  * The test cases use Unix line separators in string comparisons which on 
> Windows don't match



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


[GitHub] [sling-org-apache-sling-feature-cpconverter] rombert commented on a change in pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


rombert commented on a change in pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#discussion_r520663352



##
File path: 
src/main/java/org/apache/sling/feature/cpconverter/handlers/XmlConfigurationEntryHandler.java
##
@@ -65,13 +74,77 @@ protected void onJcrRootElement(String uri, String 
localName, String qName, Attr
 
 if (attributeValue != null && !attributeValue.isEmpty()) {
 DocViewProperty property = 
DocViewProperty.parse(attributeQName, attributeValue);
-
+Object value = property.values;
+List strValues = 
Arrays.asList(property.values);
+switch (property.type) {
+case PropertyType.DATE:
+// Date was never properly supported as osgi 
configs don't support dates so converting to millis 
+// Scenario should just be theoretical
+attributeQName += ":Long";
+value = Lists.transform(strValues, new 
Function() {
+   public Long apply(String s) {
+  Long res = null;
+  if (s != null) {
+   Calendar cal = ISO8601.parse(s);
+   if (cal != null) {
+   res = cal.getTimeInMillis();
+   }
+  } 
+  return res;
+   }
+}).toArray();
+break;
+case PropertyType.DOUBLE:
+attributeQName += ":Double";
+value = Lists.transform(strValues, new 
Function() {
+   public Double apply(String s) {
+  Double res = null;
+  try {
+  res = Double.parseDouble(s);
+  } catch ( NumberFormatException ex ){
+  // ignore as nonexisting

Review comment:
   Great, thanks!





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




Re: [VOTE] Release Apache Sling Testing Clients version 2.0.8

2020-11-10 Thread Daniel Klco
+1

On Tue, Nov 10, 2020 at 9:02 AM Andrei Dulvac  wrote:
>
> Hi, We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12349274  Staging
> repository:
> https://repository.apache.org/content/repositories/orgapachesling-2372/
> 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 2372 /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.


[VOTE] Release Apache Sling Testing Clients version 2.0.8

2020-11-10 Thread Andrei Dulvac
Hi, We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12349274  Staging
repository:
https://repository.apache.org/content/repositories/orgapachesling-2372/
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 2372 /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.


[GitHub] [sling-org-apache-sling-feature-cpconverter] DominikSuess commented on a change in pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


DominikSuess commented on a change in pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#discussion_r520572507



##
File path: 
src/main/java/org/apache/sling/feature/cpconverter/handlers/XmlConfigurationEntryHandler.java
##
@@ -65,13 +74,77 @@ protected void onJcrRootElement(String uri, String 
localName, String qName, Attr
 
 if (attributeValue != null && !attributeValue.isEmpty()) {
 DocViewProperty property = 
DocViewProperty.parse(attributeQName, attributeValue);
-
+Object value = property.values;
+List strValues = 
Arrays.asList(property.values);
+switch (property.type) {
+case PropertyType.DATE:
+// Date was never properly supported as osgi 
configs don't support dates so converting to millis 
+// Scenario should just be theoretical
+attributeQName += ":Long";
+value = Lists.transform(strValues, new 
Function() {
+   public Long apply(String s) {
+  Long res = null;
+  if (s != null) {
+   Calendar cal = ISO8601.parse(s);
+   if (cal != null) {
+   res = cal.getTimeInMillis();
+   }
+  } 
+  return res;
+   }
+}).toArray();
+break;
+case PropertyType.DOUBLE:
+attributeQName += ":Double";
+value = Lists.transform(strValues, new 
Function() {
+   public Double apply(String s) {
+  Double res = null;
+  try {
+  res = Double.parseDouble(s);
+  } catch ( NumberFormatException ex ){
+  // ignore as nonexisting

Review comment:
   @rombert ok - in theory they shouldn't exist but yes you are right if 
somebody crafted  a broken vault package that may happen - I can make this 
throw an exception.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Resolved] (SLING-9855) Invalidate login token when receiving 401

2020-11-10 Thread Andrei Dulvac (Jira)


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

Andrei Dulvac resolved SLING-9855.
--
Resolution: Fixed

> Invalidate login token when receiving 401
> -
>
> Key: SLING-9855
> URL: https://issues.apache.org/jira/browse/SLING-9855
> Project: Sling
>  Issue Type: Improvement
>  Components: Apache Sling Testing Clients
>Affects Versions: Apache Sling Testing Clients 2.0.6
>Reporter: Andrei Tuicu
>Assignee: Andrei Dulvac
>Priority: Major
> Fix For: Apache Sling Testing Clients 2.0.8
>
>
> h3. Story
> The Sling testing clients should invalidate login token when receiving 401, 
> so that subsequent requests get a fresh token. Retrying requests with a token 
> for which we already got a 401 response are very likely to continue to fail.
> h3. Acceptance Criteria
> * The login token is invalidated in the client when Sling responds with 401
> cc [~andrei.dulvac]



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


[GitHub] [sling-org-apache-sling-feature-cpconverter] bosschaert merged pull request #33: SLING-9891 Replace java.nio.Path with new RepoPath class.

2020-11-10 Thread GitBox


bosschaert merged pull request #33:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/33


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Resolved] (SLING-9889) Slingfeature-Maven-Plugin: Fix failing ITs

2020-11-10 Thread Carsten Ziegeler (Jira)


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

Carsten Ziegeler resolved SLING-9889.
-
Resolution: Fixed

The tests where indeed buggy. Fixed in 
https://github.com/apache/sling-slingfeature-maven-plugin/commit/a91761e3e10df9d76ae8001b8d98ab1e63732e59

> Slingfeature-Maven-Plugin: Fix failing ITs
> --
>
> Key: SLING-9889
> URL: https://issues.apache.org/jira/browse/SLING-9889
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
> are failing:
> {code}
> [ERROR] The following builds failed:
> [ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
> [ERROR] *  apis-jar-wrapper-bundle/pom.xml
> [ERROR] *  apis-jar/pom.xml
> {code}
> (https://ci-builds.apache.org/job/Sling/job/modules/job/sling-slingfeature-maven-plugin/job/master/48/console)



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


Re: Two "adapter annotations" module, deprecate the old one?

2020-11-10 Thread Bertrand Delacretaz
On Tue, Nov 10, 2020 at 12:59 PM Konrad Windszus  wrote:
> ...Renaming is a good idea to make it clearer but I would rather rename the 
> old one
> to make it clear that this generates a JSON!..

I like the idea but that module is already out as "Apache Sling
Adapter Annotations 1.0.0", a name which we cannot change in the
release.

So I suggest:

1) Renaming the adapter-annotations-1.0.0 section to "Adapter
Annotations (JSON)" at https://sling.apache.org/downloads.cgi and
changing the name in its source code (pom and README), including a
link to the new module

2) Releasing the new module as "Adapter Annotations 2.0.0"

3) Mentioning both modules and their difference using the new names at
https://github.com/apache/sling-org-apache-sling-adapter-annotations

I think that's a reasonable plan, or is anything missing?

-Bertrand


[GitHub] [sling-org-apache-sling-testing-clients] andreituicu closed pull request #19: In case the logintoken cookie is no longer valid, try obtaining a new one.

2020-11-10 Thread GitBox


andreituicu closed pull request #19:
URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/19


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-testing-clients] andreituicu commented on pull request #19: In case the logintoken cookie is no longer valid, try obtaining a new one.

2020-11-10 Thread GitBox


andreituicu commented on pull request #19:
URL: 
https://github.com/apache/sling-org-apache-sling-testing-clients/pull/19#issuecomment-724667371


   sounds good to me.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Commented] (SLING-9889) Slingfeature-Maven-Plugin: Fix failing ITs

2020-11-10 Thread Carsten Ziegeler (Jira)


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

Carsten Ziegeler commented on SLING-9889:
-

Thanks, I'll have a look


> Slingfeature-Maven-Plugin: Fix failing ITs
> --
>
> Key: SLING-9889
> URL: https://issues.apache.org/jira/browse/SLING-9889
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
> are failing:
> {code}
> [ERROR] The following builds failed:
> [ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
> [ERROR] *  apis-jar-wrapper-bundle/pom.xml
> [ERROR] *  apis-jar/pom.xml
> {code}
> (https://ci-builds.apache.org/job/Sling/job/modules/job/sling-slingfeature-maven-plugin/job/master/48/console)



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


[jira] [Created] (SLING-9893) Update Karaf to 4.3.1

2020-11-10 Thread Oliver Lietz (Jira)
Oliver Lietz created SLING-9893:
---

 Summary: Update Karaf to 4.3.1
 Key: SLING-9893
 URL: https://issues.apache.org/jira/browse/SLING-9893
 Project: Sling
  Issue Type: Task
  Components: Karaf
Reporter: Oliver Lietz
Assignee: Oliver Lietz
 Fix For: Karaf Launchpad Integration Tests (Oak Tar) 0.0.12, Karaf 
Integration Tests 1.0.0, Karaf Distribution 1.0.0, Karaf Features 1.0.0






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


Re: Two "adapter annotations" module, deprecate the old one?

2020-11-10 Thread Konrad Windszus
These annotations serve different purposes for details refer to 
https://issues.apache.org/jira/browse/SLING-2938?focusedCommentId=17196213=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17196213
 

Renaming is a good idea to make it clearer but I would rather rename the old 
one to make it clear that this generates a JSON!

Konrad

> On 10. Nov 2020, at 12:56, Bertrand Delacretaz  wrote:
> 
> Hi,
> 
> In https://issues.apache.org/jira/browse/SLING-2938 Henry Kuijpers has
> contributed a new module [1] for adapter annotations, that uses the
> OSGi DS 1.4 component property type annotations, making it easier to
> generate adaptable classes.
> 
> I was about to make a first release but noticed the older module at
> [2] with the same short name, which has been released as "Apache Sling
> Adapter Annotations 1.0.0". And hasn't had any changes under "src"
> since commit d9592e457100f7e7fe60bb2618720f846e02b471 on  Wed Jul 24
> 2013.
> 
> I'm not sure how to best handle this to avoid confusion, we might:
> 
> a) Release the new module as "Apache Sling Adapter Annotations 2.0.0"
> and deprecate the old one (my preferred choice)
> b) Rename the new module to avoid confusion, but which name to use?
> 
> What do people think?
> 
> -Bertrand
> 
> [1] new module:
> https://github.com/apache/sling-org-apache-sling-adapter-annotations
> [2] old module: https://github.com/apache/sling-adapter-annotations module



[jira] [Comment Edited] (SLING-2938) AdapterMethods annotation and adapter proxy service

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz edited comment on SLING-2938 at 11/10/20, 11:58 AM:


[~kwin] wrote:
{quote}(the existing) [https://github.com/apache/sling-adapter-annotations] is 
used by 
[https://sling.apache.org/components/sling-maven-plugin/generate-adapter-metadata-mojo.html]
 to build JSON metadata (only evaluated in the Felix WebConsole). It won't 
generate the actual SCR definitions. Compare also with 
[https://sling.apache.org/documentation/the-sling-engine/adapters.html#implementing-adaptable].
{quote}
Turns out that [that old 
module|https://github.com/apache/sling-adapter-annotations] was already 
released as "Adapter Annotations 1.0.0" so we need at least to bump the version 
to 2.0.0 for the [new 
module|https://github.com/apache/sling-org-apache-sling-adapter-annotations], 
or change its name to avoid confusion. I'll [discuss on our dev 
list|https://lists.apache.org/thread.html/rc9ddd78b8cebf501e24c064afaa4c3cd152589f22480837aeb1c741a%40%3Cdev.sling.apache.org%3E].

I had already created the staging repo at 
[https://repository.apache.org/content/repositories/orgapachesling-2371] when I 
noticed that potential confusion, will delete it once we agree on how to 
release the new module.


was (Author: bdelacretaz):
[~kwin] wrote:

bq. (the existing) https://github.com/apache/sling-adapter-annotations is used 
by 
https://sling.apache.org/components/sling-maven-plugin/generate-adapter-metadata-mojo.html
 to build JSON metadata (only evaluated in the Felix WebConsole). It won't 
generate the actual SCR definitions. Compare also with 
https://sling.apache.org/documentation/the-sling-engine/adapters.html#implementing-adaptable.

Turns out that [that old 
module|https://github.com/apache/sling-adapter-annotations] was already 
released as "Adapter Annotations 1.0.0" so we need at least to bump the version 
to 2.0.0 for the [new 
module|https://github.com/apache/sling-org-apache-sling-adapter-annotations], 
or change its name to avoid confusion. I'll discuss on our dev list.

I had already created the staging repo at 
https://repository.apache.org/content/repositories/orgapachesling-2371 when I 
noticed that potential confusion, will delete it once we agree on how to 
release the new module.

> AdapterMethods annotation and adapter proxy service
> ---
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter 2.1.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've 
> been working on an @AdapterMethod annotation that makes it easier to create 
> Sling adapters, as in
>   @Component
>   @Service
>   public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
>   }
> As this requires changes to the sling.api bundle, I'll commit to my 
> whiteboard first, for review



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


[jira] [Resolved] (SLING-9668) Make clamd service a content analyzer

2020-11-10 Thread Oliver Lietz (Jira)


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

Oliver Lietz resolved SLING-9668.
-
Resolution: Done

> Make clamd service a content analyzer
> -
>
> Key: SLING-9668
> URL: https://issues.apache.org/jira/browse/SLING-9668
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: Commons Clam 2.0.2
>
>




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


Two "adapter annotations" module, deprecate the old one?

2020-11-10 Thread Bertrand Delacretaz
Hi,

In https://issues.apache.org/jira/browse/SLING-2938 Henry Kuijpers has
contributed a new module [1] for adapter annotations, that uses the
OSGi DS 1.4 component property type annotations, making it easier to
generate adaptable classes.

I was about to make a first release but noticed the older module at
[2] with the same short name, which has been released as "Apache Sling
Adapter Annotations 1.0.0". And hasn't had any changes under "src"
since commit d9592e457100f7e7fe60bb2618720f846e02b471 on  Wed Jul 24
2013.

I'm not sure how to best handle this to avoid confusion, we might:

a) Release the new module as "Apache Sling Adapter Annotations 2.0.0"
and deprecate the old one (my preferred choice)
b) Rename the new module to avoid confusion, but which name to use?

What do people think?

-Bertrand

[1] new module:
https://github.com/apache/sling-org-apache-sling-adapter-annotations
[2] old module: https://github.com/apache/sling-adapter-annotations module


[jira] [Commented] (SLING-2938) AdapterMethods annotation and adapter proxy service

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz commented on SLING-2938:


[~kwin] wrote:

bq. (the existing) https://github.com/apache/sling-adapter-annotations is used 
by 
https://sling.apache.org/components/sling-maven-plugin/generate-adapter-metadata-mojo.html
 to build JSON metadata (only evaluated in the Felix WebConsole). It won't 
generate the actual SCR definitions. Compare also with 
https://sling.apache.org/documentation/the-sling-engine/adapters.html#implementing-adaptable.

Turns out that [that old 
module|https://github.com/apache/sling-adapter-annotations] was already 
released as "Adapter Annotations 1.0.0" so we need at least to bump the version 
to 2.0.0 for the [new 
module|https://github.com/apache/sling-org-apache-sling-adapter-annotations], 
or change its name to avoid confusion. I'll discuss on our dev list.

I had already created the staging repo at 
https://repository.apache.org/content/repositories/orgapachesling-2371 when I 
noticed that potential confusion, will delete it once we agree on how to 
release the new module.

> AdapterMethods annotation and adapter proxy service
> ---
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter 2.1.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've 
> been working on an @AdapterMethod annotation that makes it easier to create 
> Sling adapters, as in
>   @Component
>   @Service
>   public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
>   }
> As this requires changes to the sling.api bundle, I'll commit to my 
> whiteboard first, for review



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


[jira] [Commented] (SLING-9891) Content Package to Feature Model converter does not work on Windows

2020-11-10 Thread A. J. David Bosschaert (Jira)


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

A. J. David Bosschaert commented on SLING-9891:
---

PR: https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/33

> Content Package to Feature Model converter does not work on Windows
> ---
>
> Key: SLING-9891
> URL: https://issues.apache.org/jira/browse/SLING-9891
> Project: Sling
>  Issue Type: Bug
>  Components: Content-Package to Feature Model Converter
>Affects Versions: Content-Package to Feature Model Converter 1.0.16
>Reporter: A. J. David Bosschaert
>Assignee: A. J. David Bosschaert
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.0.18
>
>
> Run `mvn install` in the project on Windows and you'll see.
> There are 2 main problems:
>  * The {{java.nio.Path}} implementation chosen to represent Repository paths, 
> does not accept all valid repository paths when run with the Windows 
> implementation.
>  * The test cases use Unix line separators in string comparisons which on 
> Windows don't match



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


[jira] [Comment Edited] (SLING-9889) Slingfeature-Maven-Plugin: Fix failing ITs

2020-11-10 Thread Konrad Windszus (Jira)


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

Konrad Windszus edited comment on SLING-9889 at 11/10/20, 11:43 AM:


The {{apis-jar}} IT is fixed now by 
https://github.com/apache/sling-slingfeature-maven-plugin/commit/775f685a7cc6eb046661e199bee65efaa5c78862.
 The other two are actual mistakes in the ITs.


was (Author: kwin):
The `apis-jar` IT is fixed now by 
https://github.com/apache/sling-slingfeature-maven-plugin/commit/775f685a7cc6eb046661e199bee65efaa5c78862.
 The other two are actual mistakes in the ITs.

> Slingfeature-Maven-Plugin: Fix failing ITs
> --
>
> Key: SLING-9889
> URL: https://issues.apache.org/jira/browse/SLING-9889
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
> are failing:
> {code}
> [ERROR] The following builds failed:
> [ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
> [ERROR] *  apis-jar-wrapper-bundle/pom.xml
> [ERROR] *  apis-jar/pom.xml
> {code}
> (https://ci-builds.apache.org/job/Sling/job/modules/job/sling-slingfeature-maven-plugin/job/master/48/console)



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


[jira] [Commented] (SLING-9889) Slingfeature-Maven-Plugin: Fix failing ITs

2020-11-10 Thread Konrad Windszus (Jira)


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

Konrad Windszus commented on SLING-9889:


The `apis-jar` IT is fixed now by 
https://github.com/apache/sling-slingfeature-maven-plugin/commit/775f685a7cc6eb046661e199bee65efaa5c78862.
 The other two are actual mistakes in the ITs.

> Slingfeature-Maven-Plugin: Fix failing ITs
> --
>
> Key: SLING-9889
> URL: https://issues.apache.org/jira/browse/SLING-9889
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
> are failing:
> {code}
> [ERROR] The following builds failed:
> [ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
> [ERROR] *  apis-jar-wrapper-bundle/pom.xml
> [ERROR] *  apis-jar/pom.xml
> {code}
> (https://ci-builds.apache.org/job/Sling/job/modules/job/sling-slingfeature-maven-plugin/job/master/48/console)



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


[jira] [Commented] (SLING-2938) AdapterMethods annotation and adapter proxy service

2020-11-10 Thread Henry Kuijpers (Jira)


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

Henry Kuijpers commented on SLING-2938:
---

I agree! I don't think the sporadically failing IT should be in the way, since 
it's obvious that it does not have to do with the testing code, nor with an 
error in the annotations. 

I will make time (probably tomorrow) to update the documentation and also 
provide a PR for that. :) 

> AdapterMethods annotation and adapter proxy service
> ---
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter 2.1.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've 
> been working on an @AdapterMethod annotation that makes it easier to create 
> Sling adapters, as in
>   @Component
>   @Service
>   public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
>   }
> As this requires changes to the sling.api bundle, I'll commit to my 
> whiteboard first, for review



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


[jira] [Commented] (SLING-2938) AdapterMethods annotation and adapter proxy service

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz commented on SLING-2938:


The integration tests still fails infrequently, even though I tweaked them to 
use a more recent provisioning model, I have created SLING-9892 for that. 

Also created SLING-9890 for the documentation, with this I think we can go 
ahead with a release, I don't think SLING-9892 is a blocker for that (though it 
might get in the way of the release process due to failing tests).

> AdapterMethods annotation and adapter proxy service
> ---
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter 2.1.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've 
> been working on an @AdapterMethod annotation that makes it easier to create 
> Sling adapters, as in
>   @Component
>   @Service
>   public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
>   }
> As this requires changes to the sling.api bundle, I'll commit to my 
> whiteboard first, for review



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


[jira] [Commented] (SLING-9892) adapter-annotations integration tests sometimes fail

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz commented on SLING-9892:


Earlier in SLING-2938 we suspected SLING-8080 as being the cause of these 
failures but I don't think that's the case anymore as the instance is found to 
be ready before executing the tests.

> adapter-annotations integration tests sometimes fail
> 
>
> Key: SLING-9892
> URL: https://issues.apache.org/jira/browse/SLING-9892
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter Annotations 1.0.0
>Reporter: Bertrand Delacretaz
>Priority: Minor
>
> I have marked two such failing builds at 
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-adapter-annotations/job/master/]
>  as "keep forever", the error is apparently always
> {code}
> [INFO] [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time 
> elapsed: 11.235 s <<< FAILURE! - in 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT
> [INFO] [ERROR] org.apache.sling.adapter.annotations.AdapterRegistrationIT  
> Time elapsed: 11.21 s  <<< ERROR!
> [INFO] java.lang.RuntimeException: Could not read content from response
> [INFO]at 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
> [INFO] Caused by: org.apache.http.MalformedChunkCodingException: CRLF 
> expected at end of chunk
> [INFO]at 
> org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
> [INFO] 
> {code}



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


[GitHub] [sling-org-apache-sling-feature-cpconverter] sonarcloud[bot] commented on pull request #33: Replace java.nio.Path with new RepoPath class.

2020-11-10 Thread GitBox


sonarcloud[bot] commented on pull request #33:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/33#issuecomment-724641042


   Kudos, SonarCloud Quality Gate passed!
   
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=BUG)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=BUG)
 [0 
Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=BUG)
  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=VULNERABILITY)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=VULNERABILITY)
 [0 
Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=VULNERABILITY)
 (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter
 uest=33=false=SECURITY_HOTSPOT) [0 Security 
Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=SECURITY_HOTSPOT)
 to review)  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=CODE_SMELL)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=CODE_SMELL)
 [0 Code 
Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=33=false=CODE_SMELL)
   
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=33=new_coverage=list)
 [89.9% 
Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=33=new_coverage=list)
  
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=33=new_duplicated_lines_density=list)
 [0.0% 
Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=33=new_duplicated_lines_density=list)
   
The version of Java (1.8.0_252) you 
have used to run this analysis is deprecated and we will stop accepting it 
accepting it soon.Please update to at least Java 11.
   Read more [here](https://sonarcloud.io/documentation/upcoming/)
   
   
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Created] (SLING-9892) adapter-annotations integration tests sometimes fail

2020-11-10 Thread Bertrand Delacretaz (Jira)
Bertrand Delacretaz created SLING-9892:
--

 Summary: adapter-annotations integration tests sometimes fail
 Key: SLING-9892
 URL: https://issues.apache.org/jira/browse/SLING-9892
 Project: Sling
  Issue Type: Bug
  Components: Engine, Extensions
Affects Versions: Adapter Annotations 1.0.0
Reporter: Bertrand Delacretaz


I have marked two such failing builds at 
[https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-adapter-annotations/job/master/]
 as "keep forever", the error is apparently always

{code}
[INFO] [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
11.235 s <<< FAILURE! - in 
org.apache.sling.adapter.annotations.AdapterRegistrationIT
[INFO] [ERROR] org.apache.sling.adapter.annotations.AdapterRegistrationIT  Time 
elapsed: 11.21 s  <<< ERROR!
[INFO] java.lang.RuntimeException: Could not read content from response
[INFO]  at 
org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
[INFO] Caused by: org.apache.http.MalformedChunkCodingException: CRLF expected 
at end of chunk
[INFO]  at 
org.apache.sling.adapter.annotations.AdapterRegistrationIT.setUpAdaptions(AdapterRegistrationIT.java:58)
[INFO] 
{code}



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


[GitHub] [sling-org-apache-sling-feature-cpconverter] bosschaert opened a new pull request #33: Replace java.nio.Path with new RepoPath class.

2020-11-10 Thread GitBox


bosschaert opened a new pull request #33:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/33


   Also in this commit, use platform independent line separators in test
   result comparisons.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Created] (SLING-9891) Content Package to Feature Model converter does not work on Windows

2020-11-10 Thread A. J. David Bosschaert (Jira)
A. J. David Bosschaert created SLING-9891:
-

 Summary: Content Package to Feature Model converter does not work 
on Windows
 Key: SLING-9891
 URL: https://issues.apache.org/jira/browse/SLING-9891
 Project: Sling
  Issue Type: Bug
  Components: Content-Package to Feature Model Converter
Affects Versions: Content-Package to Feature Model Converter 1.0.16
Reporter: A. J. David Bosschaert
Assignee: A. J. David Bosschaert
 Fix For: Content-Package to Feature Model Converter 1.0.18


Run `mvn install` in the project on Windows and you'll see.

There are 2 main problems:
 * The {{java.nio.Path}} implementation chosen to represent Repository paths, 
does not accept all valid repository paths when run with the Windows 
implementation.
 * The test cases use Unix line separators in string comparisons which on 
Windows don't match



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


[jira] [Commented] (SLING-9889) Slingfeature-Maven-Plugin: Fix failing ITs

2020-11-10 Thread Carsten Ziegeler (Jira)


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

Carsten Ziegeler commented on SLING-9889:
-

[~kwin] I get this error:
Running post-build script: 
/mnt/c/Users/cziegele/Developer/workspaces/granite/sling-aggregator/slingfeature-maven-plugin/target/it/apis-jar/verify.groovy
groovy.lang.MissingMethodException: No signature of method: 
Script1.checkBundle() is applicable for argument types: (java.io.File, 
java.util.ArrayList, java.util.ArrayList) values: [/mnt/
c/Users/cziegele/Developer/workspaces/granite/sling-aggregator/slingfeature-maven-plugin/target/it/apis-jar/target/apis-jars/slingfeature-maven-plugin-test-1.0.0-SNAPSHOT-base-apis.jar,
 .
..]
Possible solutions: checkBundle(java.io.File, [Ljava.lang.String;, 
[Ljava.lang.String;)
at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:58)
at 
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:81)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:52)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:154)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:182)
at Script1.check(Script1.groovy:69)

> Slingfeature-Maven-Plugin: Fix failing ITs
> --
>
> Key: SLING-9889
> URL: https://issues.apache.org/jira/browse/SLING-9889
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
> are failing:
> {code}
> [ERROR] The following builds failed:
> [ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
> [ERROR] *  apis-jar-wrapper-bundle/pom.xml
> [ERROR] *  apis-jar/pom.xml
> {code}
> (https://ci-builds.apache.org/job/Sling/job/modules/job/sling-slingfeature-maven-plugin/job/master/48/console)



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


[jira] [Updated] (SLING-9889) Slingfeature-Maven-Plugin: Fix failing ITs

2020-11-10 Thread Konrad Windszus (Jira)


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

Konrad Windszus updated SLING-9889:
---
Description: 
After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
are failing:
{code}
[ERROR] The following builds failed:
[ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
[ERROR] *  apis-jar-wrapper-bundle/pom.xml
[ERROR] *  apis-jar/pom.xml
{code}

(https://ci-builds.apache.org/job/Sling/job/modules/job/sling-slingfeature-maven-plugin/job/master/48/console)

  was:
After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
are failing:
{code}
[ERROR] The following builds failed:
[ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
[ERROR] *  apis-jar-wrapper-bundle/pom.xml
[ERROR] *  apis-jar/pom.xml
{code}


> Slingfeature-Maven-Plugin: Fix failing ITs
> --
>
> Key: SLING-9889
> URL: https://issues.apache.org/jira/browse/SLING-9889
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
> are failing:
> {code}
> [ERROR] The following builds failed:
> [ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
> [ERROR] *  apis-jar-wrapper-bundle/pom.xml
> [ERROR] *  apis-jar/pom.xml
> {code}
> (https://ci-builds.apache.org/job/Sling/job/modules/job/sling-slingfeature-maven-plugin/job/master/48/console)



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


[GitHub] [sling-org-apache-sling-testing-clients] dulvac edited a comment on pull request #19: In case the logintoken cookie is no longer valid, try obtaining a new one.

2020-11-10 Thread GitBox


dulvac edited a comment on pull request #19:
URL: 
https://github.com/apache/sling-org-apache-sling-testing-clients/pull/19#issuecomment-724629582


   @andreituicu , I took your PR and modified it, since there were issues with 
implementing both `HttpRequestInterceptor` and `HttpResponseInterceptor` + 
refactored and added a test.
   
   You can see it in 
https://github.com/apache/sling-org-apache-sling-testing-clients/commit/74246de8737de9fbefcddc255bb43d40aadde8ef
 . Are you ok with this? Can we close this PR?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Created] (SLING-9890) Document the new adapter-annotations module

2020-11-10 Thread Bertrand Delacretaz (Jira)
Bertrand Delacretaz created SLING-9890:
--

 Summary: Document the new adapter-annotations module
 Key: SLING-9890
 URL: https://issues.apache.org/jira/browse/SLING-9890
 Project: Sling
  Issue Type: Task
  Components: Documentation
Affects Versions: Adapter Annotations 1.0.0
Reporter: Bertrand Delacretaz
Assignee: Henry Kuijpers


The new [https://github.com/apache/sling-org-apache-sling-adapter-annotations] 
module needs to be documented at 
[https://sling.apache.org/documentation/the-sling-engine/adapters.html]

That page can either briefly mention the module and point to its README for 
more info, or include the full documentation.

I'm assigning this ticket to [~Henry Kuijpers] who volunteered in SLING-2938



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


[jira] [Created] (SLING-9889) Slingfeature-Maven-Plugin: Fix failing ITs

2020-11-10 Thread Konrad Windszus (Jira)
Konrad Windszus created SLING-9889:
--

 Summary: Slingfeature-Maven-Plugin: Fix failing ITs
 Key: SLING-9889
 URL: https://issues.apache.org/jira/browse/SLING-9889
 Project: Sling
  Issue Type: Bug
  Components: Feature Model
Reporter: Konrad Windszus
Assignee: Carsten Ziegeler
 Fix For: slingfeature-maven-plugin 1.4.8


After the merge of https://issues.apache.org/jira/browse/SLING-9886 some ITs 
are failing:
{code}
[ERROR] The following builds failed:
[ERROR] *  apis-jar-wrapped-flattened-classes/pom.xml
[ERROR] *  apis-jar-wrapper-bundle/pom.xml
[ERROR] *  apis-jar/pom.xml
{code}



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


[GitHub] [sling-org-apache-sling-testing-clients] dulvac commented on pull request #19: In case the logintoken cookie is no longer valid, try obtaining a new one.

2020-11-10 Thread GitBox


dulvac commented on pull request #19:
URL: 
https://github.com/apache/sling-org-apache-sling-testing-clients/pull/19#issuecomment-724629582


   @andreituicu , I took your PR and modified it, since there were issues with 
implementing both `HttpRequestInterceptor` and `HttpResponseInterceptor` + 
refactored and added a test.
   
   Are you ok with this? Can we close this PR?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Resolved] (SLING-9886) Slingfeature-maven-plugin: ITs always succeed

2020-11-10 Thread Konrad Windszus (Jira)


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

Konrad Windszus resolved SLING-9886.

Resolution: Fixed

Fixed in 
https://github.com/apache/sling-slingfeature-maven-plugin/commit/a5439d441f3d394cfe5d77cb71027e3857d1dab4.

> Slingfeature-maven-plugin: ITs always succeed
> -
>
> Key: SLING-9886
> URL: https://issues.apache.org/jira/browse/SLING-9886
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Affects Versions: slingfeature-maven-plugin 1.4.6
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> Due to the way how the {{verify.bsh}} are written with a return statement 
> after try and catch the following bug is triggered in BSH: 
> https://github.com/beanshell/beanshell/issues/367.
> You can reproduce by just inverting a condition, e.g. in 
> https://github.com/apache/sling-slingfeature-maven-plugin/blob/56caf46d529f7f09e86e0a644357e17d00028263/src/it/apis-jar-wrapper-bundle/verify.bsh#L30
>  and you see that the build will still not fail.



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


[jira] [Assigned] (SLING-9886) Slingfeature-maven-plugin: ITs always succeed

2020-11-10 Thread Konrad Windszus (Jira)


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

Konrad Windszus reassigned SLING-9886:
--

Assignee: Konrad Windszus

> Slingfeature-maven-plugin: ITs always succeed
> -
>
> Key: SLING-9886
> URL: https://issues.apache.org/jira/browse/SLING-9886
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Affects Versions: slingfeature-maven-plugin 1.4.6
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> Due to the way how the {{verify.bsh}} are written with a return statement 
> after try and catch the following bug is triggered in BSH: 
> https://github.com/beanshell/beanshell/issues/367.
> You can reproduce by just inverting a condition, e.g. in 
> https://github.com/apache/sling-slingfeature-maven-plugin/blob/56caf46d529f7f09e86e0a644357e17d00028263/src/it/apis-jar-wrapper-bundle/verify.bsh#L30
>  and you see that the build will still not fail.



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


[GitHub] [sling-slingfeature-maven-plugin] kwin merged pull request #60: SLING-9886 convert ITs post-execution script from Beanshell to Groovy

2020-11-10 Thread GitBox


kwin merged pull request #60:
URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/60


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Commented] (SLING-9888) freshclam fails updating the signature database during integration tests

2020-11-10 Thread Oliver Lietz (Jira)


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

Oliver Lietz commented on SLING-9888:
-

First build with {{mk0x/docker-clamav:buster-slim}} completed successfully:
{noformat}
[main] INFO org.ops4j.pax.exam.spi.DefaultExamSystem - Pax Exam System 
(Version: 4.13.3) created.
[main] INFO org.ops4j.pax.exam.junit.impl.ProbeRunner - creating PaxExam runner 
for class org.apache.sling.commons.clam.it.tests.ClamdServiceIT
[main] INFO org.testcontainers.dockerclient.DockerClientProviderStrategy - 
Loaded 
org.testcontainers.dockerclient.EnvironmentAndSystemPropertyClientProviderStrategy
 from ~/.testcontainers.properties, will try it first
[main] INFO 
org.testcontainers.dockerclient.EnvironmentAndSystemPropertyClientProviderStrategy
 - Found docker client settings from environment
[main] INFO org.testcontainers.dockerclient.DockerClientProviderStrategy - 
Found Docker environment with Environment variables, system properties and 
defaults. Resolved dockerHost=unix:///var/run/docker.sock
[main] INFO org.testcontainers.DockerClientFactory - Docker host IP address is 
localhost
[main] INFO org.testcontainers.DockerClientFactory - Connected to docker: 
  Server Version: 19.03.13
  API Version: 1.40
  Operating System: Ubuntu 18.04.5 LTS
  Total Memory: 96630 MB
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Starting to pull image
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pulling image layers:  0 pending,  0 downloaded,  0 extracted, (0 bytes/0 bytes)
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pulling image layers:  2 pending,  1 downloaded,  0 extracted, (358 KB/? MB)
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pulling image layers:  1 pending,  2 downloaded,  0 extracted, (358 KB/? MB)
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pulling image layers:  0 pending,  3 downloaded,  0 extracted, (358 KB/4 MB)
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pulling image layers:  0 pending,  3 downloaded,  1 extracted, (2 MB/4 MB)
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pulling image layers:  0 pending,  3 downloaded,  2 extracted, (2 MB/4 MB)
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pulling image layers:  0 pending,  3 downloaded,  3 extracted, (4 MB/4 MB)
[tc-okhttp-stream-1164107853] INFO org.testcontainers.DockerClientFactory - 
Pull complete. 3 layers, pulled in 2s (downloaded 4 MB at 2 MB/s)
[main] INFO org.testcontainers.DockerClientFactory - Ryuk started - will 
monitor and terminate Testcontainers containers on JVM exit
[main] INFO org.testcontainers.DockerClientFactory - Checking the system...
[main] INFO org.testcontainers.DockerClientFactory - ✔︎ Docker server version 
should be at least 1.6.0
[main] INFO org.testcontainers.DockerClientFactory - ✔︎ Docker environment 
should have more than 2GB free disk space
[main] INFO docker[mk0x/docker-clamav:buster-slim] - Pulling docker image: 
mk0x/docker-clamav:buster-slim. Please be patient; this may take some time but 
only needs to be done once.
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Starting to pull image
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  0 pending,  0 downloaded,  0 extracted, (0 bytes/0 bytes)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  6 pending,  1 downloaded,  0 extracted, (25 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  5 pending,  2 downloaded,  0 extracted, (30 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  4 pending,  3 downloaded,  0 extracted, (56 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  3 pending,  4 downloaded,  0 extracted, (59 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  2 pending,  5 downloaded,  0 extracted, (73 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  2 pending,  5 downloaded,  1 extracted, (76 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  1 pending,  6 downloaded,  1 extracted, (78 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  1 pending,  6 downloaded,  2 extracted, (112 MB/? MB)
[tc-okhttp-stream-2033968586] INFO docker[mk0x/docker-clamav:buster-slim] - 
Pulling image layers:  0 pending,  7 downloaded,  2 extracted, (257 MB/260 MB)

[jira] [Assigned] (SLING-2938) AdapterMethods annotation and adapter proxy service

2020-11-10 Thread Bertrand Delacretaz (Jira)


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

Bertrand Delacretaz reassigned SLING-2938:
--

Assignee: Bertrand Delacretaz

> AdapterMethods annotation and adapter proxy service
> ---
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
>  Issue Type: Bug
>  Components: Engine, Extensions
>Affects Versions: Adapter 2.1.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've 
> been working on an @AdapterMethod annotation that makes it easier to create 
> Sling adapters, as in
>   @Component
>   @Service
>   public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
>   }
> As this requires changes to the sling.api bundle, I'll commit to my 
> whiteboard first, for review



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


[jira] [Commented] (SLING-9888) freshclam fails updating the signature database during integration tests

2020-11-10 Thread Oliver Lietz (Jira)


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

Oliver Lietz commented on SLING-9888:
-

Looks like a network issue as it didn't happen before changing CI and is 
working fine when running locally. Trying other Docker images where 
bootstrapping is implemented differently to workaround the issue.

> freshclam fails updating the signature database during integration tests
> 
>
> Key: SLING-9888
> URL: https://issues.apache.org/jira/browse/SLING-9888
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: Commons Clam 2.0.2
>
>
> {noformat}
> [main] INFO org.ops4j.pax.exam.spi.DefaultExamSystem - Pax Exam System 
> (Version: 4.13.3) created. 
> [main] INFO org.ops4j.pax.exam.junit.impl.ProbeRunner - creating PaxExam 
> runner for class org.apache.sling.commons.clam.it.tests.ClamdServiceIT 
> [main] INFO org.testcontainers.dockerclient.DockerClientProviderStrategy - 
> Loaded 
> org.testcontainers.dockerclient.EnvironmentAndSystemPropertyClientProviderStrategy
>  from ~/.testcontainers.properties, will try it first 
> [main] INFO 
> org.testcontainers.dockerclient.EnvironmentAndSystemPropertyClientProviderStrategy
>  - Found docker client settings from environment 
> [main] INFO org.testcontainers.dockerclient.DockerClientProviderStrategy - 
> Found Docker environment with Environment variables, system properties and 
> defaults. Resolved dockerHost=unix:///var/run/docker.sock 
> [main] INFO org.testcontainers.DockerClientFactory - Docker host IP address 
> is localhost 
> [main] INFO org.testcontainers.DockerClientFactory - Connected to docker: 
>   Server Version: 19.03.13 
>   API Version: 1.40 
>   Operating System: Ubuntu 18.04.5 LTS 
>   Total Memory: 96630 MB 
> [main] INFO org.testcontainers.DockerClientFactory - Ryuk started - will 
> monitor and terminate Testcontainers containers on JVM exit 
> [main] INFO org.testcontainers.DockerClientFactory - Checking the system... 
> [main] INFO org.testcontainers.DockerClientFactory - ✔︎ Docker server version 
> should be at least 1.6.0 
> [main] INFO org.testcontainers.DockerClientFactory - ✔︎ Docker environment 
> should have more than 2GB free disk space 
> [main] INFO docker[mk0x/docker-clamav:alpine] - Creating container for image: 
> mk0x/docker-clamav:alpine 
> [main] INFO docker[mk0x/docker-clamav:alpine] - Starting container with ID: 
> b02102292908fa22a0a88dd30488457414a24bfed37f0893a63af01bdf88b2e8 
> [main] INFO docker[mk0x/docker-clamav:alpine] - Container 
> mk0x/docker-clamav:alpine is starting: 
> b02102292908fa22a0a88dd30488457414a24bfed37f0893a63af01bdf88b2e8 
> [main] ERROR docker[mk0x/docker-clamav:alpine] - Could not start container 
> java.lang.IllegalStateException: Container exited with code 1 
> at 
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:457)
>  
> at 
> org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:317)
>  
> at 
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
>  
> at 
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:315)
>  
> at 
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:302)
>  
> at 
> org.apache.sling.commons.clam.it.tests.ClamTestSupport.configuration(ClamTestSupport.java:55)
>  
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
> at java.lang.reflect.Method.invoke(Method.java:498) 
> at 
> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:248)
>  
> at 
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>  
> at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78) 
> at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82) 
> at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73) 
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423) 
> at 
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
>  
> at 
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
>  
> at 
> 

[jira] [Created] (SLING-9888) freshclam fails updating the signature database during integration tests

2020-11-10 Thread Oliver Lietz (Jira)
Oliver Lietz created SLING-9888:
---

 Summary: freshclam fails updating the signature database during 
integration tests
 Key: SLING-9888
 URL: https://issues.apache.org/jira/browse/SLING-9888
 Project: Sling
  Issue Type: Bug
  Components: Commons
Reporter: Oliver Lietz
Assignee: Oliver Lietz
 Fix For: Commons Clam 2.0.2


{noformat}
[main] INFO org.ops4j.pax.exam.spi.DefaultExamSystem - Pax Exam System 
(Version: 4.13.3) created. 
[main] INFO org.ops4j.pax.exam.junit.impl.ProbeRunner - creating PaxExam runner 
for class org.apache.sling.commons.clam.it.tests.ClamdServiceIT 
[main] INFO org.testcontainers.dockerclient.DockerClientProviderStrategy - 
Loaded 
org.testcontainers.dockerclient.EnvironmentAndSystemPropertyClientProviderStrategy
 from ~/.testcontainers.properties, will try it first 
[main] INFO 
org.testcontainers.dockerclient.EnvironmentAndSystemPropertyClientProviderStrategy
 - Found docker client settings from environment 
[main] INFO org.testcontainers.dockerclient.DockerClientProviderStrategy - 
Found Docker environment with Environment variables, system properties and 
defaults. Resolved dockerHost=unix:///var/run/docker.sock 
[main] INFO org.testcontainers.DockerClientFactory - Docker host IP address is 
localhost 
[main] INFO org.testcontainers.DockerClientFactory - Connected to docker: 
  Server Version: 19.03.13 
  API Version: 1.40 
  Operating System: Ubuntu 18.04.5 LTS 
  Total Memory: 96630 MB 
[main] INFO org.testcontainers.DockerClientFactory - Ryuk started - will 
monitor and terminate Testcontainers containers on JVM exit 
[main] INFO org.testcontainers.DockerClientFactory - Checking the system... 
[main] INFO org.testcontainers.DockerClientFactory - ✔︎ Docker server version 
should be at least 1.6.0 
[main] INFO org.testcontainers.DockerClientFactory - ✔︎ Docker environment 
should have more than 2GB free disk space 
[main] INFO docker[mk0x/docker-clamav:alpine] - Creating container for image: 
mk0x/docker-clamav:alpine 
[main] INFO docker[mk0x/docker-clamav:alpine] - Starting container with ID: 
b02102292908fa22a0a88dd30488457414a24bfed37f0893a63af01bdf88b2e8 
[main] INFO docker[mk0x/docker-clamav:alpine] - Container 
mk0x/docker-clamav:alpine is starting: 
b02102292908fa22a0a88dd30488457414a24bfed37f0893a63af01bdf88b2e8 
[main] ERROR docker[mk0x/docker-clamav:alpine] - Could not start container 
java.lang.IllegalStateException: Container exited with code 1 
at 
org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:457)
 
at 
org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:317)
 
at 
org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
 
at 
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:315)
 
at 
org.testcontainers.containers.GenericContainer.start(GenericContainer.java:302) 
at 
org.apache.sling.commons.clam.it.tests.ClamTestSupport.configuration(ClamTestSupport.java:55)
 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) 
at 
org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:248)
 
at 
org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
 
at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78) 
at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82) 
at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73) 
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
 
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) 
at 
org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
 
at 
org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
 
at 
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) 
at 
org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
 
at 
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) 
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:33) 
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:362)
 
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
 
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
 
at 

[jira] [Closed] (SLING-9829) data-sly-element should correctly handle void elements

2020-11-10 Thread Radu Cotescu (Jira)


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

Radu Cotescu closed SLING-9829.
---

> data-sly-element should correctly handle void elements
> --
>
> Key: SLING-9829
> URL: https://issues.apache.org/jira/browse/SLING-9829
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.0, Scripting HTL Compiler 
> 1.0.0, Scripting HTL Compiler 1.1.0-1.4.0, Scripting HTL Compiler 1.2.0-1.4.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Compiler 1.2.12-1.4.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The current implementation of {{data-sly-element}} doesn't correctly handle 
> void elements which will replace the original element on which the block 
> element was placed:
> When {{$\{item.element.name}}} evaluates to {{link}} or {{meta}}, the element 
> will have a closing tag in the following example, although both {{link}} and 
> {{meta}} are void elements:
> {code:html}
> 
> {code}



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


[jira] [Closed] (SLING-9852) Move all content for HTL tests into the /content folder

2020-11-10 Thread Radu Cotescu (Jira)


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

Radu Cotescu closed SLING-9852.
---

> Move all content for HTL tests into the /content folder
> ---
>
> Key: SLING-9852
> URL: https://issues.apache.org/jira/browse/SLING-9852
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Testing 1.0.28-1.4.0, Scripting HTL 
> Testing Content 1.0.26-1.4.0
>
>
> All testing content for the HTL IT should be moved to {{/content}}, so that 
> all requests are made using the {{anonymous}} user. This should help 
> discovering regressions where the request's resource resolver is used for 
> dependency resolution (not the case right now).



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


[jira] [Closed] (SLING-9854) Formatting string is removed when no formatting type is provided

2020-11-10 Thread Radu Cotescu (Jira)


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

Radu Cotescu closed SLING-9854.
---

> Formatting string is removed when no formatting type is provided
> 
>
> Key: SLING-9854
> URL: https://issues.apache.org/jira/browse/SLING-9854
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.34, Scripting HTL Engine 
> 1.1.0-1.4.0, Scripting HTL Engine 1.2.0-1.4.0, Scripting HTL Engine 
> 1.3.0-1.4.0, Scripting HTL Engine 1.4.0-1.4.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Engine 1.4.6-1.4.0
>
>
> The HTL expression
> {code}
> ${'hello, world' @ format=''}
> {code}
> renders nothing, despite the fact that the specification mentions the 
> following \[0\]:
> {quote}
> Type of formatting will be decided based on:
> * the type option, if present (accepted values are string, date and number)
> * placeholders (eg: \{0\}) in the pattern, triggers string formatting
> * type of format option object, when the type is a Date or a Number
> * default, fallback to string formatting
> {quote}
> \[0\] - https://github.com/adobe/htl-spec/blob/1.4/SPECIFICATION.md#122-format



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


[GitHub] [sling-org-apache-sling-feature-cpconverter] rombert commented on a change in pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


rombert commented on a change in pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#discussion_r520425955



##
File path: 
src/main/java/org/apache/sling/feature/cpconverter/handlers/XmlConfigurationEntryHandler.java
##
@@ -65,13 +74,77 @@ protected void onJcrRootElement(String uri, String 
localName, String qName, Attr
 
 if (attributeValue != null && !attributeValue.isEmpty()) {
 DocViewProperty property = 
DocViewProperty.parse(attributeQName, attributeValue);
-
+Object value = property.values;
+List strValues = 
Arrays.asList(property.values);
+switch (property.type) {
+case PropertyType.DATE:
+// Date was never properly supported as osgi 
configs don't support dates so converting to millis 
+// Scenario should just be theoretical
+attributeQName += ":Long";
+value = Lists.transform(strValues, new 
Function() {
+   public Long apply(String s) {
+  Long res = null;
+  if (s != null) {
+   Calendar cal = ISO8601.parse(s);
+   if (cal != null) {
+   res = cal.getTimeInMillis();
+   }
+  } 
+  return res;
+   }
+}).toArray();
+break;
+case PropertyType.DOUBLE:
+attributeQName += ":Double";
+value = Lists.transform(strValues, new 
Function() {
+   public Double apply(String s) {
+  Double res = null;
+  try {
+  res = Double.parseDouble(s);
+  } catch ( NumberFormatException ex ){
+  // ignore as nonexisting

Review comment:
   Wouldn't the below OSGi config snippet be silently ignored with this 
change?
   
   ```xml
 alertThreshold="{Double}high"
   ```
   
   ?
   
   I think such invalid inputs should halt the conversion process.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-resourceresolver] rombert commented on a change in pull request #24: SLING-9535 - Improve performance of sling:alias

2020-11-10 Thread GitBox


rombert commented on a change in pull request #24:
URL: 
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/24#discussion_r520424294



##
File path: 
src/test/java/org/apache/sling/resourceresolver/impl/mapping/MapEntriesTest.java
##
@@ -2074,4 +2102,28 @@ public void run() {
 }
 }
 }
+
+@Test
+public void testIsValidAliasPath() throws Exception {
+Method method = MapEntries.class.getDeclaredMethod("isValidAliasPath", 
String.class);
+method.setAccessible(true);
+
+// ignore system tree - path should not start with /jcr:system -
+assertFalse((Boolean)method.invoke(mapEntries, "/jcr:system/node"));
+//valid alias path
+assertTrue((Boolean)method.invoke(mapEntries, "/parent"));
+// notallowedparent is not valid configured alias path
+assertFalse((Boolean)method.invoke(mapEntries, "/notallowedparent"));
+}
+
+@Test
+public void testNullAliasPath() throws NoSuchMethodException, 
IllegalAccessException {

Review comment:
   See my above comment - I suggested _not_ making this method private to 
ease testing.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-resourceresolver] rombert commented on a change in pull request #24: SLING-9535 - Improve performance of sling:alias

2020-11-10 Thread GitBox


rombert commented on a change in pull request #24:
URL: 
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/24#discussion_r520423627



##
File path: 
src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverFactoryActivator.java
##
@@ -304,6 +312,25 @@ protected void activate(final BundleContext bundleContext, 
final ResourceResolve
 this.observationPaths[i] = new Path(paths[i]);
 }
 
+// optimize alias path allow list
+this.aliasPathAllowList = null;

Review comment:
   Ah, I missed the fact that this was done in the `activate` method, so no 
one can read it at that point. But why do you need to explicitly set it to 
null? It already has that value since no one has changed it.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-resourceresolver] rombert commented on a change in pull request #24: SLING-9535 - Improve performance of sling:alias

2020-11-10 Thread GitBox


rombert commented on a change in pull request #24:
URL: 
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/24#discussion_r520421888



##
File path: 
src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverFactoryActivator.java
##
@@ -128,6 +129,9 @@
 
 private volatile ResourceResolverFactoryConfig config = DEFAULT_CONFIG;
 
+/** Alias path whitelist */
+private AtomicReferenceArray aliasPathAllowList;

Review comment:
   I am not sure why a `volatile CopyOnWriteArrayList` wouldn't work:
   
   - The `volatile` modifier ensures that that the readers of the field always 
get the latest value - so changing the reference works
   - the `CopyOnWriteArrayList` implementation is thread-safe internally, so 
changes made by one thread are visible to other threads
   
   Maybe SonarCloud flagged a volatile field holding a non-thread-safe list 
implementation, like `ArrayList`? That would not solve the second problem 
listed above.
   
   I think using a List is much more easier to understand than an 
AtomicReferenceArray, so I'd prefer that if at all possible.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-slingfeature-maven-plugin] cziegeler commented on pull request #60: SLING-9886 convert ITs post-execution script from Beanshell to Groovy

2020-11-10 Thread GitBox


cziegeler commented on pull request #60:
URL: 
https://github.com/apache/sling-slingfeature-maven-plugin/pull/60#issuecomment-724585211


   Yes and please create a new issue for the ITs - I'll try to look into that 
one then



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] DominikSuess commented on a change in pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


DominikSuess commented on a change in pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#discussion_r520420067



##
File path: 
src/main/java/org/apache/sling/feature/cpconverter/handlers/XmlConfigurationEntryHandler.java
##
@@ -65,13 +74,77 @@ protected void onJcrRootElement(String uri, String 
localName, String qName, Attr
 
 if (attributeValue != null && !attributeValue.isEmpty()) {
 DocViewProperty property = 
DocViewProperty.parse(attributeQName, attributeValue);
-
+Object value = property.values;
+List strValues = 
Arrays.asList(property.values);
+switch (property.type) {
+case PropertyType.DATE:
+// Date was never properly supported as osgi 
configs don't support dates so converting to millis 
+// Scenario should just be theoretical
+attributeQName += ":Long";
+value = Lists.transform(strValues, new 
Function() {
+   public Long apply(String s) {
+  Long res = null;
+  if (s != null) {
+   Calendar cal = ISO8601.parse(s);
+   if (cal != null) {
+   res = cal.getTimeInMillis();
+   }
+  } 
+  return res;
+   }
+}).toArray();
+break;
+case PropertyType.DOUBLE:
+attributeQName += ":Double";
+value = Lists.transform(strValues, new 
Function() {
+   public Double apply(String s) {
+  Double res = null;
+  try {
+  res = Double.parseDouble(s);
+  } catch ( NumberFormatException ex ){
+  // ignore as nonexisting

Review comment:
   @rombert  - as those are typed representations (it is a string 
representation of a  typed property in the end) the only "valid" case of not 
being a number is an unset value. Therefore I saw no scenario where an explicit 
handling would do anything here.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] DominikSuess commented on a change in pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


DominikSuess commented on a change in pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#discussion_r520418736



##
File path: 
src/main/java/org/apache/sling/feature/cpconverter/handlers/XmlConfigurationEntryHandler.java
##
@@ -65,13 +74,77 @@ protected void onJcrRootElement(String uri, String 
localName, String qName, Attr
 
 if (attributeValue != null && !attributeValue.isEmpty()) {
 DocViewProperty property = 
DocViewProperty.parse(attributeQName, attributeValue);
-
+Object value = property.values;
+List strValues = 
Arrays.asList(property.values);
+switch (property.type) {
+case PropertyType.DATE:

Review comment:
   @bosschaert I only handle what the sling osgi installer supports and 
handles - other types wouldn't work in sling:OsgiConfig nodes anyhow. The cnd 
doesn't constrain it but the other properties woud be handled as String 
representations in the osgi installer as well.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-slingfeature-maven-plugin] kwin edited a comment on pull request #60: SLING-9886 convert ITs post-execution script from Beanshell to Groovy

2020-11-10 Thread GitBox


kwin edited a comment on pull request #60:
URL: 
https://github.com/apache/sling-slingfeature-maven-plugin/pull/60#issuecomment-724575262


   So should I go ahead and merge and break the Jenkins build of master?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-slingfeature-maven-plugin] kwin commented on pull request #60: SLING-9886 convert ITs post-execution script from Beanshell to Groovy

2020-11-10 Thread GitBox


kwin commented on pull request #60:
URL: 
https://github.com/apache/sling-slingfeature-maven-plugin/pull/60#issuecomment-724575262


   So should I go ahead and merge and break the Jenkins build?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] sonarcloud[bot] removed a comment on pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


sonarcloud[bot] removed a comment on pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#issuecomment-723053179


   Kudos, SonarCloud Quality Gate passed!
   
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=BUG)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=BUG)
 [0 
Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=BUG)
  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=VULNERABILITY)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=VULNERABILITY)
 [0 
Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=VULNERABILITY)
 (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter
 uest=32=false=SECURITY_HOTSPOT) [0 Security 
Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=SECURITY_HOTSPOT)
 to review)  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=CODE_SMELL)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=CODE_SMELL)
 [5 Code 
Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=CODE_SMELL)
   
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_coverage=list)
 [90.9% 
Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_coverage=list)
  
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_duplicated_lines_density=list)
 [0.0% 
Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_duplicated_lines_density=list)
   
The version of Java (1.8.0_252) you 
have used to run this analysis is deprecated and we will stop accepting it 
accepting it soon.Please update to at least Java 11.
   Read more [here](https://sonarcloud.io/documentation/upcoming/)
   
   
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] sonarcloud[bot] commented on pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


sonarcloud[bot] commented on pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#issuecomment-724571619


   Kudos, SonarCloud Quality Gate passed!
   
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=BUG)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=BUG)
 [0 
Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=BUG)
  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=VULNERABILITY)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=VULNERABILITY)
 [0 
Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=VULNERABILITY)
 (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter
 uest=32=false=SECURITY_HOTSPOT) [0 Security 
Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=SECURITY_HOTSPOT)
 to review)  
   [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=CODE_SMELL)
 [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=CODE_SMELL)
 [5 Code 
Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-cpconverter=32=false=CODE_SMELL)
   
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_coverage=list)
 [90.9% 
Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_coverage=list)
  
   [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_duplicated_lines_density=list)
 [0.0% 
Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=32=new_duplicated_lines_density=list)
   
The version of Java (1.8.0_252) you 
have used to run this analysis is deprecated and we will stop accepting it 
accepting it soon.Please update to at least Java 11.
   Read more [here](https://sonarcloud.io/documentation/upcoming/)
   
   
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [sling-org-apache-sling-feature-cpconverter] DominikSuess commented on pull request #32: Issue/sling 9881

2020-11-10 Thread GitBox


DominikSuess commented on pull request #32:
URL: 
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/32#issuecomment-724570793


   Reverted the switch of separator that was accidentially  commited along but 
was found to no longer be a concrete issue (fix wouldn't change failing 
conditions)



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Resolved] (SLING-9887) Record feature origins for configurations

2020-11-10 Thread Carsten Ziegeler (Jira)


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

Carsten Ziegeler resolved SLING-9887.
-
Resolution: Fixed

Implemented in 
https://github.com/apache/sling-org-apache-sling-feature/commit/c91f51489b02346a0c04cdd3f7f843b66159454b
with a set of unit tests

> Record feature origins for configurations
> -
>
> Key: SLING-9887
> URL: https://issues.apache.org/jira/browse/SLING-9887
> Project: Sling
>  Issue Type: Improvement
>  Components: Feature Model
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Feature Model 1.2.14
>
>
> For tracking purposes we should record the feature origins of a configuration 
> (we do the same for artifacts).
> We can add a new property of type String[] to the configuration:
> If the property is not set, the origin is the current feature
> The property is set if two features are merged - the array contains the ids 
> of the feature where the configuration is defined. 



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


[GitHub] [sling-slingfeature-maven-plugin] cziegeler commented on pull request #60: SLING-9886 convert ITs post-execution script from Beanshell to Groovy

2020-11-10 Thread GitBox


cziegeler commented on pull request #60:
URL: 
https://github.com/apache/sling-slingfeature-maven-plugin/pull/60#issuecomment-724541604


   Sounds doable, I think it makes sense to create a new issue to fix the ITs



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org