[MSITE-598] Maven Site Plugin 3.x ignores Wagon extensions

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0-beta-3
• Fix Version/s: 3.0
• Component/s: site:deploy
• Assignee: Herve Boutemy
• Reporter: Robert Scholte
• Created: 23/Jul/11 08:55
• Updated: 22/Oct/11 14:30
• Resolved: 25/Jul/11 15:31

Description

The Wagon extensions are ignores if you try to do a site deployment.
Reason is that they are defined as dependency in the plugin.

<!-- 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>

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

Issue Links

• depends upon: MSITE-599 Improve error message when deploy protocol isn't available
• is related to: MSITE-615 Mercurial (HG) SCM Provider not detected in 3.0, was in 3.0-beta-3