Axton, I'm well aware of GPL and Java being opensourced under the GPL. There's one exception though, Java is GPLled with the classpath exception that allows linkage from any program, opensource or not. Without that exception, the linking program must also be GPL. See the wikipedia site on this for more info: http://en.wikipedia.org/wiki/GPL_linking_exception. The first line reads:
"*Linking this library statically or dynamically with other modules is making a combined work based on this library. Thus, the terms and conditions of the GNU General Public License cover the whole combination." *Java is now being open sourced under the GPL with the classpath exception. That allows normal developers to _use_ the jvm as usual. If they _change_ the jvm they should share those changes. Without the exception, linking would also qualify as a derrived work, thus a change. I'm not a legal guy, but I've read topics on this subject many times and I just wanted to raise the question as it might be a problem when using RTL or JOARSE at customer sites. Unless you are meaning to GPL your source ofcourse. Hugo On 12/11/06, Axton <[EMAIL PROTECTED]> wrote:
** GPL languages do not require programs written with them to be GPL. It only requires that projects derived from the GPL'd software be GPL'd (i.e., you write a fork of RTL that you want to release). Think about it, Java is moving to GPL, gnu gcc is GPL, and the list goes on and on. Axton Grams On 12/11/06, Hugo Visser <[EMAIL PROTECTED]> wrote: > > ** Dan, > > As a sidenote, why is JOARSE made GPL? GPL will require that any program > that uses JOARSE to be GPL as well. Wouldn't be LGPL be a better fit (I'd > prefer Apache or BSD license myself)? > > Hugo > > On 12/11/06, Hugo Visser <[EMAIL PROTECTED] > wrote: > > > > Dan, > > > > Personally I'm reluctant to use another library that uses JNI. > > Although the Remedy supplied API is a bit weird and maybe even buggy on > > certain areas, it is supported and also runs on all of the supported > > platforms. We have customers on about every supported platform so I really > > care about that one. That's why I'd rather "wrap" the Remedy supported API > > (with the JNI part), and not build (or reuse) something else that has > > essentially the same kind of deployment problems (JNI libraries and related > > libraries). > > > > I agree that the non-JNI route will be hard or even impossible, since > > it involves reverse enginering of the RPC protocol calls and that is probaly > > not allowed, if you get it done in the first place at all :) > > > > So don't get me wrong, I think it's great that there are alternatives > > such as RTL and JOARSE, I'm sure those libraries help many people in doing > > their jobs effectively. I was just thinking up loud considering the > > alternatives to the Remedy Java API, and maybe a bit daydreaming about a > > pure Java version of it :) > > > > Hugo > > > > On 12/8/06, Dan Hardy < [EMAIL PROTECTED] > wrote: > > > > > > ** > > > > > > > > > > > > Rather than start any new projects, please consider adding to these > > > existing projects: > > > > > > > > > > > > C++ (uses STL for collections, exceptions, and provides > > > encapsulation of memory management. Compiles on Windows, Linux, Solaris.) > > > > > > > > > > > > http://www.sourceforge.net/projects/rtl > > > > > > Why you should use this: http://rtl.sourceforge.net/doc (check out > > > the code comparison) > > > > > > > > > > > > Java (uses proper collections, and is reasonably OO – could use an > > > upgrade to Java 5 features. Works on at least Windows and Linux – can't > > > recall if I provided Solaris binaries) > > > > > > http://www.sourceforge.net/projects/joarse > > > > > > > > > > > > COM (automation compatible, uses proper COM collections and error > > > handling, and is also usable from .NET – only 168 kb) > > > > > > http://www.sourceforge.net/projects/coarse > > > > > > > > > > > > As far as I know, these are all very stable. The latter two > > > projects build on the first (they were initially examples of how trivial it > > > is to build APIs for other languages once you have RTL). > > > > > > > > > > > > Dan > > > > > > > > > > > > > > > ------------------------------ > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > > > [EMAIL PROTECTED] *On Behalf Of *Hugo Visser > > > * Sent:* Friday, December 08, 2006 3:18 AM > > > *To:* [email protected] > > > *Subject:* Re: Java Extended API for J2SE5.0 ? > > > > > > > > > > > > ** John, > > > > > > No JNI that would be great :) In the past I've investigated doing a > > > "light" api in pure Java, but the whole RPC stuff seemed the biggest hurdle. > > > One could ofcourse build a wrapper around the existing API using collections > > > and annotations (which I have done just to keep things compatible) but then > > > you'll still be stuck with the jni stuff. I think it would be nice to start > > > some kind of opensource project of some kind for making working with Remedy > > > easier. Maybe an API layer or an alternative API. > > > > > > Hugo > > > > > > On 12/8/06, *John Baker* < [EMAIL PROTECTED]> wrote: > > > > > > Julio, > > > > > > I feel your chances of getting that from the Remedy Java API are > > > around nil. > > > The API isn't even OO, let alone equipped with Collections (which > > > was a year > > > 2000 feature) - hence, while a nice Java API would be welcome, it's > > > never > > > going to happen until the Remedy Java API is taken seriously (I > > > include > > > removing JNI in this statement). > > > > > > However. I had heard of an open source Remedy Java API, if you fancy > > > > > > contriburing towards an alternative.1 > > > > > > > > > John > > > > > > Java System Solutions : http://www.javasystemsolutions.com > > > > > > > > > _______________________________________________________________________________ > > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.orgARSlist:"Where the Answers Are" > > > > > > > > > __20060125_______________________This posting was submitted with > > > HTML in it___ > > > > > > __20060125_______________________This posting was submitted with > > > HTML in it___ > > > > > > > __20060125_______________________This posting was submitted with HTML in > it___ > __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
