You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2011/07/24 22:24:42 UTC

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

     [ https://jira.codehaus.org/browse/MSITE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte updated MSITE-598:
---------------------------------

    Priority: Critical  (was: Major)

> 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
>            Priority: Critical
>
> 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