Community over Code EU 2024: The countdown has started!
[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] We are very close to Community Over Code EU -- check out the amazing program and the special discounts that we have for you. Special discounts You still have the opportunity to secure your ticket for Community Over Code EU. Explore the various options available, including the regular pass, the committer and groups pass, and now introducing the one-day pass tailored for locals in Bratislava. We also have a special discount for you to attend both Community Over Code and Berlin Buzzwords from June 9th to 11th. Visit our website to find out more about this opportunity and contact te...@sg.com.mx to get the discount code. Take advantage of the discounts and register now! https://eu.communityovercode.org/tickets/ Check out the full program! This year Community Over Code Europe will bring to you three days of keynotes and sessions that cover topics of interest for ASF projects and the greater open source ecosystem including data engineering, performance engineering, search, Internet of Things (IoT) as well as sessions with tips and lessons learned on building a healthy open source community. Check out the program: https://eu.communityovercode.org/program/ Keynote speaker highlights for Community Over Code Europe include: * Dirk-Willem Van Gulik, VP of Public Policy at the Apache Software Foundation, will discuss the Cyber Resiliency Act and its impact on open source (All your code belongs to Policy Makers, Politicians, and the Law). * Dr. Sherae Daniel will share the results of her study on the impact of self-promotion for open source software developers (To Toot or not to Toot, that is the question). * Asim Hussain, Executive Director of the Green Software Foundation will present a framework they have developed for quantifying the environmental impact of software (Doing for Sustainability what Open Source did for Software). * Ruth Ikegah will discuss the growth of the open source movement in Africa (From Local Roots to Global Impact: Building an Inclusive Open Source Community in Africa) * A discussion panel on EU policies and regulations affecting specialists working in Open Source Program Offices Additional activities * Poster sessions: We invite you to stop by our poster area and see if the ideas presented ignite a conversation within your team. * BOF time: Don't miss the opportunity to discuss in person with your open source colleagues on your shared interests. * Participants reception: At the end of the first day, we will have a reception at the event venue. All participants are welcome to attend! * Spontaneous talks: There is a dedicated room and social space for having spontaneous talks and sessions. Get ready to share with your peers. * Lighting talks: At the end of the event we will have the awaited Lighting talks, where every participant is welcome to share and enlighten us. Please remember: If you haven't applied for the visa, we will provide the necessary letter for the process. In the unfortunate case of a visa rejection, your ticket will be reimbursed. See you in Bratislava, Community Over Code EU Team
[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: (was: 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 > > 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)
Re: [VOTE] Release Apache Sling JCR Resource 3.3.0
Ah, I didn't realise. I'll remove the fix version. Thanks for that! On Tue, 14 May 2024 at 12:02, Robert Munteanu wrote: > Because it affected all Sling modules, not just this one.
Re: [PR] SLING-12315: avoid new registrations during deactivation [sling-org-apache-sling-i18n]
rombert commented on code in PR #14:
URL:
https://github.com/apache/sling-org-apache-sling-i18n/pull/14#discussion_r1599862705
##
src/main/java/org/apache/sling/i18n/impl/JcrResourceBundleProvider.java:
##
@@ -436,8 +439,10 @@ protected void deactivate() {
this.locatorPathsTracker = null;
}
-clearCache();
-this.bundleContext = null;
+synchronized(this) {
Review Comment:
I think you're looking at interleaved access between `deactivate()` and
`registerResourceBundle`, right? That is the only scenario where
`bundleServiceRegistrations` will receive new entries.
It looks like it's theoretically possible for this scenario to happen,
although I see the `bundleContext != null` checks on every code path and I am
very skeptical that a runtime compiler will reorder staments in face of
multi-thread volatile reads and writes.
I find the overall thread safety model of this class quite confusing (
multiple volatile fields, concurrent maps with Semaphore keys, synchronized
blocks ( on `this` (!) , on a private collection ) and I think expanding the
scope of the synchronized block would make things more confusing.
If you think that it's worth protecting the `bundleContext` and
`bundleServiceRegistrations` together I would prefer to not make the
`bundleContext` synchronized and instead guard access to those two fields all
the time using the same lock. Of course, that can have performance implications
so care must be taken.
--
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 JCR Resource 3.3.0
On Tue, 2024-05-14 at 10:46 +0200, Radu Cotescu wrote: > Hi Robert, > > On Tue, 7 May 2024 at 10:57, Robert Munteanu > wrote: > > > > FWIW, you probably did not want to tag > > https://issues.apache.org/jira/browse/SLING-12094 as being fixed > > for > > this release. > > > > Why not? It was committed in > https://github.com/apache/sling-org-apache-sling-jcr-resource/commit/1849e113a0ae94ca4484b1a766b97149959a06cc > . Because it affected all Sling modules, not just this one.
[jira] [Closed] (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 closed SLING-12092.
> 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
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
>
[jira] [Closed] (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 closed SLING-12076. > 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] [Closed] (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 closed SLING-12300.
> 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)
[RESULT] [VOTE] Release Apache Sling JCR Resource 3.3.0
Hi, The vote has passed with the following result: +1 (binding): Radu Cotescu, Joerg Hoh, Robert Munteanu +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
Re: [VOTE] Release Apache Sling JCR Resource 3.3.0
Hi Robert, On Tue, 7 May 2024 at 10:57, Robert Munteanu wrote: > > FWIW, you probably did not want to tag > https://issues.apache.org/jira/browse/SLING-12094 as being fixed for > this release. > Why not? It was committed in https://github.com/apache/sling-org-apache-sling-jcr-resource/commit/1849e113a0ae94ca4484b1a766b97149959a06cc. Thanks, Radu
Re: [PR] SLING-12313 bump oak.version to 1.62.0 for compatibility [sling-org-apache-sling-jcr-oak-server]
reschke commented on PR #10: URL: https://github.com/apache/sling-org-apache-sling-jcr-oak-server/pull/10#issuecomment-2109422262 @rombert - is there something we can do systematically in Oak (other than removing Guava completely) at this point? Also, can you file tickets for the classes where you noticed issues? -- 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
