On Saturday, July 12, 2003, at 12:20 PM, Dave Ford wrote:
The Maven web site lists "Keeping your test source code in a separate, but
parallel source tree" as best practices.
Q1: Why is this a best practice? It just seems like an extra thing to
maintain to me, making package name refactoring for troublesome. I've been
placing my test class next to the tested class.
smartsoft.util.Date smartsoft.util.DateTest
By naming them this way, they appear next to each other in dir listings.
True, although I rarely ever go digging around in the directory to see what's there. Generally tools do a good job, such as Eclipse or Idea.
The advantage I see is that you get to have test code that has package-level access and because it's in a separate tree, it's easy to build binaries that don't include all the test code...
geir
Q2: If I want to continue my practice of keeping them together, is there any
way to get Maven to support that?
Thanks
Dave Ford Smart Soft - The Developer Training Company http://www.smart-soft.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Geir Magnusson Jr 203-956-2604(w) Adeptra, Inc. 203-434-2093(m) [EMAIL PROTECTED] 203-247-1713(m)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
