+1
> On 30 Aug 2022, at 18:24, Radu Cotescu wrote:
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
Hi,
We solved 5 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12350393
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2672/
You can use this UNIX script to download the release and verify the signatures:
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-11458:
-
Fix Version/s: (was: GraphQL Core 0.0.6)
> Regress - "Writer has already been closed"
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597957#comment-17597957
]
Radu Cotescu commented on SLING-11458:
--
As mentioned in the PR, this should be fixed in the Sling
[
https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-10901:
-
Fix Version/s: GraphQL Core 0.0.16
(was: GraphQL Core 0.0.14)
> Allow
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-10900:
-
Fix Version/s: GraphQL Core 0.0.16
(was: GraphQL Core 0.0.14)
> Update
[
https://issues.apache.org/jira/browse/SLING-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-11563.
--
Resolution: Fixed
Updated in
Radu Cotescu created SLING-11563:
Summary: Update to Apache Sling Bundle Parent 49
Key: SLING-11563
URL: https://issues.apache.org/jira/browse/SLING-11563
Project: Sling
Issue Type:
[
https://issues.apache.org/jira/browse/SLING-11429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-11429.
--
Resolution: Fixed
Fixed in
raducotescu merged PR #32:
URL: https://github.com/apache/sling-org-apache-sling-graphql-core/pull/32
--
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:
sonarcloud[bot] commented on PR #32:
URL:
https://github.com/apache/sling-org-apache-sling-graphql-core/pull/32#issuecomment-1231757095
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
dependabot[bot] commented on PR #30:
URL:
https://github.com/apache/sling-org-apache-sling-graphql-core/pull/30#issuecomment-1231753315
OK, I won't notify you about commons-io:commons-io again, unless you re-open
this PR or update it yourself.
--
This is an automated message from the
raducotescu commented on PR #30:
URL:
https://github.com/apache/sling-org-apache-sling-graphql-core/pull/30#issuecomment-1231753252
@dependabot ignore this dependency
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
dependabot[bot] closed pull request #30: Bump commons-io from 2.4 to 2.7
URL: https://github.com/apache/sling-org-apache-sling-graphql-core/pull/30
--
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
raducotescu opened a new pull request, #32:
URL: https://github.com/apache/sling-org-apache-sling-graphql-core/pull/32
* use the GraphQLServlet service.pid in order to have unique instances for
all the required metrics
--
This is an automated message from the Apache Git Service.
To
[
https://issues.apache.org/jira/browse/SLING-11538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597868#comment-17597868
]
Konrad Windszus commented on SLING-11538:
-
The use case is inline JSON in HTML. Writing that in
sonarcloud[bot] commented on PR #81:
URL:
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/81#issuecomment-1231605180
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
T11:30:28Z
[INFO]
[INFO] [jenkins-event-spy] Generated
/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest@tmp/withMaven25f5040c/maven-spy-20220830-111812-84818200308881507096904.log
[ERROR] Failed
Hi all,
Any suggestion on this?
On 22-Aug-2022, at 2:11 PM, Sagar Miglani
mailto:sagarmigl...@live.com>> wrote:
Hi all,
I want some suggestion on the following behaviour of resource resolver:
1. When I create two resources, let's say 'child1' and 'child2' under path
'/content/demo/'
[
https://issues.apache.org/jira/browse/SLING-11248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-11248.
--
Resolution: Fixed
> Post empty body should fail gracefully
>
[
https://issues.apache.org/jira/browse/SLING-11538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597629#comment-17597629
]
Radu Cotescu commented on SLING-11538:
--
[~kwin], what's the use case? The [test you
[
https://issues.apache.org/jira/browse/SLING-11562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashok Pelluru reassigned SLING-11562:
-
Assignee: Ashok Pelluru
> Update parent bundle (49) to sling-resource-filter
>
Ashok Pelluru created SLING-11562:
-
Summary: Update parent bundle (49) to sling-resource-filter
Key: SLING-11562
URL: https://issues.apache.org/jira/browse/SLING-11562
Project: Sling
Issue
23 matches
Mail list logo
