I don't know whether this is fixed in newer versions of the Antrun
plugin, but I noticed you use version 1.3, while version 1.6 is also
available. You can give it a try and hopes it fixes your problem.
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31
shaun.t.erickson wrote:
[INFO] --- maven-antrun-plugin:1.3:run (metrics-for-eclipse) @ ccl ---
[DEBUG] org.apache.maven.plugins:maven-antrun-plugin:jar:1.3:
[DEBUG]org.apache.ant:ant-nodeps:jar:1.7.0:runtime
[DEBUG]ant-contrib:ant-contrib:jar:1.0b3:runtime
[DEBUG] ant:ant:jar:1.5:r
While I don't have time to dig into this, I'm offering a (well founded)
guess as you're mentioning maven-antrun-plugin.
In Maven 2, all executions of a plugin (maven-antrun-plugin for example)
within a build share the same classpath. So the first execution sets the
classpath, and regardless on how
I've almost succeeded in getting all of my developer end-user's projects
building under maven3 (3.0.3). This one project builds fine under maven2
(2.2.1) but fails under maven3. I'm not a programmer, just a SysAdmin, but from
looking at the debug output of a successful run and a failed one, it s
