-
1. Re: Translator License
> Firstly, Can I use my the current jdbc-translators under LGPL licenses for the development of my tool without any issues?
You are not required to relicense any of your code. If you wish to stay under the LGPL, that is fine.
> Secondly, why such an difference between the licensing in the different version of the translators.
The ASL is more permissive than the LGPL and most projects under the JBoss umbrella have moved to the ASL.
-
2. Re: Translator License
Thanks for quick reply Steven,
Few small queries on your answers:
You are not required to relicense any of your code. If you wish to stay under the LGPL, that is fine.
--- So we can use translators in commercial tool? Is it ok?
The ASL is more permissive than the LGPL and most projects under the JBoss umbrella have moved to the ASL.
--- Any date for the release of new translators under ASL.
-
3. Re: Translator License
> So we can use translators in commercial tool? Is it ok?
I'm confused about what specifically you are asking about. Are you asking about LGPL licensed or ASL Teiid jars? Or are you asking about custom code that extends the Teiid translator? In all of these paths the simple answer is that yes. See Comparison of free and open-source software licenses - Wikipedia for high-level attributes of the licenses. In general if you are modifying Teiid source to create a derived work that is under the ASL for a commercial context then you would need that to also be distributed in compliance with LGPL.
> Any date for the release of new translators under ASL.
Most of the code base has been ASL since 10.0 [TEIID-4474] Re-license under a more permissive license - JBoss Issue Tracker