Well, the purpose is what the docs says: "The test source directory containing test class sources." And it does work, otherwise no unit tests would work/run for any Maven project. As a convention, this param is defined in the Maven super pom. Have a look here: http://maven.apache.org/pom.html#The_Super_POM
If you want to change this to some other directory and that causes problem in your IDE, that's a question for that IDE's Maven integration feature. It's not a Maven issue. If you do want to change the value of the testSourceDirectory param, you should do that in your project's pom. Do that in the same manner as it's defined in the super pom (not by a 'project.build.testSourceDirectory' property). /Anders On Tue, Jan 5, 2010 at 11:36, Marcin Kwapisz <[email protected]> wrote: > Hi, > can someone tell me what is the purpose of <testSourceDirectory> in > configuration of the surefire plugin. I do not think this parameter work at > all. There is project.build.testSourceDirectory and I use it to point at my > filtered test source files. But this method is very inconvenient due to > NetBeans IDE - there is no "Test Packages" in project tree then. > > Is there another way to tell compiler where test sources are? I tried to > set project.build.testSourceDirectory (outside pom.xml) in profiles.xml, but > it doesn't work. > > Thanks in advance > Regards > -- > Marcin Kwapisz > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
