Andy,
Will you have chance to create a test project for this and submit bug
report?
It is possible that option to skip Maven compiler introduced in the
recent dev build is not compatible with plugin configuration declared
inside <executions> element. A jira issue and sample test project would
really help us to investigate, but in a mean time you can try to turn
this option off in Maven properties page on your project.
regards,
Eugene
Andy Schlaikjer wrote:
Hi all,
I have a POM containing a number of custom execution configurations for
the `antrun` and `dependency` plugins. The project is configured to
exec the `process-test-resources` goal after clean and
`process-resources resources:testResources war:war` goals on resource
changes. When I manually initiate a project clean/rebuild the custom
execution configurations seem to go unhonored.
For instance, the `antrun:run` goal is executed but without any
`tasks` configuration, so does nothing. The
`dependency:unpack-dependencies` goal is executed, but attempts to
unpack all dependencies (not just those specified in execution
configuration) including artifacts with type `pom`, so fails visibly
within Eclipse. The following previous post is highly relevant:
http://archive.hausfoundation.org/lists/org.codehaus.m2eclipse.user/msg/[EMAIL PROTECTED]
Also, note that if I run m2eclipse `Update Project Configuration` the
execution configurations are executed properly..
The relevant custom executions look like this:
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.3</version>
<executions>
<execution>
...
</executions>
</plugin>
Any thoughts?
Thanks,
Andy
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
