On Tue, 2024-03-05 at 10:22 +0100, Robert Munteanu wrote:
> Given no other comments came in, I will create the git repository as
> already 'deprecated' and we'll figure out the release process
> changes,
> if needed, at the time of the potential release.
>
> I kicked off a `git svn clone` for
Given no other comments came in, I will create the git repository as
already 'deprecated' and we'll figure out the release process changes,
if needed, at the time of the potential release.
I kicked off a `git svn clone` for commons.json since we don't have it
mirrorred as part of
On Wed, 2024-02-28 at 11:22 +0100, Carsten Ziegeler wrote:
> Can we do this without creating a new git repo? Creating a separate
> new
> repo gives a different message than what we intend it to be.
>
> It would be great if we could do this directly in SVN :)
I think that would be pretty
Can we do this without creating a new git repo? Creating a separate new
repo gives a different message than what we intend it to be.
It would be great if we could do this directly in SVN :)
Regards
Carsten
On 28.02.2024 10:52, Robert Munteanu wrote:
Hi Jörg
On Tue, 2024-02-27 at 11:06
Hi Jörg
On Tue, 2024-02-27 at 11:06 +0100, Jörg Hoh wrote:
> Hi Robert,
>
> makes sense.
>
> To clarify: We just provide this final version of commons.json as a
> convenience for all users who are still depending on commons.json;
> but
> there is no intention to continue development of
Hi Robert,
makes sense.
To clarify: We just provide this final version of commons.json as a
convenience for all users who are still depending on commons.json; but
there is no intention to continue development of commons.json or to
re-introducing this dependency again into other areas of Sling.
Hi,
A long time ago we retired the commons.json module for legal reasons
[1], leaving it only in the SVN attic [2].
After some time a CVE was reported against this module [3] which we
could not fix as we could not release new versions.
In the meantime, the JSON library we have been using has
