No, I think the order is ok, if I inverte the order, look what is
happen..
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Maven Quick Start Archetype
[INFO] task-segment: [package]
[INFO]
------------------------------------------------------------------------
----
[INFO] antrun:run {execution: generate-sources}
[INFO] Executing tasks
[ERROR] mojo-execute : antrun:run {execution: generate-sources}
Diagnosis: Error executing ant tasks
FATAL ERROR: Error executing Maven for a project
[ERROR] project-execute : com.csi.vas:vasConfigurationFactory:jar:1.0 (
task-segment: [package] )
Diagnosis: Error executing ant tasks
FATAL ERROR: Error executing Maven for a project
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing
ant tasks
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
at
org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
executing ant tasks
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntM
ojo.java:114)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:534)
... 8 more
Caused by: Could not create task or type of type: target.
Ant could not find the task or a class this task relies upon.
This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
- You have misspelt 'target'.
Fix: check your spelling.
- The task needs an external JAR file to execute
and this is not found at the right place in the classpath.
Fix: check the documentation for dependencies.
Fix: declare the task.
- The task is an Ant optional task and the JAR file and/or libraries
implementing the functionality were not found at the time you
yourself built your installation of Ant from the Ant sources.
Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
task and make sure it contains more than merely a
META-INF/MANIFEST.MF.
If all it contains is the manifest, then rebuild Ant with the
needed
libraries present in ${ant.home}/lib/optional/ , or alternatively,
download a pre-built release version from apache.org
- The build file was written for a later version of Ant
Fix: upgrade to at least the latest release version of Ant
- The task is not an Ant core or optional task
and needs to be declared using <taskdef>.
- You are attempting to use a task defined using
<presetdef> or <macrodef> but have spelt wrong or not
defined it at the point of use
Remember that for JAR files to be visible to Ant tasks implemented
in ANT_HOME/lib, the files must be in the same directory or on the
classpath
Please neither file bug reports on this problem, nor email the
Ant mailing lists, until all of these causes have been explored,
as this is not an Ant bug.
at
org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.
java:493)
at
org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:391)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:1
58)
at org.apache.tools.ant.Task.perform(Task.java:363)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntM
ojo.java:108)
... 11 more
-----Original Message-----
From: Dave Syer [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 3:53 PM
To: [email protected]
Subject: Re: pom dependences on the antrun plugin
Have you tried putting the taskdef inside the target that needs it?
E.g.
<target name="x">
<taskdef name="xjc"
classname="com.sun.tools.xjc.XJCTask"
classpathref="maven.dependency.classpath" />
<xjc
schema="${src.loc}/main/resources/TestScript.xsd"
target="src/main/java/"
package="com.avaya.automation.testscripts" />
</target>
--
View this message in context:
http://www.nabble.com/pom-dependences-on-the-antrun-plugin-tf2822307s177
.html#a7878788
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
