You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Kirk Lund <kl...@pivotal.io> on 2016/02/11 00:19:20 UTC

Apache compatibility with Eclipse license

Is the Eclipse license not compatible with Apache license? What I mean is:
does Apache allow derivative works of open source code that uses Eclipse
license?

For example, can someone write classes in an Apache project that extend,
use and derive or borrow code from JUnit (junit.org) classes?

Thanks,
Kirk

Re: Apache compatibility with Eclipse license

Posted by Kirk Lund <kl...@pivotal.io>.
I filed a bug to change the gemfire-junit code to only extend JUnit classes
(instead of borrowing/altering code).

https://issues.apache.org/jira/browse/GEODE-953

Completing this ticket should resolve the issue.

-Kirk


On Wed, Feb 10, 2016 at 4:12 PM, Kirk Lund <kl...@pivotal.io> wrote:

> Also just to be very clear even though it probably doesn't matter: DUnit
> and the classes under gemfire-junit are only used by our tests. The product
> obviously does not use any of this code.
>
> -Kirk
>
>
> On Wed, Feb 10, 2016 at 4:09 PM, Kirk Lund <kl...@pivotal.io> wrote:
>
>> SerializableExternalResource in Apache Geode borrows some code because
>> you can't override ExternalResource to add a throws-clause to the method
>> protected void after()
>>
>>
>> https://github.com/apache/incubator-geode/blob/develop/gemfire-junit/src/main/java/com/gemstone/gemfire/test/junit/rules/SerializableExternalResource.java
>>
>> JUnit's ExternalResource
>>
>>
>> https://github.com/junit-team/junit/blob/master/src/main/java/org/junit/rules/ExternalResource.java
>>
>> SerializableExternalResource doesn't look very interesting yet, but there
>> are DistributedRules that extend it on feature/GEODE-217. The whole effort
>> of evolving DUnit to use JUnit 4 fails unless we can do this.
>>
>> There is however an alternative. If we cannot base DUnit on JUnit 4, then
>> we could theoretically move to TestNG which uses Apache 2.0 license.
>>
>> Thanks,
>> Kirk
>>
>>
>> On Wed, Feb 10, 2016 at 3:31 PM, Roman Shaposhnik <ro...@shaposhnik.org>
>> wrote:
>>
>>> On Wed, Feb 10, 2016 at 3:27 PM, Dan Smith <ds...@pivotal.io> wrote:
>>> > Be clear about which license your talking about - there is both an
>>> Eclipse
>>> > Public License and Eclipse Distribution License. Junit is licensed
>>> under
>>> > the Eclipse Public License.
>>> >
>>> > This page lists the EPL under WEAK COPYLEFT:
>>> >
>>> > http://www.apache.org/legal/resolved.html
>>>
>>> That's exactly right!
>>> http://www.apache.org/legal/resolved.html#category-b gives
>>> you exact answer. IOW, extend should be totally fine. Borrow code --
>>> handled
>>> on a case-by-case basis. Can you show us what are you talking about?
>>>
>>> Thanks,
>>> Roman.
>>>
>>
>>
>

Re: Apache compatibility with Eclipse license

Posted by Kirk Lund <kl...@pivotal.io>.
Also just to be very clear even though it probably doesn't matter: DUnit
and the classes under gemfire-junit are only used by our tests. The product
obviously does not use any of this code.

-Kirk


On Wed, Feb 10, 2016 at 4:09 PM, Kirk Lund <kl...@pivotal.io> wrote:

> SerializableExternalResource in Apache Geode borrows some code because you
> can't override ExternalResource to add a throws-clause to the method
> protected void after()
>
>
> https://github.com/apache/incubator-geode/blob/develop/gemfire-junit/src/main/java/com/gemstone/gemfire/test/junit/rules/SerializableExternalResource.java
>
> JUnit's ExternalResource
>
>
> https://github.com/junit-team/junit/blob/master/src/main/java/org/junit/rules/ExternalResource.java
>
> SerializableExternalResource doesn't look very interesting yet, but there
> are DistributedRules that extend it on feature/GEODE-217. The whole effort
> of evolving DUnit to use JUnit 4 fails unless we can do this.
>
> There is however an alternative. If we cannot base DUnit on JUnit 4, then
> we could theoretically move to TestNG which uses Apache 2.0 license.
>
> Thanks,
> Kirk
>
>
> On Wed, Feb 10, 2016 at 3:31 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
>> On Wed, Feb 10, 2016 at 3:27 PM, Dan Smith <ds...@pivotal.io> wrote:
>> > Be clear about which license your talking about - there is both an
>> Eclipse
>> > Public License and Eclipse Distribution License. Junit is licensed under
>> > the Eclipse Public License.
>> >
>> > This page lists the EPL under WEAK COPYLEFT:
>> >
>> > http://www.apache.org/legal/resolved.html
>>
>> That's exactly right!
>> http://www.apache.org/legal/resolved.html#category-b gives
>> you exact answer. IOW, extend should be totally fine. Borrow code --
>> handled
>> on a case-by-case basis. Can you show us what are you talking about?
>>
>> Thanks,
>> Roman.
>>
>
>

Re: Apache compatibility with Eclipse license

Posted by Kirk Lund <kl...@pivotal.io>.
SerializableExternalResource in Apache Geode borrows some code because you
can't override ExternalResource to add a throws-clause to the method
protected void after()

https://github.com/apache/incubator-geode/blob/develop/gemfire-junit/src/main/java/com/gemstone/gemfire/test/junit/rules/SerializableExternalResource.java

JUnit's ExternalResource

https://github.com/junit-team/junit/blob/master/src/main/java/org/junit/rules/ExternalResource.java

SerializableExternalResource doesn't look very interesting yet, but there
are DistributedRules that extend it on feature/GEODE-217. The whole effort
of evolving DUnit to use JUnit 4 fails unless we can do this.

There is however an alternative. If we cannot base DUnit on JUnit 4, then
we could theoretically move to TestNG which uses Apache 2.0 license.

Thanks,
Kirk


On Wed, Feb 10, 2016 at 3:31 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> On Wed, Feb 10, 2016 at 3:27 PM, Dan Smith <ds...@pivotal.io> wrote:
> > Be clear about which license your talking about - there is both an
> Eclipse
> > Public License and Eclipse Distribution License. Junit is licensed under
> > the Eclipse Public License.
> >
> > This page lists the EPL under WEAK COPYLEFT:
> >
> > http://www.apache.org/legal/resolved.html
>
> That's exactly right! http://www.apache.org/legal/resolved.html#category-b
> gives
> you exact answer. IOW, extend should be totally fine. Borrow code --
> handled
> on a case-by-case basis. Can you show us what are you talking about?
>
> Thanks,
> Roman.
>

Re: Apache compatibility with Eclipse license

Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Wed, Feb 10, 2016 at 3:27 PM, Dan Smith <ds...@pivotal.io> wrote:
> Be clear about which license your talking about - there is both an Eclipse
> Public License and Eclipse Distribution License. Junit is licensed under
> the Eclipse Public License.
>
> This page lists the EPL under WEAK COPYLEFT:
>
> http://www.apache.org/legal/resolved.html

That's exactly right! http://www.apache.org/legal/resolved.html#category-b gives
you exact answer. IOW, extend should be totally fine. Borrow code -- handled
on a case-by-case basis. Can you show us what are you talking about?

Thanks,
Roman.

Re: Apache compatibility with Eclipse license

Posted by Dan Smith <ds...@pivotal.io>.
Be clear about which license your talking about - there is both an Eclipse
Public License and Eclipse Distribution License. Junit is licensed under
the Eclipse Public License.

This page lists the EPL under WEAK COPYLEFT:

http://www.apache.org/legal/resolved.html

-Dan

On Wed, Feb 10, 2016 at 3:19 PM, Kirk Lund <kl...@pivotal.io> wrote:

> Is the Eclipse license not compatible with Apache license? What I mean is:
> does Apache allow derivative works of open source code that uses Eclipse
> license?
>
> For example, can someone write classes in an Apache project that extend,
> use and derive or borrow code from JUnit (junit.org) classes?
>
> Thanks,
> Kirk
>