Re: [collections-dev] Adding JCStress dependency for concurrent collecti

["Nanivadekar, Nikhil" <Nikhil.Nanivadekar@xxxxxx>]

Sharon,

 

The code will be committed in: https://github.com/eclipse/eclipse-collections so it will be a part of an Eclipse repo. However, we will not be publishing it as a part of any artifacts.

I will raise an IP review as well as a PMC review.

 

Thanks,

Nikhil.

 

 

The Goldman Sachs Group, Inc. All rights reserved.

See http://www.gs.com/disclaimer/global_email for important risk disclosures, conflicts of interest and other terms and conditions relating to this e-mail and your reliance on information contained in it.  This message may contain confidential or privileged information.  If you are not the intended recipient, please advise us immediately and delete this message.  See http://www.gs.com/disclaimer/email for further information on confidentiality and the risks of non-secure electronic communication.  If you cannot access these links, please notify us by reply message and we will send the contents to you.

 

From: Sharon Corbett [mailto:sharon.corbett@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, April 03, 2018 8:38 AM
To: Nanivadekar, Nikhil [Tech] <Nikhil.Nanivadekar@xxxxxxxxxxxxxxx>
Cc: collections-dev@xxxxxxxxxxx; license <license@xxxxxxxxxxx>
Subject: RE: Adding JCStress dependency for concurrent collections testing in Eclipse Collections

 

Hello Nikhil:

Thanks for checking in.  You are correct in that GPL licensed content cannot be approved for Eclipse distribution. 

However, from what you describe it seems you may only have a requirement to use JCStress on a Build machine only.    If that is the case and the third party library will not be included in any Eclipse downloads nor checked into any Eclipse repositories, then it falls into the category of Build Dependency [1] only.  Build Dependencies fall under the umbrella of Workswith [2] Dependencies.  There is a requirement to still raise a CQ (IP Request); however, no IP review will take place.  

 

Please let us know if that is not the case and/or if you have any lingering questions.

 

[1] https://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Dependencies

[2] https://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf

Best Regards,

Sharon Corbett

Eclipse Foundation Inc.

 

 

From: Nanivadekar, Nikhil <Nikhil.Nanivadekar@xxxxxx>
Sent: April-02-18 11:27 AM
To: license@xxxxxxxxxxx
Cc: collections-dev@xxxxxxxxxxx
Subject: Adding JCStress dependency for concurrent collections testing in Eclipse Collections

 

Hi Eclipse License Team,

 

We have a Pull Request for Eclipse Collections wherein we want to add jcstress-based tests for concurrent collections. However, jcstress is GPL licensed. From the Eclipse License FAQ, EPL and GPL are not compatible. Since JCStress will not be a direct dependency but only for build, I was seeking guidance if it is fine to merge this PR from a license perspective?

 

PR link: https://github.com/eclipse/eclipse-collections/pull/430

 

JCStress license link: http://hg.openjdk.java.net/code-tools/jcstress/file/64f2cf32fa0a/LICENSE

 

License Wiki link which I referred to: http://www.eclipse.org/legal/eplfaq.php#GPLCOMPATIBLE

 

Thanks,

Nikhil.

 

The Goldman Sachs Group, Inc. All rights reserved.

See http://www.gs.com/disclaimer/global_email for important risk disclosures, conflicts of interest and other terms and conditions relating to this e-mail and your reliance on information contained in it.  This message may contain confidential or privileged information.  If you are not the intended recipient, please advise us immediately and delete this message.  See http://www.gs.com/disclaimer/email for further information on confidentiality and the risks of non-secure electronic communication.  If you cannot access these links, please notify us by reply message and we will send the contents to you.