Anders Hammar commented on Bug MSQLJ-15

IMHO, the classpath should be:
1. the plugin's classpath
2. the project's compile classpath

So it should be possible to override any dependency from the project by adding it as a dependency to the plugin. Not sure about the use case for that, but it would allow for it should it be necessary.

One limitation that I think we will have is that classes in the project can't be added to the classpath, as this mojo executes in the "generate-sources" phase and the project's classes haven't been compiled yet.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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

Reply via email to