You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a separate gora-examples module is very logical and useful for the users. However, all of the tests for gora-core and the other modules depend on the data structures, and jobs at gora-examples. Until now, thanks to ivy, we have managed this as follows:
gora-core compile configuration does not depend on anything,
gora-examples compile dependency depends on gora-core
gora-core tests dependency depends on gora-examples.
What seems a cyclic dependency above was resolved by a clever build order among compile and test dependencies. However, this has proven to be a major source of headaches. So long story short, I propose we merge gora-examples into gora-core.
The text was updated successfully, but these errors were encountered:
Having a separate gora-examples module is very logical and useful for the users. However, all of the tests for gora-core and the other modules depend on the data structures, and jobs at gora-examples. Until now, thanks to ivy, we have managed this as follows:
gora-core compile configuration does not depend on anything,
gora-examples compile dependency depends on gora-core
gora-core tests dependency depends on gora-examples.
What seems a cyclic dependency above was resolved by a clever build order among compile and test dependencies. However, this has proven to be a major source of headaches. So long story short, I propose we merge gora-examples into gora-core.
The text was updated successfully, but these errors were encountered: