My understanding from discussions and reading
http://people.apache.org/~rubys/3party.html
<http://people.apache.org/%7Erubys/3party.html>, the principles for
distributing things involving Eclipse are:
1) You can distribute binaries (but not sources) of things that are EPL
<http://opensource.org/licenses/eclipse-1.0.php> (Eclipse Public
License) licensed, as long as the notice file identifies these and
provides a link to the source for these. (This requirement comes from
the EPL license).
2) You cannot include in your distribution Eclipse "sources" - because
that would require using the EPL as the license, not the Apache
license. The 3party page has this, though:
For small amounts of source that is directly consumed by the ASF
product at runtime in source form, and for which that source is
unlikely to be changed anyway (say, by virtue of being specified by
a standard), this action is sufficient. An example of this is the
web-facesconfig_1_0.dtd
<http://java.sun.com/dtd/web-facesconfig_1_0.dtd>, whose inclusion
is mandated by the JSR 127: JavaServer Faces
<http://jcp.org/en/jsr/detail?id=127> specification.
3) If you have source code which is a "derivative work" of Eclipse
source, which can happen if you take an eclipse source file and modify
it and incorporate the modified/customized file into your source, then
that's a gray area I'm not too clear about.
Ignoring the version differences, what specific source code files are
you incorporating?
-Marshall
Jörn Kottmann wrote:
what Eclipse SW does the CAS Editor include?
This depends on the eclipse version which is used to create the build.
The current eclipse version is 3.3.1.1.
The guys from the apache directory studio
(http://directory.apache.org/studio/) also
do not include the version in the notice file.
Jörn
