Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Decide same repo/separate repo for Android Tracker #17
So after this sprint, it seems almost entirely clear that we should keep the java tracker as simple as possible, have that put up on maven and then have the Android tracker add it as a dependency in the Android gradle project, then override whatever needs to be Android specific.
EDIT: Close if all seems okay
I think that's fine. This statement won't be long-sustainable: "keep the java tracker as simple as possible" - but that's okay, at that point, we can break this project into two sub-projects (still one repo), where we have java-tracker-core and java-tracker, where java-tracker-core is the lib that both java-tracker and android-tracker then import.
Makes sense? Close if okay