I work daily on a large customized version of Android. Our work involves creating new APIs and testing them with our in-house test app. Currently, each person checks out the needed files to make API updates and then requests that I create a new version of the test app that works with their changes. The way I accomplish this, in part, is with a script that grabs their version of the OS files (the ones that declare the APIs) and generates a JAR of these files that is then thrown in the test app's "lib" directory so the test code can reference these new/changed APIs.
I've been able to automate so much of my workflow, but I can't find a way to automate the task of generating the jar from a few .java files that can't be compiled in isolation. I know how to create a jar and manually populate it, but I can't figure out how Eclipse is able to generate .class files for .java input source files that can't be compiled by themselves. The only way that I can currently compile these files is with a multi-hour full OS build, which I don't want to wait on. Also, our build servers don't spit out the individual .class files I would want to zip up in a JAR anyways.
So, does anyone know how to generate a JAR file with .class files compiled from .java src files that appear, by themselves, to be riddled with errors? I currently do this manually with Eclipse's "export project to JAR" ability, but it really irks me that it's the only "non-automate-able" step in my process so far.
I found this, which doesn't handle generation of the .class file(s) from a set of .java files that won't compile alone.
Thanks!