On 11/29/10 4:41 AM, Kabir Khan wrote:
This is also an issue with the embedded testing (or managed/remote
for that matter). If I stop a testcase in my IDE while running it, then the next time I
try to run it I get a 'blah.jar is already deployed error'. In embedded that can
possibly be avoided by setting an alternative path for standalone.xml and the output
folder. I think Thomas might have done something to handle that in the stuff I took over,
but I have been concentrating on getting the core functionality working.
One thing I wanted to ask was to maybe keep a standalone.xml.original which is never
changed?
We do keep the "last known good" copy around, which basically is the
original, unless of course you do multiple changes. We had also talke
about keeping more copies around longer on the DC.
--
Jason T. Greene
JBoss, a division of Red Hat