Re: [PR] SLING-12264 only call save() if there's something to save [sling-org-apache-sling-jcr-repoinit]
sonarcloud[bot] commented on PR #52: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/52#issuecomment-2148503993 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-repoinit=52) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=52=false=true)  [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=52=WONTFIX) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit=52=false=true)  [55.6% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit=52=new_coverage=list)  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit=52=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-repoinit=52) -- 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-12262 use a metric to indicate repoinit failures [sling-org-apache-sling-jcr-repoinit]
sonarcloud[bot] commented on PR #51: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/51#issuecomment-2148503219 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-repoinit=51) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=51=false=true)  [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=51=WONTFIX) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit=51=false=true)  [100.0% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit=51=new_coverage=list)  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit=51=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-repoinit=51) -- 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 Apache Sling Repoinit JCR 1.1.50
+1 Am Di., 4. Juni 2024 um 15:51 Uhr schrieb Julian Sedding : > Hi, > > We solved 1 issue in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354758=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2864/ > > 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 2864 /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 > Julian > -- https://cqdump.joerghoh.de
Re: [VOTE] Release Apache Sling API 2.27.4
+1 Regards Julian On Tue, Jun 4, 2024 at 3:25 PM Jörg Hoh wrote: > > +1 > > Am Di., 4. Juni 2024 um 15:24 Uhr schrieb Jörg Hoh : > > > We solved 9 issues in this > > release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353245=Text=12310710 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2865/ > > > > 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 2865 /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. > > > > > > > > -- > > https://cqdump.joerghoh.de > > > > > > -- > https://cqdump.joerghoh.de
Re: [VOTE] Release Apache Sling Repoinit JCR 1.1.50
+1 Regards Julian On Tue, Jun 4, 2024 at 3:25 PM Julian Sedding wrote: > > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354758=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2864/ > > 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 2864 /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 > Julian
[VOTE] Release Apache Sling Repoinit JCR 1.1.50
Hi, We solved 1 issue in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354758=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2864/ 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 2864 /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 Julian
Re: [VOTE] Release Apache Sling API 2.27.4
+1 Am Di., 4. Juni 2024 um 15:24 Uhr schrieb Jörg Hoh : > We solved 9 issues in this > release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353245=Text=12310710 > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2865/ > > 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 2865 /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. > > > > -- > https://cqdump.joerghoh.de > > -- https://cqdump.joerghoh.de
[VOTE] Release Apache Sling API 2.27.4
We solved 9 issues in this release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353245=Text=12310710 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2865/ 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 2865 /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. -- https://cqdump.joerghoh.de
[jira] [Updated] (SLING-11621) Outdated JCR dependencies
[
https://issues.apache.org/jira/browse/SLING-11621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated SLING-11621:
---
Fix Version/s: (was: Repoinit JCR 1.1.50)
> Outdated JCR dependencies
> -
>
> Key: SLING-11621
> URL: https://issues.apache.org/jira/browse/SLING-11621
> Project: Sling
> Issue Type: Task
> Components: Repoinit
>Reporter: Julian Reschke
>Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> https://github.com/apache/sling-org-apache-sling-jcr-repoinit/blob/9913b787574186a7a31d184480cec3862816438f/pom.xml#L39:
> {noformat}
> 2.18.2
> 1.22.1
> {noformat}
> Jackrabbit 2.18 has been EOLd quite some time ago...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-12122) Add unit-test creating group with rep:externalId property
[
https://issues.apache.org/jira/browse/SLING-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated SLING-12122:
---
Fix Version/s: (was: Repoinit JCR 1.1.50)
> Add unit-test creating group with rep:externalId property
> -
>
> Key: SLING-12122
> URL: https://issues.apache.org/jira/browse/SLING-12122
> Project: Sling
> Issue Type: Test
> Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.44
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
>
> Add a unit-test validating that repoinit can successfully create a new group
> with the {{rep:externalId}} property, that can only be set on creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-12329) Backwards compatibility for legacy repoinit statement reordering
[ https://issues.apache.org/jira/browse/SLING-12329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-12329. Resolution: Fixed > Backwards compatibility for legacy repoinit statement reordering > > > Key: SLING-12329 > URL: https://issues.apache.org/jira/browse/SLING-12329 > Project: Sling > Issue Type: Improvement > Components: Repoinit >Affects Versions: Repoinit JCR 1.1.46 >Reporter: Julian Sedding >Assignee: Julian Sedding >Priority: Minor > Fix For: Repoinit JCR 1.1.50 > > > The fix for repoinit statement reordering can cause issues for users relying > on the legacy ordering. > We should support a fallback to the legacy ordering and log a deprecation > message, warning users that their repoinit script relies on the legacy > ordering, support for which may be removed in the future. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12321) Update parent pom to latest
[ https://issues.apache.org/jira/browse/SLING-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Hoh closed SLING-12321. - > Update parent pom to latest > --- > > Key: SLING-12321 > URL: https://issues.apache.org/jira/browse/SLING-12321 > Project: Sling > Issue Type: Task > Components: Engine >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > Fix For: Engine 2.15.16 > > > Updating to parent 60 an force the result to be runable with Java 8 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12330) Fix formatting
[ https://issues.apache.org/jira/browse/SLING-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Hoh closed SLING-12330. - > Fix formatting > -- > > Key: SLING-12330 > URL: https://issues.apache.org/jira/browse/SLING-12330 > Project: Sling > Issue Type: Task > Components: Engine >Affects Versions: Engine 2.15.14 >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > Fix For: Engine 2.15.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12326) SocketExceptions are no longer handled as error
[ https://issues.apache.org/jira/browse/SLING-12326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Hoh closed SLING-12326. - > SocketExceptions are no longer handled as error > --- > > Key: SLING-12326 > URL: https://issues.apache.org/jira/browse/SLING-12326 > Project: Sling > Issue Type: Task > Components: Engine >Affects Versions: Engine 2.15.8, Engine 2.15.10, Engine 2.15.14 >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > Fix For: Engine 2.15.16 > > > [This > commit|https://github.com/apache/sling-org-apache-sling-engine/commit/8ab96759cd435520a228271fbbb9d37955954c80] > introduced a special handling for SocketExceptions under the assumptions > that the only Socket Exceptions can happen when Sling/Jetty fails to stream > back the response to the client (browser). > But there are other types of SocketExceptions, which can happen during page > rendering, e.g. when a Servlet/Script does connections on its own, for > example to fetch data from a backend system. If these exceptions are wrapped > and thrown, it could lead to a situation, that the error handling in this > place is actually not kicking in at all, and also no logging for this > exception is done at all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12317) Make Sling Engine build with Java 21
[
https://issues.apache.org/jira/browse/SLING-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh closed SLING-12317.
-
> Make Sling Engine build with Java 21
>
>
> Key: SLING-12317
> URL: https://issues.apache.org/jira/browse/SLING-12317
> Project: Sling
> Issue Type: Task
> Components: Engine
>Affects Versions: Engine 2.15.14
>Reporter: Joerg Hoh
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Engine 2.15.16
>
>
> {noformat}[ERROR]
> org.apache.sling.engine.impl.SlingHttpServletRequestImplTest.getUserPrincipal_testUnauthenticated_nonspeccompliant
> Time elapsed: 0 s <<< ERROR!
> java.lang.IllegalStateException: No code generation strategy available
> at
> org.jmock.imposters.ByteBuddyClassImposteriser.proxyClass(ByteBuddyClassImposteriser.java:167)
> at
> org.jmock.imposters.ByteBuddyClassImposteriser.access$000(ByteBuddyClassImposteriser.java:41)
> at
> org.jmock.imposters.ByteBuddyClassImposteriser$1.apply(ByteBuddyClassImposteriser.java:100)
> at
> org.jmock.imposters.ByteBuddyClassImposteriser$1.apply(ByteBuddyClassImposteriser.java:96)
> at
> java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1708)
> at
> org.jmock.imposters.ByteBuddyClassImposteriser.proxy(ByteBuddyClassImposteriser.java:95)
> at
> org.jmock.imposters.ByteBuddyClassImposteriser.imposterise(ByteBuddyClassImposteriser.java:66)
> at org.jmock.Mockery.mock(Mockery.java:167)
> at org.jmock.Mockery.mock(Mockery.java:143)
> at
> org.apache.sling.engine.impl.SlingHttpServletRequestImplTest.getUserPrincipal_testUnauthenticated_nonspeccompliant(SlingHttpServletRequestImplTest.java:176)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> 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.InvokeMethod.evaluate(InvokeMethod.java:17)
> 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:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548){noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-12316) Servlet Name might be set incorrectly after an exception
[
https://issues.apache.org/jira/browse/SLING-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh closed SLING-12316.
-
> Servlet Name might be set incorrectly after an exception
>
>
> Key: SLING-12316
> URL: https://issues.apache.org/jira/browse/SLING-12316
> Project: Sling
> Issue Type: Task
> Components: Engine
>Affects Versions: Engine 2.15.14
>Reporter: Joerg Hoh
>Assignee: Joerg Hoh
>Priority: Major
> Fix For: Engine 2.15.16
>
>
> In case an exception happens, the name is not reset properly:
> [https://github.com/apache/sling-org-apache-sling-engine/blob/ad11b3b108764312e6db87aea7de18c3fa00db34/src/main/java/org/apache/sling/engine/impl/request/RequestData.java#L553]
> {{requestData.setActiveServletName(callerServlet);}} must be moved into the
> finally block
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[Result][VOTE] Release Apache Sling Engine 2.15.16
Hi, The vote has passed with the following result : +1 (binding): Jörg Hoh, Eric Norman, Julian Sedding I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Am Di., 28. Mai 2024 um 16:59 Uhr schrieb Jörg Hoh : > Hi, > > We solved 5 issues in this > release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354681=Text > Staging > repository:https://repository.apache.org/content/repositories/orgapachesling-2863/ > > 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 2863 /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 hours5 > > Jörg > > -- > https://cqdump.joerghoh.de > > -- https://cqdump.joerghoh.de
[jira] [Closed] (SLING-12237) Extend exception message for RepositoryInitializerFactory with config PID and affected script/reference
[
https://issues.apache.org/jira/browse/SLING-12237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding closed SLING-12237.
--
> Extend exception message for RepositoryInitializerFactory with config PID and
> affected script/reference
> ---
>
> Key: SLING-12237
> URL: https://issues.apache.org/jira/browse/SLING-12237
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.46
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Repoinit JCR 1.1.48
>
>
> Currently an error in any of the repoinit scripts or reference just lead to
> an exception which does not expose the configuration PID triggering the
> exception, e.g.
> {code}
> javax.jcr.RepositoryException: Applying repoinit operation failed despite
> retry; set loglevel to DEBUG to see all exceptions. Last exception message
> was: Session.save failed: javax.jcr.nodetype.ConstraintViolationException:
> OakConstraint0001: /var/groovyconsole[[nt:folder]]: No matching definition
> found for child node audit with effective type [nt:unstructured]
> at
> org.apache.sling.jcr.repoinit.impl.RepositoryInitializerFactory.applyOperations(RepositoryInitializerFactory.java:176)
> [org.apache.sling.jcr.repoinit:1.1.38]
> {code}
> As repo init scripts are contributed from many different source locations the
> underlying configuration PID should be contained in the exception message as
> well. In addition the index of the according script or the according
> reference URL should be included.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-12323) [RepoInit] Avoid java.nio.file.Path for parsing repository paths
[
https://issues.apache.org/jira/browse/SLING-12323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding closed SLING-12323.
--
> [RepoInit] Avoid java.nio.file.Path for parsing repository paths
>
>
> Key: SLING-12323
> URL: https://issues.apache.org/jira/browse/SLING-12323
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.46
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Major
> Fix For: Repoinit JCR 1.1.48
>
>
> RepoInit uses {{java.nio.file.Path}} to determine the "parent path" and
> "name" of a relative repository path. This fails on Windows when the relative
> repository path contains a colon ":".
> The implementation should not be platform dependent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-12243) Standalone execution of Repoinit statements is not clearly documented
[ https://issues.apache.org/jira/browse/SLING-12243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-12243. -- > Standalone execution of Repoinit statements is not clearly documented > - > > Key: SLING-12243 > URL: https://issues.apache.org/jira/browse/SLING-12243 > Project: Sling > Issue Type: Bug > Components: Repoinit >Affects Versions: Repoinit JCR 1.1.46 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Repoinit JCR 1.1.48 > > > The repoinit documentation at > [https://sling.apache.org/documentation/bundles/repository-initialization.html] > does not clearly indicate how to execute repoinit statements outside of the > repository initialization cycle. The information is present but not obvious. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Apache Sling Repoinit JCR 1.1.48
Hi, The vote has passed with the following result: +1 (binding): Robert Munteanu, Radu Cotescu, Joerg Hoh, Julian Sedding +1 (non-binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards Julian
Re: [VOTE] Release Apache Sling Repoinit JCR 1.1.48
+1 Regards Julian On Mon, May 27, 2024 at 3:27 PM Jörg Hoh wrote: > > +1 > > Am Sa., 25. Mai 2024 um 11:55 Uhr schrieb Julian Sedding >: > > > Hi, > > > > We solved 3 issues in the Apache Sling Repoinit JCR 1.1.48 release: > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353873=Text > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2862/ > > > > 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 2862 /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 > > Julian > > > > > -- > https://cqdump.joerghoh.de
Re: [PR] chore(deps): update dependency org.freemarker:freemarker to v2.3.33 [sling-org-apache-sling-starter]
rombert commented on PR #332: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/332#issuecomment-2146710774 ``` [ERROR] [requirements-capabilities] org.freemarker:freemarker:2.3.33: Artifact org.freemarker:freemarker:2.3.33 requires [org.freemarker.freemarker/2.3.33.stable] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=16))" in start level 20 but no artifact is providing a matching capability in this start level. ``` -- 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
