| Re: [m2e-dev] m2e-core-tests on different repo |
IP is the reason. We'd need to get all test dependencies through CQ process to move m2e tests to eclipse.org. And we'd need to do that again each time we update test dependencies. Way too much hassle. So unless we can get blanket IP approval for all current and future test dependencies, the tests will have to stay at github.
--
Regards,
Igor
On December 11, 2017 8:14:00 AM Mickael Istria <mistria@xxxxxxxxxx> wrote:
_______________________________________________So basically, why this pattern? Any path possible to get back to the usual practices?On the long run (no commitment), I would like to evaluate whether some of those could be moved to the main repository. Indeed, as an occasional contributor, I really find that having distinct repositories for main and test code doesn't encourage to write a test with the patches, which is a pity. Then it becomes up to committer to bug the contributor for a test, which can be noise in more useful discussion and reduce a bit the efficiency of collaboration.I think the reason should be mentioned in the README of m2e-core-tests.Hi all,I'm wondering why are the m2e tests are on a different repo. I remember there's a good reason, but I can't find it in my search history.Cheers,--Elected Committer Representative at the Eclipse Foundation board of directors
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev