Hello Linus,
Linus Tolke wrote:
Somehow related to this problem I find the following:
The JUnit tests for the argouml-cpp module has not been running
correctly since April.
The Configuration for running the c++ tests from within Eclipse,
includes the ant.jar from argouml-core-tools as the source. Removing
it doesn't make the tests fail.
A couple of weeks back I noticed that the junit ant task had an
argument "includeantruntime" that is "yes" by default. I thought then
that it would be a good idea to set this to "no" throughout but that
we would never experience any problem with this. Appearantly, I was
wrong as we have a problem with this. We should set this to "no"
throughout.
/Linus
I've been running the argouml-cpp tests in 2 checkout configurations to
assert that everything was working correctly. Alas, the anarres-cpp did
caused 5 failures, but, the problem wasn't fatal for the release
(details in TODO).
Regarding that option, the Ant manual states: "includeantruntime" -
"Implicitly add the Ant classes required to run the tests and JUnit to
the classpath in forked mode. *Note:* Please read the Ant FAQ
<cid:[email protected]> if you want to set this to
|false| and use the XML formatter at the same time."
So, I wouldn't rush to remove it from the Ant build files in a hurry.
Furthermore, I detected that the anarres-cpp.jar depends in GnuOpt also.
It is included in eclipse, but, the JUnit tasks don't bark about it -
maybe this is included in Ant...
I'm looking on to how to solve this in issue-of-argouml-cpp #27
(http://argouml-cpp.tigris.org/issues/show_bug.cgi?id=27).
Regards,
Luis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
