RE: [te-code-users] Re: Parsing nested command line options...

[Andrew S. T. <ato...@ei...>]

Kat,

Glad it was helpful.

Rest of the answers are in-line.

On Tue, 2005-06-21 at 18:27, Kathiresan Nellayappan wrote:
> 1. I am trying to include te-common.jar into our jar file. Is it OK to
> re-pack the jar file ? What I mean is, extract the class files from
> te-common.jar and re-package the class files into our own jar file.

You can do what you need to do, but you do know you can use the
Class-Path attribute in the jar MANIFEST.MF to specify the classpath you
need.

However, the license says you can do with it what you need to do. 
There's nothing prohibiting you repackaging the classes.

> 2. In order to include te-common.jar's class files, what should our
> software do in terms of MPL ?
> 

The TE-Code license is derived from BSD, not the MPL, although they are
quite similar.  The specific requirements for including any part of
te-common are specified rather explicitly in the license
(http://te-code.sourceforge.net/LICENSE.html).  Unless you trim out the
bits not relating to the command package, you will also need to include
the corresponding licenses from Jaxor and Sun.  This isn't normally a
big deal.  If you look at the libro source, you'll see one way of making
sure multiple licenses are included.  Also, all of the licenses should
appear (likely in an appendix) in any documentation shipped with your
software.

Hopefully, this clears up any questions you might have.  If not, just
let me know.

ast
-- 
Andrew S. Townley <ato...@ei...>
http://atownley.blogspot.com