On Sat, Aug 16, 2008 at 1:06 PM, Brett Porter <[EMAIL PROTECTED]>
wrote:
>
> That's a reasonable option. If the FTP server is a Maven repository
> you could use distributionManagement and use the regular maven
> deployment. The only other alternative I've seen is a couple of
> different "wagon" plugins floating around that utilise the existing
> Maven deployment for arbitrary file transfer.
>
> - Brett
>
Thanks Brett.I've gone with the maven-antrun-plugin and for the lonely
soul out there wishing to do the same , my working configuration is :
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>pre-integration-test</phase>
<configuration>
<tasks>
<ftp server="server" remotedir="/whatever/it/is"
userid="your_user_name" password="your_password" action="put"
verbose="true">
<fileset dir="target" includes="**/*.tar.gz" />
</ftp>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-commons-net</artifactId>
<version>1.6.5</version>
</dependency>
<dependency>
<groupId>commons-net</groupId>
<artifactId>commons-net</artifactId>
<version>1.4.1</version>
</dependency>
<!--Didnt need the following 2 dependencies but they may be needed for
other tasks such as listing files on the ftp server,etc Jeff-->
<!--<dependency>
<groupId>ant</groupId>
<artifactId>optional</artifactId>
<version>1.5.4</version>
</dependency>
<dependency>
<groupId>oro</groupId>
<artifactId>oro</artifactId>
<version>2.0.8</version>
</dependency> -->
</dependencies>
</plugin>
--
"Don't take the name of root in vain."
Jeff Mutonho
Cape Town
South Africa
GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042
