| Integrating modified Eclipse code into an RCP [message #18199] |
Thu, 31 March 2005 10:52  |
Eclipse User |
|
|
|
Hi
I am building and RCP and I am finding most of what I want to do is
already implemented in some form within the Eclipse packages. I would
like to know what is the policy in copying the code and reusing it in my
own code. For example, the BasicNewResourceWizard is something I would
like to reuse but without the dependencies to the IDEPlugin. I could
just copy the methods and modify the code but I have no idea of what
copyright blurbs or acknowledgement that I must include in my own
refactored code.
thank you
-H
|
|
|
|
|
|
|
| Re: Integrating modified Eclipse code into an RCP [message #18386 is a reply to message #18373] |
Mon, 04 April 2005 02:05  |
| Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
Any code that was once CPL is always CPL. If you change CPL code, it's
still CPL code, and CPL code is always open source. This is really not a
burdensome constraint; it basically says, if you can meet your needs
with a simple modification of CPL code, then you should offer your mods
on the same basis the original code was offered. But hey, in this
circumstance, don't you owe it to the community to contribute your
improvements? At the end of the day, it boils down to what's fair.
Bob
Dejan Stankovic wrote:
> Is that neccessary? I thought CPL licensing doesn't force you to publish
> your changes (I might be wrong here).
>
> Dejan Stankovic
>
> Bob Foster wrote:
>
>> And by the way, your modified code is also open source, so you need to
>> be prepared to supply it to anyone who asks. What I do is ship the
>> source of modified Eclipse classes in a *src.zip with my plugin.
>>
>> Bob Foster
|
|
|
| Re: Integrating modified Eclipse code into an RCP [message #18402 is a reply to message #18386] |
Mon, 04 April 2005 02:28 |
| Eclipse User |
|
|
|
Originally posted by: dstanko_auMAPS.hotmail.com
Bob,
I understood you said that code *must* be supplied or at least
available. My understanding was that you *must* do that under GPL, but
that it is optional with CPL.
We do agree that it would be fair and responsible thing to make your
code available to everyone.
Dejan
Bob Foster wrote:
> Any code that was once CPL is always CPL. If you change CPL code, it's
> still CPL code, and CPL code is always open source. This is really not a
> burdensome constraint; it basically says, if you can meet your needs
> with a simple modification of CPL code, then you should offer your mods
> on the same basis the original code was offered. But hey, in this
> circumstance, don't you owe it to the community to contribute your
> improvements? At the end of the day, it boils down to what's fair.
>
> Bob
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04642 seconds
Home