I'm looking for a general technique here, but let's give a specific example.
 I have a multi-module project and I'd like to run the exec:java plugin from
the command-line against one of the sub-modules of my project.

I know one approach is that I can run "mvn install" on the whole project and
then just go into the sub-module directory, run the exec:java command from
the command line, and have artifacts resolved to my local repository.  But
running "mvn install" all the time gets pretty tedious.

What I'd really like is the ability to run exec:java against the Maven
reactor, where the classpath is constructed from the active modules of the
project in the Maven reactor.  The problem is that I'm not sure this is
possible.  A naive approach is to run the exec:java goal from the root of
the project, but this tries to run the plugin against every module in the
project, as opposed to the target module I'm interested in.

Any idea?  I know my motivating example was exec:java, but really there are
a number of single plugin goals that I'd like to run against my project from
time to time outside of the scope of the full build lifecycle.

Thanks,
Brian

Reply via email to