0

with 

List<Plugin> plugins = project.getBuild().getPlugins();

I can get all plugins. 

plugin.getDependencies()

only delivers the dependencies declared when using it. But how can I get the (transitive) list of the dependencies of each plugin ? The dependencies necessary to build it.

openCage
  • 2,735
  • 1
  • 18
  • 24
  • What is the purpose of this? What would you like to achive? – khmarbaise Jun 09 '16 at 13:04
  • @ khmarbaise I want to look at the full tree of dependencies necessary to build an artifact. And then determine their licenses. – openCage Jun 09 '16 at 13:08
  • The dependencies to build an artifact is already done by Maven etc. for license i would recommend to take a look at http://www.mojohaus.org/license-maven-plugin/ – khmarbaise Jun 09 '16 at 13:16
  • @khmarbaise a) Of course this is done by maven, otherwise the plugin can not run. I just want this list. b) I know the license-maven-plugin. I want to do a bit more and I am not sure it looks at plugin dependencies. – openCage Jun 09 '16 at 13:20
  • The plugin dependencies usually are not a problem cause they will never become part of your product...? – khmarbaise Jun 09 '16 at 13:25
  • @khmarbaise I am fully with you here. I am worried a bit about the "usually" part, i.e. a followup question would be: Is there a prossibility that a plugins license may restrict its use or the result ? – openCage Jun 09 '16 at 13:32
  • Could be...to be honest never seen such plugin. Furthermore if i like to use a plugin i take a look before if it does not have MIT, APL i will not use it...But of course that could have an impact...sure. – khmarbaise Jun 09 '16 at 14:52

0 Answers0