Just to clarify:
All clops library/tool code and documentation is under the MIT license.
The clops release also contains the antlr, velocity and some velocity
dependencies. Each of these is under a separate license. None of these
libraries are required at the time of using the generated code (just the
clops-runtime.jar), so there is obviously no need to include them in your
product.
So the terms of the MIT license is all you have to worry about.
We mistakenly didn't previously include the license text in our releases on
sourceforge. We've remedied that now.
By the way, we appreciate your questions and use of the tool, so if you have
any feedback big or small, please send it our way!
Cheers,
Fintan
On Wed, Apr 29, 2009 at 8:14 PM, Viliam Holub <vil...@uc...> wrote:
> On 29. Apr (Wednesday) v 19:05:22 +0000 2009, David W wrote:
> > I did have one question about the licensing for CLOPS. I will check
> > again, but is there a file or a license notice that I need to add
> > somewhere if I plan to redistribute CLOPS runtime along with the CLI
> > I'm working on (it will be in a commercial product)?
>
> We haven't discussed it yet explicitly. But the whole project is MIT
> license
> thus the only obligation for you is not to remove the license from the
> source code (if there is any).
>
> Regards,
> Viliam
>
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Clops-users mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clops-users
>
|
