|Re: [wtp-dev] JSDT Sync call minutes |
+1 from me too, but...
Yes, I've asked not to include any JUnit tests into the contribution. Otherwise I have had to open a number of additional CQs for those tests, while we are limited in time.
Any JUnit Tests which aren't bringing a licensing problems are welcomed and can be added at any time after the contribution is done.
There is a couple of little licensing problems regarding these tests:
1) any json file (like bower.json, for example) is to be written by a committer or a contributor (we must respect authors) - I think it's the smallest problem.
As far as I understood, we have to open a CQ every time we need to use something "from outside" in case we're not sure that it's license allows us to do it from Eclipse.
Ilya has some JUnit tests for bower/npm tools - but those tests don't download anything afaik. So, if we have some tests which aren't using a content not authored by a contributor (Angelo or the other ones) or a committer - we CAN push such tests into Source Editing repo. Otherwise we have to open a CQ for every file or a library to be used and/or downloaded by JUnit test during its work.
In most cases there are no problems to open a CQ... It just takes to long to resolve sometimes.
On 01/13/2016 11:29 AM, Mickael Istria wrote:
CONFIDENTIALITY NOTICE: This email and files attached to it are confidential. If you are not the intended recipient you are hereby notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
Back to the top