Right, according to https://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Dependencies
But it also says "*Test-only dependencies must not be checked into Eclipse SCM in any form*" which doesn't work for m2e. Anyways, I don't want to highjack the JSDT thread with m2e specific issues. I'll try to follow up on that matter when I get spare cycles. Fred On Wed, Jan 13, 2016 at 4:44 PM, Mike Milinkovich < mike.milinkov...@eclipse.org> wrote: > On 13/01/2016 4:13 PM, Fred Bricon wrote: > >> This is less than ideal, obviously, I'd prefer if we could have all code >> and run all tests on the same infra, but I just can't imagine having to >> open ~400 CQs (it'd be probably forbidden upon by the Geneva convention) >> > > Perhaps I am misunderstanding this thread, but to me these tests sound > like Build and Test dependencies. I am pretty sure that you can file one CQ > for all the test dependencies and you're done. > > -- > Mike Milinkovich > mike.milinkov...@eclipse.org > +1.613.220.3223 (mobile) > > > _______________________________________________ > wtp-dev mailing list > wtp-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/wtp-dev > -- "Have you tried turning it off and on again" - The IT Crowd And if that fails, then http://goo.gl/tnBgH5
_______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
