How are your dependencies defined? Looking at the java exec mojo:
/** * Executes the supplied java class in the current VM with the enclosing project's * dependencies as classpath. * * @goal java * @requiresDependencyResolution runtime * @execute phase="validate" * @author <a href="mailto:[EMAIL PROTECTED]">Kaare Nilsen</a> * */ They should be there if they are at least runtime scope dependencies. Unless you're trying to run something in the current project, in which case I would imagine it would need to be built beforehand, in the same execution of maven. On 8/10/06, Tim Patton <[EMAIL PROTECTED]> wrote:
I'm trying to get the exec plugin to work, since maven seems like it would make a great application launcher and save me time editing my 1000 char classpath. I have this in my pom.xml for a project consisting of several modules: <build> .. <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.0.1</version> <configuration> <mainClass>dealcatcher.kolinka.profiler.SingleForumProfile</mainClass> </configuration> </plugin> .. </build> When I run it with "mvn exec:java" I get "Could not load main class. Terminating.". I try running mvn package or mvn install beforehand but I'm not sure what I am missing to make this work. Tim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]