maven-site plugins 3.3 java.lang.ClassNotFoundException: org.apache.maven.doxia.siterenderer.DocumentContent

后端 未结 8 1975
感动是毒
感动是毒 2020-11-29 01:07

Since this night, maven site 3.3 plugins stop to work.

Try to delete local repository, but no change. Maven 3.3.9 java 1.8

No config or dependencies defined

相关标签:
8条回答
  • 2020-11-29 01:21

    Maven 3 doesn't support Doxia anymore.

    Use

    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-project-info-reports-plugin</artifactId>
      <version>2.2</version>
    </plugin>
    

    Reference: https://maven.apache.org/plugins/maven-site-plugin/maven-3.html

    0 讨论(0)
  • 2020-11-29 01:22

    The following versions in pom.xml fixed the problem for me:

                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-site-plugin</artifactId>
                    <version>3.7</version>
                </plugin>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-project-info-reports-plugin</artifactId>
                    <version>2.9</version>
                </plugin>
    
    0 讨论(0)
  • 2020-11-29 01:23

    You really need to add more information (I didn't downvote BTW).

    IIRC; if you don't specify a version for a plugin bound to lifecycle phases, you'll get the latest.

    Try:

    • Upgrading to the latest version of maven - 3.5.4 ATOW
    • Running mvn help:effective-pom and checking which versions are actually being resolved - if you have an old log from CI or wherever to compare with..
    • Explicity setting the maven-site-plugin version in pluginManagement section
    • Adding a dependency to maven-site-plugin (see below)

    org/apache/maven/doxia/siterenderer/DocumentContent can be found in doxia-site-renderer:

        <dependency>
            <groupId>org.apache.maven.doxia</groupId>
            <artifactId>doxia-site-renderer</artifactId>
            <version>1.8.1</version>
        </dependency>
    

    I suspect explicitly setting the version of maven-site-plugin to whatever you used to use (incidentally) will work.


    Edit: Was chasing a similar issue in maven plugin build testing, explicitly setting maven-site-plugin version (3.7.1 ATOW) in integration pom used by maven-invoker-plugin has worked for me.

    0 讨论(0)
  • 2020-11-29 01:32

    This is caused by maven-project-info-reports-plugin updated to 3.0.0, and rely on doxia-site-renderer 1.8 (and have org.apache.maven.doxia.siterenderer.DocumentContent this class), but maven-site-plugin:3.3 rely on doxia-site-renderer:1.4 (and do not have org.apache.maven.doxia.siterenderer.DocumentContent)

    We can specific maven-project-info-reports-plugin version in reporting part:

    <reporting>
            <plugins>           
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-project-info-reports-plugin</artifactId>
                    <version>2.9</version>
                </plugin>           
            </plugins>    
        </reporting>
    

    Or we can specify maven-site-plugin to the latest 3.7.1 like:

    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-site-plugin</artifactId>
        <version>3.7.1</version>
    </plugin>
    

    in build part of pom

    0 讨论(0)
  • 2020-11-29 01:36

    I also hit this error on some of my build jobs today. The fix suggested above, adding a concrete dependency for the maven-site-plugin does work and fixes this issue.

    However, what it highlighted for me was the fact I was even running the mvn site goal, which I didn't even know we were running and we don't really require.

    My fix was to therefore remove the site goal from my mvn arg, as although the site it creates is actually quite useful, I never knew we were creating it, we never published it anywhere and were actually deleting it every build anyway.

    0 讨论(0)
  • 2020-11-29 01:37

    I had just started to get this issue also during builds. What worked for me was to specifically define the maven-site-plugin and the maven-project-info-reports-plugin along with the version numbers in the pom.

    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-site-plugin</artifactId>
      <version>3.7.1</version>
    </plugin>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-project-info-reports-plugin</artifactId>
      <version>3.0.0</version>
    </plugin>
    
    0 讨论(0)
提交回复
热议问题