rvesse commented on issue #3561: URL: https://github.com/apache/jena/issues/3561#issuecomment-3496237426
> This is our current approach as well, but I'd say it would be preferable if these kinds of workaround would not be needed in the first place. Sure but like many open source projects Jena is entirely volunteer driven and has a relatively slow release cadence (~3 months) unless there's a critical security issue we need to address sooner. This is part of the trade off to choosing to use open source, sometimes you have to own the workarounds and fixes until those can filter back upstream. If there's a newer dependency version for us to take then that's relatively simple to do, but if there isn't, as appears to be the case here, and we'd have to swap in a different dependency that takes time and effort to understand the implications, especially when it isn't a direct dependency of Jena but coming via an upstream library - https://github.com/filip26/titanium-json-ld - as already noted. You may also want to consider filing an issue there but that project is effectively a solo volunteer effort so I wouldn't expect the resolution there to be particularly any faster. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
