thanks for the feedback Davide and Julian, in summary I share your same concerns and therefore I don't have a good solution myself. For now I've only backported it to the "safe" branches. I'm thinking of backporting the previous upgrade to Solr 5.5.5 to branch 1.6, which would be JDK 1.7 compatible.
Regards, Tommaso Il giorno mar 11 giu 2019 alle ore 16:06 Julian Reschke < julian.resc...@gmx.de> ha scritto: > On 11.06.2019 12:42, Davide Giannella wrote: > > ... > > -1 on the additional branch. It will be yet one more branch to maintain > > that will go very easily out of sync from the "official" 1.6. > > > > The only way to solve this is to increase the JDK compatibility. However > > we have to account for consumer projects and their JDK compatibility. > > They may have set JDK7 and cannot easily update JDK. Which in turns will > > make any future 1.6 releases not suitable for the product. > > > > Other solution is to NOT backport the change as it is. We live with the > > bugs in that area and produce some statement on the lines of: if you use > > solr, you HAVE to upgrade to latest and greatest Oak release. Or at > > lease 1.10.x. > > > > Or we manage to backport the security fixes in solr in a way that is JVM > > compatible. > > > > Unfortunately I don't have a real solution. > > +1 on the summary... > >
