[
http://jira.codehaus.org/browse/MDEPLOY-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann closed MDEPLOY-128.
-----------------------------------
Resolution: Won't Fix
Thanks for the suggestion, Dan. I did not know the wagon-maven-plugin, but the
following snippet does exactly what I had in mind:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>wagon-maven-plugin</artifactId>
<version>1.0-beta-3</version>
<executions>
<execution>
<id>deploy-update-site</id>
<phase>deploy</phase>
<goals>
<goal>upload</goal>
</goals>
<configuration>
<fromDir>${project.build.directory}/site</fromDir>
<url>sftp://web.sourceforge.net/home/groups/m/mo/mongrel/htdocs/updates</url>
<serverId>mongrel.sf.net</serverId>
</configuration>
</execution>
</executions>
</plugin>
I am therefore closing this issue.
> Add deploy-dir goal
> -------------------
>
> Key: MDEPLOY-128
> URL: http://jira.codehaus.org/browse/MDEPLOY-128
> Project: Maven 2.x Deploy Plugin
> Issue Type: New Feature
> Affects Versions: 2.6
> Reporter: Jochen Wiedmann
> Attachments: deploy-dir-mojo.patch
>
>
> The attached patch introduces a deploy-dir Mojo, which basically works just
> like the site plugins site-deploy mojo, except that it is configured manually
> (like deploy-file) and not from within the POM.
> My personal use case is as follows: I've got an Eclipse update site, which is
> built with Tycho. However, Tycho doesn't allow me to deploy the created
> update site. Deploying this update site currently requires the antrun plugin,
> or similar mechanisms, which completely circumvent Wagon and all these
> things, which are already built into Maven. In particular, I can't use the
> authentication, which is configured anyways, because the host carrying my
> update site is (surprise!) the same host, which carries my repository and my
> deployed site and everything is deployed using SFTP anyways.
> Rather than building this into Tycho, I choosed a more generic approach, as I
> believe that my requirement might be useful for other purposes as well.
> The patch includes a test case based on the plugin-testing-harness.
> The patch borrows heavily from site:site-deploy. I won't comment, whether
> this makes sense or not. I am ready to refactor the patch, should that be
> required. However, I'd like to have something like a basic "Ok", before doing
> this additional work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
