| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
The code read java resources using relative path which
breaks when the classes and their packages are renamed
(the java resource isn't moved to the new package name.)
Change-Id: I9b9d14288d8c16fd7342cd743251e5681bb0f1ef
|
|
|
|
| |
Change-Id: I823bcc19b7de6cea4c985f2c01feccddd6f8022d
|
|
|
|
| |
Change-Id: Ieae3414762d062b745b9b47bdea8c31a6593e34f
|
|
|
|
|
|
|
| |
They shouldn't manually add their jar to the classpath anymore.
Putting jar files in libs/ is enough now.
Change-Id: I3ea7731082f306257531798f34eaa8eb68109c18
|
|
|
|
|
|
|
|
|
|
| |
- add eclipse files for a bunch of them
- package name refactoring to match the folder structure somehow (more
need this)
- updated the javaproject to have an extra java project and to have
code that access java resources to test packaging too.
Change-Id: Ie13842c1b891e495e04d8a157a12cac9db13f30e
|
|
Also make it more complex:
- java project references a jar file.
- 2 libs depend on the java project
- app project only reference the libs, not the java project
(it still does but indirectly).
Change-Id: I8fc53e0f868ce014ea99486e7b1fa6fe0f197daa
|