<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Reid Kaufmann wrote:
<blockquote cite="mid:48690F74.6020404@Sun.COM" type="cite">Because
several projects in Sun are evaluating Drools, it is being
considered for distribution with OpenSolaris. </blockquote>
Out of interest is Drools used in any sun apps, or are you just
distributing it incase third parties need it?<br>
<blockquote cite="mid:48690F74.6020404@Sun.COM" type="cite">I'm
weighing the pros
and cons of building from source locally or using the distributed
binaries. So, with that in mind I would like some help understanding
an issue related to your binary distribution:<br>
While it is very convenient that Drools' binary distribution contains
its dependencies, I'm curious how you are complying with the licenses
of those dependencies, particularly those that are third-party. I see
no licensing information or attribution in the tarball/zip that I
downloaded (except for the ASL license).<br>
<br>
Take xpp3 for example; xpp3-min-1.1.3.4.O.jar is included in the zip I
downloaded. Independently, I found this in the xpp3 source tarball
(see the attachment for the complete license):<br>
<blockquote><tt>2. Redistributions in binary form must reproduce the
above copyright <br>
notice, this list of conditions and the following disclaimer in <br>
the documentation and/or other materials provided with the
distribution.<br>
...<br>
Alternately, this acknowledgment may appear in the software itself, <br>
if and wherever such third-party acknowledgments normally appear.<br>
</tt></blockquote>
Does this information appear in the binary package? I've read the wiki
page on dependencies and done some greps in the source download and
binary download and haven't found it...<br>
</blockquote>
We use Maven and maven specifies the dependency poms, which specifies
and provides the licenses. We actually use Maven to suck in the
dependencies into
the bin zip. Maybe we should think about including a licenses for each
dependency too, for that to happen I'd like to see it automated as part
of the maven build. I don't have time for that now, if anyone wants to
submit a patch to automate maven for this, let me know.<br>
<blockquote cite="mid:48690F74.6020404@Sun.COM" type="cite"><br>
Reid Kaufmann<br>
<pre wrap=""><pre wrap="">
<hr size="4" width="90%">
_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre></pre>
</blockquote>
<br>
</body>
</html>