[jira] [Commented] (ARCHETYPE-488) Goal integration-test of maven-archetype-plugin fails with 'Cannot run additions goals." in version 3.3.1
[
https://issues.apache.org/jira/browse/ARCHETYPE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599235#comment-17599235
]
Manata Simanjuntak commented on ARCHETYPE-488:
--
Thank you @Sven Rottstock my problems was solve using you method(y)(y)
> Goal integration-test of maven-archetype-plugin fails with 'Cannot run
> additions goals." in version 3.3.1
> -
>
> Key: ARCHETYPE-488
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-488
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.4
> Environment: maven-archetype-plugin 2.3
>Reporter: Andreas Horst
>Assignee: Robert Scholte
>Priority: Major
> Labels: archetype, integration-test
> Fix For: 3.0.0
>
>
> Running the goal 'integration-test' of the 'maven-archetype-plugin' fails
> with the following output:
> {noformat}
> [INFO] Invoking post-archetype-generation goals: verify
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.048 s
> [INFO] Finished at: 2015-04-23T18:17:07+02:00
> [INFO] Final Memory: 18M/309M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.3:integration-test
> (default-integration-test) on project simple-archetype:
> [ERROR] Archetype IT 'it' failed: Cannot run additions goals.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-archetype-plugin:2.3:integration-test
> (default-integration-test) on project simple-archetype:
> Archetype IT 'it' failed: Cannot run additions goals.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException:
> Archetype IT 'it' failed: Cannot run additions goals.
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> [ERROR]
> [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}
> This works fine in earlier versions (tested with Maven 3.2.5 and 3.2.3).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request, #243: Bump jsoup from 1.14.2 to 1.15.3 in /src/it/projects/analyze-testDependencyWithNonTestScope
dependabot[bot] opened a new pull request, #243: URL: https://github.com/apache/maven-dependency-plugin/pull/243 Bumps [jsoup](https://github.com/jhy/jsoup) from 1.14.2 to 1.15.3. Release notes Sourced from https://github.com/jhy/jsoup/releases;>jsoup's releases. jsoup 1.15.3 jsoup 1.15.3 is out now, and includes a security fix for potential XSS attacks, along with other bug fixes and improvements, including more descriptive validation error messages. Details: https://github.com/jhy/jsoup/security/advisories/GHSA-gp7f-rwcx-9369;>Security advisory https://jsoup.org/news/release-1.15.3;>Release notes https://jsoup.org/download;>Download jsoup 1.15.2 is out now with a bunch of https://jsoup.org/news/release-1.15.2;>improvements and bug fixes. jsoup 1.15.1 is out now with a bunch of https://jsoup.org/news/release-1.15.1;>improvements and bug fixes. jsoup 1.14.3 jsoup 1.14.3 is out now, adding native XPath selector support, improved \template support, and also includes a bunch of bug fixes, improvements, and performance enhancements. See the https://jsoup.org/news/release-1.14.3;>release announcement for the full changelog. Changelog Sourced from https://github.com/jhy/jsoup/blob/master/CHANGES;>jsoup's changelog. jsoup changelog Release 1.15.3 [2022-Aug-24] Security: fixed an issue where the jsoup cleaner may incorrectly sanitize crafted XSS attempts if SafeList.preserveRelativeLinks is enabled. https://github.com/jhy/jsoup/security/advisories/GHSA-gp7f-rwcx-9369;>https://github.com/jhy/jsoup/security/advisories/GHSA-gp7f-rwcx-9369 Improvement: the Cleaner will preserve the source position of cleaned elements, if source tracking is enabled in the original parse. Improvement: the error messages output from Validate are more descriptive. Exceptions are now ValidationExceptions (extending IllegalArgumentException). Stack traces do not include the Validate class, to make it simpler to see where the exception originated. Common validation errors including malformed URLs and empty selector results have more explicit error messages. Bugfix: the DataUtil would incorrectly read from InputStreams that emitted reads less than the requested size. This lead to incorrect results when parsing from chunked server responses, for e.g. https://github-redirect.dependabot.com/jhy/jsoup/issues/1807;>jhy/jsoup#1807 Build Improvement: added implementation version and related fields to the jar manifest. https://github-redirect.dependabot.com/jhy/jsoup/issues/1809;>jhy/jsoup#1809 *** Release 1.15.2 [2022-Jul-04] Improvement: added the ability to track the position (line, column, index) in the original input source from where a given node was parsed. Accessible via Node.sourceRange() and Element.endSourceRange(). https://github-redirect.dependabot.com/jhy/jsoup/pull/1790;>jhy/jsoup#1790 Improvement: added Element.firstElementChild(), Element.lastElementChild(), Node.firstChild(), Node.lastChild(), as convenient accessors to those child nodes and elements. Improvement: added Element.expectFirst(cssQuery), which is just like Element.selectFirst(), but instead of returning a null if there is no match, will throw an IllegalArgumentException. This is useful if you want to simply abort processing if an expected match is not found. Improvement: when pretty-printing HTML, doctypes are emitted on a newline if there is a preceding comment. https://github-redirect.dependabot.com/jhy/jsoup/pull/1664;>jhy/jsoup#1664 Improvement: when pretty-printing, trim the leading and trailing spaces of textnodes in block tags when possible, so that they are indented correctly. https://github-redirect.dependabot.com/jhy/jsoup/issues/1798;>jhy/jsoup#1798 Improvement: in Element#selectXpath(), disable namespace awareness. This makes it possible to always select elements by their simple local name, regardless of whether an xmlns attribute was set. https://github-redirect.dependabot.com/jhy/jsoup/issues/1801;>jhy/jsoup#1801 Bugfix: when using the readToByteBuffer method, such as in Connection.Response.body(), if the document has not already been parsed and must be read fully, and there is any maximum buffer size being applied, only the default internal buffer size is read. https://github-redirect.dependabot.com/jhy/jsoup/issues/1774;>jhy/jsoup#1774 ... (truncated) Commits https://github.com/jhy/jsoup/commit/c5964172763e1495786ad584c368ac3346d0ca8c;>c596417 [maven-release-plugin] prepare release jsoup-1.15.3 https://github.com/jhy/jsoup/commit/d2d9ac341dbd48e75c6dd09c571216a81939604f;>d2d9ac3 Changelog for URL cleaner improvement
[jira] [Created] (MSHARED-1127) Remove main method from Verifier
Slawomir Jaranowski created MSHARED-1127:
Summary: Remove main method from Verifier
Key: MSHARED-1127
URL: https://issues.apache.org/jira/browse/MSHARED-1127
Project: Maven Shared Components
Issue Type: Task
Components: maven-verifier
Reporter: Slawomir Jaranowski
Fix For: maven-verifier-2.0.0
There is {{main}} method in Verifier, it is undocumented feature and probably
not used.
Verifier should be called form test code not from command line.
We can also remove code used only for it.
Code use in main method parse arguments for command line.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7535) Latest release of Maven contain EOL component - EOL-Google Guava 25.1
[ https://issues.apache.org/jira/browse/MNG-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7535: Fix Version/s: waiting-for-feedback > Latest release of Maven contain EOL component - EOL-Google Guava 25.1 > - > > Key: MNG-7535 > URL: https://issues.apache.org/jira/browse/MNG-7535 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.8.6 >Reporter: Chris Campbell >Priority: Minor > Fix For: waiting-for-feedback > > > We are utilizing the latest maven releases and getting EOL findings ( > EOL-Google Guava 25.1 ) from our internal Enterprise Security team that we > must remediate. > Will maven releases update to a newer, non-EOL of these components? If not, > is there anything we can do ourselves to remediate and use non-EOL versions? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHADE-323) Flatten Maven Plugin conflicts with Maven Shade Plugin
[
https://issues.apache.org/jira/browse/MSHADE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599113#comment-17599113
]
Jesse Glick commented on MSHADE-323:
https://github.com/mojohaus/flatten-maven-plugin/releases/tag/flatten-maven-plugin-1.3.0
> Flatten Maven Plugin conflicts with Maven Shade Plugin
> --
>
> Key: MSHADE-323
> URL: https://issues.apache.org/jira/browse/MSHADE-323
> Project: Maven Shade Plugin
> Issue Type: Bug
>Reporter: lakunma
>Priority: Minor
>
> When using Flatten Maven Plugin in the same project with Maven Shade Plugin
> then the dependency reduced POM is _not_ flattened.
> What i encountered that having flatten plugin configured according to
> [https://maven.apache.org/maven-ci-friendly.html], and having shade plugin
> configured with the default settings to produce uber jar the ${revision}
> variable remains and gets installed/deployed within the final pom, thus
> making the pom in the repository invalid.
> It seems that both plugins transform original pom. And then what gets
> installed in the last one, which is the 'shades' one. I'm not sure that's a
> bug (in a sense that it is shade's fault).
> See also [https://github.com/mojohaus/flatten-maven-plugin/issues/100]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-verifier] slawekjaranowski opened a new pull request, #39: [MSHARED-1124] Add new version of methods filterFile and newDefaultFilterMap
slawekjaranowski opened a new pull request, #39: URL: https://github.com/apache/maven-verifier/pull/39 in order to easier migrate -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MSHARED-1124) Remove deprecated methods for next major release
[
https://issues.apache.org/jira/browse/MSHARED-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599107#comment-17599107
]
Slawomir Jaranowski edited comment on MSHARED-1124 at 9/1/22 6:42 PM:
--
Most of deprecated methods was removed in: MSHARED-1089
There is one more method {{filterFile}}, but I would to postpone it for next
major.
was (Author: slawekjaranowski):
Most of deprecated methods was removed in: MSHARED-1089
> Remove deprecated methods for next major release
>
>
> Key: MSHARED-1124
> URL: https://issues.apache.org/jira/browse/MSHARED-1124
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-verifier
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: maven-verifier-2.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1089) Update maven-verifier to JDK 8 / Junit 5
[ https://issues.apache.org/jira/browse/MSHARED-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1089. Resolution: Fixed > Update maven-verifier to JDK 8 / Junit 5 > > > Key: MSHARED-1089 > URL: https://issues.apache.org/jira/browse/MSHARED-1089 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-verifier >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1089) Update maven-verifier to JDK 8 / Junit 5
[ https://issues.apache.org/jira/browse/MSHARED-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MSHARED-1089: - Fix Version/s: maven-verifier-2.0.0 > Update maven-verifier to JDK 8 / Junit 5 > > > Key: MSHARED-1089 > URL: https://issues.apache.org/jira/browse/MSHARED-1089 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-verifier >Reporter: Guillaume Nodet >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1124) Remove deprecated methods for next major release
[ https://issues.apache.org/jira/browse/MSHARED-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599107#comment-17599107 ] Slawomir Jaranowski commented on MSHARED-1124: -- Most of deprecated methods was removed in: MSHARED-1089 > Remove deprecated methods for next major release > > > Key: MSHARED-1124 > URL: https://issues.apache.org/jira/browse/MSHARED-1124 > Project: Maven Shared Components > Issue Type: Task > Components: maven-verifier >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSHARED-1089) Update maven-verifier to JDK 8 / Junit 5
[ https://issues.apache.org/jira/browse/MSHARED-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski reassigned MSHARED-1089: Assignee: Guillaume Nodet > Update maven-verifier to JDK 8 / Junit 5 > > > Key: MSHARED-1089 > URL: https://issues.apache.org/jira/browse/MSHARED-1089 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-verifier >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSHARED-1124) Remove deprecated methods for next major release
[ https://issues.apache.org/jira/browse/MSHARED-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski reassigned MSHARED-1124: Assignee: Slawomir Jaranowski > Remove deprecated methods for next major release > > > Key: MSHARED-1124 > URL: https://issues.apache.org/jira/browse/MSHARED-1124 > Project: Maven Shared Components > Issue Type: Task > Components: maven-verifier >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-721) Parse stderr output and suppress informational lines
[
https://issues.apache.org/jira/browse/MJAVADOC-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599077#comment-17599077
]
Michael Osipov commented on MJAVADOC-721:
-
So as far as I understand the JIRA issues, the have harmonized the output
target with {{{}java(1){}}}?
> Parse stderr output and suppress informational lines
>
>
> Key: MJAVADOC-721
> URL: https://issues.apache.org/jira/browse/MJAVADOC-721
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: javadoc
>Affects Versions: 3.4.0
>Reporter: Markus Spann
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.4.2
>
>
> From Java 17 the Javadoc tool prints informational output to stderr mixed
> with actual errors and warnings (see
> [JDK-8268774|https://bugs.openjdk.org/browse/JDK-8268774],
> [JDK-8270831|https://bugs.openjdk.org/browse/JDK-8270831]).
> Currently the maven-javadoc-plugin logs the complete content of the tool's
> stderr as warning or includes it completely in the message of a
> MavenReportException (in case of an unsuccessful exit code of the tool). This
> behavior is not optimal with Java 17 onwards.
> The output can be lengthy and the informational messages very distracting.
> This is particularly true for larger projects.
> This improvement enables the developer/user to focus on the actual warnings
> or errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-jar-plugin] slachiewicz merged pull request #51: Restore mavenArchiverVersion property used in the site
slachiewicz merged PR #51: URL: https://github.com/apache/maven-jar-plugin/pull/51 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] sman-81 commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
sman-81 commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960776732
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
Code amended. Hope I got it now :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] sman-81 commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
sman-81 commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960763999
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
Ok. Valid point.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] michael-o commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
michael-o commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960763018
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
I would prefer the original prefixes from the resource bundles for
consistency reasons.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] sman-81 commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
sman-81 commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960759787
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
Thanks for your feedback @michael-o!
- [x] PR updated and forced pushed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] sman-81 commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
sman-81 commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960759787
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
Thanks for your feedback @michael-o
PR updated forced pushed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] sman-81 commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
sman-81 commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960757260
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
Both, "Loading source file " and "Loading source files " can occur.
Will update my code to `str.startsWith( "Loading source file" )` which
catches singular and plural.
This should be it. Hope I understood your comment correctly though :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] sman-81 commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
sman-81 commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960748864
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
Review Comment:
A null string should not go to the non-informational output therefore it is
considered informational. The null check is also to ensure the following
statements will never cause NPE.
You are right, I should include empty and blank strings.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MJAVADOC-715) Generated @options caused in an error when using german umlauts in organization name
[ https://issues.apache.org/jira/browse/MJAVADOC-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599004#comment-17599004 ] Michael Osipov commented on MJAVADOC-715: - I cannot reproduce your sample with Zulu 8, 11, 17 on PowerShell in Windows Terminal on Windows 10. Can you preproduce on Windows 10? > Generated @options caused in an error when using german umlauts in > organization name > > > Key: MJAVADOC-715 > URL: https://issues.apache.org/jira/browse/MJAVADOC-715 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: javadoc >Affects Versions: 3.4.0 > Environment: Windows 11 >Reporter: Andreas Riesel >Priority: Critical > Labels: encoding > Attachments: javadoc-bug.zip > > > When you try generate javadocs with german umlauts in organization name, you > gets an javadoc error. The problem exists only on windows 11 command line, > the same build runs under Debian fine. > The bug will demonstrated by the attached project and is commented inside the > pom.xml (section organization). > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAVADOC-715) Generated @options caused in an error when using german umlauts in organization name
[ https://issues.apache.org/jira/browse/MJAVADOC-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-715: Fix Version/s: waiting-for-feedback > Generated @options caused in an error when using german umlauts in > organization name > > > Key: MJAVADOC-715 > URL: https://issues.apache.org/jira/browse/MJAVADOC-715 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: javadoc >Affects Versions: 3.4.0 > Environment: Windows 11 >Reporter: Andreas Riesel >Priority: Critical > Labels: encoding > Fix For: waiting-for-feedback > > Attachments: javadoc-bug.zip > > > When you try generate javadocs with german umlauts in organization name, you > gets an javadoc error. The problem exists only on windows 11 command line, > the same build runs under Debian fine. > The bug will demonstrated by the attached project and is commented inside the > pom.xml (section organization). > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAVADOC-715) Generated @options caused in an error when using german umlauts in organization name
[ https://issues.apache.org/jira/browse/MJAVADOC-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-715: Language: (was: JAVA) > Generated @options caused in an error when using german umlauts in > organization name > > > Key: MJAVADOC-715 > URL: https://issues.apache.org/jira/browse/MJAVADOC-715 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: javadoc >Affects Versions: 3.4.0 > Environment: Windows 11 >Reporter: Andreas Riesel >Priority: Critical > Labels: encoding > Attachments: javadoc-bug.zip > > > When you try generate javadocs with german umlauts in organization name, you > gets an javadoc error. The problem exists only on windows 11 command line, > the same build runs under Debian fine. > The bug will demonstrated by the attached project and is commented inside the > pom.xml (section organization). > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAVADOC-721) Parse stderr output and suppress informational lines
[ https://issues.apache.org/jira/browse/MJAVADOC-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-721: Description: >From Java 17 the Javadoc tool prints informational output to stderr mixed with >actual errors and warnings (see >[JDK-8268774|https://bugs.openjdk.org/browse/JDK-8268774], >[JDK-8270831|https://bugs.openjdk.org/browse/JDK-8270831]). Currently the maven-javadoc-plugin logs the complete content of the tool's stderr as warning or includes it completely in the message of a MavenReportException (in case of an unsuccessful exit code of the tool). This behavior is not optimal with Java 17 onwards. The output can be lengthy and the informational messages very distracting. This is particularly true for larger projects. This improvement enables the developer/user to focus on the actual warnings or errors. was: >From Java 17 the Javadoc tool prints informational output to stderr mixed with >actual errors and warnings (see >[JDK-8268774|https://bugs.openjdk.org/browse/JDK-8268774]/[JDK-8270831|https://bugs.openjdk.org/browse/JDK-8270831]). Currently the maven-javadoc-plugin logs the complete content of the tool's stderr as warning or includes it completely in the message of a MavenReportException (in case of an unsuccessful exit code of the tool). This behavior is not optimal with Java 17 onwards. The output can be lengthy and the informational messages very distracting. This is particularly true for larger projects. This improvement enables the developer/user to focus on the actual warnings or errors. > Parse stderr output and suppress informational lines > > > Key: MJAVADOC-721 > URL: https://issues.apache.org/jira/browse/MJAVADOC-721 > Project: Maven Javadoc Plugin > Issue Type: Improvement > Components: javadoc >Affects Versions: 3.4.0 >Reporter: Markus Spann >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.4.2 > > > From Java 17 the Javadoc tool prints informational output to stderr mixed > with actual errors and warnings (see > [JDK-8268774|https://bugs.openjdk.org/browse/JDK-8268774], > [JDK-8270831|https://bugs.openjdk.org/browse/JDK-8270831]). > Currently the maven-javadoc-plugin logs the complete content of the tool's > stderr as warning or includes it completely in the message of a > MavenReportException (in case of an unsuccessful exit code of the tool). This > behavior is not optimal with Java 17 onwards. > The output can be lengthy and the informational messages very distracting. > This is particularly true for larger projects. > This improvement enables the developer/user to focus on the actual warnings > or errors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAVADOC-721) Parse stderr output and suppress informational lines
[ https://issues.apache.org/jira/browse/MJAVADOC-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-721: Description: >From Java 17 the Javadoc tool prints informational output to stderr mixed with >actual errors and warnings (see >[JDK-8268774|https://bugs.openjdk.org/browse/JDK-8268774]/[JDK-8270831|https://bugs.openjdk.org/browse/JDK-8270831]). Currently the maven-javadoc-plugin logs the complete content of the tool's stderr as warning or includes it completely in the message of a MavenReportException (in case of an unsuccessful exit code of the tool). This behavior is not optimal with Java 17 onwards. The output can be lengthy and the informational messages very distracting. This is particularly true for larger projects. This improvement enables the developer/user to focus on the actual warnings or errors. was: >From Java 17 the Javadoc tool prints informational output to stderr mixed with >actual errors and warnings (see JDK-8268774 / JDK-8270831). Currently the maven-javadoc-plugin logs the complete content of the tool's stderr as warning or includes it completely in the message of a MavenReportException (in case of an unsuccessful exit code of the tool). This behavior is not optimal with Java 17 onwards. The output can be lengthy and the informational messages very distracting. This is particularly true for larger projects. This improvement enables the developer/user to focus on the actual warnings or errors. > Parse stderr output and suppress informational lines > > > Key: MJAVADOC-721 > URL: https://issues.apache.org/jira/browse/MJAVADOC-721 > Project: Maven Javadoc Plugin > Issue Type: Improvement > Components: javadoc >Affects Versions: 3.4.0 >Reporter: Markus Spann >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.4.2 > > > From Java 17 the Javadoc tool prints informational output to stderr mixed > with actual errors and warnings (see > [JDK-8268774|https://bugs.openjdk.org/browse/JDK-8268774]/[JDK-8270831|https://bugs.openjdk.org/browse/JDK-8270831]). > Currently the maven-javadoc-plugin logs the complete content of the tool's > stderr as warning or includes it completely in the message of a > MavenReportException (in case of an unsuccessful exit code of the tool). This > behavior is not optimal with Java 17 onwards. > The output can be lengthy and the informational messages very distracting. > This is particularly true for larger projects. > This improvement enables the developer/user to focus on the actual warnings > or errors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MJAVADOC-721) Parse stderr output and suppress informational lines
[ https://issues.apache.org/jira/browse/MJAVADOC-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MJAVADOC-721: --- Assignee: Michael Osipov > Parse stderr output and suppress informational lines > > > Key: MJAVADOC-721 > URL: https://issues.apache.org/jira/browse/MJAVADOC-721 > Project: Maven Javadoc Plugin > Issue Type: Improvement > Components: javadoc >Affects Versions: 3.4.0 >Reporter: Markus Spann >Assignee: Michael Osipov >Priority: Minor > > From Java 17 the Javadoc tool prints informational output to stderr mixed > with actual errors and warnings (see JDK-8268774 / JDK-8270831). > Currently the maven-javadoc-plugin logs the complete content of the tool's > stderr as warning or includes it completely in the message of a > MavenReportException (in case of an unsuccessful exit code of the tool). This > behavior is not optimal with Java 17 onwards. > The output can be lengthy and the informational messages very distracting. > This is particularly true for larger projects. > This improvement enables the developer/user to focus on the actual warnings > or errors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAVADOC-721) Parse stderr output and suppress informational lines
[ https://issues.apache.org/jira/browse/MJAVADOC-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-721: Fix Version/s: 3.4.2 > Parse stderr output and suppress informational lines > > > Key: MJAVADOC-721 > URL: https://issues.apache.org/jira/browse/MJAVADOC-721 > Project: Maven Javadoc Plugin > Issue Type: Improvement > Components: javadoc >Affects Versions: 3.4.0 >Reporter: Markus Spann >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.4.2 > > > From Java 17 the Javadoc tool prints informational output to stderr mixed > with actual errors and warnings (see JDK-8268774 / JDK-8270831). > Currently the maven-javadoc-plugin logs the complete content of the tool's > stderr as warning or includes it completely in the message of a > MavenReportException (in case of an unsuccessful exit code of the tool). This > behavior is not optimal with Java 17 onwards. > The output can be lengthy and the informational messages very distracting. > This is particularly true for larger projects. > This improvement enables the developer/user to focus on the actual warnings > or errors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-javadoc-plugin] michael-o commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
michael-o commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960700249
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
I think this is incomplete. See:
```
13392 [WARNING] Javadoc Warnings
13393 [WARNING] Loading source files for package com.mycompany.myapp...
13394 -[WARNING] Constructing Javadoc information...
13395 -[WARNING] Building index for all the packages and classes...
13396 -[WARNING] Standard Doclet version 17.0.3+7-1
13397 -[WARNING] Building tree for all the packages and classes...
13398 -[WARNING] Generating
/var/osipovmi/Projekte/maven-javadoc-plugin/target/it/MJAVADOC-259/target/site/apidocs/com/mycompany/myapp/App.html...
13399 +[DEBUG] Constructing Javadoc information...
13400 +[DEBUG] Building index for all the packages and classes...
13401 +[DEBUG] Standard Doclet version 17.0.3+7-1
13402 +[DEBUG] Building tree for all the packages and classes...
13403 +[DEBUG] Generating
/var/osipovmi/Projekte/maven-javadoc-plugin/target/it/MJAVADOC-259/target/site/apidocs/com/mycompany/myapp/App.html...
```
see:
https://github.com/AdoptOpenJDK/openjdk-jdk11u/blob/master/src/jdk.javadoc/share/classes/jdk/javadoc/internal/tool/resources/javadoc.properties#L272
am I right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] michael-o commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
michael-o commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960700249
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
+|| str.startsWith( "Loading source file " )
Review Comment:
I think this is a typo. See:
```
13392 [WARNING] Javadoc Warnings
13393 [WARNING] Loading source files for package com.mycompany.myapp...
13394 -[WARNING] Constructing Javadoc information...
13395 -[WARNING] Building index for all the packages and classes...
13396 -[WARNING] Standard Doclet version 17.0.3+7-1
13397 -[WARNING] Building tree for all the packages and classes...
13398 -[WARNING] Generating
/var/osipovmi/Projekte/maven-javadoc-plugin/target/it/MJAVADOC-259/target/site/apidocs/com/mycompany/myapp/App.html...
13399 +[DEBUG] Constructing Javadoc information...
13400 +[DEBUG] Building index for all the packages and classes...
13401 +[DEBUG] Standard Doclet version 17.0.3+7-1
13402 +[DEBUG] Building tree for all the packages and classes...
13403 +[DEBUG] Generating
/var/osipovmi/Projekte/maven-javadoc-plugin/target/it/MJAVADOC-259/target/site/apidocs/com/mycompany/myapp/App.html...
```
am I right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] michael-o commented on a diff in pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
michael-o commented on code in PR #157:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/157#discussion_r960666436
##
src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java:
##
@@ -6144,6 +6171,23 @@ private boolean containsWarnings( String output )
}
}
+/**
+ * Determines whether the specified string is informational output of the
Javadoc tool.
+ *
+ * @param str string to check
+ * @return true if informational output, false if not or cannot be
determined
+ */
+private boolean isInfoOutput( String str )
+{
+return str == null
Review Comment:
Last question. Why do you consider a null string informational? Do you
expect a line to be `null` and not `""`?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-integration-testing] gnodet closed pull request #191: Move ITs to JDK 8 / JUnit 5
gnodet closed pull request #191: Move ITs to JDK 8 / JUnit 5 URL: https://github.com/apache/maven-integration-testing/pull/191 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] gnodet commented on pull request #191: Move ITs to JDK 8 / JUnit 5
gnodet commented on PR #191: URL: https://github.com/apache/maven-integration-testing/pull/191#issuecomment-1234283524 Duplicates #176 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MJAVADOC-726) Maven Java Doc Plug-in v3.4.0 downloads Log4j-1.2.12 dependency transitively
[ https://issues.apache.org/jira/browse/MJAVADOC-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-726: Fix Version/s: wontfix-candidate > Maven Java Doc Plug-in v3.4.0 downloads Log4j-1.2.12 dependency transitively > > > Key: MJAVADOC-726 > URL: https://issues.apache.org/jira/browse/MJAVADOC-726 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: jar, javadoc >Affects Versions: 3.4.0 > Environment: Windows 10 >Reporter: Yogesh Desai >Priority: Major > Labels: Vulnerability, vulnerability > Fix For: wontfix-candidate, waiting-for-feedback > > Attachments: log4j-1.2.12.png > > > I have observed that Maven Javadoc Plug-in v3.4.0 downloads Log4j-1.2.12 > dependency transitively in local maven repository i.e. .m2 folder upon > running maven update in eclipse IDE or from command line. Since Log4j-1.X is > strictly prohibited for use in many organisations, we had no other option > that not using the plugin. Please plan to fix this issue and get rid of the > log4j-1.X dependency. > *Steps to Reproduce-* > 1. Add maven javadoc plugin v3.4.0 in your project POM file > > org.apache.maven.plugins > maven-javadoc-plugin > 3.4.0 > > UTF-8 > -Xdoclint:none > > > > attach-javadocs > > jar > > > > > 2. Observe your local maven repository ie. .m2 folder and see if there are > any log4j-1.2.12 artifacts are present in log4j folder of it. If artifacts > are present already, delete them for now. > 3. Run maven update command for your project (additionally run maven install > command as needed) > 4. Observe your local maven repository ie. .m2 folder and see if there are > any log4j-1.2.12 artifacts are generated with latest timestamp inside log4j > folder. > Attached is the screenshot showing, maven javadoc plugin v3.4.0 used in > POM.xml and log4j-1.2.12 dependency getting downloaded in local maven > repository i.e. .m2 folder. > Let me know if any other information is required. Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-726) Maven Java Doc Plug-in v3.4.0 downloads Log4j-1.2.12 dependency transitively
[ https://issues.apache.org/jira/browse/MJAVADOC-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598955#comment-17598955 ] Michael Osipov commented on MJAVADOC-726: - Still waiting for your sample project... > Maven Java Doc Plug-in v3.4.0 downloads Log4j-1.2.12 dependency transitively > > > Key: MJAVADOC-726 > URL: https://issues.apache.org/jira/browse/MJAVADOC-726 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: jar, javadoc >Affects Versions: 3.4.0 > Environment: Windows 10 >Reporter: Yogesh Desai >Priority: Major > Labels: Vulnerability, vulnerability > Fix For: waiting-for-feedback > > Attachments: log4j-1.2.12.png > > > I have observed that Maven Javadoc Plug-in v3.4.0 downloads Log4j-1.2.12 > dependency transitively in local maven repository i.e. .m2 folder upon > running maven update in eclipse IDE or from command line. Since Log4j-1.X is > strictly prohibited for use in many organisations, we had no other option > that not using the plugin. Please plan to fix this issue and get rid of the > log4j-1.X dependency. > *Steps to Reproduce-* > 1. Add maven javadoc plugin v3.4.0 in your project POM file > > org.apache.maven.plugins > maven-javadoc-plugin > 3.4.0 > > UTF-8 > -Xdoclint:none > > > > attach-javadocs > > jar > > > > > 2. Observe your local maven repository ie. .m2 folder and see if there are > any log4j-1.2.12 artifacts are present in log4j folder of it. If artifacts > are present already, delete them for now. > 3. Run maven update command for your project (additionally run maven install > command as needed) > 4. Observe your local maven repository ie. .m2 folder and see if there are > any log4j-1.2.12 artifacts are generated with latest timestamp inside log4j > folder. > Attached is the screenshot showing, maven javadoc plugin v3.4.0 used in > POM.xml and log4j-1.2.12 dependency getting downloaded in local maven > repository i.e. .m2 folder. > Let me know if any other information is required. Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1126) Bump maven-shared-components from 36 to 37
[ https://issues.apache.org/jira/browse/MSHARED-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1126. Resolution: Fixed > Bump maven-shared-components from 36 to 37 > -- > > Key: MSHARED-1126 > URL: https://issues.apache.org/jira/browse/MSHARED-1126 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-verifier >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-verifier-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1126) Bump maven-shared-components from 36 to 37
Slawomir Jaranowski created MSHARED-1126: Summary: Bump maven-shared-components from 36 to 37 Key: MSHARED-1126 URL: https://issues.apache.org/jira/browse/MSHARED-1126 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-verifier Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: maven-verifier-2.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-verifier] slawekjaranowski merged pull request #32: Bump maven-shared-components from 36 to 37
slawekjaranowski merged PR #32: URL: https://github.com/apache/maven-verifier/pull/32 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MJAVADOC-722) Allow Logging Javadoc Warnings and Errors to File
[ https://issues.apache.org/jira/browse/MJAVADOC-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598900#comment-17598900 ] Alan Zimmer commented on MJAVADOC-722: -- Thanks for pointing that issue out! Sounds like this would be best to include the work from that change to make the error messaging more parse-able then to write it to a persistent file. Am I understanding you comment correctly? > Allow Logging Javadoc Warnings and Errors to File > - > > Key: MJAVADOC-722 > URL: https://issues.apache.org/jira/browse/MJAVADOC-722 > Project: Maven Javadoc Plugin > Issue Type: New Feature > Components: javadoc >Reporter: Alan Zimmer >Priority: Trivial > > Allow for Javadoc generation, either implicitly or through a new > configuration, to generate a file containing the warnings and errors that > were found during Javadoc generation. Possibly following a similar pattern to > the argfile and options that are generated containing parameters passed to > Javadoc create an errors files that will be placed in the Javadoc output > folder that is ignored during Javadoc JAR creation. > > This change would allow for CI systems to run Javadoc builds in parallel > while still easily capturing any errors without the need for complex logging > systems and would strongly ensure that there is a unique error report for > each project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-pmd-plugin] adangel merged pull request #88: Bump animal-sniffer-maven-plugin from 1.21 to 1.22
adangel merged PR #88: URL: https://github.com/apache/maven-pmd-plugin/pull/88 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] adangel merged pull request #57: Bump wiremock from 1.49 to 2.27.2
adangel merged PR #57: URL: https://github.com/apache/maven-pmd-plugin/pull/57 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] dependabot[bot] commented on pull request #89: Bump slf4jVersion from 1.7.36 to 2.0.0
dependabot[bot] commented on PR #89: URL: https://github.com/apache/maven-pmd-plugin/pull/89#issuecomment-1233890107 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] slachiewicz closed pull request #89: Bump slf4jVersion from 1.7.36 to 2.0.0
slachiewicz closed pull request #89: Bump slf4jVersion from 1.7.36 to 2.0.0 URL: https://github.com/apache/maven-pmd-plugin/pull/89 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] adangel commented on pull request #57: Bump wiremock from 1.49 to 2.27.2
adangel commented on PR #57: URL: https://github.com/apache/maven-pmd-plugin/pull/57#issuecomment-1233879011 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] adangel commented on pull request #88: Bump animal-sniffer-maven-plugin from 1.21 to 1.22
adangel commented on PR #88: URL: https://github.com/apache/maven-pmd-plugin/pull/88#issuecomment-1233878732 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-354. - Fix Version/s: 3.19.0 Resolution: Fixed > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-353.
---
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.19.0
>
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error: urls[29] =
[jira] [Updated] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-353:
Fix Version/s: 3.19.0
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.19.0
>
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
>
[jira] [Closed] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-354. --- > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-javadoc-plugin] sman-81 commented on pull request #157: [MJAVADOC-721] Parse stderr output and suppress informational lines
sman-81 commented on PR #157: URL: https://github.com/apache/maven-javadoc-plugin/pull/157#issuecomment-1233875998 Good morning @michael-o, are you willing to merge this pr or are there ToDos left for me? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MJAVADOC-722) Allow Logging Javadoc Warnings and Errors to File
[ https://issues.apache.org/jira/browse/MJAVADOC-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598785#comment-17598785 ] Markus Spann commented on MJAVADOC-722: --- What you are aiming to achieve might not be as simple as it seems. Take a look at MJAVADOC-721. > Allow Logging Javadoc Warnings and Errors to File > - > > Key: MJAVADOC-722 > URL: https://issues.apache.org/jira/browse/MJAVADOC-722 > Project: Maven Javadoc Plugin > Issue Type: New Feature > Components: javadoc >Reporter: Alan Zimmer >Priority: Trivial > > Allow for Javadoc generation, either implicitly or through a new > configuration, to generate a file containing the warnings and errors that > were found during Javadoc generation. Possibly following a similar pattern to > the argfile and options that are generated containing parameters passed to > Javadoc create an errors files that will be placed in the Javadoc output > folder that is ignored during Javadoc JAR creation. > > This change would allow for CI systems to run Javadoc builds in parallel > while still easily capturing any errors without the need for complex logging > systems and would strongly ensure that there is a unique error report for > each project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598783#comment-17598783 ] Hudson commented on MPMD-354: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #56 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/56/ > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-verifier] slachiewicz merged pull request #38: Bump junit-jupiter from 5.8.0 to 5.9.0
slachiewicz merged PR #38: URL: https://github.com/apache/maven-verifier/pull/38 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598778#comment-17598778 ] Andreas Dangel commented on MPMD-354: - Fixed with: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=ebd3579da3099ab558e4414029ae2149eebc4178 > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel resolved MPMD-353.
-
Resolution: Fixed
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error: urls[29] =
>
[GitHub] [maven-pmd-plugin] adangel merged pull request #92: [MPMD-354] - Upgrade to PMD 6.49.0
adangel merged PR #92: URL: https://github.com/apache/maven-pmd-plugin/pull/92 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598775#comment-17598775
]
Hudson commented on MPMD-353:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #55
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/55/
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
>
[jira] [Commented] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598771#comment-17598771
]
Andreas Dangel commented on MPMD-353:
-
Fixed with:
https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=7b4c330399faa65b8800b6a3dfd9d60a661178b8
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
>
[GitHub] [maven-pmd-plugin] adangel merged pull request #91: [MPMD-353] - API incompatibility with jansi after upgrading m-shared-…
adangel merged PR #91: URL: https://github.com/apache/maven-pmd-plugin/pull/91 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-690) Change package from org.apache.maven.it to org.apache.maven.shared.verifier
[
https://issues.apache.org/jira/browse/MSHARED-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598768#comment-17598768
]
Hudson commented on MSHARED-690:
Build succeeded in Jenkins: Maven » Maven TLP » maven-verifier » master #29
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-verifier/job/master/29/
> Change package from org.apache.maven.it to org.apache.maven.shared.verifier
> ---
>
> Key: MSHARED-690
> URL: https://issues.apache.org/jira/browse/MSHARED-690
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-verifier
>Affects Versions: maven-verifier-1.7.0
>Reporter: Karl Heinz Marbaise
>Assignee: Robert Scholte
>Priority: Major
> Fix For: maven-verifier-2.0.0
>
>
> I think it makes sense to change the package name from
> {{org.apache.maven.it}} to {{org.apache.maven.shared.verifier}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-verifier] gnodet merged pull request #36: [MSHARED-690] Change package from org.apache.maven.it to o.a.m.shared.verifier
gnodet merged PR #36: URL: https://github.com/apache/maven-verifier/pull/36 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] adangel commented on pull request #91: [MPMD-353] - API incompatibility with jansi after upgrading m-shared-…
adangel commented on PR #91: URL: https://github.com/apache/maven-pmd-plugin/pull/91#issuecomment-1233826296 > I wonder why it was necessary before? Was behavior of Jansi in previously different? I can't recall anymore, why I thought this was necessary. The coloring seems to be working correctly automatically. I've also tested older maven versions, but didn't figure out any thing. I'll simply fix the issue then by merging this PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-690) go-offline fails when optional dependencies cannot be resolved
[
https://issues.apache.org/jira/browse/MDEP-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598764#comment-17598764
]
Menno commented on MDEP-690:
This bug also affects version 3.3.0
> go-offline fails when optional dependencies cannot be resolved
> --
>
> Key: MDEP-690
> URL: https://issues.apache.org/jira/browse/MDEP-690
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
>Affects Versions: 3.1.2
>Reporter: Stephan Schroevers
>Priority: Major
>
> Consider the following dummy project:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> com.example
> example
> 0.0.1-SNAPSHOT
>
>
> io.projectreactor.addons
> reactor-extra
> 3.3.3.RELEASE
>
>
>
> {code}
> Running {{org.apache.maven.plugins:maven-dependency-plugin:3.1.1:go-offline}}
> against this project passes. With version 3.1.2 the goal fails with:
> {noformat}
> org.eclipse.aether.resolution.DependencyResolutionException: Could not find
> artifact org.eclipse.swt:org.eclipse.swt.gtk.linux.x86_64:jar:4.5.2 in
> central (https://repo.maven.apache.org/maven2)
> {noformat}
> The reason for the failure appears to be that {{reactor-extra}} declares an
> [optional|https://repo1.maven.org/maven2/io/projectreactor/addons/reactor-extra/3.3.3.RELEASE/reactor-extra-3.3.3.RELEASE.pom]
> dependency on {{org.eclipse.swt.gtk.linux.x86_64}}, an artifact which is not
> present in Maven Central.
> It'd be nice if the version 3.1.1 behavior of the plugin could be reinstated.
> Alternatively (perhaps better?) it should be possible to conditionally
> exclude optional dependencies, just like the goal allows one to exclude
> dependencies by artifact ID, group ID, classifier, scope and type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-pmd-plugin] adangel opened a new pull request, #92: [MPMD-354] - Upgrade to PMD 6.49.0
adangel opened a new pull request, #92: URL: https://github.com/apache/maven-pmd-plugin/pull/92 https://issues.apache.org/jira/browse/MPMD-354 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MPMD) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MPMD-XXX] - Subject of the JIRA Ticket`, where you replace `MPMD-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-354: Fix Version/s: (was: 3.18.0) > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-354) Upgrade to PMD 6.49.0
Andreas Dangel created MPMD-354: --- Summary: Upgrade to PMD 6.49.0 Key: MPMD-354 URL: https://issues.apache.org/jira/browse/MPMD-354 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
