AFAIK, it should be fixed in trunk. Milos
On Thu, Dec 11, 2008 at 11:26 PM, Andy Schlaikjer <[email protected]> wrote: > I'm trying to configure exec-maven-plugin to exec java with a classpath > constructed using "runtime" dependencies along with my project's output jar > artifact. Is this possible? > > Here's what I've got so far: > > ... > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>exec-maven-plugin</artifactId> > <configuration> > <classpathScope>runtime</classpathScope> > <executable>java</executable> > <arguments> > <argument>-classpath</argument> > <classpath /> > ... > </arguments> > </configuration> > </plugin> > ... > > Unfortunately, the generated classpath doesn't include the output build > directory nor the project's output jar artifact. > > Looking at the source [1] it seems as though the "classpathScope" param > determines what additional resources, besides dependencies, are added to the > classpath. When the value is "runtime", no extra paths are added.. > > [1] > http://svn.codehaus.org/mojo/tags/exec-maven-plugin-1.1/src/main/java/org/codehaus/mojo/exec/AbstractExecMojo.java > > Thanks, > Andy > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
