niekraaijmakers opened a new pull request #114:
URL:
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/114
Add custom node type support for sling initial content
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
[
https://issues.apache.org/jira/browse/SLING-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco closed SLING-10864.
> Update Sling CMS Quickstart Docs
>
>
> Key: SLING-10864
>
[
https://issues.apache.org/jira/browse/SLING-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco resolved SLING-10864.
--
Resolution: Fixed
Fixed in
[
https://issues.apache.org/jira/browse/SLING-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco reassigned SLING-10864:
Assignee: Dan Klco
> Update Sling CMS Quickstart Docs
>
>
>
Cris Rockwell created SLING-10864:
-
Summary: Update Sling CMS Quickstart Docs
Key: SLING-10864
URL: https://issues.apache.org/jira/browse/SLING-10864
Project: Sling
Issue Type: Task
kwin edited a comment on pull request #8:
URL:
https://github.com/apache/sling-org-apache-sling-commons-log/pull/8#issuecomment-940138897
IMHO this is a false positive of baselining as
http://logback.qos.ch/apidocs/ch/qos/logback/core/Appender.html implements
kwin commented on pull request #8:
URL:
https://github.com/apache/sling-org-apache-sling-commons-log/pull/8#issuecomment-940138897
IMHO this is a false positive of baselining as
http://logback.qos.ch/apidocs/ch/qos/logback/core/Appender.html derives from
On Mon, 2021-10-11 at 15:10 +, Robert Munteanu wrote:
> Please vote to approve this release:
+1
Robert
Hi,
We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12348407
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2539/
You can use this UNIX script to download the release and verify the signatures:
[
https://issues.apache.org/jira/browse/SLING-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-8039:
---
Fix Version/s: (was: Commons Log 5.1.14)
Commons Log 5.1.16
> Inline
[
https://issues.apache.org/jira/browse/SLING-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-9528:
---
Fix Version/s: (was: Commons Log 5.1.14)
Commons Log 5.1.16
> Update
rombert edited a comment on pull request #8:
URL:
https://github.com/apache/sling-org-apache-sling-commons-log/pull/8#issuecomment-940112272
@kwin @karlpauls - the build now fails because of baselining issues in the
Logback packages, e.g.
```
[ERROR] Baseline mismatch for
rombert commented on pull request #8:
URL:
https://github.com/apache/sling-org-apache-sling-commons-log/pull/8#issuecomment-940112272
@kwin @karlpauls - the build now fails because of baselining issues in the
Logback packages, e.g.
```
[ERROR] Baseline mismatch for package
Hi,
I am investigating a reasonable way to cache objects which have the same
livecycle as a resource resolver, because they are retrieved or derived
from it.
For example this could be the result of query, which is used at multiple
locations within my application, all in the context of the same
[
https://issues.apache.org/jira/browse/SLING-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-10862:
Summary: Expose more details on servlet candidates in Servlet Resolver Web
Console Plugin
[
https://issues.apache.org/jira/browse/SLING-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-10862:
Description:
Currently the list of servlet candidates exposed via
[
https://issues.apache.org/jira/browse/SLING-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-10862.
-
Resolution: Fixed
Fixed in
kwin merged pull request #20:
URL: https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/20
--
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
sonarcloud[bot] commented on pull request #20:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/20#issuecomment-939941898
SonarCloud Quality Gate failed. ![Quality Gate
sonarcloud[bot] removed a comment on pull request #20:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/20#issuecomment-939851313
SonarCloud Quality Gate failed. ![Quality Gate
-
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 03:03 min
[INFO] Finished at: 2021-10-11T11:25:49Z
[INFO] ---
[
https://issues.apache.org/jira/browse/SLING-10852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-10852.
> Upgrade ESAPI to 2.2.3.0
> -
>
> Key: SLING-10852
>
Hi,
The vote has passed with the following result:
+1 (binding): Oliver Lietz, Robert Munteanu, Nicolas Peltier, Dan Klco
+1 (non-binding): none
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Regards,
Radu Cotescu
sonarcloud[bot] commented on pull request #20:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/20#issuecomment-939851313
SonarCloud Quality Gate failed. ![Quality Gate
sonarcloud[bot] removed a comment on pull request #20:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/20#issuecomment-939044060
SonarCloud Quality Gate failed. 