[jira] [Commented] (MJAVADOC-737) error: cannot find symbol @Test since plugin version 3.3.0
[
https://issues.apache.org/jira/browse/MJAVADOC-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687858#comment-17687858
]
Kai Hofmann commented on MJAVADOC-737:
--
See *External issue URL*
> error: cannot find symbol @Test since plugin version 3.3.0
>
>
> Key: MJAVADOC-737
> URL: https://issues.apache.org/jira/browse/MJAVADOC-737
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.0, 3.3.1, 3.3.2, 3.4.0, 3.4.1
> Environment: Windows 10, Maven 3.6.0
>Reporter: Kai Hofmann
>Priority: Blocker
>
> After updating maven-javadoc-plugin from 3.2.0 to 3.4.1 I got the following
> error messages for my test code only, when executing
> {code:java}
> mvn site{code}
> Constructing Javadoc information...
> 100 errors
> [ERROR] Error while creating javadoc report:
> Exit code: 1 -
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
> error: package org.junit.jupiter.api does not exist
> import static org.junit.jupiter.api.Assertions.assertAll;
> [...]
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:27:
> error: package org.junit.jupiter.api does not exist
> import org.junit.jupiter.api.Test;
> ^
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:31:
> error: package edu.umd.cs.findbugs.annotations does not exist
> import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
> ^
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
> error: cannot find symbol
> @SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
> ^
> symbol: class SuppressFBWarnings
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
> error: cannot find symbol
> @Test
> ^
> [...]
> Command line was: cmd.exe /X /C ""C:\Program
> Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
> Refer to the generated Javadoc files in
> 'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
> org.apache.maven.reporting.MavenReportException:
> Exit code: 1 -
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
> error: package org.junit.jupiter.api does not exist
> import static org.junit.jupiter.api.Assertions.assertAll;
> [...]
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
> error: cannot find symbol
> @SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
> ^
> symbol: class SuppressFBWarnings
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
> error: cannot find symbol
> @Test
> ^
> symbol: class Test
> location: class TemplateEngineTests
> [...]
> Command line was: cmd.exe /X /C ""C:\Program
> Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
> Refer to the generated Javadoc files in
> 'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.doExecuteJavadocCommandLine
> (AbstractJavadocMojo.java:6092)
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeJavadocCommandLine
> (AbstractJavadocMojo.java:5968)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
> (AbstractJavadocMojo.java:2277)
> at org.apache.maven.plugins.javadoc.TestJavadocReport.executeReport
> (TestJavadocReport.java:162)
> at org.apache.maven.plugins.javadoc.JavadocReport.generate
> (JavadocReport.java:150)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org
[jira] [Created] (MJAVADOC-778) Module not visible when creating test javadocs
Kai Hofmann created MJAVADOC-778:
Summary: Module not visible when creating test javadocs
Key: MJAVADOC-778
URL: https://issues.apache.org/jira/browse/MJAVADOC-778
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 3.6.0
Environment: maven, java 17, windows 10
Reporter: Kai Hofmann
I have an open source java project with java module system on github:
[https://github.com/PowerStat/Validation]
When doing a
{code:java}
mvn site{code}
This will result in the following:
{code:java}
[INFO] Generating "Test Javadoc" report ---
maven-javadoc-plugin:3.6.0:test-aggregate-no-fork
[INFO] Configuration changed, re-generating javadoc.
[ERROR] Error while creating javadoc report:
Exit code: 1
C:\Users\PowerStat\Documents\Validation\src\test\java\de\powerstat\comparators\test\ComparatorEMailByDomainTests.java:7:
error: package org.junit.jupiter.api is not visible
import static org.junit.jupiter.api.Assertions.assertEquals;
^
(package org.junit.jupiter.api is declared in the unnamed module, but
module de.powerstat.validation does not read it)
C:\Users\PowerStat\Documents\Validation\src\test\java\de\powerstat\comparators\test\ComparatorEMailByDomainTests.java:7:
error: static import only from classes and interfaces
import static org.junit.jupiter.api.Assertions.assertEquals;
^
[...]
100 errors
Command line was: cmd.exe /X /C ""C:\Program
Files\Java\jdk-17\bin\javadoc.exe" @options @argfile"
Refer to the generated Javadoc files in
'C:\Users\PowerStat\Documents\Validation\target\site\testapidocs' dir.
org.apache.maven.reporting.MavenReportException:
Exit code: 1
C:\Users\PowerStat\Documents\Validation\src\test\java\de\powerstat\comparators\test\ComparatorEMailByDomainTests.java:7:
error: package org.junit.jupiter.api is not visible
import static org.junit.jupiter.api.Assertions.assertEquals;
^
(package org.junit.jupiter.api is declared in the unnamed module, but
module de.powerstat.validation does not read it)
C:\Users\PowerStat\Documents\Validation\src\test\java\de\powerstat\comparators\test\ComparatorEMailByDomainTests.java:7:
error: static import only from classes and interfaces
import static org.junit.jupiter.api.Assertions.assertEquals;
^
[...]
100 errors
Command line was: cmd.exe /X /C ""C:\Program
Files\Java\jdk-17\bin\javadoc.exe" @options @argfile"
Refer to the generated Javadoc files in
'C:\Users\PowerStat\Documents\Validation\target\site\testapidocs' dir.
at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.doExecuteJavadocCommandLine
(AbstractJavadocMojo.java:5183)
at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeJavadocCommandLine
(AbstractJavadocMojo.java:5068)
at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
(AbstractJavadocMojo.java:2028)
at org.apache.maven.plugins.javadoc.TestJavadocReport.executeReport
(TestJavadocReport.java:153)
at org.apache.maven.plugins.javadoc.JavadocReport.generate
(JavadocReport.java:135)
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:226)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:348)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:194)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.
[jira] [Created] (MJAVADOC-737) error: cannot find symbol @Test since plugin version 3.3.0
Kai Hofmann created MJAVADOC-737:
Summary: error: cannot find symbol @Test since plugin version
3.3.0
Key: MJAVADOC-737
URL: https://issues.apache.org/jira/browse/MJAVADOC-737
Project: Maven Javadoc Plugin
Issue Type: Bug
Components: javadoc
Affects Versions: 3.4.1, 3.4.0, 3.3.2, 3.3.1, 3.3.0
Environment: Windows 10, Maven 3.6.0
Reporter: Kai Hofmann
After updating maven-javadoc-plugin from 3.2.0 to 3.4.1 I got the following
error messages for my test code only, when executing
{code:java}
mvn site{code}
Constructing Javadoc information...
100 errors
[ERROR] Error while creating javadoc report:
Exit code: 1 -
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
error: package org.junit.jupiter.api does not exist
import static org.junit.jupiter.api.Assertions.assertAll;
[...]
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:27:
error: package org.junit.jupiter.api does not exist
import org.junit.jupiter.api.Test;
^
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:31:
error: package edu.umd.cs.findbugs.annotations does not exist
import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
^
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
error: cannot find symbol
@SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
^
symbol: class SuppressFBWarnings
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
error: cannot find symbol
@Test
^
[...]
Command line was: cmd.exe /X /C ""C:\Program
Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
Refer to the generated Javadoc files in
'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
org.apache.maven.reporting.MavenReportException:
Exit code: 1 -
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
error: package org.junit.jupiter.api does not exist
import static org.junit.jupiter.api.Assertions.assertAll;
[...]
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
error: cannot find symbol
@SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
^
symbol: class SuppressFBWarnings
C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
error: cannot find symbol
@Test
^
symbol: class Test
location: class TemplateEngineTests
[...]
Command line was: cmd.exe /X /C ""C:\Program
Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
Refer to the generated Javadoc files in
'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.doExecuteJavadocCommandLine
(AbstractJavadocMojo.java:6092)
at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeJavadocCommandLine
(AbstractJavadocMojo.java:5968)
at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
(AbstractJavadocMojo.java:2277)
at org.apache.maven.plugins.javadoc.TestJavadocReport.executeReport
(TestJavadocReport.java:162)
at org.apache.maven.plugins.javadoc.JavadocReport.generate
(JavadocReport.java:150)
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:226)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:349)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:194)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apach
[jira] [Updated] (MJAVADOC-737) error: cannot find symbol @Test since plugin version 3.3.0
[
https://issues.apache.org/jira/browse/MJAVADOC-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Hofmann updated MJAVADOC-737:
-
External issue URL: https://github.com/PowerStat/TemplateEngine
> error: cannot find symbol @Test since plugin version 3.3.0
>
>
> Key: MJAVADOC-737
> URL: https://issues.apache.org/jira/browse/MJAVADOC-737
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.0, 3.3.1, 3.3.2, 3.4.0, 3.4.1
> Environment: Windows 10, Maven 3.6.0
>Reporter: Kai Hofmann
>Priority: Blocker
>
> After updating maven-javadoc-plugin from 3.2.0 to 3.4.1 I got the following
> error messages for my test code only, when executing
> {code:java}
> mvn site{code}
> Constructing Javadoc information...
> 100 errors
> [ERROR] Error while creating javadoc report:
> Exit code: 1 -
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
> error: package org.junit.jupiter.api does not exist
> import static org.junit.jupiter.api.Assertions.assertAll;
> [...]
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:27:
> error: package org.junit.jupiter.api does not exist
> import org.junit.jupiter.api.Test;
> ^
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:31:
> error: package edu.umd.cs.findbugs.annotations does not exist
> import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
> ^
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
> error: cannot find symbol
> @SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
> ^
> symbol: class SuppressFBWarnings
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
> error: cannot find symbol
> @Test
> ^
> [...]
> Command line was: cmd.exe /X /C ""C:\Program
> Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
> Refer to the generated Javadoc files in
> 'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
> org.apache.maven.reporting.MavenReportException:
> Exit code: 1 -
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
> error: package org.junit.jupiter.api does not exist
> import static org.junit.jupiter.api.Assertions.assertAll;
> [...]
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
> error: cannot find symbol
> @SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
> ^
> symbol: class SuppressFBWarnings
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
> error: cannot find symbol
> @Test
> ^
> symbol: class Test
> location: class TemplateEngineTests
> [...]
> Command line was: cmd.exe /X /C ""C:\Program
> Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
> Refer to the generated Javadoc files in
> 'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.doExecuteJavadocCommandLine
> (AbstractJavadocMojo.java:6092)
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeJavadocCommandLine
> (AbstractJavadocMojo.java:5968)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
> (AbstractJavadocMojo.java:2277)
> at org.apache.maven.plugins.javadoc.TestJavadocReport.executeReport
> (TestJavadocReport.java:162)
> at org.apache.maven.plugins.javadoc.JavadocReport.generate
> (JavadocReport.java:150)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.l
[jira] [Commented] (MJAVADOC-737) error: cannot find symbol @Test since plugin version 3.3.0
[
https://issues.apache.org/jira/browse/MJAVADOC-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629783#comment-17629783
]
Kai Hofmann commented on MJAVADOC-737:
--
I have already tested all versions between - thats why I all marked them as
affected.
> error: cannot find symbol @Test since plugin version 3.3.0
>
>
> Key: MJAVADOC-737
> URL: https://issues.apache.org/jira/browse/MJAVADOC-737
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.0, 3.3.1, 3.3.2, 3.4.0, 3.4.1
> Environment: Windows 10, Maven 3.6.0
>Reporter: Kai Hofmann
>Priority: Blocker
>
> After updating maven-javadoc-plugin from 3.2.0 to 3.4.1 I got the following
> error messages for my test code only, when executing
> {code:java}
> mvn site{code}
> Constructing Javadoc information...
> 100 errors
> [ERROR] Error while creating javadoc report:
> Exit code: 1 -
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
> error: package org.junit.jupiter.api does not exist
> import static org.junit.jupiter.api.Assertions.assertAll;
> [...]
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:27:
> error: package org.junit.jupiter.api does not exist
> import org.junit.jupiter.api.Test;
> ^
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:31:
> error: package edu.umd.cs.findbugs.annotations does not exist
> import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
> ^
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
> error: cannot find symbol
> @SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
> ^
> symbol: class SuppressFBWarnings
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
> error: cannot find symbol
> @Test
> ^
> [...]
> Command line was: cmd.exe /X /C ""C:\Program
> Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
> Refer to the generated Javadoc files in
> 'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
> org.apache.maven.reporting.MavenReportException:
> Exit code: 1 -
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:7:
> error: package org.junit.jupiter.api does not exist
> import static org.junit.jupiter.api.Assertions.assertAll;
> [...]
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:37:
> error: cannot find symbol
> @SuppressFBWarnings(\{"CE_CLASS_ENVY", "EC_NULL_ARG"})
> ^
> symbol: class SuppressFBWarnings
> C:\Users\PowerStat\Documents\TemplateEngine\src\test\java\de\powerstat\phplib\templateengine\test\TemplateEngineTests.java:342:
> error: cannot find symbol
> @Test
> ^
> symbol: class Test
> location: class TemplateEngineTests
> [...]
> Command line was: cmd.exe /X /C ""C:\Program
> Files\Java\jdk-11.0.10\bin\javadoc.exe" @options @packages @argfile"
> Refer to the generated Javadoc files in
> 'C:\Users\PowerStat\Documents\TemplateEngine\target\site\testapidocs' dir.
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.doExecuteJavadocCommandLine
> (AbstractJavadocMojo.java:6092)
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeJavadocCommandLine
> (AbstractJavadocMojo.java:5968)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
> (AbstractJavadocMojo.java:2277)
> at org.apache.maven.plugins.javadoc.TestJavadocReport.executeReport
> (TestJavadocReport.java:162)
> at org.apache.maven.plugins.javadoc.JavadocReport.generate
> (JavadocReport.java:150)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.interna
[jira] [Commented] (MJDEPS-20) jdeps for modularized code should use --module-path
[
https://issues.apache.org/jira/browse/MJDEPS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275499#comment-17275499
]
Kai Hofmann commented on MJDEPS-20:
---
Same problem
> jdeps for modularized code should use --module-path
> ---
>
> Key: MJDEPS-20
> URL: https://issues.apache.org/jira/browse/MJDEPS-20
> Project: Maven JDeps Plugin
> Issue Type: Bug
>Affects Versions: 3.1.2
>Reporter: Andre Tadeu de Carvalho
>Priority: Major
>
> In the attempt to solve https://issues.apache.org/jira/browse/MJDEPS-16, I
> discover that the plugin is not settings *--module-path* when the code is
> modularized. It also need to set the target to
> _target/classes/module-info.class_ instead _target/classes_.
> As an example in [https://github.com/andretadeu/maven-jdeps-plugin.git,]
> branch MJDEPS-16, running the test *MJDEPS-16_jdkinternals*:
> {code}
> jdeps --module-path repo>/com/google/inject/guice/4.2.0/guice-4.2.0.jar: repo>/javax/inject/javax.inject/1/javax.inject-1.jar: repo>/aopalliance/aopalliance/1.0/aopalliance-1.0.jar: repo>/com/google/guava/guava/25.1-jre/guava-25.1-jre.jar: repo>/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar: repo>/org/checkerframework/checker-qual/2.0.0/checker-qual-2.0.0.jar: repo>/com/google/errorprone/error_prone_annotations/2.1.3/error_prone_annotations-2.1.3.jar:
> repo>/com/google/j2objc/j2objc-annotations/1.1/j2objc-annotations-1.1.jar:
> repo>/org/codehaus/mojo/animal-sniffer-annotations/1.14/animal-sniffer-annotations-1.14.jar
> -jdkinternals root>/target/it/MJDEPS-16_jdkinternals/target/classes/module-info.class
> {code}
> should return:
> {code:java}
> com.google.common automatic
> [file:///home/andre/workspaces/oss/maven-jdeps-plugin/target/local-repo/com/google/guava/guava/25.1-jre/guava-25.1-jre.jar]
> requires mandated java.base
> com.google.common -> jdk.unsupported
> com.google.common.cache.Striped64 -> sun.misc.Unsafe JDK internal API
> (jdk.unsupported)
> com.google.common.cache.Striped64$1 -> sun.misc.Unsafe JDK internal API
> (jdk.unsupported)
> com.google.common.cache.Striped64$Cell -> sun.misc.Unsafe JDK internal API
> (jdk.unsupported)
> com.google.common.hash.LittleEndianByteArray$UnsafeByteArray ->
> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> com.google.common.hash.LittleEndianByteArray$UnsafeByteArray$1 ->
> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> com.google.common.hash.LittleEndianByteArray$UnsafeByteArray$2 ->
> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> com.google.common.hash.LittleEndianByteArray$UnsafeByteArray$3 ->
> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> com.google.common.hash.Striped64 -> sun.misc.Unsafe JDK internal API
> (jdk.unsupported)
> com.google.common.hash.Striped64$1 -> sun.misc.Unsafe JDK internal API
> (jdk.unsupported)
> com.google.common.hash.Striped64$Cell -> sun.misc.Unsafe JDK internal API
> (jdk.unsupported)
> com.google.common.primitives.UnsignedBytes$LexicographicalComparatorHolder$UnsafeComparator
> -> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> com.google.common.primitives.UnsignedBytes$LexicographicalComparatorHolder$UnsafeComparator$1
> -> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper ->
> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper$1 ->
> sun.misc.Unsafe JDK internal API (jdk.unsupported)
> Warning: JDK internal APIs are unsupported and private to JDK implementation
> that are
> subject to be removed or changed incompatibly and could break your
> application.
> Please modify your code to eliminate dependence on any JDK internal APIs.
> For the most recent update on JDK internal API replacements, please check:
> https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
> JDK Internal API Suggested Replacement
> -
> sun.misc.Unsafe See http://openjdk.java.net/jeps/260
> {code}
> If the code is not modularized, it should keep using *-cp* instead of
> *--module-path* and it will point to _target/classes**_. If jdeps command is
> using *--module-path*, it should point to *module-info.class*, or the command
> won't return a single line.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MJDEPS-25) jdeps commandline parameters are not correctly constructed
Kai Hofmann created MJDEPS-25: - Summary: jdeps commandline parameters are not correctly constructed Key: MJDEPS-25 URL: https://issues.apache.org/jira/browse/MJDEPS-25 Project: Maven JDeps Plugin Issue Type: Bug Affects Versions: 3.1.2 Environment: MacOS 10.13, maven 3.6.3 Reporter: Kai Hofmann In my pom.xml I used the following plugin configuration: org.apache.maven.plugins maven-jdeps-plugin 3.1.2 de.powerstat.phplib.templateengine 11 true and calling it with mvn jdeps:jdkinternals Because I am using jdk9 modules, I always got an error message - because of MJDEPS-19/20. During this error message the jdeps commandline will be written as: [ERROR] Command line was: /bin/sh -c '/Library/Java/JavaVirtualMachines/jdk-12.0.1.jdk/Contents/Home/bin/jdeps' '-cp' '/Users/powerstat/.m2/repository/org/apache/logging/log4j/log4j-api/2.14.0/log4j-api-2.14.0.jar:/Users/powerstat/.m2/repository/org/apache/logging/log4j/log4j-core/2.14.0/log4j-core-2.14.0.jar' '/Users/powerstat/Documents/dev/TemplateEngine/target/classes' What I am missing here are two things: 1) --jdk-internals, because I called the plugin with jdeps:jdkinternals! 2) --multi-release 11, as given by my plugin configuration! So it would be nice to fix these 3 things (MJDEPS-19/20 included). For testing you could use my project on github: https://github.com/PowerStat/TemplateEngine -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MJAVADOC-673) Generating wrong commandline option for javadoc tool when using Java9+ modules
Kai Hofmann created MJAVADOC-673:
Summary: Generating wrong commandline option for javadoc tool when
using Java9+ modules
Key: MJAVADOC-673
URL: https://issues.apache.org/jira/browse/MJAVADOC-673
Project: Maven Javadoc Plugin
Issue Type: Bug
Components: javadoc
Affects Versions: 3.2.0
Environment: MacOS, Window, Linux, Java 11.0.10 +
With older java versions like 11.0.3 you will got more errors!
Reporter: Kai Hofmann
When you checkout my open source
[TemplateEnginel|https://github.com/PowerStat/TemplateEngine] and simply run
{code:java}
mvn javadoc:javadoc
{code}
you will get the following error message:
{noformat}
[INFO] <<< maven-javadoc-plugin:3.2.0:javadoc (default-cli) < generate-sources
@ templateengine <<<
[INFO]
[INFO]
[INFO] --- maven-javadoc-plugin:3.2.0:javadoc (default-cli) @ templateengine ---
[INFO] No previous run data found, generating javadoc.
[INFO]
Loading source file
D:\work\eclipse\java\github\TemplateEngine\src\main\java\module-info.java...
1 error
[ERROR] Error while creating javadoc report:
Exit code: 1 - error: module not found: de.powerstat.phplib.templateengine
Command line was: cmd.exe /X /C "D:\Programme\Java\jdk-11.0.10\bin\javadoc.exe
@options @packages @argfile"
Refer to the generated Javadoc files in
'D:\work\eclipse\java\github\TemplateEngine\target\site\apidocs' dir.
org.apache.maven.reporting.MavenReportException:
Exit code: 1 - error: module not found: de.powerstat.phplib.templateengine
Commandline was: cmd.exe /X /C "D:\Programme\Java\jdk-11.0.10\bin\javadoc.exe
@options @packages @argfile"Refer to the generated Javadoc files in
'D:\work\eclipse\java\github\TemplateEngine\target\site\apidocs' dir.
[...]{noformat}
Now go to *target/site/apidocs*
There you could run the generated script by *javadoc.bat*|*sh*
Which results in the same error!
Please note that the subdirectory *src/de.powerstat.phplib.templateengine* is
empty.
Now open the *options* file
and remove the following lines:
{code:java}
--module-source-path
'D:/work/eclipse/java/github/TemplateEngine/target/site/apidocs/src'
{code}
Run the *javadoc.bat*|*sh* again.
Now the error
{noformat}
error: module not found: de.powerstat.phplib.templateengine{noformat}
is gone. And the javadocs are generated as expected!
So for me it looks like the generated --module-source-path option for the
javadoc command is wrong in this (and maybe other) context(s)!
The generation happens in org.apache.maven.plugins.javadoc.AbstractJavadocMojo
around line 5316.
Because of the complexity of this code and it's context (maven Reactor) I am
not able to provide a patch for this.
But hopefully you could fix this fast, because it is a real blocker that makes
maven javadoc generation for java 9+ modules imposible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] (MDEPLOY-150) deploy-file does not use repository in the same way as deploy
Kai Hofmann created MDEPLOY-150:
---
Summary: deploy-file does not use repository in the same
way as deploy
Key: MDEPLOY-150
URL: https://jira.codehaus.org/browse/MDEPLOY-150
Project: Maven 2.x and 3.x Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: Windows 7, Maven 2.2.1
Reporter: Kai Hofmann
Priority: Critical
We use an own lifecycle here which creates a zip file instead of a jar file.
So we use
org.apache.maven.plugins:maven-install-plugin:install,org.apache.maven.plugins:maven-install-plugin:install-file
which installs the zip file correctly.
Additionally I now wanted to also allow deploying of this zip file to nexus by:
org.apache.maven.plugins:maven-deploy-plugin:deploy,org.apache.maven.plugins:maven-deploy-plugin:deploy-file
in the pom I have then:
${project.build.directory}/${project.artifactId}-${project.version}.zip
org.apache.maven.plugins
maven-install-plugin
2.3.1
install-service-zip
install-file
org.apache.maven.plugins
maven-deploy-plugin
2.7
deploy-service-zip
deploy-file
as well as settings for the repositories within the maven settings.xml.
As said the install process works perfectly, but I have trouble with the
deploy-file.
When working without the deploy-file (only with the deploy) everything also
works correct for the deployment.
After adding the deploy-file as shown above I come into trouble, because beside
the property the deploy-plugin requests for the required parameter.
I wonder about this, because I assumed that the parameter will come from
the choosen repository (release vs snapshot) settings?
When I set the as property beside the property, then I can deploy
a snapshot.
But to deploying snapshot/release this will not work.
In deploy the url parameter is implicitly correctly choosen, why not in
deploy-file? this would make the url parameter optional.
So I see this as a bug/feature, because when deploy works in this way, then
deploy-file should work analogous. Or have I missed something here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DOXIA-744) Null Pointer Exception
Kai Hofmann created DOXIA-744: - Summary: Null Pointer Exception Key: DOXIA-744 URL: https://issues.apache.org/jira/browse/DOXIA-744 Project: Maven Doxia Issue Type: Bug Components: Core Affects Versions: 2.0.0 Environment: Windows 10 Reporter: Kai Hofmann While trying to run mvn site the following happens: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 01:50 min [INFO] Finished at: 2024-10-02T03:55:28+02:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on project templateengine: Failed to render site: Error generating maven-surefire-report-plugin:3.5.0:report report: Cannot invoke "Object.toString()" because "value" is null -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on project templateengine: Failed to render site at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174) at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75) at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162) at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:903) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:280) at org.apache.maven.cli.MavenCli.main (MavenCli.java:203) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:568) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render site at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:119) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174) at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75) at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162) at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (Lif
[jira] [Created] (MSITE-1017) Cannot invoke "Object.toString()" because "value" is null
Kai Hofmann created MSITE-1017: -- Summary: Cannot invoke "Object.toString()" because "value" is null Key: MSITE-1017 URL: https://issues.apache.org/jira/browse/MSITE-1017 Project: Maven Site Plugin Issue Type: Bug Components: doxia integration Affects Versions: 3.20.0 Environment: Windows 10 Reporter: Kai Hofmann [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on project templateengine: Failed to render site: Error generating maven-surefire-report-plugin:3.5.0:report report: Cannot invoke "Object.toString()" because "value" is null -> [Help 1] I have already reported this to the doxia project. See https://issues.apache.org/jira/browse/DOXIA-744 So you only need to update your dependencies on doxia as soon as a bugfix is available. For the moment I have been gone back to version 3.12.1 which works without problems. So I think this report is best placed here and not by the surefire-report-plugin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIA-745) Bug within test found
[
https://issues.apache.org/jira/browse/DOXIA-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Hofmann updated DOXIA-745:
--
Affects Version/s: 2.0.0
Description:
[WARN]
C:\Users\PowerStat\Documents\Maven\maven-doxia\doxia-core\src\test\java\org\apache\maven\doxia\parser\AbstractParserTest.java:277:40:
Der Vergleich von String-Literalen sollte mit equals() erfolgen, nicht mit
'!='. [StringLiteralEquality]
Line
if (currentEvent.getName() != "text") {
should be replaced with:
if (!"text".equals(currentEvent.getName())) {
> Bug within test found
> -
>
> Key: DOXIA-745
> URL: https://issues.apache.org/jira/browse/DOXIA-745
> Project: Maven Doxia
> Issue Type: Test
> Components: Core
>Affects Versions: 2.0.0
>Reporter: Kai Hofmann
>Priority: Major
>
> [WARN]
> C:\Users\PowerStat\Documents\Maven\maven-doxia\doxia-core\src\test\java\org\apache\maven\doxia\parser\AbstractParserTest.java:277:40:
> Der Vergleich von String-Literalen sollte mit equals() erfolgen, nicht mit
> '!='. [StringLiteralEquality]
> Line
> if (currentEvent.getName() != "text") {
> should be replaced with:
> if (!"text".equals(currentEvent.getName())) {
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (DOXIA-745) Bug within test found
Kai Hofmann created DOXIA-745: - Summary: Bug within test found Key: DOXIA-745 URL: https://issues.apache.org/jira/browse/DOXIA-745 Project: Maven Doxia Issue Type: Test Components: Core Reporter: Kai Hofmann -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIA-745) Bug within test found
[
https://issues.apache.org/jira/browse/DOXIA-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Hofmann updated DOXIA-745:
--
Language: java
> Bug within test found
> -
>
> Key: DOXIA-745
> URL: https://issues.apache.org/jira/browse/DOXIA-745
> Project: Maven Doxia
> Issue Type: Test
> Components: Core
>Affects Versions: 2.0.0
>Reporter: Kai Hofmann
>Priority: Major
>
> [WARN]
> C:\Users\PowerStat\Documents\Maven\maven-doxia\doxia-core\src\test\java\org\apache\maven\doxia\parser\AbstractParserTest.java:277:40:
> Der Vergleich von String-Literalen sollte mit equals() erfolgen, nicht mit
> '!='. [StringLiteralEquality]
> Line
> if (currentEvent.getName() != "text") {
> should be replaced with:
> if (!"text".equals(currentEvent.getName())) {
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
