You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Site plugin with maven 3.x

Due to MNG-4162, all reporting logic has been removed from trunk.
So a branch of the site plugin has been created https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-3.x/ in order to have a site plugin working with maven 3.x .

Plugins Compatibility Matrix

Plugins Maintained by the Apache Maven Community

Tests has been made on the reporting profile of the maven parent pom which enables some reports.
Some of those plugins will need releases to work with maven 3.x :

Plugin

Version

Status

Comments

maven-javadoc-plugin

2.6

(error)

need a release see MJAVADOC-251, some its failed MJAVADOC-180, MJAVADOC-181 : need more investiguation

maven-project-info-reports-plugin

2.1.2

(error) (dependencies report)

need a release due to a use of plexusContainer.getLoggerManager() which has been removed see MPIR-174

surefire-report

2.4.3

(tick)

 

jxr

2.1

(tick)

 

maven-changelog-plugin

2.1

(tick)

 

maven-changes-plugin

2.1

(question)

some its failed

maven-checkstyle-plugin

2.2

(error)

see MCHECKSTYLE-123

maven-pmd-plugin

2.4

(tick)

 

Plugins Maintained by the Mojo Community

Plugin

Version

Status

Comments

cobertura-maven-plugin

2.3

(tick)

 

emma-maven-plugin

1.0-alpha-2

(question)

 

Snapshots dependencies.

This new version 3.0-beta-1 requires some dependencies release :

Know issues

Configuration format.

The current reporting section of the pom have to be moved in a new site plugin configuration.
The proposal is to have a configuration as much similar as possible with the current one.
The model builder will transform it on the fly with displaying a warning concerning this change.

Old configuration

  <reporting>
    <excludeDefaults>true</excludeDefaults>
    <outputDirectory></outputDirectory>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-project-info-reports-plugin</artifactId>
        <version><at:var at:name="projectInfoReportsPluginVersion" /></version>
        <configuration>
          <dependencyDetailsEnabled>false</dependencyDetailsEnabled>
          <dependencyLocationsEnabled>false</dependencyLocationsEnabled>
        </configuration>
      </plugin>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-javadoc-plugin</artifactId>
        <version>${javadocPluginVersion}</version>          
      </plugin>  
          
    </plugins>
  </reporting>

New Configuration


  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-site-plugin</artifactId>
        <version>@project.version@</version>
        <configuration>
          .....
          <reportPlugins>
            <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-project-info-reports-plugin</artifactId>
              <version><at:var at:name="projectInfoReportsPluginVersion" /></version>
              <configuration>
                <dependencyDetailsEnabled>false</dependencyDetailsEnabled>
                <dependencyLocationsEnabled>false</dependencyLocationsEnabled>
              </configuration>
            </plugin>
            <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-javadoc-plugin</artifactId>
              <version>${javadocPluginVersion}</version>          
            </plugin>            
          </reportPlugins>
        </configuration>
      </plugin>
    </plugins>

TODO

  • consider plugin without version specified : using version of build plugin then pluginManagement at the end use last version available
  • No labels