Re: [PR] Bump plexus-utils from 3.0.9 to 3.0.16 [sling-org-apache-sling-launchpad-integration-tests]
sonarcloud[bot] commented on PR #6: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/6#issuecomment-1879796387 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=6) **Quality Gate passed** Kudos, no new issues were introduced! [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=6&resolved=false&inNewCodePeriod=true) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=6&resolved=false&inNewCodePeriod=true) No data about Coverage [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=6&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=6) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.sling.jcr.base from 3.0.2 to 3.1.12 [sling-org-apache-sling-launchpad-integration-tests]
sonarcloud[bot] commented on PR #11: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/11#issuecomment-1879796377 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=11) **Quality Gate passed** Kudos, no new issues were introduced! [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=11&resolved=false&inNewCodePeriod=true) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=11&resolved=false&inNewCodePeriod=true) No data about Coverage [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=11&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=11) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.sling.servlets.post from 2.3.0 to 2.3.8 [sling-org-apache-sling-launchpad-integration-tests]
sonarcloud[bot] commented on PR #7: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/7#issuecomment-1879796265 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=7) **Quality Gate passed** Kudos, no new issues were introduced! [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=7&resolved=false&inNewCodePeriod=true) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=7&resolved=false&inNewCodePeriod=true) No data about Coverage [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=7&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=7) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.sling.api from 2.3.0 to 2.25.4 [sling-org-apache-sling-launchpad-integration-tests]
sonarcloud[bot] commented on PR #8: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/8#issuecomment-1879796349 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=8) **Quality Gate passed** Kudos, no new issues were introduced! [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=8&resolved=false&inNewCodePeriod=true) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=8&resolved=false&inNewCodePeriod=true) No data about Coverage [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=8&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=8) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SLING-9417] Added test for an nt:file child of a versioned node [sling-org-apache-sling-launchpad-integration-tests]
sonarcloud[bot] commented on PR #1: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/1#issuecomment-1879796326 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=1) **Quality Gate failed** Failed conditions [0.0% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=1&metric=new_coverage&view=list) (required ≥ 80%) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=1) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump commons-io from 2.5 to 2.7 [sling-org-apache-sling-launchpad-integration-tests]
sonarcloud[bot] commented on PR #14: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/14#issuecomment-1879796269 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=14) **Quality Gate passed** Kudos, no new issues were introduced! [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=14&resolved=false&inNewCodePeriod=true) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=14&resolved=false&inNewCodePeriod=true) No data about Coverage [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=14&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests&pullRequest=14) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-12186) Automatic code formatting with spotless-maven-plugin
[
https://issues.apache.org/jira/browse/SLING-12186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803803#comment-17803803
]
Konrad Windszus commented on SLING-12186:
-
I added a wiki page with hints what to consider with the update to Parent 60:
https://cwiki.apache.org/confluence/x/SI75E
> Automatic code formatting with spotless-maven-plugin
>
>
> Key: SLING-12186
> URL: https://issues.apache.org/jira/browse/SLING-12186
> Project: Sling
> Issue Type: Improvement
> Components: General
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Parent 60 (Java 11)
>
>
> As discussed in
> https://lists.apache.org/thread/t32o425mttoftfr622wkvp4s5br4wzt1 we should
> introduce
> [spotless-maven-plugin|https://github.com/diffplug/spotless/tree/main/plugin-maven]
> to enforce a common code formatting similar to what was done for Maven in
> https://issues.apache.org/jira/browse/MPOM-349.
> With each reformatting a {{.git-blame-ignore-revs}} should be added/enriched
> which is considered by git blame in GitHub
> (https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)
> and optionally with Git CLI
> (https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt).
>
> I propose to reuse the following configuration files from Apache Maven Shared
> Resources
> *
> https://github.com/apache/maven-shared-resources/blob/master/src/main/resources/config/maven-eclipse-importorder.txt
> *
> https://github.com/apache/maven-shared-resources/blob/master/src/main/resources/config/maven-header-plain.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-12207) Use adjusted inheritance rules for URLs
[
https://issues.apache.org/jira/browse/SLING-12207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803799#comment-17803799
]
Konrad Windszus commented on SLING-12207:
-
Moving the SCM elements doesn't really make a difference until MPOM-450 is
fixed.
> Use adjusted inheritance rules for URLs
> ---
>
> Key: SLING-12207
> URL: https://issues.apache.org/jira/browse/SLING-12207
> Project: Sling
> Issue Type: Bug
> Components: General
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Parent 60 (Java 11)
>
>
> For Sling projects the default inheritance rules for URLs are not applicable:
> https://maven.apache.org/ref/3.8.4/maven-model-builder/index.html#Inheritance_Assembly.
> Therefore the dedicated attribute {{@child.project.url.inherit.append.path}}
> should be set to {{false}} (requires Maven 3.6.1 or newer,
> https://issues.apache.org/jira/browse/MNG-6059).
> Also the SCM element and children should be moved to the profile only active
> when the parent pom is built (as they are never applicable as is to derived
> modules).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] SLING-12207 Adjust url inheritance [sling-parent]
kwin opened a new pull request, #42: URL: https://github.com/apache/sling-parent/pull/42 (no comment) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (SLING-12207) Use adjusted inheritance rules for URLs
[
https://issues.apache.org/jira/browse/SLING-12207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-12207:
---
Assignee: Konrad Windszus
> Use adjusted inheritance rules for URLs
> ---
>
> Key: SLING-12207
> URL: https://issues.apache.org/jira/browse/SLING-12207
> Project: Sling
> Issue Type: Bug
> Components: General
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Parent 60 (Java 11)
>
>
> For Sling projects the default inheritance rules for URLs are not applicable:
> https://maven.apache.org/ref/3.8.4/maven-model-builder/index.html#Inheritance_Assembly.
> Therefore the dedicated attribute {{@child.project.url.inherit.append.path}}
> should be set to {{false}} (requires Maven 3.6.1 or newer,
> https://issues.apache.org/jira/browse/MNG-6059).
> Also the SCM element and children should be moved to the profile only active
> when the parent pom is built (as they are never applicable as is to derived
> modules).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-12186) Automatic code formatting with spotless-maven-plugin
[
https://issues.apache.org/jira/browse/SLING-12186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-12186:
Fix Version/s: Parent 60 (Java 11)
> Automatic code formatting with spotless-maven-plugin
>
>
> Key: SLING-12186
> URL: https://issues.apache.org/jira/browse/SLING-12186
> Project: Sling
> Issue Type: Improvement
> Components: General
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Parent 60 (Java 11)
>
>
> As discussed in
> https://lists.apache.org/thread/t32o425mttoftfr622wkvp4s5br4wzt1 we should
> introduce
> [spotless-maven-plugin|https://github.com/diffplug/spotless/tree/main/plugin-maven]
> to enforce a common code formatting similar to what was done for Maven in
> https://issues.apache.org/jira/browse/MPOM-349.
> With each reformatting a {{.git-blame-ignore-revs}} should be added/enriched
> which is considered by git blame in GitHub
> (https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)
> and optionally with Git CLI
> (https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt).
>
> I propose to reuse the following configuration files from Apache Maven Shared
> Resources
> *
> https://github.com/apache/maven-shared-resources/blob/master/src/main/resources/config/maven-eclipse-importorder.txt
> *
> https://github.com/apache/maven-shared-resources/blob/master/src/main/resources/config/maven-header-plain.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-12186) Automatic code formatting with spotless-maven-plugin
[
https://issues.apache.org/jira/browse/SLING-12186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803796#comment-17803796
]
Konrad Windszus commented on SLING-12186:
-
Fixed in
https://github.com/apache/sling-parent/commit/5dce12f64543c7b810df3982fb63ba08a4981d7e
and
https://github.com/apache/sling-parent/commit/33e394e9b055dcf0ff6b82c6e68fb325bdcbe6ce
> Automatic code formatting with spotless-maven-plugin
>
>
> Key: SLING-12186
> URL: https://issues.apache.org/jira/browse/SLING-12186
> Project: Sling
> Issue Type: Improvement
> Components: General
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> As discussed in
> https://lists.apache.org/thread/t32o425mttoftfr622wkvp4s5br4wzt1 we should
> introduce
> [spotless-maven-plugin|https://github.com/diffplug/spotless/tree/main/plugin-maven]
> to enforce a common code formatting similar to what was done for Maven in
> https://issues.apache.org/jira/browse/MPOM-349.
> With each reformatting a {{.git-blame-ignore-revs}} should be added/enriched
> which is considered by git blame in GitHub
> (https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)
> and optionally with Git CLI
> (https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt).
>
> I propose to reuse the following configuration files from Apache Maven Shared
> Resources
> *
> https://github.com/apache/maven-shared-resources/blob/master/src/main/resources/config/maven-eclipse-importorder.txt
> *
> https://github.com/apache/maven-shared-resources/blob/master/src/main/resources/config/maven-header-plain.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] SLING-12186 Enforce source code formatting with spotless-maven-plugin [sling-parent]
kwin merged PR #41: URL: https://github.com/apache/sling-parent/pull/41 -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
