[
https://jira.codehaus.org/browse/MNG-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339899#comment-339899
]
Marcin Wisnicki commented on MNG-5505:
--------------------------------------
That is a lot of work compared to simply adding few lines of xml for system
dependency and I'm already wasting way too much time with maven compared to
similar systems for other languages :(
> 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
