[mojo-dev] [jira] (MEXEC-17) system dependencies are not put on exec:java classpath

[Martijn Verburg (JIRA)]

Title: Message Title

Martijn Verburg commented on an issue   Re: system dependencies are not put on exec:java classpath This appears to have resurfaced since version 1.2. The following dependency is included in 1.1.1, but not from 1.2 onwards: ``` <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <!-- version is actually irrelevant --> <version>localVersion</version> <scope>system</system> <systemPath>$ {java.home} /../lib/tools.jar</systemPath> </dependency> ``` Add Comment   Mojo's Exec Maven Plugin / MEXEC-17 system dependencies are not put on exec:java classpath My project uses a system dependency to get tools.jar onto the project classpath. when running the exec:java plugin, that dependency is not being put on the classpath. I've debugged the plugin output (using the -X flag) and have verified that tools.jar is not being added to the classpath: [DEBUG] Plugin Dependencies will be excluded. [DEBUG] Project De... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email