Re: How to handle patches for external binaries?

Sounds good for me.. -Sven Am 14.10.2017 13:33 schrieb "Antonio" : On 14/10/17 11:17, Emilian Bold wrote: > 1. What’s the license of these patches? Same as the original project? Or >> Apache 2? >> > > Since it's code from Oracle, it's going to be relicensed as Apache 2. >

Re: How to handle patches for external binaries?

On 14/10/17 11:17, Emilian Bold wrote: 1. What’s the license of these patches? Same as the original project? Or Apache 2? Since it's code from Oracle, it's going to be relicensed as Apache 2. Ok. If I see something weird I'll raise my hand (patching non Apache-2 licensed binaries with an

Re: How to handle patches for external binaries?

Or 3. Build a small ant project that downloads sources from Maven, applies patches as required and recreates the binaries. > El 14 oct 2017, a las 9:15, Antonio Vieiro escribió: > > Hi all, > > Some modules contain patches that must be applied to third-party source >

How to handle patches for external binaries?

Hi all, Some modules contain patches that must be applied to third-party source projects in order to generate external binaries (an example at [1]). 1. What’s the license of these patches? Same as the original project? Or Apache 2? 2. I will not add maven coordinates for these, right? Shall I