You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org> on 2007/12/18 23:47:43 UTC

[jira] Created: (UIMA-678) Update notice file

Update notice file
------------------

                 Key: UIMA-678
                 URL: https://issues.apache.org/jira/browse/UIMA-678
             Project: UIMA
          Issue Type: Improvement
          Components: Sandbox-CasEditor
    Affects Versions: 2.2.1
            Reporter: Jörn Kottmann
            Assignee: Jörn Kottmann


Add inclusion of eclipse (eclipse.org)
Add inclusion of svgicons (http://sourceforge.net/projects/svgicons)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Created: (UIMA-678) Update notice file

Posted by Jörn Kottmann <ko...@gmail.com>.
> The RCP runtime should be ok, classified as binary.  So I guess we  
> should
> be looking at having more than one NOTICE file for the CAS editor.   
> The
> one that goes with the source distribution (every Apache project  
> must have
> a source distribution) should not have the mention of Eclipse code,  
> because
> it's only part of the binary distribution (at least that's what I'm
> guessing).  Right?

yes, thats right the eclipse product export wizard automatically adds  
the rcp
runtime during the build from the local eclipse installation.

Jörn



Re: [jira] Created: (UIMA-678) Update notice file

Posted by Thilo Goetz <tw...@gmx.de>.
Jörn Kottmann wrote:
>> 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).
>>
>> Ignoring the version differences, what specific source code files are 
>> you incorporating?
> 
> 
> The cas editor should be packaged togehter with the eclipse rcp runtime.
> 
> The rcp runtime contains mostly binary files, but maybe some files are 
> classified as source files
> like scripts or config files. I am not sure.
> 
> I think its ok to include the rcp runtime in the release togehter with 
> an appropriate entry in the
> notice file (thats what the apache directory studio guys have done).
> 
> If you would like to take a look at the whole package I can go forward 
> and build the first
> release candidate.
> 
> Jörn

The RCP runtime should be ok, classified as binary.  So I guess we should
be looking at having more than one NOTICE file for the CAS editor.  The
one that goes with the source distribution (every Apache project must have
a source distribution) should not have the mention of Eclipse code, because
it's only part of the binary distribution (at least that's what I'm
guessing).  Right?

--Thilo


Re: [jira] Created: (UIMA-678) Update notice file

Posted by Jörn Kottmann <ko...@gmail.com>.
> 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).
>
> Ignoring the version differences, what specific source code files  
> are you incorporating?


The cas editor should be packaged togehter with the eclipse rcp runtime.

The rcp runtime contains mostly binary files, but maybe some files are  
classified as source files
like scripts or config files. I am not sure.

I think its ok to include the rcp runtime in the release togehter with  
an appropriate entry in the
notice file (thats what the apache directory studio guys have done).

If you would like to take a look at the whole package I can go forward  
and build the first
release candidate.

Jörn

Re: [jira] Created: (UIMA-678) Update notice file

Posted by Marshall Schor <ms...@schor.com>.
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
>


Re: [jira] Created: (UIMA-678) Update notice file

Posted by Jörn Kottmann <ko...@gmail.com>.
> 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

Re: [jira] Created: (UIMA-678) Update notice file

Posted by Thilo Goetz <tw...@gmx.de>.
Joern,

what Eclipse SW does the CAS Editor include?

--Thilo

Jörn Kottmann (JIRA) wrote:
> Update notice file
> ------------------
> 
>                  Key: UIMA-678
>                  URL: https://issues.apache.org/jira/browse/UIMA-678
>              Project: UIMA
>           Issue Type: Improvement
>           Components: Sandbox-CasEditor
>     Affects Versions: 2.2.1
>             Reporter: Jörn Kottmann
>             Assignee: Jörn Kottmann
> 
> 
> Add inclusion of eclipse (eclipse.org)
> Add inclusion of svgicons (http://sourceforge.net/projects/svgicons)
> 

[jira] Closed: (UIMA-678) Update notice file

Posted by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann closed UIMA-678.
------------------------------

    Resolution: Fixed

> Update notice file
> ------------------
>
>                 Key: UIMA-678
>                 URL: https://issues.apache.org/jira/browse/UIMA-678
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Sandbox-CasEditor
>    Affects Versions: 2.2.1
>            Reporter: Jörn Kottmann
>            Assignee: Jörn Kottmann
>
> Add inclusion of eclipse (eclipse.org)
> Add inclusion of svgicons (http://sourceforge.net/projects/svgicons)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.