This content has been marked as final.
Show 6 replies
-
1. Re: nukes license
julien1 Nov 19, 2003 7:31 PM (in response to sysuser1)GPL, I commited files with the wrong Banner because I am developing JBoss code at the same time and I did not pay attention to it.
julien -
2. Re: nukes license
joanrey Nov 20, 2003 1:30 AM (in response to sysuser1)hello julien,
Does this mean that we're required to open up the source for new modules?
I do believe that if we modify the core and other GPL'd modules we're required to give back the changes.. but if we build an entirely different module, is it required to set the license to GPL?
-joanrey -
3. Re: nukes license
sysuser1 Dec 1, 2003 4:28 AM (in response to sysuser1)Hi Julien,
i think the GPL license will not work for us, is there a possibility to obtain a commercial license ?
Steffen -
4. Re: nukes license
sgwood Feb 11, 2004 7:43 AM (in response to sysuser1)"cooper" wrote:
GPL, I commited files with the wrong Banner because I am developing JBoss code at the same time and I did not pay attention to it.
julien
Julien,
Could you clarify this? JBoss is LGPL, not GPL. Is Nukes GPL or not? If not, the banners in the code have to change.
I would suggest some clarification on the project web site and including a license reference in the distribution.
Thanks for pulling this all together,
Sherman -
5. Re: nukes license
julien1 Feb 11, 2004 1:53 PM (in response to sysuser1)this is GPL, we need to be consistent
-
6. Re: nukes license
sgwood Feb 12, 2004 9:55 AM (in response to sysuser1)"joanrey" wrote:
hello julien,
Does this mean that we're required to open up the source for new modules?
I do believe that if we modify the core and other GPL'd modules we're required to give back the changes.. but if we build an entirely different module, is it required to set the license to GPL?
-joanrey
See http://www.gnu.org/licenses/gpl-faq.html#MereAggregation.
Particularly,If the modules are included in the same executable file, they are definitely combined in one program. If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.
My interpretation (and, just for the record, I am not a lawyer) is:
Since a module uses the JBoss Nukes API/code, it is required to be GPL. If you layer your code so that it can be used independently of using the JBoss Nukes API/code, then you can license your models etc how you want. An example is the relationship between JBoss and Nukes - Nukes needs JBoss to run, not the other way around. Using Nukes does not magically make JBoss change its license to GPL.
So your module UI will be GPL, but not necessarily all your code.
Cheers,
Sherman