java - Add sibling project resources to Android assets without tight coupling -

problem

i developing game using libgdx project structure similar to:

root project 'gdx-play' +--- project ':android' +--- project ':core' \--- project ':desktop' 

subprojects android , desktop depend on core.

i want keep assets in resources folder of core project. depending on core desktop works fine, libgdx happy loading assets packaged jar root. on android, however, libgdx expects assets reside in assets folder of packaged apk.

how best can configure multi-project build without tight coupling among projects?

possible solutions

one

store assets in assets subfolder in core project, magically end in assets folder of apk when packaged.

two

publish 2 separate jars core; 1 classes , 1 resources. or separate core project two. then, in android, somehow add items in resources jar android plugin's assets sourcedirectoryset , remove jar classpath (so items not redundantly included apk). don't know if dangerous.

three

add android-library plugin core project , export aar. i'm sure compatible android, however, not know how normal jar desktop project.

i take 1 of 2 approaches. either @jake-wharton's approach creating jars apk's in similar question that, basically, involves creating jar tasks each release variant of library (skipping on debug variants).

or pull assets own android library, core-assets, leaving behind java code in core. 1 benefit of approach pure java projects easier thoroughly test. android's testing support bit lacking, @ moment.