On 09/08/2011, at 10:19 PM, Andrew Lee Rubinger wrote:
Hiya.
Since we've stopped copying the modules under JBOSS_HOME for the
testsuite (in order to save space), the default launch config from the
IDE doesn't know where to pick these up (unless manually configured with
a sysprop at launch).
How do we feel about:
1) Doing full copies of JBOSS_HOME like we used to? (Drawback: space)
No. This also trashed the OS swap cache during the build, and also seemed to interfere
with idea's scanning of the project files and just generally caused performance
problems.
2) Trying to put something in the AS7 ARQ Containers so that
it'll find
the modules by default (Drawback: Hacky/Programmatic Guesswork)
I am not sure how you could do this properly.
3) Reorganizing things such that the testsuite module source keeps
their
current structure, but instead we fire off the testsuite runs from
another module all in one go, with a full JBOSS_HOME to back it?
(Drawback: Build Complexity)
I don't really like either of these.
What exactly is the problem? Is eclipse not picking up the configuration in the pom when
running the tests, or something else?
Stuart
I think I lean for 3), assuming it can be done intelligently enough.
Then we'll only start/stop the server ONCE for a full build, and blow
through all tests there regardless of their source module. The source
modules are important as they stand in order to assert our compile
dependencies.
S,
ALR
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev