Re: [egit-dev] UI tests: current SWTBot requires JUnit 4

[Shawn Pearce <spearce@xxxxxxxxxxx>]

On Sun, Jan 31, 2010 at 1:51 PM, Matthias Sohn
<matthias.sohn@xxxxxxxxxxxxxx> wrote:
> 2010/1/31 Chris Aniszczyk <caniszczyk@xxxxxxxxx>
>>
>> On Sun, Jan 31, 2010 at 12:07 PM, Matthias Sohn
>> <matthias.sohn@xxxxxxxxxxxxxx> wrote:
>> > Could you advise how to proceed here ? In order to allow test execution
>> > in
>> > Eclipse 3.4, 3.5, 3.6 we should depend on JUnit 4.3.1 (which is the
>> > version
>> > coming
>> > with Eclipse 3.4). Eclipse 3.5 comes with JUnit 4.5.1 and 3.6 currently
>> > has
>> > 4.7.1.
>> > For which JUnit versions do we need to create a CQ ?
>>
>> Since we don't ship the tests, we don't need to create CQs for them.
>>
>> CQs are only needed when you ship code from Eclipse.org, tests are
>> generally excluded from them.
>
> Ok, this implies we also don't need a CQ for hamcrest.org since that is
> required for SWTBot tests only :-)

I've gotten incredibly vague replies back from EMO IP team about this.

I asked for confirmation about which items we might need to include as
a CQ, and which items we don't in both the EGit and the JGit IP log.  What
I got back was a link to [1] and a non-committal answer, because attorneys
are terrified of giving out what later might amount to being the wrong answer.

Right now my limited understanding is, we have to list everything as a CQ if
we link to it, even if we don't generally redistribute it to
end-users.  That way
we at least fully disclose our requirements.

Given the recent private thread about our copyright headers in our sources,
I also now have absolutely no faith in the IP log approval and review processes.
We've approved the IP log for EGit, like twice now, but our copyright headers
apparently don't meet the foundation's standards.  And we might not yet have
our CQ list complete.

Uhm.  Yay?

[1] http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf