Your application does not need to be LGPL as long as it follows the
rules layed out in LGPL. i.e.
as long as user can replace the hibernate jars with their own - and
unless you are doing really funky
things in your Eclipse RCP app then that is all doable by modifiying the
plugin directory or .zip that includes it.
And of course if you have done some changes to your distributed version
of hibernate you need to
make those changes available to those you have distributed it to.
But yes, the url Emanuel sends is describing it all in more general terms ;)
/max
Keiko Murakami wrote:
Hi everyone,
I've been developing an application related Eclipase with hibernate
libarary.
When I build the application as RCP file that includes hibernate library,
should I distribute it under LGPL?
I read LGPL v2.1 section 5, I know my application in isolation is
"work that uses the Library(hibernate)",
but my concern is that RCPed application(executable form)
must be applied LGPL,
because it includes full hibernate library as jar files and
its hibernate library can not separate from RCPed application.
I'm not sure whether this is the right place to ask,
but I appreciate your help.
Thank you,
Keiko
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev