From: "Lord Bulbous" <[EMAIL PROTECTED]> > Hi folks, > > First of all, let me say that I am a huge dom4j fan. > I think dom4j is one of the most useful libraries around. > I now put dom4j on my cereal every morning instead of milk!
:-) > I'm currently packaging a release of an open-source project > that includes dom4j (http://www.xmltester.org). Naturally, > I am going to give due credit to the dom4j project. You don't have to at all, but its nice if you do. > I think > it is also my responsibility to provide credit to the > authors of libraries included WITH dom4j. However, it's > not clear to me how to do so. Hence this missive. > > The Dom4j 1.3 distribution includes the jars shown below, > but does not (as far as I can tell) include a file > identifying the source of each jar, the type of license > that jar carries, or what version of the library is included. It should do really. > I don't want to be a weenie, but isn't this sort of a minor > violation of the license of at least the apache components > (xalan, xerces, ant, etc.)? Redistribution of these jars > requires including a statement in the documentation like > "This product includes software developed by the Apache > Software Foundation (http://www.apache.org/)"? AFAIK you don't need to make that statement, though the licences should be included in the distribution. So we should ship a copy of the ASF licence with dom4j. > I know it's a pain-in-the-editor to attribute all this stuff, > but isn't that one of the debts we owe each other as open > source developers? > > I know what a lot of these jars are. I can go search and > find out where each of the other files comes from, but it > won't be easy for me to guess what version is included. > It sure would be nice to have an authoritative list of > credits from the authors. > > If I simply missed these attributions in the documentation, > I beg of you a thousand pardons. The Maven build of dom4j (which is nearly complete now) has explicit references to the dependencies, all of which are hosted at Maven's repository. It should be possible to get Maven to automatically copy licences & a list of credits as part of any Maven build. (This is a common problem in all open source software builds). Note also that inside the manifest of each JAR should be a reference to who makes the software, what its version is, its website etc. So these typically should be inside the jars themselves. Again using Maven can help make this happen. James ------- http://radio.weblogs.com/0112098/ __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user
