On Jan 11, 2008 11:06 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > On Jan 11, 2008 11:50 AM, Litrik De Roy <[EMAIL PROTECTED]> wrote: > > And more importantly - because I don't want to get into trouble - how > > do I figure out what the license of each dependency is? > > They are all either ALv2 or compatible licenses, so you'll be fine as > long as you include all the relevant copyright notices. If you like, I > can help you with that.
That would be great. I'm was hoping that maven would be able to spit out all license/copyrights as well. I guess you'll need those licenses sooner or later anyway, if you plan to provide a binary release (including dependencies). > Legally there's no trouble if you just put your sources available, you > only need to worry about the licenses of the dependencies if you > release a binary plugin that contains the dependency jars. Hmm... I don't see how I can get the Eclipse plug-in to work without including the dependencies in my own project. Unless I go for a source only plug-in where you'll have to build Tika first and then copy the dependencies yourself. For the Eclipse plug-in to work, the dependency jars must be located inside the plug-in. I don't think Eclipse OSGi is able to dynamically pull them from a maven repository. I think I'll just read each 3rd party license and if OK I'll check them in (together with their license/copyright) file. This allows me to do a binary release. -- Litrik De Roy Norio ICT Consulting - http://www.norio.be/
