|Headless building and testing - need advice for better organization [message #645121]
||Wed, 15 December 2010 16:07
| Mike Gering
Registered: July 2009
I have a working headless build and junit test setup, but I'm not happy |
with how I've structured it. I'm doing a feature build. I have the base
code structured in one feature (F) and unit test code structured in a
separate feature (T). The plugins in T naturally depend on those in F.
The build output is a p2 repository with just F (not to include T). My
build process is two steps: 1) build F and its repo, 2) build T and run
the tests. Currently, I have to define T such that it *includes* F so
that its dependencies on F are resolved, essentially building F twice.
Is there a better way to build F, T, and the repository?
To run the unit tests, my script copies all the plugins for T and F into
a test platform/dropins directory. Is there a better way to setup a test
I've searched the wikis, this forum, and some eclipse dev projects, but
haven't found an answer to these questions.
Powered by FUDForum
. Page generated in 0.01652 seconds