[jira] [Assigned] (MPMD-405) No release notes for 3.25.0 on https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html
[ https://issues.apache.org/jira/browse/MPMD-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPMD-405: --- Assignee: (was: Michael Osipov) > No release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html > -- > > Key: MPMD-405 > URL: https://issues.apache.org/jira/browse/MPMD-405 > Project: Maven PMD Plugin > Issue Type: Bug >Reporter: Gary D. Gregory >Priority: Major > > HI All, > There are no release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPMD-405) No release notes for 3.25.0 on https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html
[ https://issues.apache.org/jira/browse/MPMD-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPMD-405: --- Assignee: Michael Osipov > No release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html > -- > > Key: MPMD-405 > URL: https://issues.apache.org/jira/browse/MPMD-405 > Project: Maven PMD Plugin > Issue Type: Bug >Reporter: Gary D. Gregory >Assignee: Michael Osipov >Priority: Major > > HI All, > There are no release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-405) No release notes for 3.25.0 on https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html
[ https://issues.apache.org/jira/browse/MPMD-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884590#comment-17884590 ] Michael Osipov commented on MPMD-405: - [~adangel], do you want to keep updating this for every single release? > No release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html > -- > > Key: MPMD-405 > URL: https://issues.apache.org/jira/browse/MPMD-405 > Project: Maven PMD Plugin > Issue Type: Bug >Reporter: Gary D. Gregory >Priority: Major > > HI All, > There are no release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-406.
---
Fix Version/s: (was: waiting-for-feedback)
(was: wontfix-candidate)
Resolution: Information Provided
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> 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: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
> (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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> 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:569)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher
[jira] [Comment Edited] (MJAVADOC-814) Ability to split grouped packages over multiple lines
[
https://issues.apache.org/jira/browse/MJAVADOC-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884577#comment-17884577
]
Michael Osipov edited comment on MJAVADOC-814 at 9/25/24 11:44 AM:
---
I believe that implementing this will be incomplete because the same issue
applies to these as well:
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#docletPath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#bootclasspath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludePackageNames
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludedocfilessubdir
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#extdirs
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#sourcepath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#subpackages
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#tagletpath
was (Author: michael-o):
I believe that implementing this should be incomplete because the same issue
applies to these as well:
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#docletPath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#bootclasspath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludePackageNames
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludedocfilessubdir
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#extdirs
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#sourcepath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#subpackages
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#tagletpath
> Ability to split grouped packages over multiple lines
> -
>
> Key: MJAVADOC-814
> URL: https://issues.apache.org/jira/browse/MJAVADOC-814
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Richard Eckart de Castilho
>Priority: Major
>
> When configuring groups, the packages in the group need to be written on a
> single line separated with colons.
> {noformat}
>
>
> Core
>
> org.apache.uima.analysis_component:org.apache.uima.analysis_engine
>
>
>
> {noformat}
> If there are many packages that can not easily be captured using a prefix
> pattern, this yields a very long line.
> It would be greate if one could split the packages over multiple lines such as
> {noformat}
>
>
> Core
>
> org.apache.uima.analysis_component:
> org.apache.uima.analysis_engine
>
>
>
> {noformat}
> The code internally already calls
> {{org.apache.maven.plugins.javadoc.JavadocUtil.quotedArgument(String)}} to
> sanitze the line breaks away, but it seems the whitespace still breaks it and
> javadoc tool in the end only recognizes the first package in the multi-line
> group.
> Even nicer may be.
> {noformat}
>
>
> Core
>
> org.apache.uima.analysis_component
> org.apache.uima.analysis_engine
>
>
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-814) Ability to split grouped packages over multiple lines
[
https://issues.apache.org/jira/browse/MJAVADOC-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884577#comment-17884577
]
Michael Osipov commented on MJAVADOC-814:
-
I believe that implementing this should be incomplete because the same issue
applies to these as well:
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#docletPath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#bootclasspath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludePackageNames
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludedocfilessubdir
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#extdirs
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#sourcepath
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#subpackages
*
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#tagletpath
> Ability to split grouped packages over multiple lines
> -
>
> Key: MJAVADOC-814
> URL: https://issues.apache.org/jira/browse/MJAVADOC-814
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Richard Eckart de Castilho
>Priority: Major
>
> When configuring groups, the packages in the group need to be written on a
> single line separated with colons.
> {noformat}
>
>
> Core
>
> org.apache.uima.analysis_component:org.apache.uima.analysis_engine
>
>
>
> {noformat}
> If there are many packages that can not easily be captured using a prefix
> pattern, this yields a very long line.
> It would be greate if one could split the packages over multiple lines such as
> {noformat}
>
>
> Core
>
> org.apache.uima.analysis_component:
> org.apache.uima.analysis_engine
>
>
>
> {noformat}
> The code internally already calls
> {{org.apache.maven.plugins.javadoc.JavadocUtil.quotedArgument(String)}} to
> sanitze the line breaks away, but it seems the whitespace still breaks it and
> javadoc tool in the end only recognizes the first package in the multi-line
> group.
> Even nicer may be.
> {noformat}
>
>
> Core
>
> org.apache.uima.analysis_component
> org.apache.uima.analysis_engine
>
>
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-815) Aggregate goal misses skipped reactor modules when resuming build
[
https://issues.apache.org/jira/browse/MJAVADOC-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884569#comment-17884569
]
Michael Osipov commented on MJAVADOC-815:
-
I wonder whether this is a plugin issue or rather a Maven Core issue.
[~gnodet], [~mthmulders], [~cstamas], WDYT?
> Aggregate goal misses skipped reactor modules when resuming build
> -
>
> Key: MJAVADOC-815
> URL: https://issues.apache.org/jira/browse/MJAVADOC-815
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Richard Eckart de Castilho
>Priority: Major
>
> When resuming a build using {{-rf}}, then the {{javadoc:aggregate}} goal is
> not injected with the reactor modules that are skipped (are before the module
> being resumed from).
> That means the JavaDoc for those skipped modules is not included in the
> aggregate.
> I can imagine that to happen when I build using {{-pl}} to build individual
> modules, but if I resume, I would expect all the reactor modules that have
> already been covered and are being resumed over to be part of the reactor
> modules that are provided to the javadoc plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-813) [REGRESSION] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884521#comment-17884521
]
Michael Osipov commented on MJAVADOC-813:
-
It is an outcome of MJAVADOC-785 to complete align this plugin with all other
plugins using maven-reporting-impl and this plugin cannot for technical reasons.
> [REGRESSION] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: javadoc-test.zip
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MJAVADOC-812) [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-812.
---
Resolution: Fixed
Fixed with
[cde7c56baff9d14b7ab98ced4137488048589419|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git&a=commit&h=cde7c56baff9d14b7ab98ced4137488048589419].
> [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
> ---
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.10.1
>
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-811.
---
Resolution: Fixed
Fixed with
[db6d7f6ec355dd26c7f4841ad2c63ff4df456422|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git&a=commit&h=db6d7f6ec355dd26c7f4841ad2c63ff4df456422].
> javadoc.bat fails to execute on Windows when project is not on drive C and
> AutoRun is configured
>
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
>Reporter: Sebastian T
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.10.1
>
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on
> project myproject: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read options (The system
> cannot find the file specified)
> [ERROR]
> [ERROR] Command line was: cmd.exe /X /C
> "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'F:\projects\myproject\target\apidocs' dir.
> {noformat}
> when the project is not on the system drive and
> {{HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun}} is
> configured to some directory on drive C. Then cmd.exe will not execute in the
> current directory but in the directory specified via AutoRun. This is the
> case in a corporate environment I am working in.
> The solution is trivial by adding the /D flag to cmd.exe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAVADOC-812) [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-812:
Fix Version/s: 3.10.1
> [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
> ---
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.10.1
>
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884134#comment-17884134
]
Michael Osipov commented on MJAVADOC-811:
-
[~seb], branch created, please test.
> javadoc.bat fails to execute on Windows when project is not on drive C and
> AutoRun is configured
>
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
>Reporter: Sebastian T
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.10.1
>
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on
> project myproject: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read options (The system
> cannot find the file specified)
> [ERROR]
> [ERROR] Command line was: cmd.exe /X /C
> "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'F:\projects\myproject\target\apidocs' dir.
> {noformat}
> when the project is not on the system drive and
> {{HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun}} is
> configured to some directory on drive C. Then cmd.exe will not execute in the
> current directory but in the directory specified via AutoRun. This is the
> case in a corporate environment I am working in.
> The solution is trivial by adding the /D flag to cmd.exe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-811:
Fix Version/s: 3.10.1
> javadoc.bat fails to execute on Windows when project is not on drive C and
> AutoRun is configured
>
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
>Reporter: Sebastian T
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.10.1
>
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on
> project myproject: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read options (The system
> cannot find the file specified)
> [ERROR]
> [ERROR] Command line was: cmd.exe /X /C
> "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'F:\projects\myproject\target\apidocs' dir.
> {noformat}
> when the project is not on the system drive and
> {{HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun}} is
> configured to some directory on drive C. Then cmd.exe will not execute in the
> current directory but in the directory specified via AutoRun. This is the
> case in a corporate environment I am working in.
> The solution is trivial by adding the /D flag to cmd.exe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884007#comment-17884007
]
Michael Osipov commented on MJAVADOC-811:
-
Can't release anything for Codehaus Plexus, need someone else to push the new
release.
> javadoc.bat fails to execute on Windows when project is not on drive C and
> AutoRun is configured
>
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
>Reporter: Sebastian T
>Assignee: Michael Osipov
>Priority: Major
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on
> project myproject: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read options (The system
> cannot find the file specified)
> [ERROR]
> [ERROR] Command line was: cmd.exe /X /C
> "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'F:\projects\myproject\target\apidocs' dir.
> {noformat}
> when the project is not on the system drive and
> {{HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun}} is
> configured to some directory on drive C. Then cmd.exe will not execute in the
> current directory but in the directory specified via AutoRun. This is the
> case in a corporate environment I am working in.
> The solution is trivial by adding the /D flag to cmd.exe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MGPG-137) Un-deprecate passphraseServerId
[ https://issues.apache.org/jira/browse/MGPG-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883977#comment-17883977 ] Michael Osipov commented on MGPG-137: - [~cstamas], we should deprecate Plexus Cipher or reduce the amount of feature in the midrun. > Un-deprecate passphraseServerId > --- > > Key: MGPG-137 > URL: https://issues.apache.org/jira/browse/MGPG-137 > Project: Maven GPG Plugin > Issue Type: Bug >Affects Versions: 3.2.5 >Reporter: Lenny Primak >Priority: Major > > IMHO this parameter has been deprecated in error. > It is used to referenced the "server" field in settings.xml, where > passphrases are stored in an encrypted fashion. This is actually safer than > setting clear-text passwords in environment variables in practice. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAVADOC-813) [REGRESSION] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-813:
Summary: [REGRESSION] The given File link: X is not a dir (was:
[regression] The given File link: X is not a dir)
> [REGRESSION] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: javadoc-test.zip
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-813) [regression] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883913#comment-17883913
]
Michael Osipov edited comment on MJAVADOC-813 at 9/23/24 3:21 PM:
--
Well, the actual reproducer creates a chicken-and-egg problem. You cannot link
to something which is not there, but if it is not there you cannot generate it.
Here it makes on sense to do, but if you are using the wrong directory. Fix:
{noformat}
$ diff pom.xml.orig pom.xml --ignore-all-space
--- pom.xml.orig2024-09-23 17:12:31.497543000 +0200
+++ pom.xml 2024-09-23 17:16:13.386163000 +0200
@@ -35,7 +35,7 @@
https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
-
${project.basedir}/target/apidocs/
+
${project.build.directory}/reports/apidocs/
{noformat}
You haven't paid attention to the announcement:
https://www.mail-archive.com/announce@maven.apache.org/msg01478.html
MJAVADOC-560 which in turn is also
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235836144#TowardsDoxia2.0.0Stack-MavenReportingImpl4.0.0
was (Author: michael-o):
Well, the actual reproducer creates a chicken-and-egg problem. You cannot link
to something which is not there, but if it is not there you cannot generate it.
Here it makes on sense to do, but if you are using the wrong directory. Fix:
{code:patch}
$ diff pom.xml.orig pom.xml --ignore-all-space
--- pom.xml.orig2024-09-23 17:12:31.497543000 +0200
+++ pom.xml 2024-09-23 17:16:13.386163000 +0200
@@ -35,7 +35,7 @@
https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
-
${project.basedir}/target/apidocs/
+
${project.build.directory}/reports/apidocs/
{code}
You haven't paid attention to the announcement:
https://www.mail-archive.com/announce@maven.apache.org/msg01478.html
MJAVADOC-560 which in turn is also
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235836144#TowardsDoxia2.0.0Stack-MavenReportingImpl4.0.0
> [regression] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: javadoc-test.zip
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MJAVADOC-813) [regression] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-813.
---
Fix Version/s: (was: waiting-for-feedback)
(was: wontfix-candidate)
Resolution: Information Provided
Well, the actual reproducer creates a chicken-and-egg problem. You cannot link
to something which is not there, but if it is not there you cannot generate it.
Here it makes on sense to do, but if you are using the wrong directory. Fix:
{code:patch}
$ diff pom.xml.orig pom.xml --ignore-all-space
--- pom.xml.orig2024-09-23 17:12:31.497543000 +0200
+++ pom.xml 2024-09-23 17:16:13.386163000 +0200
@@ -35,7 +35,7 @@
https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
-
${project.basedir}/target/apidocs/
+
${project.build.directory}/reports/apidocs/
{code}
You haven't paid attention to the announcement:
https://www.mail-archive.com/announce@maven.apache.org/msg01478.html
MJAVADOC-560 which in turn is also
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235836144#TowardsDoxia2.0.0Stack-MavenReportingImpl4.0.0
> [regression] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Assignee: Michael Osipov
>Priority: Major
> Attachments: javadoc-test.zip
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-405) No release notes for 3.25.0 on https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html
[ https://issues.apache.org/jira/browse/MPMD-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883856#comment-17883856 ] Michael Osipov commented on MPMD-405: - I agree with you Gary. Either provide correct information or no information at all. > No release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html > -- > > Key: MPMD-405 > URL: https://issues.apache.org/jira/browse/MPMD-405 > Project: Maven PMD Plugin > Issue Type: Bug >Reporter: Gary D. Gregory >Priority: Major > > HI All, > There are no release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-405) No release notes for 3.25.0 on https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html
[ https://issues.apache.org/jira/browse/MPMD-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883836#comment-17883836 ] Michael Osipov commented on MPMD-405: - [~ggregory], I agree with you, but that decision should be taken for the entire Maven TLP to make it consistent. In this specific case I'd simply delete it. Done. > No release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html > -- > > Key: MPMD-405 > URL: https://issues.apache.org/jira/browse/MPMD-405 > Project: Maven PMD Plugin > Issue Type: Bug >Reporter: Gary D. Gregory >Priority: Major > > HI All, > There are no release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883802#comment-17883802
]
Michael Osipov commented on MJAVADOC-811:
-
I will take care of the PU PR and same for Maven Shared Utils.
> javadoc.bat fails to execute on Windows when project is not on drive C and
> AutoRun is configured
>
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
>Reporter: Sebastian T
>Assignee: Michael Osipov
>Priority: Major
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on
> project myproject: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read options (The system
> cannot find the file specified)
> [ERROR]
> [ERROR] Command line was: cmd.exe /X /C
> "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'F:\projects\myproject\target\apidocs' dir.
> {noformat}
> when the project is not on the system drive and
> {{HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun}} is
> configured to some directory on drive C. Then cmd.exe will not execute in the
> current directory but in the directory specified via AutoRun. This is the
> case in a corporate environment I am working in.
> The solution is trivial by adding the /D flag to cmd.exe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MJAVADOC-811:
---
Assignee: Michael Osipov
> javadoc.bat fails to execute on Windows when project is not on drive C and
> AutoRun is configured
>
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
>Reporter: Sebastian T
>Assignee: Michael Osipov
>Priority: Major
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on
> project myproject: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read options (The system
> cannot find the file specified)
> [ERROR]
> [ERROR] Command line was: cmd.exe /X /C
> "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'F:\projects\myproject\target\apidocs' dir.
> {noformat}
> when the project is not on the system drive and
> {{HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun}} is
> configured to some directory on drive C. Then cmd.exe will not execute in the
> current directory but in the directory specified via AutoRun. This is the
> case in a corporate environment I am working in.
> The solution is trivial by adding the /D flag to cmd.exe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPMD-406:
---
Assignee: Michael Osipov
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> 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: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
> (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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> 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:569)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.ple
[jira] [Comment Edited] (MJAVADOC-813) [regression] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883764#comment-17883764
]
Michael Osipov edited comment on MJAVADOC-813 at 9/23/24 9:21 AM:
--
Please provide the full command line. That is very likely expected.
If necessary, also a reproducer.
was (Author: michael-o):
Please provide the full command line. That is very likely expected.
> [regression] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MJAVADOC-813) [regression] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MJAVADOC-813:
---
Assignee: Michael Osipov
> [regression] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Assignee: Michael Osipov
>Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1015) Get rid of Wagon dependency
[ https://issues.apache.org/jira/browse/MSITE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883774#comment-17883774 ] Michael Osipov commented on MSITE-1015: --- You cannot make this assumption about 4. You do not know, nor do I know. I will not make such an assumption. At the moment, nothing is broken with Wagon, it just works. > Get rid of Wagon dependency > --- > > Key: MSITE-1015 > URL: https://issues.apache.org/jira/browse/MSITE-1015 > Project: Maven Site Plugin > Issue Type: Improvement > Components: site:deploy >Reporter: Konrad Windszus >Priority: Major > > As Maven Wagon is lacking maintenance and most of the sites leverage > https://maven.apache.org/plugins/maven-scm-publish-plugin/ nowadays to deploy > a site we should get rid of the Wagon dependency and support certain > transport protocols directly: > # GitHub Pages via > https://docs.github.com/en/rest/pages/pages?apiVersion=2022-11-28#create-a-github-pages-deployment, > the [ReST API for uploading the artifact is not > documented|https://github.com/actions/upload-artifact/issues/180] > # SCMs via https://maven.apache.org/scm/ > # SFTP via https://github.com/apache/mina-sshd/blob/master/docs/sftp.md > This would allow to get rid of one abstraction layer, improve error reporting > and finally deprecate > https://maven.apache.org/plugins/maven-scm-publish-plugin/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2270) Use JUnit5 in surefire-shadefire
[ https://issues.apache.org/jira/browse/SUREFIRE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883769#comment-17883769 ] Michael Osipov commented on SUREFIRE-2270: -- Can we already make that jump? Not JUnit 4? Is this purely Surefire-internal? I do not know > Use JUnit5 in surefire-shadefire > > > Key: SUREFIRE-2270 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2270 > Project: Maven Surefire > Issue Type: Improvement > Components: surefire-shadefire >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.5.1 > > > surefire-shadefire is used internaly for testing surefire > Currently surefire-shadefire use JUnit 3 so we need a use it for testing > or make a special case like JUnit4TestAdapter for JUNit 3 suite > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-1015) Get rid of Wagon dependency
[ https://issues.apache.org/jira/browse/MSITE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883768#comment-17883768 ] Michael Osipov commented on MSITE-1015: --- the description you provide only applies to the projects at ASF, you cannot use it for other projects, especially private ones. Please still need through SCM, SFTP, WebDAV and file. > Get rid of Wagon dependency > --- > > Key: MSITE-1015 > URL: https://issues.apache.org/jira/browse/MSITE-1015 > Project: Maven Site Plugin > Issue Type: Improvement > Components: site:deploy >Reporter: Konrad Windszus >Priority: Major > > As Maven Wagon is lacking maintenance and most of the sites leverage > https://maven.apache.org/plugins/maven-scm-publish-plugin/ nowadays to deploy > a site we should get rid of the Wagon dependency and support certain > transport protocols directly: > # GitHub Pages via > https://docs.github.com/en/rest/pages/pages?apiVersion=2022-11-28#create-a-github-pages-deployment, > the [ReST API for uploading the artifact is not > documented|https://github.com/actions/upload-artifact/issues/180] > # SCMs via https://maven.apache.org/scm/ > # SFTP via https://github.com/apache/mina-sshd/blob/master/docs/sftp.md > This would allow to get rid of one abstraction layer, improve error reporting > and finally deprecate > https://maven.apache.org/plugins/maven-scm-publish-plugin/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883767#comment-17883767
]
Michael Osipov commented on MPMD-406:
-
[~ggregory], as advised either upgrade Maven Site Plugin or downgrade this
plugin for the time being.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> 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: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
> (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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> 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:569)
> at org.codehaus.plexus.classw
[jira] [Comment Edited] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883457#comment-17883457
]
Michael Osipov edited comment on MPMD-406 at 9/23/24 8:09 AM:
--
You need stay with a new version on m-site-p 3.20.0 as pmd 3.25.0 use Doxia 2.x
was (Author: slawekjaranowski):
You need tray with a new version on m-site-p 3.20.0 as pmd 3.25.0 use Doxia 2.x
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> 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: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
> (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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.inv
[jira] [Updated] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPMD-406:
Fix Version/s: waiting-for-feedback
wontfix-candidate
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> 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: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
> (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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> 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:569)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.
[jira] [Commented] (MPMD-405) No release notes for 3.25.0 on https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html
[ https://issues.apache.org/jira/browse/MPMD-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883766#comment-17883766 ] Michael Osipov commented on MPMD-405: - [~adangel], I'd prefer to drop these notes altogether because the official release notes are on mailing lists. We will keep playing this game with every single release. > No release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html > -- > > Key: MPMD-405 > URL: https://issues.apache.org/jira/browse/MPMD-405 > Project: Maven PMD Plugin > Issue Type: Bug >Reporter: Gary D. Gregory >Priority: Major > > HI All, > There are no release notes for 3.25.0 on > https://maven.apache.org/plugins/maven-pmd-plugin/releasenotes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-813) [regression] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883764#comment-17883764
]
Michael Osipov edited comment on MJAVADOC-813 at 9/23/24 8:07 AM:
--
Please provide the full command line. That is very likely expected.
was (Author: michael-o):
Please provide the full command line.
> [regression] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAVADOC-813) [regression] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-813:
Fix Version/s: wontfix-candidate
waiting-for-feedback
> [regression] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-813) [regression] The given File link: X is not a dir
[
https://issues.apache.org/jira/browse/MJAVADOC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883764#comment-17883764
]
Michael Osipov commented on MJAVADOC-813:
-
Please provide the full command line.
> [regression] The given File link: X is not a dir
>
>
> Key: MJAVADOC-813
> URL: https://issues.apache.org/jira/browse/MJAVADOC-813
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.10.0
>Reporter: Gili
>Priority: Major
>
> Given:
> {noformat}
>
>
>
> https://cowwoc.github.io/requirements.java/${project.version}/docs/api/
> ${rootBaseDir}/java/target/apidocs/
>
> {noformat}
>
>
> Running the "attach-javadocs" goal works fine in version 3.8.0 but if I
> update to version 3.10.0 the execution fails with:
>
>
> {noformat}
> [ERROR] The given File link:
> C:\Users\Gili\Documents\requirements.java\guava\..\java\target\apidocs is not
> a dir.
> [ERROR] Error fetching link:
> C:\Users\Gili\Documents\requirements.java\guava/../java/target/apidocs/.
> Ignored it. {noformat}
>
> Under version 3.8.0 the target/apidocs directory is created and the javadoc
> is generated. Under version 3.10.0 the error is thrown and the apidocs
> directory is never created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-812) [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883524#comment-17883524
]
Michael Osipov commented on MJAVADOC-812:
-
[~zirakrezovic], PR created. Please verify.
> [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
> ---
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Assignee: Michael Osipov
>Priority: Major
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAVADOC-812) [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-812:
Summary: [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs (was:
REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs)
> [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
> ---
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Assignee: Michael Osipov
>Priority: Major
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883263#comment-17883263
]
Michael Osipov edited comment on MJAVADOC-812 at 9/20/24 1:17 PM:
--
I have identified the offending commit, but don't yet understand the cause.
Please revert to 3.8.0 until I understand the actual issue here. I am very
suprised that no unit or integration test has failed here...weird.
Thanks for the report.
was (Author: michael-o):
I have identified the offending commit, but don't yet understand the cause.
Please revert to 3.8.0 until I understand the actual issue here.
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Assignee: Michael Osipov
>Priority: Major
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883263#comment-17883263
]
Michael Osipov commented on MJAVADOC-812:
-
I have identified the offending commit, but don't yet understand the cause.
Please revert to 3.8.0 until I understand the actual issue here.
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Assignee: Michael Osipov
>Priority: Major
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MJAVADOC-812:
---
Assignee: Michael Osipov
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Assignee: Michael Osipov
>Priority: Major
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-812:
Fix Version/s: (was: waiting-for-feedback)
(was: wontfix-candidate)
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Priority: Major
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883245#comment-17883245
]
Michael Osipov commented on MJAVADOC-812:
-
I see the difference now, but I happen dropped the repackager because it just
produces noise. Hang on...
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[ https://issues.apache.org/jira/browse/MJAVADOC-812 ]
Michael Osipov deleted comment on MJAVADOC-812:
-
was (Author: michael-o):
Where is the Javadoc when produced with 3.8.0:
{noformat}
osipovmi@deblndw011x:/tmp/maven-javadoc-reproducer (main =)
$ find . -name \*.jar -exec sh -c 'echo "{}:"; tar tzf {}' \;
./javadoc-reproducer-spring/target/javadoc-reproducer-spring-0.0.1-SNAPSHOT.jar:
META-INF/
META-INF/MANIFEST.MF
com/
com/example/
com/example/demo/
META-INF/maven/
META-INF/maven/com.example/
META-INF/maven/com.example/javadoc-reproducer-spring/
application.properties
com/example/demo/DemoApplication.class
META-INF/maven/com.example/javadoc-reproducer-spring/pom.xml
META-INF/maven/com.example/javadoc-reproducer-spring/pom.properties
./javadoc/target/javadoc-0.0.1-SNAPSHOT.jar:
META-INF/
META-INF/MANIFEST.MF
META-INF/services/
META-INF/services/java.nio.file.spi.FileSystemProvider
org/
org/springframework/
org/springframework/boot/
org/springframework/boot/loader/
org/springframework/boot/loader/jar/
org/springframework/boot/loader/jar/JarEntriesStream$InputStreamSupplier.class
org/springframework/boot/loader/jar/JarEntriesStream.class
org/springframework/boot/loader/jar/ManifestInfo.class
org/springframework/boot/loader/jar/MetaInfVersionsInfo.class
org/springframework/boot/loader/jar/NestedJarFile$JarEntriesEnumeration.class
org/springframework/boot/loader/jar/NestedJarFile$JarEntryInflaterInputStream.class
org/springframework/boot/loader/jar/NestedJarFile$JarEntryInputStream.class
org/springframework/boot/loader/jar/NestedJarFile$NestedJarEntry.class
org/springframework/boot/loader/jar/NestedJarFile$RawZipDataInputStream.class
org/springframework/boot/loader/jar/NestedJarFile$ZipContentEntriesSpliterator.class
org/springframework/boot/loader/jar/NestedJarFile.class
org/springframework/boot/loader/jar/NestedJarFileResources.class
org/springframework/boot/loader/jar/SecurityInfo.class
org/springframework/boot/loader/jar/ZipInflaterInputStream.class
org/springframework/boot/loader/jarmode/
org/springframework/boot/loader/jarmode/JarMode.class
org/springframework/boot/loader/launch/
org/springframework/boot/loader/launch/Archive$Entry.class
org/springframework/boot/loader/launch/Archive.class
org/springframework/boot/loader/launch/ClassPathIndexFile.class
org/springframework/boot/loader/launch/ExecutableArchiveLauncher.class
org/springframework/boot/loader/launch/ExplodedArchive$FileArchiveEntry.class
org/springframework/boot/loader/launch/ExplodedArchive.class
org/springframework/boot/loader/launch/JarFileArchive$JarArchiveEntry.class
org/springframework/boot/loader/launch/JarFileArchive.class
org/springframework/boot/loader/launch/JarLauncher.class
org/springframework/boot/loader/launch/JarModeRunner.class
org/springframework/boot/loader/launch/LaunchedClassLoader$DefinePackageCallType.class
org/springframework/boot/loader/launch/LaunchedClassLoader.class
org/springframework/boot/loader/launch/Launcher.class
org/springframework/boot/loader/launch/PropertiesLauncher$Instantiator$Using.class
org/springframework/boot/loader/launch/PropertiesLauncher$Instantiator.class
org/springframework/boot/loader/launch/PropertiesLauncher.class
org/springframework/boot/loader/launch/SystemPropertyUtils.class
org/springframework/boot/loader/launch/WarLauncher.class
org/springframework/boot/loader/log/
org/springframework/boot/loader/log/DebugLogger$DisabledDebugLogger.class
org/springframework/boot/loader/log/DebugLogger$SystemErrDebugLogger.class
org/springframework/boot/loader/log/DebugLogger.class
org/springframework/boot/loader/net/
org/springframework/boot/loader/net/protocol/
org/springframework/boot/loader/net/protocol/Handlers.class
org/springframework/boot/loader/net/protocol/jar/
org/springframework/boot/loader/net/protocol/jar/Canonicalizer.class
org/springframework/boot/loader/net/protocol/jar/Handler.class
org/springframework/boot/loader/net/protocol/jar/JarFileUrlKey.class
org/springframework/boot/loader/net/protocol/jar/JarUrl.class
org/springframework/boot/loader/net/protocol/jar/JarUrlClassLoader$OptimizedEnumeration.class
org/springframework/boot/loader/net/protocol/jar/JarUrlClassLoader.class
org/springframework/boot/loader/net/protocol/jar/JarUrlConnection$ConnectionInputStream.class
org/springframework/boot/loader/net/protocol/jar/JarUrlConnection$EmptyUrlStreamHandler.class
org/springframework/boot/loader/net/protocol/jar/JarUrlConnection.class
org/springframework/boot/loader/net/protocol/jar/LazyDelegatingInputStream.class
org/springframework/boot/loader/net/protocol/jar/Optimizations.class
org/springframework/boot/loader/net/protocol/jar/UrlJarEntry.class
org/springframework/boot/loader/net/protocol/jar/UrlJarFile.class
org/springframework/boot/loader/net/protocol/jar/UrlJarFileFactory.class
org/springframework/boot/loader/net/protocol/jar/UrlJarFiles$Cache.class
org/springframework/boot/loader/net/protocol/jar/UrlJarFiles.class
org/springf
[jira] [Comment Edited] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883232#comment-17883232
]
Michael Osipov edited comment on MJAVADOC-812 at 9/20/24 12:11 PM:
---
Where is the Javadoc when produced with 3.8.0:
{noformat}
osipovmi@deblndw011x:/tmp/maven-javadoc-reproducer (main =)
$ find . -name \*.jar -exec sh -c 'echo "{}:"; tar tzf {}' \;
./javadoc-reproducer-spring/target/javadoc-reproducer-spring-0.0.1-SNAPSHOT.jar:
META-INF/
META-INF/MANIFEST.MF
com/
com/example/
com/example/demo/
META-INF/maven/
META-INF/maven/com.example/
META-INF/maven/com.example/javadoc-reproducer-spring/
application.properties
com/example/demo/DemoApplication.class
META-INF/maven/com.example/javadoc-reproducer-spring/pom.xml
META-INF/maven/com.example/javadoc-reproducer-spring/pom.properties
./javadoc/target/javadoc-0.0.1-SNAPSHOT.jar:
META-INF/
META-INF/MANIFEST.MF
META-INF/services/
META-INF/services/java.nio.file.spi.FileSystemProvider
org/
org/springframework/
org/springframework/boot/
org/springframework/boot/loader/
org/springframework/boot/loader/jar/
org/springframework/boot/loader/jar/JarEntriesStream$InputStreamSupplier.class
org/springframework/boot/loader/jar/JarEntriesStream.class
org/springframework/boot/loader/jar/ManifestInfo.class
org/springframework/boot/loader/jar/MetaInfVersionsInfo.class
org/springframework/boot/loader/jar/NestedJarFile$JarEntriesEnumeration.class
org/springframework/boot/loader/jar/NestedJarFile$JarEntryInflaterInputStream.class
org/springframework/boot/loader/jar/NestedJarFile$JarEntryInputStream.class
org/springframework/boot/loader/jar/NestedJarFile$NestedJarEntry.class
org/springframework/boot/loader/jar/NestedJarFile$RawZipDataInputStream.class
org/springframework/boot/loader/jar/NestedJarFile$ZipContentEntriesSpliterator.class
org/springframework/boot/loader/jar/NestedJarFile.class
org/springframework/boot/loader/jar/NestedJarFileResources.class
org/springframework/boot/loader/jar/SecurityInfo.class
org/springframework/boot/loader/jar/ZipInflaterInputStream.class
org/springframework/boot/loader/jarmode/
org/springframework/boot/loader/jarmode/JarMode.class
org/springframework/boot/loader/launch/
org/springframework/boot/loader/launch/Archive$Entry.class
org/springframework/boot/loader/launch/Archive.class
org/springframework/boot/loader/launch/ClassPathIndexFile.class
org/springframework/boot/loader/launch/ExecutableArchiveLauncher.class
org/springframework/boot/loader/launch/ExplodedArchive$FileArchiveEntry.class
org/springframework/boot/loader/launch/ExplodedArchive.class
org/springframework/boot/loader/launch/JarFileArchive$JarArchiveEntry.class
org/springframework/boot/loader/launch/JarFileArchive.class
org/springframework/boot/loader/launch/JarLauncher.class
org/springframework/boot/loader/launch/JarModeRunner.class
org/springframework/boot/loader/launch/LaunchedClassLoader$DefinePackageCallType.class
org/springframework/boot/loader/launch/LaunchedClassLoader.class
org/springframework/boot/loader/launch/Launcher.class
org/springframework/boot/loader/launch/PropertiesLauncher$Instantiator$Using.class
org/springframework/boot/loader/launch/PropertiesLauncher$Instantiator.class
org/springframework/boot/loader/launch/PropertiesLauncher.class
org/springframework/boot/loader/launch/SystemPropertyUtils.class
org/springframework/boot/loader/launch/WarLauncher.class
org/springframework/boot/loader/log/
org/springframework/boot/loader/log/DebugLogger$DisabledDebugLogger.class
org/springframework/boot/loader/log/DebugLogger$SystemErrDebugLogger.class
org/springframework/boot/loader/log/DebugLogger.class
org/springframework/boot/loader/net/
org/springframework/boot/loader/net/protocol/
org/springframework/boot/loader/net/protocol/Handlers.class
org/springframework/boot/loader/net/protocol/jar/
org/springframework/boot/loader/net/protocol/jar/Canonicalizer.class
org/springframework/boot/loader/net/protocol/jar/Handler.class
org/springframework/boot/loader/net/protocol/jar/JarFileUrlKey.class
org/springframework/boot/loader/net/protocol/jar/JarUrl.class
org/springframework/boot/loader/net/protocol/jar/JarUrlClassLoader$OptimizedEnumeration.class
org/springframework/boot/loader/net/protocol/jar/JarUrlClassLoader.class
org/springframework/boot/loader/net/protocol/jar/JarUrlConnection$ConnectionInputStream.class
org/springframework/boot/loader/net/protocol/jar/JarUrlConnection$EmptyUrlStreamHandler.class
org/springframework/boot/loader/net/protocol/jar/JarUrlConnection.class
org/springframework/boot/loader/net/protocol/jar/LazyDelegatingInputStream.class
org/springframework/boot/loader/net/protocol/jar/Optimizations.class
org/springframework/boot/loader/net/protocol/jar/UrlJarEntry.class
org/springframework/boot/loader/net/protocol/jar/UrlJarFile.class
org/springframework/boot/loader/net/protocol/jar/UrlJarFileFactory.class
org/springframework/boot
[jira] [Commented] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883232#comment-17883232
]
Michael Osipov commented on MJAVADOC-812:
-
Where is the Javadoc when produced with 3.8.0:
{noformat}
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
> Attachments: maven-javadoc-invocation.log
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-812:
Fix Version/s: wontfix-candidate
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-812:
Fix Version/s: waiting-for-feedback
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-812) REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
[
https://issues.apache.org/jira/browse/MJAVADOC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883186#comment-17883186
]
Michael Osipov commented on MJAVADOC-812:
-
Provide full verbose output.
> REGRESSION: maven-javadoc-plugin 3.10.0 creates empty JARs
> --
>
> Key: MJAVADOC-812
> URL: https://issues.apache.org/jira/browse/MJAVADOC-812
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.10.0
>Reporter: Armin Krezovic
>Priority: Major
>
> After updating to maven-javadoc-plugin 3.10.0, I am getting empty javadoc
> jars created.
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d.jar
> [INFO]
> [INFO] --- javadoc:3.10.0:jar (attach-javadocs) @ configuration ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192051.4892c3d-javadoc.jar
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ configuration ---
> [INFO] No sources in project. Archive not created.{code}
>
> Prior version, 3.8.0, had no such problem
> {code:java}
> [INFO] --- jar:3.4.2:jar (default-jar) @ configuration ---
> [INFO] Building jar:
> C:\path\to\configuration\target\configuration-10.1.0-SNAPSHOT-2409192102.595f143.jar
> [INFO]
> [INFO] --- javadoc:3.8.0:jar (attach-javadocs) @ configuration ---
> [INFO]
> [INFO] >>> source:3.3.1:jar (attach-sources) > generate-sources @
> configuration >>>{code}
>
> Plugin configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.10.0
>
>all,-missing
>
>
>
> attach-javadocs
>
> jar
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DOXIA-743) Markdown parsing broken
[ https://issues.apache.org/jira/browse/DOXIA-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-743. Resolution: Duplicate Closing as duplicate. > Markdown parsing broken > --- > > Key: DOXIA-743 > URL: https://issues.apache.org/jira/browse/DOXIA-743 > Project: Maven Doxia > Issue Type: Improvement >Reporter: Christoph Läubrich >Priority: Major > > I today noticed that some (but not all) markdown files only create an empty > file, but the build itself does not fails and I can't spot any obvious > issue/warning: > https://github.com/eclipse-tycho/tycho/issues/4288 > Build logs: > https://github.com/eclipse-tycho/tycho/actions/runs/10922980068/job/30318518041 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882751#comment-17882751
]
Michael Osipov commented on MJAVADOC-811:
-
[~sjaranowski], I have this Plexus crap running a wrapping around processes.
> javadoc.bat fails to execute on Windows when project is not on drive C and
> AutoRun is configured
>
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
>Reporter: Sebastian T
>Priority: Major
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on
> project myproject: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read options (The system
> cannot find the file specified)
> [ERROR]
> [ERROR] Command line was: cmd.exe /X /C
> "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'F:\projects\myproject\target\apidocs' dir.
> {noformat}
> when the project is not on the system drive and {{HKEY_CURRENT_USER \
> Software \ Microsoft \ Command Processor \ AutoRun}} is configured to some
> directory on drive C. Then cmd.exe will not execute in the current directory
> but in the directory specified via AutoRun. This is the case in a corporate
> environment I am working in.
> The solution is trivial by adding the /D flag to cmd.exe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DOXIA-740) Rendering Markdown silently truncates files that skip a heading level
[
https://issues.apache.org/jira/browse/DOXIA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882372#comment-17882372
]
Michael Osipov commented on DOXIA-740:
--
Great, can you work on a patch since you know that spot best?
> Rendering Markdown silently truncates files that skip a heading level
> -
>
> Key: DOXIA-740
> URL: https://issues.apache.org/jira/browse/DOXIA-740
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Reporter: John Dimeo
>Priority: Major
>
> I am using a fork of the latest Doxia site tools because I am testing my
> performance fix, so it's possible this is related to my fork, but I don't
> _think_ so...
> If your Markdown skips a heading level i.e.
> {noformat}
> # Heading 1
> Text
> ### Heading 3
> Text 2{noformat}
> Then the rendered HTML only contains Heading 1 and Text. This is a major
> regression compared to past versions, so I must be missing something. Thank
> you.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DOXIA-740) Rendering Markdown silently truncates files that skip a heading level
[
https://issues.apache.org/jira/browse/DOXIA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882345#comment-17882345
]
Michael Osipov commented on DOXIA-740:
--
So looking at the discussion the PR, shall we keep as is?
> Rendering Markdown silently truncates files that skip a heading level
> -
>
> Key: DOXIA-740
> URL: https://issues.apache.org/jira/browse/DOXIA-740
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Reporter: John Dimeo
>Priority: Major
>
> I am using a fork of the latest Doxia site tools because I am testing my
> performance fix, so it's possible this is related to my fork, but I don't
> _think_ so...
> If your Markdown skips a heading level i.e.
> {noformat}
> # Heading 1
> Text
> ### Heading 3
> Text 2{noformat}
> Then the rendered HTML only contains Heading 1 and Text. This is a major
> regression compared to past versions, so I must be missing something. Thank
> you.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DOXIA-740) Rendering Markdown silently truncates files that skip a heading level
[
https://issues.apache.org/jira/browse/DOXIA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIA-740:
-
Fix Version/s: (was: wontfix-candidate)
> Rendering Markdown silently truncates files that skip a heading level
> -
>
> Key: DOXIA-740
> URL: https://issues.apache.org/jira/browse/DOXIA-740
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Reporter: John Dimeo
>Priority: Major
>
> I am using a fork of the latest Doxia site tools because I am testing my
> performance fix, so it's possible this is related to my fork, but I don't
> _think_ so...
> If your Markdown skips a heading level i.e.
> {noformat}
> # Heading 1
> Text
> ### Heading 3
> Text 2{noformat}
> Then the rendered HTML only contains Heading 1 and Text. This is a major
> regression compared to past versions, so I must be missing something. Thank
> you.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DOXIA-740) Rendering Markdown silently truncates files that skip a heading level
[
https://issues.apache.org/jira/browse/DOXIA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882265#comment-17882265
]
Michael Osipov commented on DOXIA-740:
--
[~kwin], do you think you can improve that by a warning?
> Rendering Markdown silently truncates files that skip a heading level
> -
>
> Key: DOXIA-740
> URL: https://issues.apache.org/jira/browse/DOXIA-740
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Reporter: John Dimeo
>Priority: Major
> Fix For: wontfix-candidate
>
>
> I am using a fork of the latest Doxia site tools because I am testing my
> performance fix, so it's possible this is related to my fork, but I don't
> _think_ so...
> If your Markdown skips a heading level i.e.
> {noformat}
> # Heading 1
> Text
> ### Heading 3
> Text 2{noformat}
> Then the rendered HTML only contains Heading 1 and Text. This is a major
> regression compared to past versions, so I must be missing something. Thank
> you.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSKINS-252) Upgrade to Parent 43
[ https://issues.apache.org/jira/browse/MSKINS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSKINS-252. - Resolution: Fixed Fixed with [2457e26fdbe700c3fc9aabbb25dc6ef044e9e0ba|https://gitbox.apache.org/repos/asf?p=maven-fluido-skin.git;a=commit;h=2457e26fdbe700c3fc9aabbb25dc6ef044e9e0ba]. > Upgrade to Parent 43 > > > Key: MSKINS-252 > URL: https://issues.apache.org/jira/browse/MSKINS-252 > Project: Maven Skins > Issue Type: Dependency upgrade > Components: Fluido Skin >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSKINS-252) Upgrade to Parent 43
Michael Osipov created MSKINS-252: - Summary: Upgrade to Parent 43 Key: MSKINS-252 URL: https://issues.apache.org/jira/browse/MSKINS-252 Project: Maven Skins Issue Type: Dependency upgrade Components: Fluido Skin Reporter: Michael Osipov Assignee: Michael Osipov Fix For: fluido-2.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRELEASE-1156) The release plugin should "pass on" batch mode
[
https://issues.apache.org/jira/browse/MRELEASE-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880968#comment-17880968
]
Michael Osipov commented on MRELEASE-1156:
--
There was a similar issue in the past and it caused problems. I think [~kwin]
reported it.
> The release plugin should "pass on" batch mode
> --
>
> Key: MRELEASE-1156
> URL: https://issues.apache.org/jira/browse/MRELEASE-1156
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: perform, prepare
>Reporter: Tamas Cservenak
>Priority: Major
>
> If {{mvn release:prepare}} was invoked in batch mode, the passed on
> invocation of the project (in prepare and release steps) should have the
> batch mode passed on.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHARED-1153) FilteringUtils makes incorrect assumption about filesystem
[
https://issues.apache.org/jira/browse/MSHARED-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880638#comment-17880638
]
Michael Osipov commented on MSHARED-1153:
-
You wrote here:
https://issues.apache.org/jira/browse/MSHARED-1153?focusedCommentId=17879264&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17879264
that you have created an issue with upstream. It should be mentioned here.
> FilteringUtils makes incorrect assumption about filesystem
> --
>
> Key: MSHARED-1153
> URL: https://issues.apache.org/jira/browse/MSHARED-1153
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Reporter: James Nord
>Assignee: Michael Osipov
>Priority: Blocker
> Fix For: maven-filtering-4.0.0, maven-filtering-3.4.1
>
>
> when copying files using filtering during a project build the build can fail
> with the following exception due to an incorrect assumption in
> [FilteringUtils.java#L474-L489|https://github.com/apache/maven-filtering/blob/456b03a9510f1e64e457f393a4e04cbeeebd9538/src/main/java/org/apache/maven/shared/filtering/FilteringUtils.java#L474-L489]
> The filesystem in use may present a posix view (ie it is a mounted
> filesystem) but itself may not support setting posix attributes.
> This is common when using docker on windows and mounting windows directory
> into the container.
> this then causes the following exception :
> {noformat}
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: copying
> /home/ath-user/code/src/main/resources/ath-container/Dockerfile to
> /home/ath-user/code/target/classes/ath-container/Dockerfile failed with
> FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile
> (DefaultMavenFileFilter.java:118)
> at
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources
> (DefaultMavenResourcesFiltering.java:277)
> at org.apache.maven.plugins.resources.ResourcesMojo.execute
> (ResourcesMojo.java:356)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:370)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> 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:294)
> 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:960)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.nio.file.FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:100)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:111)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:116)
> at sun.nio.fs.UnixFileAttributeViews$Posix.setMode
[jira] [Closed] (MSHARED-1153) FilteringUtils makes incorrect assumption about filesystem
[
https://issues.apache.org/jira/browse/MSHARED-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSHARED-1153.
---
Resolution: Fixed
Fixed with
[0e96f0113a8cd92616dd3251e5ed6cef18eafed7|https://gitbox.apache.org/repos/asf?p=maven-filtering.git&a=commit&h=0e96f0113a8cd92616dd3251e5ed6cef18eafed7]
and with
[2860039597ab60827a1b6347889aa112f285bf5f|https://gitbox.apache.org/repos/asf?p=maven-filtering.git&a=commit&h=2860039597ab60827a1b6347889aa112f285bf5f]
for 3.x.
> FilteringUtils makes incorrect assumption about filesystem
> --
>
> Key: MSHARED-1153
> URL: https://issues.apache.org/jira/browse/MSHARED-1153
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Reporter: James Nord
>Assignee: Michael Osipov
>Priority: Blocker
> Fix For: maven-filtering-4.0.0, maven-filtering-3.4.1
>
>
> when copying files using filtering during a project build the build can fail
> with the following exception due to an incorrect assumption in
> [FilteringUtils.java#L474-L489|https://github.com/apache/maven-filtering/blob/456b03a9510f1e64e457f393a4e04cbeeebd9538/src/main/java/org/apache/maven/shared/filtering/FilteringUtils.java#L474-L489]
> The filesystem in use may present a posix view (ie it is a mounted
> filesystem) but itself may not support setting posix attributes.
> This is common when using docker on windows and mounting windows directory
> into the container.
> this then causes the following exception :
> {noformat}
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: copying
> /home/ath-user/code/src/main/resources/ath-container/Dockerfile to
> /home/ath-user/code/target/classes/ath-container/Dockerfile failed with
> FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile
> (DefaultMavenFileFilter.java:118)
> at
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources
> (DefaultMavenResourcesFiltering.java:277)
> at org.apache.maven.plugins.resources.ResourcesMojo.execute
> (ResourcesMojo.java:356)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:370)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> 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:294)
> 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:960)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.nio.file.FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:100)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:111)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:116)
> at sun.
[jira] [Updated] (MSHARED-1153) FilteringUtils makes incorrect assumption about filesystem
[
https://issues.apache.org/jira/browse/MSHARED-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHARED-1153:
Fix Version/s: maven-filtering-4.0.0
> FilteringUtils makes incorrect assumption about filesystem
> --
>
> Key: MSHARED-1153
> URL: https://issues.apache.org/jira/browse/MSHARED-1153
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Reporter: James Nord
>Assignee: Michael Osipov
>Priority: Blocker
> Fix For: maven-filtering-4.0.0, maven-filtering-3.4.1
>
>
> when copying files using filtering during a project build the build can fail
> with the following exception due to an incorrect assumption in
> [FilteringUtils.java#L474-L489|https://github.com/apache/maven-filtering/blob/456b03a9510f1e64e457f393a4e04cbeeebd9538/src/main/java/org/apache/maven/shared/filtering/FilteringUtils.java#L474-L489]
> The filesystem in use may present a posix view (ie it is a mounted
> filesystem) but itself may not support setting posix attributes.
> This is common when using docker on windows and mounting windows directory
> into the container.
> this then causes the following exception :
> {noformat}
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: copying
> /home/ath-user/code/src/main/resources/ath-container/Dockerfile to
> /home/ath-user/code/target/classes/ath-container/Dockerfile failed with
> FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile
> (DefaultMavenFileFilter.java:118)
> at
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources
> (DefaultMavenResourcesFiltering.java:277)
> at org.apache.maven.plugins.resources.ResourcesMojo.execute
> (ResourcesMojo.java:356)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:370)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> 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:294)
> 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:960)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.nio.file.FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:100)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:111)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:116)
> at sun.nio.fs.UnixFileAttributeViews$Posix.setMode
> (UnixFileAttributeViews.java:254)
> at sun.nio.fs.UnixFileAttributeViews$Posix.setPermissions
> (UnixFileAttributeViews.java:276)
> at java.nio.file.Files.setPosixFilePermissions (Files.java:2080)
> at org.apache.maven.shared.filtering.FilteringUtils.copyFile
[jira] [Commented] (MPMD-404) Upgrade to PMD 7.5.0
[ https://issues.apache.org/jira/browse/MPMD-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880259#comment-17880259 ] Michael Osipov commented on MPMD-404: - 7.100? I am confused now. > Upgrade to PMD 7.5.0 > > > Key: MPMD-404 > URL: https://issues.apache.org/jira/browse/MPMD-404 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Piotr Zygielo >Assignee: Michael Osipov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPMD-404) Upgrade to PMD 7.5.0
[ https://issues.apache.org/jira/browse/MPMD-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPMD-404: --- Assignee: Michael Osipov > Upgrade to PMD 7.5.0 > > > Key: MPMD-404 > URL: https://issues.apache.org/jira/browse/MPMD-404 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Piotr Zygielo >Assignee: Michael Osipov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSKINS-250) bannerLeft/Right have external link decoration when consisting only out of image
[
https://issues.apache.org/jira/browse/MSKINS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSKINS-250.
-
Resolution: Fixed
Fixed with
[d21cf9356f4ccb0f20b994b30b2207ddc0160204|https://gitbox.apache.org/repos/asf?p=maven-fluido-skin.git;a=commit;h=d21cf9356f4ccb0f20b994b30b2207ddc0160204].
> bannerLeft/Right have external link decoration when consisting only out of
> image
>
>
> Key: MSKINS-250
> URL: https://issues.apache.org/jira/browse/MSKINS-250
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M10
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
> Fix For: fluido-2.0.0
>
>
> I have the following snippet in my site descriptor (v1.8)
> {code}
>
> My Name
> someimage.png
> https://google.com/
>
> {code}
> with Fluido 1.12.0 this renders the image only, i.e.
> {code}
>
> https://google.com/";
> id="bannerLeft">
> {code}
> With Fluido 2.0.0-M10 and Site Descriptor 2.0:
> {code}
> https://google.com/";>
>
>
> {code}
> it renders as
> {code}
> https://google.com/";
> class="externalLink"> />
> {code}
> The class {{externalLink}} leads to an additional unwanted decorator next to
> the image.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880151#comment-17880151
]
Michael Osipov commented on MPMD-403:
-
Very good.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880121#comment-17880121
]
Michael Osipov commented on MPMD-403:
-
If you mean the skin issue. No, no issue required because the behavior is
expected. New Doxia stack needs updated skin.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880109#comment-17880109
]
Michael Osipov commented on MPMD-403:
-
Yes, one needs to update the skin first then the rendering will work.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DOXIA-742) Upgrade to Plexus Utils 4.0.1 and XML 3.0.1
[ https://issues.apache.org/jira/browse/DOXIA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-742. Resolution: Fixed Fixed with [32b489c1e5346aa14228d9c6b40b53d4851824d0|https://gitbox.apache.org/repos/asf?p=maven-doxia.git;a=commit;h=32b489c1e5346aa14228d9c6b40b53d4851824d0]. > Upgrade to Plexus Utils 4.0.1 and XML 3.0.1 > --- > > Key: DOXIA-742 > URL: https://issues.apache.org/jira/browse/DOXIA-742 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-344) Improve performance of case-sensitive file key checking
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-344.
-
Resolution: Fixed
Fixed with
[a040bceb23efbb58ea8fb04b20d97ce8efefa1b7|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=a040bceb23efbb58ea8fb04b20d97ce8efefa1b7].
> Improve performance of case-sensitive file key checking
> ---
>
> Key: DOXIASITETOOLS-344
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-344
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Affects Versions: 2.0.0-M19
>Reporter: John Dimeo
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0
>
>
> Our Maven site now has about 150,000 Doxia files to render (mostly Markdown
> and some ASCII doc). During profiling, I realized the Maven site plugin was
> spending around 18 minutes in the {{addModuleFiles()}} method. When looking
> at the code, I realized the algorithm was *O(n² - n / 2)* the way it adds
> each file it discovers to a map and the iterates through the map for each
> file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-403.
---
Fix Version/s: (was: waiting-for-feedback)
(was: wontfix-candidate)
Resolution: Not A Problem
So all is good and the failure is correct.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (DOXIA-742) Upgrade to Plexus Utils 4.0.1 and XML 3.0.1
Michael Osipov created DOXIA-742: Summary: Upgrade to Plexus Utils 4.0.1 and XML 3.0.1 Key: DOXIA-742 URL: https://issues.apache.org/jira/browse/DOXIA-742 Project: Maven Doxia Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPMD-403:
Fix Version/s: waiting-for-feedback
wontfix-candidate
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880096#comment-17880096
]
Michael Osipov commented on MPMD-403:
-
Same:
{noformat}
D:\Entwicklung\Projekte\maven-jar-plugin [master ≡]>
D:\Entwicklung\Programme\apache-maven-3.9.9\bin\mvn.cmd
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd -V
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: D:\Entwicklung\Programme\apache-maven-3.9.9
Java version: 21.0.3, vendor: Eclipse Adoptium, runtime: C:\Program
Files\Eclipse Adoptium\jdk-21.0.3.9-hotspot
Default locale: de_DE, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] -< org.apache.maven.plugins:maven-jar-plugin >--
[INFO] Building Apache Maven JAR Plugin 4.0.0-beta-2-SNAPSHOT
[INFO] from pom.xml
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- pmd:3.25.0:pmd (default-cli) @ maven-jar-plugin ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] PMD version: 7.3.0
[WARNING] Site model of
'org.apache.maven.plugins:maven-jar-plugin:maven-plugin:4.0.0-beta-2-SNAPSHOT'
for default locale is still using the old pre-version 2.0.0 model. You MUST
migrate to the new model as soon as possible otherwise your build will break in
the future!
[WARNING] Site model of 'org.apache.maven.plugins:maven-plugins:pom:42' for
default locale is still using the old pre-version 2.0.0 model. You MUST migrate
to the new model as soon as possible otherwise your build will break in the
future!
[WARNING] Site model of 'org.apache.maven:maven-parent:pom:42' for default
locale is still using the old pre-version 2.0.0 model. You MUST migrate to the
new model as soon as possible otherwise your build will break in the future!
[INFO] Rendering content with
org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.309 s
[INFO] Finished at: 2024-09-08T10:31:20+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
maven-jar-plugin: An error has occurred in PMD report generation.: Failed to
create context for skin: Cannot use skin: has [1.11.1,2.0.0-M1) Doxia Sitetools
prerequisite, but current is 2.0.0-M19 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
Purge your local Maven repo and try again.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880095#comment-17880095
]
Michael Osipov commented on MPMD-403:
-
I cannot reproduce:
{noformat}
D:\Entwicklung\Projekte> git clone
https://github.com/apache/maven-jar-plugin.git
Cloning into 'maven-jar-plugin'...
remote: Enumerating objects: 4305, done.
remote: Counting objects: 100% (810/810), done.
remote: Compressing objects: 100% (384/384), done.
remote: Total 4305 (delta 356), reused 660 (delta 248), pack-reused 3495 (from
1)
Receiving objects: 100% (4305/4305), 577.84 KiB | 4.13 MiB/s, done.
Resolving deltas: 100% (1462/1462), done.
D:\Entwicklung\Projekte> cd .\maven-jar-plugin\
D:\Entwicklung\Projekte\maven-jar-plugin [master ≡]>
D:\Entwicklung\Programme\apache-maven-3.9.9\bin\mvn.cmd
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd -V
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: D:\Entwicklung\Programme\apache-maven-3.9.9
Java version: 1.8.0_412, vendor: Temurin, runtime: C:\Program Files\Eclipse
Adoptium\jdk-8.0.412.8-hotspot\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] -< org.apache.maven.plugins:maven-jar-plugin >--
[INFO] Building Apache Maven JAR Plugin 4.0.0-beta-2-SNAPSHOT
[INFO] from pom.xml
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- pmd:3.25.0:pmd (default-cli) @ maven-jar-plugin ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] PMD version: 7.3.0
[WARNING] Site model of
'org.apache.maven.plugins:maven-jar-plugin:maven-plugin:4.0.0-beta-2-SNAPSHOT'
for default locale is still using the old pre-version 2.0.0 model. You MUST
migrate to the new model as soon as possible otherwise your build will break in
the future!
[WARNING] Site model of 'org.apache.maven.plugins:maven-plugins:pom:42' for
default locale is still using the old pre-version 2.0.0 model. You MUST migrate
to the new model as soon as possible otherwise your build will break in the
future!
[WARNING] Site model of 'org.apache.maven:maven-parent:pom:42' for default
locale is still using the old pre-version 2.0.0 model. You MUST migrate to the
new model as soon as possible otherwise your build will break in the future!
[INFO] Rendering content with
org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.129 s
[INFO] Finished at: 2024-09-08T10:29:33+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
maven-jar-plugin: An error has occurred in PMD report generation.: Failed to
create context for skin: Cannot use skin: has [1.11.1,2.0.0-M1) Doxia Sitetools
prerequisite, but current is 2.0.0-M19 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
Will try Java 21, but highly doubt that that is the reason.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
> ---
[jira] [Commented] (MSHARED-1153) FilteringUtils makes incorrect assumption about filesystem
[
https://issues.apache.org/jira/browse/MSHARED-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880090#comment-17880090
]
Michael Osipov commented on MSHARED-1153:
-
[~jnord_cbs], you are right. The behavior violates the contract. Can you raise
a PR for that?
Please also link the docker issue.
> FilteringUtils makes incorrect assumption about filesystem
> --
>
> Key: MSHARED-1153
> URL: https://issues.apache.org/jira/browse/MSHARED-1153
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Reporter: James Nord
>Priority: Blocker
>
> when copying files using filtering during a project build the build can fail
> with the following exception due to an incorrect assumption in
> [FilteringUtils.java#L474-L489|https://github.com/apache/maven-filtering/blob/456b03a9510f1e64e457f393a4e04cbeeebd9538/src/main/java/org/apache/maven/shared/filtering/FilteringUtils.java#L474-L489]
> The filesystem in use may present a posix view (ie it is a mounted
> filesystem) but itself may not support setting posix attributes.
> This is common when using docker on windows and mounting windows directory
> into the container.
> this then causes the following exception :
> {noformat}
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: copying
> /home/ath-user/code/src/main/resources/ath-container/Dockerfile to
> /home/ath-user/code/target/classes/ath-container/Dockerfile failed with
> FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile
> (DefaultMavenFileFilter.java:118)
> at
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources
> (DefaultMavenResourcesFiltering.java:277)
> at org.apache.maven.plugins.resources.ResourcesMojo.execute
> (ResourcesMojo.java:356)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:370)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> 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:294)
> 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:960)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.nio.file.FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:100)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:111)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:116)
> at sun.nio.fs.UnixFileAttributeViews$Posix.setMode
> (UnixFileAttributeViews.java:254)
> at sun.nio.fs.UnixFileAttributeViews$Posix.setPermissions
> (UnixFileAttributeViews.java:276)
> at java.nio.file.Files.setPosixFilePermissions (Files.java:2080)
> at org.apache.maven.s
[jira] [Deleted] (MWRAPPER-149) Maven Wrapper doesn't work on Windows PCs w/ long filenames
[
https://issues.apache.org/jira/browse/MWRAPPER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov deleted MWRAPPER-149:
> Maven Wrapper doesn't work on Windows PCs w/ long filenames
> ---
>
> Key: MWRAPPER-149
> URL: https://issues.apache.org/jira/browse/MWRAPPER-149
> Project: Maven Wrapper
> Issue Type: Bug
> Environment: Windows 10 / Windows 11
>Reporter: Sledge Hammer
>Priority: Major
>
> The mvnw.cmd generated doesn't work on Windows 11 if long file names
> containing a space are used.
> This line (around line 43):
>
> @IF NOT "%__MVNW_CMD__%"=="" (%__MVNW_CMD__% %*)
>
> Is missing quotes, should be:
>
> ("%__MVNW_CMD__%" %*)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPIR-468) Warning is issued but no way to fix it is provided
[
https://issues.apache.org/jira/browse/MPIR-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880015#comment-17880015
]
Michael Osipov commented on MPIR-468:
-
Why don't use enable the logger name with SLF4J Simple? It will give you the
source of the log message.
> Warning is issued but no way to fix it is provided
> --
>
> Key: MPIR-468
> URL: https://issues.apache.org/jira/browse/MPIR-468
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Philipp Ottlinger
>Priority: Major
>
> Running the site build on my
> [example|https://github.com/ottlinger/fotorenamer/blob/master/pom.xml]
> project yields the following warning, which I would like to fix, but the
> mentioned configuration option is not defined somewhere in my pom.xml.
> {quote}
> $ ./mvnw site
>
> [INFO] Configuring report plugin maven-project-info-reports-plugin:3.7.0
> [INFO] Detected 15 reports for maven-project-info-reports-plugin:3.7.0:
> ci-management, dependencies, dependency-info, dependency-management,
> distribution-management, index, issue-management, licenses, mailing-lists,
> modules, plugin-management, plugins, scm, summary, team
> [WARNING] The option skipLexicalErrors is deprecated. Use failOnError instead.
>
> {quote}
> Where is skipLexicalErrors used and should be replaced by failOnError?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-403) Generating site reports for plugin results in NoSuchMethodError
[ https://issues.apache.org/jira/browse/MPLUGIN-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879430#comment-17879430 ] Michael Osipov commented on MPLUGIN-403: See the release notes, you must upgrade to Maven Site Plugin 3.20.0 or newer. > Generating site reports for plugin results in NoSuchMethodError > --- > > Key: MPLUGIN-403 > URL: https://issues.apache.org/jira/browse/MPLUGIN-403 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.6.4 > Environment: Maven 3.8.5 > JDK 8 > Windows 10 >Reporter: Brad Larrick >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > When generating the site for a maven plugin I get the following: > java.lang.NoSuchMethodError: org.apache.maven.doxia.sink.Sink.verbatim(Z)V > at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText > (AbstractMavenReportRenderer.java:448) > at > org.apache.maven.plugin.plugin.PluginReport$PluginOverviewRenderer.renderUsageSection > (PluginReport.java:694) > at > org.apache.maven.plugin.plugin.PluginReport$PluginOverviewRenderer.renderBody > (PluginReport.java:616) > at org.apache.maven.reporting.AbstractMavenReportRenderer.render > (AbstractMavenReportRenderer.java:80) > at org.apache.maven.plugin.plugin.PluginReport.executeReport > (PluginReport.java:266) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1153) FilteringUtils makes incorrect assumption about filesystem
[
https://issues.apache.org/jira/browse/MSHARED-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879253#comment-17879253
]
Michael Osipov commented on MSHARED-1153:
-
Sigh, I don't see anything we can do from our side, can we?
> FilteringUtils makes incorrect assumption about filesystem
> --
>
> Key: MSHARED-1153
> URL: https://issues.apache.org/jira/browse/MSHARED-1153
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Reporter: James Nord
>Priority: Blocker
>
> when copying files using filtering during a project build the build can fail
> with the following exception due to an incorrect assumption in
> [FilteringUtils.java#L474-L489|https://github.com/apache/maven-filtering/blob/456b03a9510f1e64e457f393a4e04cbeeebd9538/src/main/java/org/apache/maven/shared/filtering/FilteringUtils.java#L474-L489]
> The filesystem in use may present a posix view (ie it is a mounted
> filesystem) but itself may not support setting posix attributes.
> This is common when using docker on windows and mounting windows directory
> into the container.
> this then causes the following exception :
> {noformat}
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: copying
> /home/ath-user/code/src/main/resources/ath-container/Dockerfile to
> /home/ath-user/code/target/classes/ath-container/Dockerfile failed with
> FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile
> (DefaultMavenFileFilter.java:118)
> at
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources
> (DefaultMavenResourcesFiltering.java:277)
> at org.apache.maven.plugins.resources.ResourcesMojo.execute
> (ResourcesMojo.java:356)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:370)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> 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:294)
> 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:960)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.nio.file.FileSystemException:
> /home/ath-user/code/target/classes/ath-container/Dockerfile: Operation not
> permitted
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:100)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:111)
> at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:116)
> at sun.nio.fs.UnixFileAttributeViews$Posix.setMode
> (UnixFileAttributeViews.java:254)
> at sun.nio.fs.UnixFileAttributeViews$Posix.setPermissions
> (UnixFileAttributeViews.java:276)
> at java.nio.file.Files.setPosixFilePermissions (Files.java:2080)
> at org.apache.maven.shared.filtering.FilteringUtils.copyFilePermissions
> (FilteringUtils.
[jira] [Commented] (MNG-8237) Option deprecation notices cleanup
[
https://issues.apache.org/jira/browse/MNG-8237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878832#comment-17878832
]
Michael Osipov commented on MNG-8237:
-
[~gnodet]
> Option deprecation notices cleanup
> --
>
> Key: MNG-8237
> URL: https://issues.apache.org/jira/browse/MNG-8237
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-beta-4
>Reporter: Delany
>Priority: Minor
>
> When I run a build with the deprecated global-setting option I'm told four
> times about it
> {noformat}
> $ ./mvnw validate -N --global-settings ~/.m2/settings.xml
> Option 'gs''global-settings': Deprecated
> Option 'gs''global-settings': Deprecated
> Option 'gs''global-settings': Deprecated
> Option 'gs''global-settings': Deprecated{noformat}
> The documentation from
> {noformat}
> ./mvnw --help{noformat}
> however does not mention this
> {noformat}
> -gs,--global-settings Alternate path for the
> global settings file{noformat}
> It could rather be
> {noformat}
> -gs,--global-settings Alternate
> path for the global settings file{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2227) Dynamically calculate xrefTestLocation
[
https://issues.apache.org/jira/browse/SUREFIRE-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878548#comment-17878548
]
Michael Osipov commented on SUREFIRE-2227:
--
Maybe someone else can/will do that, I do not maintain release notes twice. The
canonical releases notes are at
https://lists.apache.org/thread/t40nhfck87f6kx1rkx3ykz3tzvj6wmcp.
> Dynamically calculate xrefTestLocation
> --
>
> Key: SUREFIRE-2227
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2227
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.2.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.5.0
>
>
> After MSHARED-1327 we need to dynamically calculate where (Test) XRef report
> resides. Unless an explicit value has been provided.
> The calculation considers both standalone mode *and* site mode.
> The parameter {{xrefLocation}} will be renamed to {{xrefTestLocation}}
> because we only link to test source code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MRESOLVER-600) Implement RFC 9457
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-600: - Summary: Implement RFC 9457 (was: Implement RFC9457) > Implement RFC 9457 > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Priority: Minor > > HTTP1.1 [RFC > 9112|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 > defines the response status code to optionally include a text description > (human readable) of the reason for the status code. > There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which > makes use of the body to inform of a reason for the error response allowing > for easier investigation. > h2. Why is this important > [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-600) Implement RFC9457
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878445#comment-17878445 ] Michael Osipov commented on MRESOLVER-600: -- 90 % what you have written refers to obsolete RFCs. Please rewrite your description. > Implement RFC9457 > - > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Priority: Minor > > HTTP1.1 [RFC7230|https://www.rfc-editor.org/rfc/rfc7230#section-3.1.2] > section 3.1.2 defines the response status code to optionally include a text > description (human readable) of the reason for the status code. A more > detailed RFC is > [RFC2616|https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html] > There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which > makes use of the body to inform of a reason for the error response allowing > for easier investigation. > h2. Why is this important > [RFC9113|https://datatracker.ietf.org/doc/html/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2261) NullPointerException when generating a test report
[
https://issues.apache.org/jira/browse/SUREFIRE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2261.
Resolution: Duplicate
Too lazy to search, but not too lazy to describe everything.
> NullPointerException when generating a test report
> --
>
> Key: SUREFIRE-2261
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2261
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Andrei Solntsev
>Priority: Major
>
> I am getting NullPointerException when trying to generate test report.
> The problem is NOT reproducible with version 3.4.0.
>
> Step to reproduce:
> # `git clone g...@github.com:selenide-examples/cucumber.git`
> # `mvn surefire-report:report -Dselenide.headless=true -e`
> Result:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> (default-cli) on project selenide-cucumber: Execution default-cli of goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> failed: Cannot invoke "Object.toString()" because "value" is null -> [Help
> 1]}}
> {{org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> (default-cli) on project selenide-cucumber: Execution default-cli of goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> failed: Cannot invoke "Object.toString()" because "value" is null}}
> {{ 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:906)}}
> {{ at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)}}
> {{ at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)}}
> {{ 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:569)}}
> {{ 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.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> failed: Cannot invoke "Object.toString()" because "value" is null}}
> {{ at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:133)}}
> {{ 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
[jira] [Closed] (DOXIASITETOOLS-347) Upgrade to Parent 43
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-347. - Resolution: Fixed Fixed with [a5a2ebe6e8d73ad3385ceb4528eb692937355acb|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=a5a2ebe6e8d73ad3385ceb4528eb692937355acb]. > Upgrade to Parent 43 > > > Key: DOXIASITETOOLS-347 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-347 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIASITETOOLS-347) Upgrade to Parent 43
Michael Osipov created DOXIASITETOOLS-347: - Summary: Upgrade to Parent 43 Key: DOXIASITETOOLS-347 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-347 Project: Maven Doxia Sitetools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIA-741) Upgrade to Parent 43
[ https://issues.apache.org/jira/browse/DOXIA-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-741. Resolution: Fixed Fixed with [d10c979d72a86e328fe0e3dd4b7f573cac6e4147|https://gitbox.apache.org/repos/asf?p=maven-doxia.git;a=commit;h=d10c979d72a86e328fe0e3dd4b7f573cac6e4147]. > Upgrade to Parent 43 > > > Key: DOXIA-741 > URL: https://issues.apache.org/jira/browse/DOXIA-741 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIA-741) Upgrade to Parent 43
Michael Osipov created DOXIA-741: Summary: Upgrade to Parent 43 Key: DOXIA-741 URL: https://issues.apache.org/jira/browse/DOXIA-741 Project: Maven Doxia Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIA-739) Disable source code highlighters for verbatim blocks for Markdown
[ https://issues.apache.org/jira/browse/DOXIA-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-739. Resolution: Fixed Fixed with [c35c571f56488d37aeb57b147dc848bce050f597|https://gitbox.apache.org/repos/asf?p=maven-doxia.git;a=commit;h=c35c571f56488d37aeb57b147dc848bce050f597]. > Disable source code highlighters for verbatim blocks for Markdown > - > > Key: DOXIA-739 > URL: https://issues.apache.org/jira/browse/DOXIA-739 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Markdown >Affects Versions: 2.0.0-M12 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0 > > > If a fenced block without a language is provided the output should be just > plaintext. No source code highlighter shall process it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSKINS-251) Make image class optional
[
https://issues.apache.org/jira/browse/MSKINS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSKINS-251:
--
Summary: Make image class optional (was: Make img class optional)
> Make image class optional
> -
>
> Key: MSKINS-251
> URL: https://issues.apache.org/jira/browse/MSKINS-251
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M10
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: fluido-2.0.0
>
>
> There are cases where an {{}} does not need to have a class by default
> (e.g., {{imageLink}}). A case is banner images.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSKINS-251) Make img class optional
Michael Osipov created MSKINS-251:
-
Summary: Make img class optional
Key: MSKINS-251
URL: https://issues.apache.org/jira/browse/MSKINS-251
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Affects Versions: fluido-2.0.0-M10
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: fluido-2.0.0
There are cases where an {{}} does not need to have a class by default
(e.g., {{imageLink}}). A case is banner images.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSKINS-250) bannerLeft/Right have external link decoration when consisting only out of image
[
https://issues.apache.org/jira/browse/MSKINS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878323#comment-17878323
]
Michael Osipov commented on MSKINS-250:
---
Checked case in line 151, that is not a mismatch. It is not purpose. Dynamic
typing like in JavaScript or PHP.
> bannerLeft/Right have external link decoration when consisting only out of
> image
>
>
> Key: MSKINS-250
> URL: https://issues.apache.org/jira/browse/MSKINS-250
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M10
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
> Fix For: fluido-2.0.0
>
>
> I have the following snippet in my site descriptor (v1.8)
> {code}
>
> My Name
> someimage.png
> https://google.com/
>
> {code}
> with Fluido 1.12.0 this renders the image only, i.e.
> {code}
>
> https://google.com/";
> id="bannerLeft">
> {code}
> With Fluido 2.0.0-M10 and Site Descriptor 2.0:
> {code}
> https://google.com/";>
>
>
> {code}
> it renders as
> {code}
> https://google.com/";
> class="externalLink"> />
> {code}
> The class {{externalLink}} leads to an additional unwanted decorator next to
> the image.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSKINS-250) bannerLeft/Right have external link decoration when consisting only out of image
[
https://issues.apache.org/jira/browse/MSKINS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878189#comment-17878189
]
Michael Osipov commented on MSKINS-250:
---
Our messages overlapped. I agree that {{externalLink}} is pointless on
banners. Will take care. I will analyze the mismatch and let you know.
> bannerLeft/Right have external link decoration when consisting only out of
> image
>
>
> Key: MSKINS-250
> URL: https://issues.apache.org/jira/browse/MSKINS-250
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M10
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
> Fix For: fluido-2.0.0
>
>
> I have the following snippet in my site descriptor (v1.8)
> {code}
>
> My Name
> someimage.png
> https://google.com/
>
> {code}
> with Fluido 1.12.0 this renders the image only, i.e.
> {code}
>
> https://google.com/";
> id="bannerLeft">
> {code}
> With Fluido 2.0.0-M10 and Site Descriptor 2.0:
> {code}
> https://google.com/";>
>
>
> {code}
> it renders as
> {code}
> https://google.com/";
> class="externalLink"> />
> {code}
> The class {{externalLink}} leads to an additional unwanted decorator next to
> the image.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSKINS-250) bannerLeft/Right have external link decoration when consisting only out of image
[
https://issues.apache.org/jira/browse/MSKINS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSKINS-250:
--
Fix Version/s: fluido-2.0.0
> bannerLeft/Right have external link decoration when consisting only out of
> image
>
>
> Key: MSKINS-250
> URL: https://issues.apache.org/jira/browse/MSKINS-250
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M10
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
> Fix For: fluido-2.0.0
>
>
> I have the following snippet in my site descriptor (v1.8)
> {code}
>
> My Name
> someimage.png
> https://google.com/
>
> {code}
> with Fluido 1.12.0 this renders the image only, i.e.
> {code}
>
> https://google.com/";
> id="bannerLeft">
> {code}
> With Fluido 2.0.0-M10 and Site Descriptor 2.0:
> {code}
> https://google.com/";>
>
>
> {code}
> it renders as
> {code}
> https://google.com/";
> class="externalLink"> />
> {code}
> The class {{externalLink}} leads to an additional unwanted decorator next to
> the image.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MSKINS-250) bannerLeft/Right have external link decoration when consisting only out of image
[
https://issues.apache.org/jira/browse/MSKINS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MSKINS-250:
-
Assignee: Michael Osipov
> bannerLeft/Right have external link decoration when consisting only out of
> image
>
>
> Key: MSKINS-250
> URL: https://issues.apache.org/jira/browse/MSKINS-250
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M10
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
>
> I have the following snippet in my site descriptor (v1.8)
> {code}
>
> My Name
> someimage.png
> https://google.com/
>
> {code}
> with Fluido 1.12.0 this renders the image only, i.e.
> {code}
>
> https://google.com/";
> id="bannerLeft">
> {code}
> With Fluido 2.0.0-M10 and Site Descriptor 2.0:
> {code}
> https://google.com/";>
>
>
> {code}
> it renders as
> {code}
> https://google.com/";
> class="externalLink"> />
> {code}
> The class {{externalLink}} leads to an additional unwanted decorator next to
> the image.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSKINS-250) bannerLeft/Right have external link decoration when consisting only out of image
[
https://issues.apache.org/jira/browse/MSKINS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878170#comment-17878170
]
Michael Osipov commented on MSKINS-250:
---
That is the outcome of the harmonization of the link code. All links are
treated equal.
Questions:
* {{imageLink}} is never defined by us, I guess it is a convenience for users.
Should the banner contain it?
* Should the banner never contain {{externalLink}}?
> bannerLeft/Right have external link decoration when consisting only out of
> image
>
>
> Key: MSKINS-250
> URL: https://issues.apache.org/jira/browse/MSKINS-250
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M10
>Reporter: Konrad Windszus
>Priority: Major
>
> I have the following snippet in my site descriptor (v1.8)
> {code}
>
> My Name
> someimage.png
> https://google.com/
>
> {code}
> with Fluido 1.12.0 this renders the image only, i.e.
> {code}
>
> https://google.com/";
> id="bannerLeft">
> {code}
> With Fluido 2.0.0-M10 and Site Descriptor 2.0:
> {code}
> https://google.com/";>
>
>
> {code}
> it renders as
> {code}
> https://google.com/";
> class="externalLink"> />
> {code}
> The class {{externalLink}} leads to an additional unwanted decorator next to
> the image.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8230) Rewrite CI friendly versions
[ https://issues.apache.org/jira/browse/MNG-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878036#comment-17878036 ] Michael Osipov commented on MNG-8230: - This is also broken in Maven Release. > Rewrite CI friendly versions > > > Key: MNG-8230 > URL: https://issues.apache.org/jira/browse/MNG-8230 > Project: Maven > Issue Type: New Feature >Affects Versions: 4.0.0-beta-3 >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8226) Unable to parse maven.config
[ https://issues.apache.org/jira/browse/MNG-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877628#comment-17877628 ] Michael Osipov commented on MNG-8226: - Check MavenCli.java > Unable to parse maven.config > > > Key: MNG-8226 > URL: https://issues.apache.org/jira/browse/MNG-8226 > Project: Maven > Issue Type: Bug > Components: Command Line, Settings >Affects Versions: 3.9.9 >Reporter: Hüseyin Kartal >Priority: Blocker > Attachments: maven.config > > > Maven don't recognize options in .mvn/maven.conf file. > Following options are not recognized in maven.conf file. > -s,--settings > -t,--toolchains > The resulting error is: > Unable to parse maven.config file options: Unrecognized option: --settings > .mvn/settings.xml > If the short options used without space -s it works. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2257) [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2257.
Resolution: Fixed
Fixed with
[69c1b46d85e77dc25a8639fc20d9ae596917e8ce|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=69c1b46d85e77dc25a8639fc20d9ae596917e8ce].
> [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
>
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.5.1
>
> Attachments: 3.4.0-surefire-report.png, screenshot-1.png,
> screenshot-2.png, surefire-3.5.0-2-g69c1b46d8.png
>
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only 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 X: 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> 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
[jira] [Commented] (SUREFIRE-2257) [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877404#comment-17877404
]
Michael Osipov commented on SUREFIRE-2257:
--
That's interesting...though it would require some significant effort to
integrate into Surefire. Given than I am currently the only one working on
Surefire, I don't expect it to happen anytime soon :-(
> [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
>
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.5.1
>
> Attachments: 3.4.0-surefire-report.png, screenshot-1.png,
> screenshot-2.png, surefire-3.5.0-2-g69c1b46d8.png
>
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only 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 X: 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> 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
[jira] [Commented] (MNG-8226) Unable to parse maven.config
[ https://issues.apache.org/jira/browse/MNG-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877402#comment-17877402 ] Michael Osipov commented on MNG-8226: - [~hsyn], what you are referring to is a feature of Commons CLI to contract option and option value. This isn't something we imply/impose. > Unable to parse maven.config > > > Key: MNG-8226 > URL: https://issues.apache.org/jira/browse/MNG-8226 > Project: Maven > Issue Type: Bug > Components: Command Line, Settings >Affects Versions: 3.9.9 >Reporter: Hüseyin Kartal >Priority: Blocker > Attachments: maven.config > > > Maven don't recognize options in .mvn/maven.conf file. > Following options are not recognized in maven.conf file. > -s,--settings > -t,--toolchains > The resulting error is: > Unable to parse maven.config file options: Unrecognized option: --settings > .mvn/settings.xml > If the short options used without space -s it works. -- This message was sent by Atlassian Jira (v8.20.10#820010)
