Hi Sterling,
Thanks for the quick response.
Unfortunately, due to diversity requirements of the project, the environment one libraries have to be developed and built separately from the second test and validate environment during a secondary phase of the project.
As it stands, during main development they are actually part of a single multi-project build, the intention, was to build environment one, capture it into a deliverable, which strips the source and build mechanisms. Convert the build.gradle files to encapsulate the “repositories” for that item and allow the test item to reference the prebuilt variant. However we have hit 2 stumbling blocks, the one mentioned in this thread and the second that a repository doesnt resolve between projects, as mentioned in this thread.
The fake target platform may work, however, it could also lead to confusion for the development teams, who may try target that build, think more thought may be required from us.
As a side note: We are running a custom compile of gradle (supporting an alternative set of tool chains, non gcc), could I modify the gradle to always include the platform, any pointers on the right area to review?
Thanks again,
Shaun