Re: Intent to backport OAK-8235

2019-06-21 Thread Julian Reschke
On 14.06.2019 16:08, Tommaso Teofili wrote: 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

Re: Intent to backport OAK-8235

2019-06-14 Thread Tommaso Teofili
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

Re: Intent to backport OAK-8235

2019-06-11 Thread Julian Reschke
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

Intent to backport OAK-8235

2019-06-07 Thread Tommaso Teofili
Hi all, I'd like to backport OAK-8235 to branch 1.10, 1.8 and 1.6. For branch 1.10 and 1.8 everything should be just fine, however for 1.6 we had set our java compatibility to JDK 1.7, however Solr 6.6.6 requires at least JDK 1.8. In most cases I