> 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. > 2. I will not add maven coordinates for these, right? Shall I open an issue > or mark the review as “Done” in the List of Modules to Review? > Or > 3. Build a small ant project that downloads sources from Maven, applies > patches as required and recreates the binaries. Building those in an automatic fashion would be great! --emi On Sat, Oct 14, 2017 at 10:22 AM, Antonio Vieiro <[email protected]> wrote: > 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 <[email protected]> escribió: >> >> 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 open an issue >> or mark the review as “Done” in the List of Modules to Review? >> >> Thanks, >> Antonio >> >> >> [1] >> https://github.com/apache/incubator-netbeans/blob/master/o.apache.xml.resolver/external/resolver.patch >
