?
for your next run can you display debug info and error info so we can see
determine the behaviour of the reactor?
mvn -e -X phase
?
Martin
From: g...@apnic.net
To: users@maven.apache.org
Subject: Plugin dependency resolution from plugin pom?
Date: Mon, 23 Mar 2015 22:41:39 +
Yes, that would be the smarter option, wouldn't it. :$ *bangs head on desk*
I am still curious though as to why the plugin.xml contains a dependency
section if it's the plugin's pom file that is used for resolution, and/or why
the pom file is used over the plugin file? The plugin.xml file
Hi Gary,
I'm trying to patch a third-party plugin at the moment as a temporary
workaround for a problem. (I don't want to get into details because
it's not important)
Since the workaround is temporary, could you not simply clone the plugin's
SCM repository to a local Git repository, then
debug info and error info so we can see
determine the behaviour of the reactor?
mvn -e -X phase
?
Martin
From: g...@apnic.net
To: users@maven.apache.org
Subject: Plugin dependency resolution from plugin pom?
Date: Mon, 23 Mar 2015 22:41:39 +
I'm trying to patch a third-party plugin
I'm trying to patch a third-party plugin at the moment as a temporary
workaround for a problem. (I don't want to get into details because it's not
important)
So I currently have a 'patch project' that depends on the plugin, uses the
maven-dependency-plugin to unpack the dependant plugin
