dimanche 24 janvier 2016

ivy configurations - how to manage test utilities?

I'll present a simplified version of our problem, but know that we have way more than 2 projects, and so on.

So, at our job, we have 2 projects -

  • A
  • B

where B depends on A through ivy.
Recently we added configurations to the mix, mainly default and test.
The problem we ran into is that in A we have test utilities, which B needs in order to run it's own tests, so we need B to get these utilities from A.
We've thought of 2 ways to solve this:

  • make the test configuration public
  • create a new conf - test-utils - that will be public, and A will publish it's own tests under that configuration

The problem is that both solutions seem somewhat forced, and I wanted to get an idea how people do this world-wide.

Any ideas?

Aucun commentaire:

Enregistrer un commentaire