-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Linux (Debian)
I have a particular workspace configuration :
I have a library project (lets call it "lib"), a unit test project (lets call it "test"), and a demo project using the lib (lets call it "demo").
Now both the "test" and "demo" project share the same package name (and its impossible for me to change the package names for either of them as it needs to be this package name). The problem is that the test project works on its own (it has its own activities) and only relies on the "lib" project. But the task insist on making the "test" dependant on the "demo" project.
This results in jenkins building both project, and installing both on the emulator. The "demo" project being installed after, it replaces the "test" projects and so the instrumentation doesn't work.