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?
Regards,
Stephan
On 2023/10/11 17:21:38 Julian Reschke wrote:
> Hi there,
>
> I believe we should consider requiring Java 11 for trunk work, and when
> done, create a new maintenance branch from it.
>
> Reasons:
>
> - some of our dependencies now require Java 11
>
> - we currently use Jackrabbit 2.20 (Java 8) in both Oak 1.22 (Java 8)
> and Oak 1.58 ("latest stable", Java 11); on the other hand, we
> *implement* jackrabbit API from Oak, and haven't been able to update
> that since Oak switched to 11
>
> Other thoughts:
>
> - we currently have only one maintenance branch, so adding another one
> which is mostly identical shouldn't create a lot of work
>
> - we'll need to maintain 2.20 (Java 8) until Oak 1.22 switches to Java
> 11 (or some new Oak maintenance branch for Java 11 is created)
>
> Proposal:
>
> - make one more unstable release, removing RMI support
> (https://issues.apache.org/jira/browse/JCR-4972) (ca December)
>
> - branch 2.22 and release 2.22.0 from trunk around February
>
> Questions:
>
> - apart from RMI, is there anything else we could discontinue? JCA maybe?
>
> Feeback appreciated, Julian
>
>
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you. Message Encrypted via TLS
connection
