It's absotlutely GOLD to have test-classes and production classes separated. My packages usually contain 20 or more classes, and since there is at least as many test classes, is it nice to be able to separate them in separate source folders.
Before you suggest a "test" package, let me remind you there is something called "package default access" which I won't have in a test package. The absolutely best approach is to have separate source folders. Cheers Thomas Bentzen -----Oprindelig meddelelse----- Fra: Peter Bright [mailto:[EMAIL PROTECTED] Sendt: 9. december 2003 11:58 Til: 'Maven Users List' Emne: RE: Is it possible to keep unit tests in the same directories as production classes? > I am harsh, but honest $DIETY (sic) I am only trying to make your life easier. You may be trying to make the lives of plugin developers a little easier, but it doesn't seem at all clear that you're trying to make any user's lives easier. The only "advantages" appear to be working around the inability of some plugins to exclude filesets. The notion that application code must be distinguished from test code by a path is absurd; an arbitrary file specification is surely sufficient (for example, "all files in src except those whose names begin with Test"), and surely more expressive. The ability to put tests and source together should simply be a repercussion of this greater expressiveness. No? Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
