[
http://jira.codehaus.org/browse/MEXEC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Lacoste updated MEXEC-17:
--------------------------------
Fix Version/s: (was: before-1.1)
1.1-beta-1
> system dependencies are not put on exec:java classpath
> ------------------------------------------------------
>
> Key: MEXEC-17
> URL: http://jira.codehaus.org/browse/MEXEC-17
> Project: Maven 2.x Exec Plugin
> Issue Type: Bug
> Affects Versions: 1.0.2
> Reporter: Ryan Sonnek
> Assignee: Jerome Lacoste
> Priority: Critical
> Fix For: 1.1-beta-1
>
>
> 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 Dependencies will be included.
> [DEBUG] Adding to classpath :
> file:/product01/x-stream/users/rsonnek/pacific/modules/pacific-backend/target/classes/
> [DEBUG] Adding to classpath :
> file:/product01/x-stream/users/rsonnek/pacific/modules/pacific-backend/target/test-classes
> [DEBUG] Adding project dependency artifact: aopalliance to classpath
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
