Yes the project test code uses annotations and API. The test code is in the Eclipse Collections GitHub repository maintained by the project team.
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: technology-pmc-bounces@xxxxxxxxxxx [mailto:technology-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Wayne Beaton
Sent: Thursday, April 05, 2018 11:17 AM
To: Technology PMC <technology-pmc@xxxxxxxxxxx>
Subject: Re: [technology-pmc] Adding JCStress dependency for concurrent collections testing in Eclipse Collections
We are using the API only during testing.
Does any of the project test code (i.e. code maintained by the project team in a project source code repository) need to implement an API, use an annotation, or anything that might be considered linking?
On Thu, Apr 5, 2018 at 1:13 PM, Nanivadekar, Nikhil <Nikhil.Nanivadekar@xxxxxx> wrote:
Hi Wayne,
The dependency is only for testing and is added in a separate module in the project. It will not touch
any modules which are pushed to maven central. We are using the API only during testing. Neither the production code nor the released artifacts depend on the API of jcstress.
Regarding gluing it to project code library, the dependency will be downloaded as a part of a maven
build (similar to any other maven download). Since this is a stress test we do not plan to run it with every PR but it will be executed using Travis cron jobs.
Happy to create a new CQ per the documentation.
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:
technology-pmc-bounces@xxxxxxxxxxx [mailto:technology-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Wayne Beaton
Sent: Thursday, April 05, 2018 11:04 AM
To: Technology PMC <technology-pmc@xxxxxxxxxxx>
Subject: Re: [technology-pmc] Adding JCStress dependency for concurrent collections testing in Eclipse Collections
I'm not subscribed to the Eclipse Collections dev list, so you'll have to summarize this discussion there.
Combining with the GPL can be a bit problematic from a licensing POV. How do you glue project code to the library? Are there APIs that you need to use? How are those APIs licensed?
--
Wayne Beaton
Director of Open Source Projects
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/technology-pmc
--
Wayne Beaton
Director of Open Source Projects
|
