[
https://jira.codehaus.org/browse/MNG-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339893#comment-339893
]
Jason van Zyl commented on MNG-5505:
------------------------------------
For testing plugins you should make a separate integration test and you can
either set the dependencies section of the plugin in the test. We have many
examples of testing plugins that work in a portable way without runtime
manipulation of the classpath or use the system scope dependencies (which are
going away).
> Support system scope for additional dependencies of plugins
> -----------------------------------------------------------
>
> Key: MNG-5505
> URL: https://jira.codehaus.org/browse/MNG-5505
> Project: Maven 2 & 3
> Issue Type: Bug
> Reporter: Marcin Wisnicki
>
> Sometimes I want to quickly test something with a jars outside maven and it
> would be nice if I could simply add it as system scope of e.g. exec plugin.
> Currently such dependencies are completely ignored.
> Yes I know you would rather have me wasting time with install-file. If you
> feel a need to punish me and other users with similar use cases then print a
> huge warning about non-portable build etc. but please don't be such a
> classpath nazi and let us live our lives the way we want. Thanks!
> Alternatively, is it possible to make a plugin that could manipulate another
> plugin's classpath (not silently installing jars into local repo) ?
--
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
