J. den Boer wrote:
> The test project, just a generated simple j2ee project, used this custom
> ear plugin. When running eclipse:eclipse still the
> ear:generate-application-xml goal is sought but this goal does not exist
> anymore.
I assume your custom plugin has the same groupId and artifactId as the
real plugin, otherwise you can't override the plugin execution
contributed from the lifecycle bindings for the "ear" packaging.
Did you verify the debug logs, i.e. "mvn <goal> -X", that both builds
really use the plugin version you intend? Also make sure to explicitly
declare the plugin version you want in the POM, otherwise you would get
a default version from the super POM (assuming a recent Maven version).
A workaround for your original dependency resolution problem should be
running something like
mvn package eclipse:eclipse -D skipTests
While still quite expensive, it at least does not install stuff into the
local repo.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
