Hello Tom and Linus,

I would also agree that moving more things from argouml/tools into the argouml/src directory tree would be a bad move. One of the reasons behind the restructuring was to lower the basic checkout time.

cobertura and similar libraries and targets even if kept in argouml/src/argouml-build/build.xml, should be only possible to execute in the full SVN checkout or in the context of the nightly build in argouml-gen.

Luis

PS: it is always good to keep two separate automated test targets: 1 for coverage tests and one without anything like that - bare tests. This enable us to know where the coverage framework is causing false positives.

Linus Tolke wrote:
Hello Tom!
If someone wants to work with and run a nightly build set-up, a CI-server, or just the coverage analysis, I think it is acceptable to let them check out another project where the configuration files and tools required are place. I consider such developers to go beyond what we require for all developers. The argouml-gen project is that other project. The argouml-gen project already contains cobertura and build files to run all unit tests with coverage. Alas they are not working but I'd appreciate a statement that it is beyond repair before we abandon it to create a new set-up. The build.xml file of the argouml-app "subsystem" is not the core build.xml. It is the build.xml file for the argouml-app part of the code i.e. currently everything that is not split into its own subsystem. In the nightly build set-up the build.xml from the argouml-build directory (previously the src directory) is extended with cobertura things (as well as jdepend, checkstyle, and findbugs) most of which is not currently working. Is the coverage contribution from the tests in the argouml-core-model-mdr subsystem included in the report? Will it be? Can we get a coverage report from the tests in the argouml-cpp project? /Linus


2008/4/27, Tom Morris <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    Since these are all build time tools, another possibility might be
    argouml-build instead of argouml-core-infra.  Of course they could
    also move to src/argouml-core-tools, but I'm not sure we need all
    three projects/directories.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to