You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "John D. Ament" <jo...@apache.org> on 2016/06/07 11:25:58 UTC
EPL Dependency - Notice required?
All,
Apache DeltaSpike has a compile-time dependency on junit for its test
control module -
https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/impl/pom.xml#L63
I was wondering, do we in fact need a NOTICE file calling out this
dependency, since its Cat B (EPL)? We mark it as provided, but
realistically the module doesn't work without it. So we're not providing
the dependency, but do require a user to bring it.
John
Re: EPL Dependency - Notice required?
Posted by "John D. Ament" <jo...@apache.org>.
On 2016-06-07 14:59 (-0400), Stian Soiland-Reyes <st...@apache.org> wrote:
> No NOTICE should be required if you do not bundle/embed or distribute
> junit, a regular <dependency> is fine.
>
> You should not need to make use <scope>provided, compile or test (normally)
> scope is OK, that's how many ASF Java projects do unit testing.
Stian,
Just to clarify, we use compile/provided scope as we are creating an extension to JUnit (other areas of the project use JUnit to test).
Thanks for the clarification.
John
> On 7 Jun 2016 12:26 p.m., "John D. Ament" <jo...@apache.org> wrote:
>
> All,
>
> Apache DeltaSpike has a compile-time dependency on junit for its test
> control module -
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/impl/pom.xml#L63
>
> I was wondering, do we in fact need a NOTICE file calling out this
> dependency, since its Cat B (EPL)? We mark it as provided, but
> realistically the module doesn't work without it. So we're not providing
> the dependency, but do require a user to bring it.
>
> John
>
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: EPL Dependency - Notice required?
Posted by Stian Soiland-Reyes <st...@apache.org>.
No NOTICE should be required if you do not bundle/embed or distribute
junit, a regular <dependency> is fine.
You should not need to make use <scope>provided, compile or test (normally)
scope is OK, that's how many ASF Java projects do unit testing.
On 7 Jun 2016 12:26 p.m., "John D. Ament" <jo...@apache.org> wrote:
All,
Apache DeltaSpike has a compile-time dependency on junit for its test
control module -
https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/impl/pom.xml#L63
I was wondering, do we in fact need a NOTICE file calling out this
dependency, since its Cat B (EPL)? We mark it as provided, but
realistically the module doesn't work without it. So we're not providing
the dependency, but do require a user to bring it.
John
Re: EPL Dependency - Notice required?
Posted by Philippe Ombredanne <po...@nexb.com>.
On Tue, Jun 7, 2016 at 1:25 PM, John D. Ament <jo...@apache.org> wrote:
> All,
>
> Apache DeltaSpike has a compile-time dependency on junit for its test
> control module -
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/impl/pom.xml#L63
>
> I was wondering, do we in fact need a NOTICE file calling out this
> dependency, since its Cat B (EPL)? We mark it as provided, but
> realistically the module doesn't work without it. So we're not providing
> the dependency, but do require a user to bring it.
FWIW, Tomcat bundles and redistributes the EPL-licensed Eclipse Java Compiler.
This may give you some hints.
--
Cordially
Philippe Ombredanne
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org