Embedding the classes from one jar in another tends to lead to jar hell; namely people wondering why putting a later version of sanselan in their classpath isn't working. If you're a user end application then you can get away with it.
Legally; follow the license. For me that means including the LICENSE and NOTICE in my distribution, but there's more to the license than that and you should make sure you and your legal advisor don't have concerns. I wouldn't worry about copying the jar amongst apps; that allows for better autonomous coding. If size is an issue, use tools to shrink sanselan down to the bits each app is actually using. Hen On Thu, Jul 1, 2010 at 10:51 AM, Norman Shapiro <[email protected]> wrote: > I want to distribute applications that use sanselan, and want to meet all > legal, > ethical and practical requirements. > > I don't know where to put the required copyright notice(s). > > Also, I don't know how to distribute sanselan-*-incubator.jar. If I distribute > it as a separate jar file, or as reference to a copy on a web site, the > installation scripts and Microsoft batch files will have to know where on the > host computer it is installed. I'm thinking that it would be best to > incorporate > the contents of sanselan-*-incubator.jar into my jar file and then just > distribute my jar file, along with my sources. I know that doing so would > mean, > in effect, a separate copy of sanselan-*-incubator.jar for each application, > but > its only half a megabyte. > > Advice will be appreciated. > > > Norman Shapiro > 798 Barron Avenue > Palo Alto CA 94306-3109 > (650) 565-8215 > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
