project.build.testOutputDirectory Jeff
On Thu, Oct 9, 2014 at 3:48 PM, Volkan YAZICI <[email protected]> wrote: > Hello, > > I have a Maven plugin that instruments the classes in > *project.build.directory*. Further, I have a unit test that checks whether > the plugin kicks in and instruments the classes right, or not. When I run > *mvn > install*, the instrumentation does not kick in since the plugin instruments > the class files under *project.build.directory*, which points to > *target/classes*, but misses *target/test-classes*. Here, I either need to > explicitly let the plugin to access *target/test-classes* directory (if so, > which *project.build.X* property should I prefer), or configure *pom.xml* > such that test classes are compiled using the built plugin JAR. > > *Long story short:* Plugin instruments the classes, but while building, I > also need it to instrument its own test classes as well. > > Any ideas will be really appreciated. > > Best. > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
