> I'm curious to know why you need to include the cactus jar to your > dependency list as this is done automatically by the cactus plugin?
Well, I was never quite able to get Cactus to *work* without it in my dependency list. I realize it's a big kludge, but at the time, I needed the functionality, and I needed to move on quickly. I believe part of the issue is not having my classpaths sorted out in my project.xml/properties file for the java:compile task. If the cactus jar is in my dependencies, Maven saw it when I compiled the app. bmj --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
