J libraries and addons, unless explicitly stated, are all under Jsoftware copyright and are covered by the documentation in the J Help -> User Manual -> General Information -> Copyright / Warranty / License.
Jsoftware products are not under GPL and there are no GPL considerations. Jsoftware separately released a copy of the J Engine source under GPL, but this in no way affects Jsoftware's own use and distribution of its J Engine source or users who have a commercial license to that source. GPL is only an issue if you use an engine built with the GPL source. In that case you have to make your own assessment of where GPL starts and where it ends. The Jsoftware position is that it begins and ends with the GPL engine source and that scripts and libraries are in no way affected. Summary: 1. Jsofware license is simple and clearly stated in the docs 2. if you don't use the GPL engine source there are no GPL issues 3. if you use the GPL source, then whether there are GPL issues only you and your lawyers can decide (we think it is silly to think that scripts are affected by a GPL engine as then GPL would be like ice-9). If you have further questions I suggest you contact me directly outside of the forum. You might be interested in a commercial J Engine source license to avoid any GPL. You might also be interested in the imminent release of Jd, and new, much improved JDB, that will be a Jsoftware commercial product. On Sun, May 11, 2014 at 8:45 AM, Michal Wallace <[email protected]> wrote: > Are these two libraries considered part of J? > If so, do they share J's license? > If so, am I required to put any code that uses JDB under the GPL? > > What about the rest of JAL? > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
