Re: [PR] SLING-12283 : changed the config Pid to separate factoryPID & PID wit… [sling-org-apache-sling-installer-factory-configuration]
sonarcloud[bot] commented on PR #13: URL: https://github.com/apache/sling-org-apache-sling-installer-factory-configuration/pull/13#issuecomment-2096967292 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-installer-factory-configuration=13) **Quality Gate passed** Issues  [2 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-installer-factory-configuration=13=false=true)  [0 Accepted issues](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-installer-factory-configuration=13=new_accepted_issues=list) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-installer-factory-configuration=13=false=true)  [100.0% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-installer-factory-configuration=13=new_coverage=list)  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-installer-factory-configuration=13=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-installer-factory-configuration=13) -- 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
[PR] Update dependency org.apache.sling:org.apache.sling.distribution.journal to v0.3.0 [sling-site]
renovate-bot opened a new pull request, #163: URL: https://github.com/apache/sling-site/pull/163 [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [org.apache.sling:org.apache.sling.distribution.journal](https://sling.apache.org) ([source](https://togithub.com/apache/sling-org-apache-sling-distribution-journal)) | `0.2.0` -> `0.3.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Configuration **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/apache/sling-site). -- 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
[PR] Update dependency org.apache.sling:org.apache.sling.distribution.journal.messages to v0.5.10 [sling-site]
renovate-bot opened a new pull request, #162: URL: https://github.com/apache/sling-site/pull/162 [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [org.apache.sling:org.apache.sling.distribution.journal.messages](https://sling.apache.org) ([source](https://togithub.com/apache/sling-org-apache-sling-distribution-journal-messages)) | `0.5.6` -> `0.5.10` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovat ebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Configuration **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/apache/sling-site). -- 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
[PR] Update dependency org.apache.sling:org.apache.sling.distribution.api to v0.7.2 [sling-site]
renovate-bot opened a new pull request, #161: URL: https://github.com/apache/sling-site/pull/161 [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [org.apache.sling:org.apache.sling.distribution.api](https://sling.apache.org) ([source](https://togithub.com/apache/sling-org-apache-sling-distribution-api)) | `0.7.0` -> `0.7.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Configuration **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/apache/sling-site). -- 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] [Resolved] (SLING-12311) Remove empty paths
[ https://issues.apache.org/jira/browse/SLING-12311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved SLING-12311. - Resolution: Fixed > Remove empty paths > -- > > Key: SLING-12311 > URL: https://issues.apache.org/jira/browse/SLING-12311 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution API 0.7.2 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution API 0.7.2 > > > We should remove empty paths from the list of paths in > org.apache.sling.distribution.SimpleDistributionRequest -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release Content Distribution Journal Core 0.3.0 , Content Distribution API 0.7.2, Content Distribution Journal Messages 0.5.10
This vote passes with 3 +1 and no other votes. I will deploy the artifacts. Christian Am Fr., 3. Mai 2024 um 09:51 Uhr schrieb Christian Schneider < ch...@die-schneider.net>: > Hi Sling Developers, > > I prepared releases of: > > Content Distribution Journal Core 0.3.0 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353656 > > Content Distribution API 0.7.2 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12351665 > > Content Distribution Journal Messages 0.5.10 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353859 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2859 > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh [YOUR REPOSITORY ID] /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. > > Christian > > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
Re: [VOTE] Release Apache Sling JCR Resource 3.3.0
+1 Am Mo., 6. Mai 2024 um 18:20 Uhr schrieb Radu Cotescu : > Hi, > > We solved 4 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354599=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2860/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2860 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Radu Cotescu > -- https://cqdump.joerghoh.de
Re: [VOTE] Release Apache Sling JCR Resource 3.3.0
+1 On Mon, 6 May 2024 at 18:20, Radu Cotescu wrote: > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Radu Cotescu
[VOTE] Release Apache Sling JCR Resource 3.3.0
Hi, We solved 4 issues in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354599=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2860/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2860 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards, Radu Cotescu
[jira] [Updated] (SLING-12076) ResourceListener should expose the JCR observation's user data
[ https://issues.apache.org/jira/browse/SLING-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-12076: - Fix Version/s: JCR Resource 3.3.0 (was: JCR Resource 3.2.6) > ResourceListener should expose the JCR observation's user data > -- > > Key: SLING-12076 > URL: https://issues.apache.org/jira/browse/SLING-12076 > Project: Sling > Issue Type: Improvement > Components: JCR >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: JCR Resource 3.3.0 > > > The ResourceChange > (https://github.com/apache/sling-org-apache-sling-api/blob/f58111baf07b6ae525aec2c6792e949786df7beb/src/main/java/org/apache/sling/api/resource/observation/ResourceChange.java#L50) > should optionally expose a context (arbitrary String). In the case of the > JCR Resource Provider this should be populated by the JCR Event's User Data > (https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/12_Observation.html#12.3.5%20User%20Data). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12094) Use GitHub for the Maven scm.url value
[ https://issues.apache.org/jira/browse/SLING-12094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-12094: - Fix Version/s: JCR Resource 3.3.0 > Use GitHub for the Maven scm.url value > -- > > Key: SLING-12094 > URL: https://issues.apache.org/jira/browse/SLING-12094 > Project: Sling > Issue Type: Improvement > Components: Build and Source Control >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: JCR Resource 3.3.0 > > > Currently, the "Browsing URL" in the POMs is pointing to GitBox. Those > URLs are used by various tooling and humans. > We should switch it directly to GitHub to easy the discovery process > The Source Code URLs used for Release Process stick with GitBox -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12092) Build fails with Java 11
[
https://issues.apache.org/jira/browse/SLING-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-12092:
-
Fix Version/s: JCR Resource 3.3.0
(was: JCR Resource 3.2.6)
> Build fails with Java 11
>
>
> Key: SLING-12092
> URL: https://issues.apache.org/jira/browse/SLING-12092
> Project: Sling
> Issue Type: Improvement
> Components: JCR
>Affects Versions: JCR Resource 3.2.4
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: JCR Resource 3.3.0
>
>
> From
> [https://ci-builds.apache.org/blue/rest/organizations/jenkins/pipelines/Sling/pipelines/modules/pipelines/sling-org-apache-sling-jcr-resource/branches/master/runs/216/nodes/60/steps/105/log/?start=0:]
> {code}
> [ERROR]
> org.apache.sling.jcr.resource.internal.JcrResourceListenerTest.testSimpleOperations
> Time elapsed: 0.095 s <<< ERROR!
> java.lang.ExceptionInInitializerError
> at
> org.mockito.cglib.core.KeyFactory$Generator.generateClass(KeyFactory.java:167)
> at
> org.mockito.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:25)
> at
> org.mockito.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:217)
> at
> org.mockito.cglib.core.KeyFactory$Generator.create(KeyFactory.java:145)
> at org.mockito.cglib.core.KeyFactory.create(KeyFactory.java:117)
> at org.mockito.cglib.core.KeyFactory.create(KeyFactory.java:109)
> at org.mockito.cglib.core.KeyFactory.create(KeyFactory.java:105)
> at org.mockito.cglib.proxy.Enhancer.(Enhancer.java:70)
> at
> org.mockito.internal.creation.jmock.ClassImposterizer.createProxyClass(ClassImposterizer.java:85)
> at
> org.mockito.internal.creation.jmock.ClassImposterizer.imposterise(ClassImposterizer.java:62)
> at
> org.mockito.internal.creation.jmock.ClassImposterizer.imposterise(ClassImposterizer.java:56)
> at
> org.mockito.internal.creation.CglibMockMaker.createMock(CglibMockMaker.java:23)
> at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:26)
> at org.mockito.internal.MockitoCore.mock(MockitoCore.java:51)
> at org.mockito.Mockito.mock(Mockito.java:1243)
> at org.mockito.Mockito.mock(Mockito.java:1120)
> at
> org.apache.sling.jcr.resource.internal.helper.jcr.SlingRepositoryProvider.getFakeContext(SlingRepositoryProvider.java:56)
> at
> org.apache.sling.jcr.resource.internal.helper.jcr.SlingRepositoryProvider.getRepository(SlingRepositoryProvider.java:41)
> at
> org.apache.sling.jcr.resource.internal.JcrResourceListenerTest.setUp(JcrResourceListenerTest.java:74)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
>
[jira] [Resolved] (SLING-12300) Provide a way to retrieve a JCR backed resource by its node identifier
[
https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-12300.
--
Resolution: Fixed
> Provide a way to retrieve a JCR backed resource by its node identifier
> --
>
> Key: SLING-12300
> URL: https://issues.apache.org/jira/browse/SLING-12300
> Project: Sling
> Issue Type: New Feature
> Components: JCR
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: JCR Resource 3.3.0
>
>
> Since all {{javax.jcr.Nodes}} have an identifier [0], a useful feature would
> be {{Resource}} retrieval by node id, which could be its {{jcr:uuid}}
> property for referenceable nodes or the path. In systems that would like to
> use UUID addressing, this would reduce the need for executing JCR queries for
> resource retrieval and would avoid double-reads via the JCR and then Sling
> API to obtain the resource.
> In order to provide a unified behaviour, paths starting with the {{/jcr:id/}}
> prefix should use the resource retrieval by node identifier.
> [0] -
> https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/Node.html#getIdentifier()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] SLING-12300 - Provide a way to retrieve a JCR backed resource by its node identifier [sling-org-apache-sling-jcr-resource]
raducotescu merged PR #42: URL: https://github.com/apache/sling-org-apache-sling-jcr-resource/pull/42 -- 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-12300 - Provide a way to retrieve a JCR backed resource by its node identifier [sling-org-apache-sling-jcr-resource]
sonarcloud[bot] commented on PR #42: URL: https://github.com/apache/sling-org-apache-sling-jcr-resource/pull/42#issuecomment-2095864213 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-resource=42) **Quality Gate passed** Issues  [1 New issue](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-resource=42=false=true)  [0 Accepted issues](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-resource=42=new_accepted_issues=list) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-resource=42=false=true)  [94.4% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-resource=42=new_coverage=list)  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-resource=42=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-resource=42) -- 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: [VOTE] Release Content Distribution Journal Core 0.3.0 , Content Distribution API 0.7.2, Content Distribution Journal Messages 0.5.10
+1 Timothee Le ven. 3 mai 2024 à 09:51, Christian Schneider a écrit : > Hi Sling Developers, > > I prepared releases of: > > Content Distribution Journal Core 0.3.0 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353656 > > Content Distribution API 0.7.2 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12351665 > > Content Distribution Journal Messages 0.5.10 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353859 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2859 > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh [YOUR REPOSITORY ID] /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. > > Christian >
