> -----Original Message----- > From: brian janaszek [mailto:[EMAIL PROTECTED] > Sent: 02 June 2003 16:38 > To: [EMAIL PROTECTED] > Subject: Cactus Test Classpath Problems > > Hi > > I'm not sure if I'm simply missing something in the docs regarding > Cactus and the Maven unit testing goals, but I'm having an issue with > the classpath when Maven tries to compile my tests. > > My tests reside in the /WEB-INF/src/test directory generated by Maven,
err? Your cactus tests should be in <project>/src/test-cactus (as explained here: http://maven.apache.org/reference/plugins/cactus/properties.html). > and the tests import other classes from the application. When Maven > attempts to compile the test classes, it cannot find the previously > compiled application classes. If I run Maven in verbose mode, the > classpath used by the tests includes all of my dependencies, but none of > the application classes. Am I simply missing an option in my > project.xml to include those classes? The cactus plugins will use the following classpath: <ant:classpath> <ant:path refid="maven.dependency.classpath"/> <ant:path refid="cactus.classpath"/> <ant:pathelement path="${maven.build.dest}"/> </ant:classpath> which means you get all the dependencies defined in your project.xml + the cactus related jars + the compiles classes that you have put in src/java -Vincent > > TIA > bmj > > > --------------------------------------------------------------------- > 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]
