On Mon, Jul 1, 2019 at 8:06 AM Michael Rogers wrote:
>
> On 01/07/2019 15:57, Tatu Saloranta wrote:
> > If anyone is aware of retro-weaver style tools that can take jars with
> > newer declared bytecode version and convert to older, that'd be great,
> > sharing most appreciated.
>
> I haven't trie
On 01/07/2019 15:57, Tatu Saloranta wrote:
> If anyone is aware of retro-weaver style tools that can take jars with
> newer declared bytecode version and convert to older, that'd be great,
> sharing most appreciated.
I haven't tried it myself, but I believe Retrolambda can convert Java 8
bytecode
On Mon, Jul 1, 2019 at 7:44 AM Mediocaballero MidKnight
wrote:
>
> Sorry to revive this old, thread, but it's related to an issue I'm finding
> now.
>
> We are also in the situation of upgrading some dependencies on corporate
> legacy software, which, for runtime platform restrictions can only u
Sorry to revive this old, thread, but it's related to an issue I'm finding
now.
We are also in the situation of upgrading some dependencies on corporate
legacy software, which, for runtime platform restrictions can only use jdk
6.
We've found that jackson 2.9.9 solves all current vulnerabiliti
On Thu, Jan 31, 2019 at 3:34 PM Penny Wells wrote:
>
> The Jackson component is embedded into an enterprise software of our company
> that will not go beyond Java 7 for many years to come.
> Can we safely make the assumption that Jackson 2.9.8 will never require Java
> version 7 ? We will not us
The Jackson component is embedded into an enterprise software of our
company that will not go beyond Java 7 for many years to come.
Can we safely make the assumption that Jackson 2.9.8 will never require
Java version 7 ? We will not use any Java 8-specific features (Lambda
expressions, etc), but
