[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3557: ---------------------------------- If ASLv2 is acceptable as a compatible license to EPL, then I would think we don't have to relicense the izpack stuff. If ASLv2 and LGPL in the installer's *output* is acceptable (but GPL is *unacceptable*) then we have to change the licenses in central/plugins/org.jboss.tools.central.themes -- multi-licensed somehow under EPL, *GPL*, LGPL, Apache v2 and BSD! -- but probably the rest of JBT is OK. I'll look for more examples of *GPL* code. My only question here remains: if it's OK to ship a bundle (installer jar) which is created/distributed under EPL, how is it OK to include software inside that bundle which is under a DIFFERENT license? Seems a bit bait-and-switch to me... you accept EPL for the installer, but then suddenly you've got differently-licensed code on disk. [~fontana] ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)