|
[jira] Commented: (MEXEC-17) system dependencies are not put on exec:java c: msg#00369java.maven-plugins.mojo.devel
[ http://jira.codehaus.org/browse/MEXEC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86435 ] Jerome Lacoste commented on MEXEC-17: ------------------------------------- I have committed a fix for the issue, which I can confirm manually, but I failed getting a proper automated test case for it. I tried creating a test class that given a class name as argument to its main method would print OK or fail if the class wasn't to be found in the classpath. Then the containing project would have to define a system dependency and use a class only found in one of these dependencies. This isn't very useful as by default the tools.jar is already in the classpath.... or someone might want to use a different compiler. The idea might be to use a dependency we are sure wasn't part of the default classpath, but then it might not be downloaded as system scope dependencies are not when they are resolved. In the mean time, the added test case is commented out. > system dependencies are not put on exec:java classpath > ------------------------------------------------------ > > Key: MEXEC-17 > URL: http://jira.codehaus.org/browse/MEXEC-17 > Project: Mojo Exec Plugin > Issue Type: Bug > Affects Versions: 1.0.2 > Reporter: Ryan Sonnek > Priority: Critical > Fix For: 1.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
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Plugins for dependences and Fitness, Carlos Sanchez |
|---|---|
| Next by Date: | [jira] Closed: (MEXEC-17) system dependencies are not put on exec:java classpath, Jerome Lacoste (JIRA) |
| Previous by Thread: | [jira] Commented: (MEXEC-17) system dependencies are not put on exec:java classpath, Jerome Lacoste (JIRA) |
| Next by Thread: | [jira] Closed: (MEXEC-17) system dependencies are not put on exec:java classpath, Jerome Lacoste (JIRA) |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |