Re: [m2e-dev] m2e-core-tests on different repo

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [m2e-dev] m2e-core-tests on different repo

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Mon, 11 Dec 2017 20:14:42 +0100
Delivered-to: m2e-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/m2e-dev>
List-help: <mailto:m2e-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/m2e-dev>, <mailto:m2e-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/m2e-dev>, <mailto:m2e-dev-request@eclipse.org?subject=unsubscribe>

Ok,

When you say test dependencies, it means the things that are used to *code* the tests, or the test artifacts that are used for testing?

If it's because of the test artifacts, could we consider a workaround to have the test code in the same repo, and the test "resources" on GitHub on a 1st iteration? So contributors would be able to more easily write test reusing the artifacts already available.

Follow-Ups:
- Re: [m2e-dev] m2e-core-tests on different repo
  - From: Igor Fedorenko

References:
- [m2e-dev] m2e-core-tests on different repo
  - From: Mickael Istria
- Re: [m2e-dev] m2e-core-tests on different repo
  - From: Igor Fedorenko

Prev by Date: Re: [m2e-dev] m2e-core-tests on different repo
Next by Date: Re: [m2e-dev] m2e-core-tests on different repo
Previous by thread: Re: [m2e-dev] m2e-core-tests on different repo
Next by thread: Re: [m2e-dev] m2e-core-tests on different repo
Index(es):
- Date
- Thread

Breadcrumbs