> Sounds nice, but this doesn't meet my requirement, that the tests with > coverage-checks (and only one time, not twice) should run, when the developers > do "mvn test".
It sounds like Maven cannot, for whatever reason, meet your "requirement." > We have a quite small difference between coverage-threshold > and actual coverage, so I think it's important, that the developers check > their > coverage during development, so they can react early. It seems like you are only running into this problem because your coverage is running arbitrarily close to the 80% cutoff that you defined for test coverage. Perhaps you should instead focus some energies on bumping your test coverage a lot so you are not so close to the cutoff (so people aren't casually bumping into it so regularly), or knock the cutoff down to 75% or so to give some breathing room? > Another problem to your solution is, that we unfortunately don't use a regular > CI-server but a bunch of shellscripts and cron-jobs. So it's not as trivial > as with > Hudson (Jenkins?) to use this kind of build-pipeline. Why can't you set up a more formal CI server like Hudson? This is solution proposed by Jeff is a reasonable one and I know this same strategy is used by a lot of groups doing CI. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
