[
https://issues.apache.org/jira/browse/UIMA-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530529
]
Marshall Schor commented on UIMA-536:
-------------------------------------
before I write to legal-discuss, let's explore one other thing. Suppose these
3 files "configure" the RCP building process, but don't get incorporated into
the resulting thing that is built.
Then we *could* have an approach where we don't distribute these files, but
instead treat them as part of our "build" process. We could even exclude them
from the "src" distribution - and say people who want to "build" have to get
things from our SVN.
Do we have another issue, though, on top of this? I'm thinking (I haven't
looked into it yet..) that the Eclipse "build" process essentially takes your
software modules, these config files, and *some Eclipse boilerplate code* and
creates a set of executables, for various platforms. These executables contain
copies of Eclipse boilerplate code - is that correct? So if we distribute
this, we're distributing a package which combines code from Eclipse with our
stuff - is this right?
Thanks for clarifying...
> Build Cas Editor as rcp application with maven
> ----------------------------------------------
>
> Key: UIMA-536
> URL: https://issues.apache.org/jira/browse/UIMA-536
> Project: UIMA
> Issue Type: Improvement
> Components: Sandbox
> Reporter: Jörn Kottmann
> Assignee: Jörn Kottmann
> Attachments: UIMA-536.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
