You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by RobJac <ro...@caritor.com> on 2006/04/25 19:20:40 UTC
Doubt in using wagon plugin
Has some one used wagon plugin in your pom xml. I was trying to ftp an ear
using the wagon plugin to a particular location in a remote server but i
dont see any options to provide the destination directory. If wagon can help
me in solving this requirement, could you please send me the entry for this
plugin in your pom xml. The entry for this plugin in my pom xml is
<plugin>
<groupId>org.apache.myfaces.maven</groupId>
<artifactId>wagon-maven-plugin</artifactId>
<configuration>
<id>10.151.1.202</id>
<inputDirectory>${basedir}</inputDirectory>
<url>10.151.1.202</url>
</configuration>
</plugin>
is this correct? and finally what is the command that is used to run this
mvn install was not helping me. I would appreciate if some one could throw
some light on this.
--
View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4086387
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by Alexandre Poitras <al...@gmail.com>.
Small mistake
On 4/28/06, Alexandre Poitras <al...@gmail.com> wrote:
> The exception messages are still in french but I think you can figure
> out what it means:
> http://ez-files.net/download.php?file=b0faa260600c0f4f9e4a97be7ce0d496
>
> You need to change the ID field so it fits your server ID (defined in
> settings.xml). To install this mojo, use the mojo plugin. To use it,
> just specify an url parameter and an archiveName parameter either inve
archiveName should be nomArchive.
> your pom or on the command line. I haven't tried using it with FTP
> just WebDav (WebDav support has some bugs in Maven btw) but it should
> work
>
> Don't be afraid to ask if you need more help.
>
> On 4/27/06, RobJac <ro...@caritor.com> wrote:
> >
> > Hi Alexandre,
> > could you please send me the upload plugin?
> > --
> > View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4115982
> > Sent from the Maven - Users forum at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by Alexandre Poitras <al...@gmail.com>.
The exception messages are still in french but I think you can figure
out what it means:
http://ez-files.net/download.php?file=b0faa260600c0f4f9e4a97be7ce0d496
You need to change the ID field so it fits your server ID (defined in
settings.xml). To install this mojo, use the mojo plugin. To use it,
just specify an url parameter and an archiveName parameter either in
your pom or on the command line. I haven't tried using it with FTP
just WebDav (WebDav support has some bugs in Maven btw) but it should
work
Don't be afraid to ask if you need more help.
On 4/27/06, RobJac <ro...@caritor.com> wrote:
>
> Hi Alexandre,
> could you please send me the upload plugin?
> --
> View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4115982
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by RobJac <ro...@caritor.com>.
Hi Alexandre,
could you please send me the upload plugin?
--
View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4115982
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by Alexandre Poitras <al...@gmail.com>.
I am not working today but I can post tomorrow my upload plugin which
uses Maven wagon. The code is very simple since most of the job is
done by Maven wagon.
On 4/25/06, RobJac <ro...@caritor.com> wrote:
>
> I am getting the same error still. Please find below my ear pom xml.
>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>DefinedBenefit_EA</groupId>
> <artifactId>DefinedBenefit_EA</artifactId>
> <packaging>ear</packaging>
> <version>1.0</version>
> <dependencies>
> <dependency>
> <groupId>DefinedBenefit_BackgroundJobs</groupId>
> <artifactId>DefinedBenefit_BackgroundJobs</artifactId>
> <version>1.0</version>
> <type>jar</type>
> </dependency>
> </dependencies>
> <build>
> <directory>${basedir}</directory>
> <finalName>${project.artifactId}</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <configuration>
> <archive>
> <manifestFile>${basedir}/src/META-INF/MANIFEST.MF</manifestFile>
> </archive>
> <earSourceDirectory>${basedir}/src</earSourceDirectory>
> <generateApplicationXml>false</generateApplicationXml>
> <resources>
> <resource>
> <directory>${basedir}/src</directory>
> </resource>
> </resources>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-antrun-plugin</artifactId>
> <dependencies>
> <dependency>
> <groupId>ant</groupId>
> <artifactId>ant-nodeps</artifactId>
> <version>1.6.5</version>
> </dependency>
> </dependencies>
> <executions>
> <execution>
> <phase>generate-sources</phase>
> <configuration>
> <tasks>
> <ftp server="10.151.1.202"
> remotedir="/opt/jboss403SP1"
> depends="yes"
> userid="jboss"
> password="passw0rd">
> <fileset dir="${basedir}"/>
> </ftp>
> </tasks>
> </configuration>
> <goals>
> <goal>run</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> </project>
>
> Please find below the exception
> ------------------------------------------
> Embedded error: Could not create task or type of type: ftp.
>
> 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 'ftp'.
> 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.
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
> task
> s
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:544)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:469)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:448)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:301)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:268)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:137)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing
> ant t
> asks
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA
> ntMojo.java:114)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:399)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:519)
> ... 16 more
> Caused by: Could not create task or type of type: ftp.
>
> 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 'ftp'.
> 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(UnknownEleme
> nt.java:493)
> at
> org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:39
> 1)
> at
> org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
> a:158)
> 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(AbstractA
> ntMojo.java:108)
> ... 19 more
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Total time: 1 second
> [INFO] Finished at: Tue Apr 25 19:43:12 BST 2006
> [INFO] Final Memory: 3M/6M
> [INFO]
> -------------------------------------------------------------------------
> ---
> --
> View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4088232
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by Wayne Fay <wa...@gmail.com>.
Based on that same error, I suppose you still don't have all the
proper dependencies you need in the Antrun plugin.
Take a look at the Ant FTP Task webpage for more details, I'm sure you
can figure it out:
http://ant.apache.org/manual/OptionalTasks/ftp.html
Wayne
On 4/25/06, RobJac <ro...@caritor.com> wrote:
>
> I am getting the same error still. Please find below my ear pom xml.
>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>DefinedBenefit_EA</groupId>
> <artifactId>DefinedBenefit_EA</artifactId>
> <packaging>ear</packaging>
> <version>1.0</version>
> <dependencies>
> <dependency>
> <groupId>DefinedBenefit_BackgroundJobs</groupId>
> <artifactId>DefinedBenefit_BackgroundJobs</artifactId>
> <version>1.0</version>
> <type>jar</type>
> </dependency>
> </dependencies>
> <build>
> <directory>${basedir}</directory>
> <finalName>${project.artifactId}</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <configuration>
> <archive>
> <manifestFile>${basedir}/src/META-INF/MANIFEST.MF</manifestFile>
> </archive>
> <earSourceDirectory>${basedir}/src</earSourceDirectory>
> <generateApplicationXml>false</generateApplicationXml>
> <resources>
> <resource>
> <directory>${basedir}/src</directory>
> </resource>
> </resources>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-antrun-plugin</artifactId>
> <dependencies>
> <dependency>
> <groupId>ant</groupId>
> <artifactId>ant-nodeps</artifactId>
> <version>1.6.5</version>
> </dependency>
> </dependencies>
> <executions>
> <execution>
> <phase>generate-sources</phase>
> <configuration>
> <tasks>
> <ftp server="10.151.1.202"
> remotedir="/opt/jboss403SP1"
> depends="yes"
> userid="jboss"
> password="passw0rd">
> <fileset dir="${basedir}"/>
> </ftp>
> </tasks>
> </configuration>
> <goals>
> <goal>run</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> </project>
>
> Please find below the exception
> ------------------------------------------
> Embedded error: Could not create task or type of type: ftp.
>
> 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 'ftp'.
> 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.
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
> task
> s
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:544)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:469)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:448)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:301)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:268)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:137)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing
> ant t
> asks
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA
> ntMojo.java:114)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:399)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:519)
> ... 16 more
> Caused by: Could not create task or type of type: ftp.
>
> 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 'ftp'.
> 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(UnknownEleme
> nt.java:493)
> at
> org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:39
> 1)
> at
> org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
> a:158)
> 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(AbstractA
> ntMojo.java:108)
> ... 19 more
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Total time: 1 second
> [INFO] Finished at: Tue Apr 25 19:43:12 BST 2006
> [INFO] Final Memory: 3M/6M
> [INFO]
> -------------------------------------------------------------------------
> ---
> --
> View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4088232
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Doubt in using wagon plugin
Posted by RobJac <ro...@caritor.com>.
I am getting the same error still. Please find below my ear pom xml.
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>DefinedBenefit_EA</groupId>
<artifactId>DefinedBenefit_EA</artifactId>
<packaging>ear</packaging>
<version>1.0</version>
<dependencies>
<dependency>
<groupId>DefinedBenefit_BackgroundJobs</groupId>
<artifactId>DefinedBenefit_BackgroundJobs</artifactId>
<version>1.0</version>
<type>jar</type>
</dependency>
</dependencies>
<build>
<directory>${basedir}</directory>
<finalName>${project.artifactId}</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<configuration>
<archive>
<manifestFile>${basedir}/src/META-INF/MANIFEST.MF</manifestFile>
</archive>
<earSourceDirectory>${basedir}/src</earSourceDirectory>
<generateApplicationXml>false</generateApplicationXml>
<resources>
<resource>
<directory>${basedir}/src</directory>
</resource>
</resources>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<dependencies>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-nodeps</artifactId>
<version>1.6.5</version>
</dependency>
</dependencies>
<executions>
<execution>
<phase>generate-sources</phase>
<configuration>
<tasks>
<ftp server="10.151.1.202"
remotedir="/opt/jboss403SP1"
depends="yes"
userid="jboss"
password="passw0rd">
<fileset dir="${basedir}"/>
</ftp>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
Please find below the exception
------------------------------------------
Embedded error: Could not create task or type of type: ftp.
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 'ftp'.
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.
[INFO]
-------------------------------------------------------------------------
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
task
s
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:544)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing
ant t
asks
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA
ntMojo.java:114)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:399)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:519)
... 16 more
Caused by: Could not create task or type of type: ftp.
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 'ftp'.
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(UnknownEleme
nt.java:493)
at
org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:39
1)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
a:158)
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(AbstractA
ntMojo.java:108)
... 19 more
[INFO]
-------------------------------------------------------------------------
---
[INFO] Total time: 1 second
[INFO] Finished at: Tue Apr 25 19:43:12 BST 2006
[INFO] Final Memory: 3M/6M
[INFO]
-------------------------------------------------------------------------
---
--
View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4088232
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by Wayne Fay <wa...@gmail.com>.
Ant's FTP functionality is not provided by the Ant core modules. So
while Ant is being found and working properly, you haven't declared an
additional dependency to bring in the FTP task.
The easiest way to solve this is to use the Ant nodeps plugin.
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<dependencies>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-nodeps</artifactId>
<version>1.6.5</version>
</dependency>
<executions>
<execution>
<phase>generate-sources</phase>
<configuration>
<tasks>
<ftp server="10.151.1.202"
remotedir="/opt/jboss403SP1"
depends="yes"
userid="jboss"
password="passw0rd">
<fileset dir="${basedir}"/>
</ftp>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
Wayne
On 4/25/06, RobJac <ro...@caritor.com> wrote:
>
> sorry wayne.. forgot to add the exception. Please find below. I was trying
> to execute "mvn install" fir my ear pom xml. It created an EAR fine and
> while trying to ftp it I guess the below exception is occuring.
>
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Building Unnamed - DefinedBenefit_EA:DefinedBenefit_EA:ear:1.0
> [INFO] task-segment: [install]
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO]
> -------------------------------------------------------------------------
> ---
> [ERROR] BUILD ERROR
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Error executing ant tasks
>
> Embedded error: Could not create task or type of type: ftp.
>
> 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 'ftp'.
> 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.
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
> task
> s
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:544)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:469)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:448)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:301)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:268)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:137)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing
> ant t
> asks
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA
> ntMojo.java:114)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:399)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:519)
> ... 16 more
> Caused by: Could not create task or type of type: ftp.
>
> 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 'ftp'.
> 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(UnknownEleme
> nt.java:493)
> at
> org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:39
> 1)
> at
> org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
> a:158)
> 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(AbstractA
> ntMojo.java:108)
> ... 19 more
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Total time: 1 second
> [INFO] Finished at: Tue Apr 25 19:17:52 BST 2006
> [INFO] Final Memory: 3M/7M
> [INFO]
> -------------------------------------------------------------------------
> ---
> --
> View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4087557
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE : Doubt in using wagon plugin
Posted by Olivier Lamy <ol...@accor.com>.
Have a look
http://ant.apache.org/manual/install.html#commons-net
http://ant.apache.org/manual/install.html
Certainly not a maven trouble !
But try the maven-wagon-plugin with an url like sftp://host/path
- Olivier
-----Message d'origine-----
De : RobJac [mailto:robin.jacob@caritor.com]
Envoyé : mardi 25 avril 2006 20:21
À : users@maven.apache.org
Objet : Re: Doubt in using wagon plugin
sorry wayne.. forgot to add the exception. Please find below. I was
trying to execute "mvn install" fir my ear pom xml. It created an EAR
fine and while trying to ftp it I guess the below exception is occuring.
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
-
---
[INFO] Building Unnamed - DefinedBenefit_EA:DefinedBenefit_EA:ear:1.0
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
-
---
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO]
------------------------------------------------------------------------
-
---
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
-
---
[INFO] Error executing ant tasks
Embedded error: Could not create task or type of type: ftp.
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 'ftp'.
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. [INFO]
------------------------------------------------------------------------
-
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing
ant task s
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:544)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:137)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
executing ant t asks
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA
ntMojo.java:114)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:399)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:519)
... 16 more
Caused by: Could not create task or type of type: ftp.
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 'ftp'.
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(UnknownEleme
nt.java:493)
at
org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:39
1)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
a:158)
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(AbstractA
ntMojo.java:108)
... 19 more
[INFO]
------------------------------------------------------------------------
-
---
[INFO] Total time: 1 second
[INFO] Finished at: Tue Apr 25 19:17:52 BST 2006
[INFO] Final Memory: 3M/7M
[INFO]
------------------------------------------------------------------------
-
---
--
View this message in context:
http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4087557
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited.
**********************************************************************
Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by RobJac <ro...@caritor.com>.
sorry wayne.. forgot to add the exception. Please find below. I was trying
to execute "mvn install" fir my ear pom xml. It created an EAR fine and
while trying to ftp it I guess the below exception is occuring.
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building Unnamed - DefinedBenefit_EA:DefinedBenefit_EA:ear:1.0
[INFO] task-segment: [install]
[INFO]
-------------------------------------------------------------------------
---
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO]
-------------------------------------------------------------------------
---
[ERROR] BUILD ERROR
[INFO]
-------------------------------------------------------------------------
---
[INFO] Error executing ant tasks
Embedded error: Could not create task or type of type: ftp.
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 'ftp'.
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.
[INFO]
-------------------------------------------------------------------------
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
task
s
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:544)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing
ant t
asks
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA
ntMojo.java:114)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:399)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:519)
... 16 more
Caused by: Could not create task or type of type: ftp.
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 'ftp'.
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(UnknownEleme
nt.java:493)
at
org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:39
1)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
a:158)
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(AbstractA
ntMojo.java:108)
... 19 more
[INFO]
-------------------------------------------------------------------------
---
[INFO] Total time: 1 second
[INFO] Finished at: Tue Apr 25 19:17:52 BST 2006
[INFO] Final Memory: 3M/7M
[INFO]
-------------------------------------------------------------------------
---
--
View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4087557
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by Wayne Fay <wa...@gmail.com>.
"does not work" is not sufficient to try and debug your issue. What's
the error message exactly, and what command are you running, etc?
Wayne
On 4/25/06, RobJac <ro...@caritor.com> wrote:
>
> I want to FTP and ear from a location in my local m/c into a particular
> location in a remote machine using as soon as i run an mvn install command.
> I tried using ant plugin for Maven, but it does not seem to work. Please
> find below my entry in the ear pom xml for this
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-antrun-plugin</artifactId>
> <executions>
> <execution>
> <phase>generate-sources</phase>
> <configuration>
> <tasks>
> <ftp server="10.151.1.202"
>
> remotedir="/opt/jboss403SP1"
>
> depends="yes"
>
> userid="jboss"
>
> password="passw0rd">
>
> <fileset dir="${basedir}"/>
>
> </ftp>
>
> </tasks>
> </configuration>
> <goals>
> <goal>run</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> --
> View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4087204
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Doubt in using wagon plugin
Posted by RobJac <ro...@caritor.com>.
I want to FTP and ear from a location in my local m/c into a particular
location in a remote machine using as soon as i run an mvn install command.
I tried using ant plugin for Maven, but it does not seem to work. Please
find below my entry in the ear pom xml for this
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>generate-sources</phase>
<configuration>
<tasks>
<ftp server="10.151.1.202"
remotedir="/opt/jboss403SP1"
depends="yes"
userid="jboss"
password="passw0rd">
<fileset dir="${basedir}"/>
</ftp>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
--
View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4087204
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Doubt in using wagon plugin
Posted by Wayne Fay <wa...@gmail.com>.
This will not work. Wagon is simply the transport mechanism for moving
files around over various protocols including FTP, HTTP, etc.
What *exactly* is your use case? Do you want to simply "move" an EAR
file to a remote server using FTP, or do you want to "deploy" an EAR
file into a remote application server, or what exactly?
If you simply want to FTP the file, I don't believe there are any M2
plugins that can help. You will need to use an Antrun task or call out
to an Operating System ftp command.
Wayne
On 4/25/06, RobJac <ro...@caritor.com> wrote:
>
> Has some one used wagon plugin in your pom xml. I was trying to ftp an ear
> using the wagon plugin to a particular location in a remote server but i
> dont see any options to provide the destination directory. If wagon can help
> me in solving this requirement, could you please send me the entry for this
> plugin in your pom xml. The entry for this plugin in my pom xml is
>
> <plugin>
> <groupId>org.apache.myfaces.maven</groupId>
> <artifactId>wagon-maven-plugin</artifactId>
> <configuration>
> <id>10.151.1.202</id>
> <inputDirectory>${basedir}</inputDirectory>
> <url>10.151.1.202</url>
> </configuration>
> </plugin>
>
> is this correct? and finally what is the command that is used to run this
> mvn install was not helping me. I would appreciate if some one could throw
> some light on this.
> --
> View this message in context: http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4086387
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: RE : Doubt in using wagon plugin
Posted by Wayne Fay <wa...@gmail.com>.
Good point Olivier. I suppose this is a "new to me" plugin from the
MyFaces group which might actually support this FTP transfer a file
function he's looking for?
If so, this is good news. I know some other Maven Users have requested
such a plugin in the past few months...
Wayne
On 4/25/06, Olivier Lamy <ol...@accor.com> wrote:
> The url must be something a wagon url like sftp , scp , file ? Not sure
> But ask your question in myfaces-user@ because it's not a
> org.apache.maven.plugins.
>
> - Olivier
>
> -----Message d'origine-----
> De : RobJac [mailto:robin.jacob@caritor.com]
> Envoyé : mardi 25 avril 2006 19:21
> À : users@maven.apache.org
> Objet : Doubt in using wagon plugin
>
>
>
> Has some one used wagon plugin in your pom xml. I was trying to ftp an
> ear using the wagon plugin to a particular location in a remote server
> but i dont see any options to provide the destination directory. If
> wagon can help me in solving this requirement, could you please send me
> the entry for this plugin in your pom xml. The entry for this plugin in
> my pom xml is
>
> <plugin>
> <groupId>org.apache.myfaces.maven</groupId>
>
> <artifactId>wagon-maven-plugin</artifactId>
> <configuration>
> <id>10.151.1.202</id>
> <inputDirectory>${basedir}</inputDirectory>
> <url>10.151.1.202</url>
> </configuration>
> </plugin>
>
> is this correct? and finally what is the command that is used to run
> this mvn install was not helping me. I would appreciate if some one
> could throw some light on this.
> --
> View this message in context:
> http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4086387
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited.
> **********************************************************************
> Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites.
> **********************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE : Doubt in using wagon plugin
Posted by Olivier Lamy <ol...@accor.com>.
The url must be something a wagon url like sftp , scp , file ? Not sure
But ask your question in myfaces-user@ because it's not a
org.apache.maven.plugins.
- Olivier
-----Message d'origine-----
De : RobJac [mailto:robin.jacob@caritor.com]
Envoyé : mardi 25 avril 2006 19:21
À : users@maven.apache.org
Objet : Doubt in using wagon plugin
Has some one used wagon plugin in your pom xml. I was trying to ftp an
ear using the wagon plugin to a particular location in a remote server
but i dont see any options to provide the destination directory. If
wagon can help me in solving this requirement, could you please send me
the entry for this plugin in your pom xml. The entry for this plugin in
my pom xml is
<plugin>
<groupId>org.apache.myfaces.maven</groupId>
<artifactId>wagon-maven-plugin</artifactId>
<configuration>
<id>10.151.1.202</id>
<inputDirectory>${basedir}</inputDirectory>
<url>10.151.1.202</url>
</configuration>
</plugin>
is this correct? and finally what is the command that is used to run
this mvn install was not helping me. I would appreciate if some one
could throw some light on this.
--
View this message in context:
http://www.nabble.com/Doubt-in-using-wagon-plugin-t1506734.html#a4086387
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited.
**********************************************************************
Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org