On 09.07.2024 16:15, Born, Stephan via dev wrote:
Hi,
This is an answer to your question if there is
* anything else we could discontinue? JCA maybe?
Please do not desupport jackrabbit-jca. In fact, for us it would be
necessary to even make it compatible with Jakarta 10.
It seems that jackrabbit-jca could be relatively simple to be converted
to Jackrabbit 10 by
replacing
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-j2ee-connector_1.5_spec</artifactId>
<version>2.0.0</version>
<scope>provided</scope>
</dependency>
with
<dependency>
<groupId>jakarta.resource</groupId>
<artifactId>jakarta.resource-api</artifactId>
<version>2.1.0</version>
</dependency>
and by replacing
import javax.resource….
with
import jakarta.resource…..
At least the corresponding test cases seem to run fine when built with
Java17
Would like to know if there is a chance to get put this on your agenda.
Also, what time frame would be possible. Would it help to provide a
patch file?
1. Nobody is currently working on JCA (or has in the past decade, I
guess), so we'd need you to provide changes and verify them. Optimally
including test coverage that we currently lack (I think).
2. We can't just replace the API signatures. We'd need a new component,
and to avoid duplication of sources, use a transform job to convert
them. <https://issues.apache.org/jira/browse/JCR-4892> might give you
some ideas.
3. As for timing: before we do this, I'd want to get JCR-4892 resolved
first. Again that one depends on volunteers finishing the PR.
4. Did you consider just forking the JCA component, and maintaining it
yourself?
Best regards, Julian
