[jira] Commented: (MSITE-598) Maven Site Plugin 3.x ignores Wagon extensions

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MSITE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274040#comment-274040 ] 

Robert Scholte commented on MSITE-598:
--------------------------------------

Some additional background info.

The reason why they were added:
{quote}r810799 | olamy | 2009-09-03 09:58:39 +0200 (Do, 03 Sep 2009) | 2 lines
add back wagon providers which are not anymore in core to be able to deploy with scp/scpexe/ftp/webdav
Note : currently webdav deployment failed with a CNFE (need more investigation)
{quote}

And the reason why they were removed (from maven-site-plugin *_after_* branching for maven-site-plugin-3.x) :
{quote}r1003778 | bentmann | 2010-10-02 13:59:44 +0200 (Sa, 02 Okt 2010) | 1 line
o Decoupled from erroneous assumption about wagon providers bundled with core, the set of wagon providers shipped with the core is an implementation detail, not a service contract
{quote}

> Maven Site Plugin 3.x ignores Wagon extensions
> ----------------------------------------------
>
>                 Key: MSITE-598
>                 URL: https://jira.codehaus.org/browse/MSITE-598
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Improvement
>          Components: site:deploy
>    Affects Versions: 3.0-beta-3
>            Reporter: Robert Scholte
>
> The Wagon extensions are ignores if you try to do a site deployment.
> Reason is that they are defined as dependency in the plugin.
> {code:xml}
> <!-- Wagon -->
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-provider-api</artifactId>
>       <version>${wagonVersion}</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-file</artifactId>
>       <version>${wagonVersion}</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-http-lightweight</artifactId>
>       <version>${wagonVersion}</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-ssh</artifactId>
>       <version>${wagonVersion}</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-ssh-external</artifactId>
>       <version>${wagonVersion}</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-ftp</artifactId>
>       <version>${wagonVersion}</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-webdav-jackrabbit</artifactId>
>       <version>${wagonVersion}</version>
>       <exclusions>
>         <exclusion>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-nop</artifactId>
>         </exclusion>
>       </exclusions>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven.wagon</groupId>
>       <artifactId>wagon-scm</artifactId>
>       <version>${wagonVersion}</version>
>     </dependency>
> {code}
> The only way to override them is to add the specific wagon-impl as a dependency to the plugin.
> Right now this just leads to unexpected usage of extensions.
> I suggest to remove these specific impl's, try to catch exceptions on missing wagons if they occur and advice to use extensions.
> Btw, it seems like they are already removed from the maven-site-plugin-2.x

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira