Conversation
There was a problem hiding this comment.
The change of the scope resulted in the Derby database driver no longer being delivered as part of the WAR (under WEB-INF/lib)
- https://archive.apache.org/dist/jackrabbit/2.20.17/jackrabbit-webapp-2.20.17.war - Derby driver is included
- https://archive.apache.org/dist/jackrabbit/2.22.0/jackrabbit-webapp-2.22.0.war - no Derby driver included
There was a problem hiding this comment.
That's likely caused by the change to make Derby just a test depency when updating the version.
There was a problem hiding this comment.
So, would you like me to update the patch then, with some likeliness of going forward with it?
There was a problem hiding this comment.
The Derby change to a test depency was intentional (AFAIR, due to https://www.cve.org/CVERecord?id=CVE-2022-46337).
So I would prefer to keep it out of the WAR we generate.
And no, I really can't estimate if or when we can merge this, because I'm still not sure that this is the best way forward.
Would it be ok to have this only in the BETA branch for now?
There was a problem hiding this comment.
Since the DerbyPersistenceManager is still there, I only need to include the Derby JARs in a WAR overlay.
3 participants
No description provided.