Follow-up Comment #4, task #15227 (project administration): Hi Ineiev,
> All files should contain them, not just "source files". Which files need the license notice? There are images, translation files (language bundle) and property files for user settings. Is it OK to add the license notice in a README file in that directory for all files? > What about giving the GNU Project due credit? How much would the extra effort be? I have no objections to the philosophy of the FSF, but the program does not meet the GNU coding standards yet and it seems that Java programs are a little unpopular in the GNU project.... I could try to meet the most important standards bit by bit, but that would take some time. > Also, please include an exact copy of the GPL from gnu.org (in your case, https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt), without re-wrapping the lines. I just didn't find the text of the GNU license; I'll include the original text. > EPL-1.0 is GPL-incompatible; if this is just a compiler, it shouldn't affect the licensing of your code, but you should make sure it doesn't. The Eclipse compiler is used internally for compiling, I don't know if this is a problem. It will soon be replaced by the OpenJDK compiler anyway. But I would like to move it to the next version, because this modification needs some testing. The program was developed on OpenJDK (IcedTea), even though it also runs on Oracles JRE. So, the target Java platform does not contain any proprietary components. Regards Axel _______________________________________________________ Reply to this item at: <https://savannah.nongnu.org/task/?15227> _______________________________________________ Message sent via Savannah https://savannah.nongnu.org/
