Uploaded image for project: 'Maven Javadoc Plugin'
  1. Maven Javadoc Plugin
  2. MJAVADOC-694

Empty warning with maven-javadoc-plugin 3.3.1

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 3.3.1
    • 3.3.2
    • None
    • None

    Description

      I tested recently to upgrade to v3.3.1 and I get an empyt [WARNING] in my maven logs.

      Tested with v3.3.0, v3.2.0 and v3.1.1 and I don't face this issue.

      E.g. :

      [INFO] <<< maven-javadoc-plugin:3.3.1:javadoc (default-cli) < generate-sources @ leshan-server-redis <<<
      [INFO] 
      [INFO] 
      [INFO] --- maven-javadoc-plugin:3.3.1:javadoc (default-cli) @ leshan-server-redis ---
      [WARNING] 
      [INFO] Configuration changed, re-generating javadoc.
      [INFO] 
      [INFO] ---------------< org.eclipse.leshan:leshan-client-core >----------------
      [INFO] Building leshan - client core 2.0.0-SNAPSHOT                      [7/14]
      [INFO] -------------------------------[ bundle ]-------------------------------
      
      

       

      Attachments

        Activity

          The cause is, that UnsupportedOperationException doesn't have exception message, but we try:

          getLog().warn( e.getMessage() );
          
          java.lang.UnsupportedOperationException
              at org.codehaus.plexus.languages.java.jpms.CmdModuleNameExtractor.getModuleName (CmdModuleNameExtractor.java:46)
              at org.codehaus.plexus.languages.java.jpms.LocationManager$1.extract (LocationManager.java:130)
              at org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePath (LocationManager.java:381)
              at org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePath (LocationManager.java:135)
              at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getResolvePathResult (AbstractJavadocMojo.java:5536)
          

          Above exception occurs on jdk < 9 - without modules

          sjaranowski Slawomir Jaranowski added a comment - The cause is, that UnsupportedOperationException doesn't have exception message, but we try: getLog().warn( e.getMessage() ); java.lang.UnsupportedOperationException at org.codehaus.plexus.languages.java.jpms.CmdModuleNameExtractor.getModuleName (CmdModuleNameExtractor.java:46) at org.codehaus.plexus.languages.java.jpms.LocationManager$1.extract (LocationManager.java:130) at org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePath (LocationManager.java:381) at org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePath (LocationManager.java:135) at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getResolvePathResult (AbstractJavadocMojo.java:5536) Above exception occurs on jdk < 9 - without modules

          I will fix it.

          sjaranowski Slawomir Jaranowski added a comment - I will fix it.

          People

            sjaranowski Slawomir Jaranowski
            sbernard Simon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: