[jira] [Commented] (MJAVADOC-578) Groups parameter is not compatibile with Surefire
[ https://issues.apache.org/jira/browse/MJAVADOC-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782966#comment-16782966 ] Tibor Digana commented on MJAVADOC-578: --- [~eolivelli] Sorry, I did not see the email from this Jira. We will change system property for Surefire groups in the last 3.0.0-M6 as external backwards compatibility. So far it's better to break only internal backwards compatibility. This strategy makes Surefire users feeling still comfortable. > Groups parameter is not compatibile with Surefire > - > > Key: MJAVADOC-578 > URL: https://issues.apache.org/jira/browse/MJAVADOC-578 > Project: Maven Javadoc Plugin > Issue Type: Improvement > Components: javadoc >Affects Versions: 3.0.1 >Reporter: Enrico Olivelli >Assignee: Enrico Olivelli >Priority: Critical > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > If you run: > mvn javadoc:javadoc test -Dgroups=MyTestCategory you get this error > Failed to execute goal > org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on > project magnews.embedded: Unable to parse configuration of mojo > org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar for parameter #: > Cannot find default setter in class > org.apache.maven.plugins.javadoc.options.Group -> [Help 1] > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MCHANGES-396) Upgrade GitHub client to 5.3.0
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782764#comment-16782764 ] Michael Osipov edited comment on MCHANGES-396 at 3/3/19 4:01 PM: - An upgrade won't be possible until 5.3.0 is released. was (Author: michael-o): An upgrade won't be possible until 5.3.0 won't be released. > Upgrade GitHub client to 5.3.0 > -- > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Priority: Major > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MCHANGES-396) Upgrade GitHub client to 5.3.0
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MCHANGES-396: --- Assignee: (was: Michael Osipov) > Upgrade GitHub client to 5.3.0 > -- > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Priority: Major > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-396) Upgrade GitHub client to 5.3.0
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MCHANGES-396: Summary: Upgrade GitHub client to 5.3.0 (was: Upgrade GitHub client to) > Upgrade GitHub client to 5.3.0 > -- > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCHANGES-396) Upgrade GitHub client to 5.3.0
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782764#comment-16782764 ] Michael Osipov commented on MCHANGES-396: - An upgrade won't be possible until 5.3.0 won't be released. > Upgrade GitHub client to 5.3.0 > -- > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-396) Upgrade GitHub client to 5.3.0
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MCHANGES-396: Fix Version/s: (was: 3.0.0) > Upgrade GitHub client to 5.3.0 > -- > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Assignee: Michael Osipov >Priority: Major > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-396) Upgrade GitHub client to
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MCHANGES-396: Summary: Upgrade GitHub client to (was: Update GitHub client) > Upgrade GitHub client to > > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MJAVADOC-581) critical error with non-ASCII charcters in directory name: cannot read Input length = 1
[
https://issues.apache.org/jira/browse/MJAVADOC-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-581:
Fix Version/s: waiting-for-feedback
> critical error with non-ASCII charcters in directory name: cannot read Input
> length = 1
> ---
>
> Key: MJAVADOC-581
> URL: https://issues.apache.org/jira/browse/MJAVADOC-581
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.0.1
>Reporter: Garret Wilson
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> This is a critical bug that breaks the build. I originally posted this [on
> Stack Overflow|https://stackoverflow.com/q/53449049/421049] but got no
> response.
> I'm using OpenJDK 11 on Windows 10. I have a very simple POM, for a single
> Java file, that generates Javadocs. Here is an extract:
> {code:xml}
>
> UTF-8
> 11
> 11
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.0.1
>
>
>
> jar
>
>
>
>
>
>
> {code}
> Strangely just running {{mvn clean package}} causes an error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default) on project
> foobar: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read Input length = 1
> [ERROR]
> [ERROR] Command line was: C:\bin\jdk-11\bin\javadoc.exe @options @packages
> {noformat}
> In {{target/apidocs}} there are only three files: {{javadoc.bat}},
> {{options}}, and {{packages}}. The {{options}} file is the most interesting.
> It explicitly says {{UTF-8}} everywhere, as it should. But look at these
> lines:
> {noformat}
> -sourcepath
> C:/projects/li��o 1/src/main/java
> {noformat}
> This project is in {{C:\projects\lição 1}}. It appears that somewhere along
> the chain Java or Maven or the Javadoc plugin didn't correctly convert the
> directory name to UTF-8.
> Sure enough; when I renamed the directories in Windows to remove non-ASCII
> characters, {{mvn clean package}} worked just fine.
> This would seem like a blatant bug; once Maven starts, everything should be
> UTF-8 throughout.
> One [answer on Stack Overflow|https://stackoverflow.com/a/53528778/421049]
> gives you a hint of what's going wrong.
> In any case, I consider this to be a huge bug related to fundamental
> functioning. It absolutely must be fixed. Users can't suddenly see their
> build broken if their directory name has a non-ASCII character in it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MJAVADOC-582) Getting "Unsupported class file major version 55" when trying to run Javadoc
[ https://issues.apache.org/jira/browse/MJAVADOC-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MJAVADOC-582. --- Resolution: Duplicate Assignee: Robert Scholte > Getting "Unsupported class file major version 55" when trying to run Javadoc > > > Key: MJAVADOC-582 > URL: https://issues.apache.org/jira/browse/MJAVADOC-582 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: javadoc >Affects Versions: 3.0.1 > Environment: I have managed to reproduce this with WIndows and Linux > computers running Java 11. With Java 10 it seems to work fine. >Reporter: Keeyan Nejad >Assignee: Robert Scholte >Priority: Minor > > When running `mvn javadoc:javadoc -e` on a Java 11 project I get the below > error. This seems to only be happening with Java 11. The maven plugin works > fine for Java 10. > I have stripped my project down to the bare minimum where I could reproduce > it. Currently the project has 2 sub modules along with a pom file (content > listed below) > pom.xml > core/ (sub-module) > emulator/ (sub-module) > ``` > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc (default-cli) on > project emulator: Execution default-cli of goal > org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc failed: > Unsupported class file major version 55 -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc > (default-cli) on project emulator: Execution default-cli of goal > org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc failed: > Unsupported class file major version 55 > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:215) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:566) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java: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.PluginExecutionException: Execution > default-cli of goal > org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc failed: > Unsupported class file major version 55 > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:148) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute
[jira] [Created] (MJAVADOC-582) Getting "Unsupported class file major version 55" when trying to run Javadoc
Keeyan Nejad created MJAVADOC-582: - Summary: Getting "Unsupported class file major version 55" when trying to run Javadoc Key: MJAVADOC-582 URL: https://issues.apache.org/jira/browse/MJAVADOC-582 Project: Maven Javadoc Plugin Issue Type: Bug Components: javadoc Affects Versions: 3.0.1 Environment: I have managed to reproduce this with WIndows and Linux computers running Java 11. With Java 10 it seems to work fine. Reporter: Keeyan Nejad When running `mvn javadoc:javadoc -e` on a Java 11 project I get the below error. This seems to only be happening with Java 11. The maven plugin works fine for Java 10. I have stripped my project down to the bare minimum where I could reproduce it. Currently the project has 2 sub modules along with a pom file (content listed below) pom.xml core/ (sub-module) emulator/ (sub-module) ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc (default-cli) on project emulator: Execution default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc failed: Unsupported class file major version 55 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc (default-cli) on project emulator: Execution default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc failed: Unsupported class file major version 55 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:566) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java: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.PluginExecutionException: Execution default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc failed: Unsupported class file major version 55 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at
[jira] [Commented] (MNG-6530) Regression in ProjectBuilder when file change between invocations (introduced by MNG-6311)
[ https://issues.apache.org/jira/browse/MNG-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782697#comment-16782697 ] Hudson commented on MNG-6530: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Regression in ProjectBuilder when file change between invocations (introduced > by MNG-6311) > -- > > Key: MNG-6530 > URL: https://issues.apache.org/jira/browse/MNG-6530 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.6.0 >Reporter: Mickael Istria >Assignee: Michael Osipov >Priority: Critical > Fix For: 3.6.1 > > Time Spent: 10m > Remaining Estimate: 0h > > The patch for MNG-6311 introduces a regression in ProjectBuilder due to > missing cache invalidation when content change. > It was identified as a potential issue by [~fbricon] on Oct 10, yet no > further investigation happened and Maven 3.6.0 was released with this > regression. > This regression prevents Eclipse m2e (and probably most APIs using the > ProjectBuilder for a longer session which allows pom.xml files to be > modified) from adopting 3.6.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6559) Mailing list URL is incorrect in CONTRIBUTING.md
[ https://issues.apache.org/jira/browse/MNG-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782699#comment-16782699 ] Hudson commented on MNG-6559: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Mailing list URL is incorrect in CONTRIBUTING.md > > > Key: MNG-6559 > URL: https://issues.apache.org/jira/browse/MNG-6559 > Project: Maven > Issue Type: Bug > Components: Documentation: General >Reporter: John Lin >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > The mailing list URL in CONTRIBUTING.md is currently > [https://maven.apache.org/mail-lists.html], but it should have been > [https://maven.apache.org/mailing-lists.html]. > Besides, I also found that problem in > [https://github.com/apache/maven/tree/master/apache-maven|https://github.com/apache/maven/tree/master/apache-maven]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6069) Migrate to non deprecated parts of Commons CLI
[
https://issues.apache.org/jira/browse/MNG-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782700#comment-16782700
]
Hudson commented on MNG-6069:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> Migrate to non deprecated parts of Commons CLI
> --
>
> Key: MNG-6069
> URL: https://issues.apache.org/jira/browse/MNG-6069
> Project: Maven
> Issue Type: Improvement
> Components: Embedding
>Affects Versions: 3.3.9, 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.x / Backlog
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment all parts of {{OptionBuilder...}} are marked deprecated in
> {{CLIManager}}. They should be migrated to:
> {code:java}
> Option.builder( HELP ).longOpt( "help" ).desc( "Display help information"
> ).build()
> {code}
> Ensure that the following command succeeds: {{mvn -X -D x=1 -D y=2 test}} (
> watch out for the space after {{-D}} )
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6261) Relative parent POM resolution failing in 3.5.0 with complex multimodule builds
[
https://issues.apache.org/jira/browse/MNG-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782689#comment-16782689
]
Hudson commented on MNG-6261:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> Relative parent POM resolution failing in 3.5.0 with complex multimodule
> builds
> ---
>
> Key: MNG-6261
> URL: https://issues.apache.org/jira/browse/MNG-6261
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Dawid Weiss
>Assignee: Robert Scholte
>Priority: Minor
> Labels: up-for-grabs
> Fix For: 3.6.1
>
> Attachments: capture-6.png, repro.zip
>
>
> In my effort to upgrade an existing (fairly complex) Maven build to Java
> 1.9.0 I updated Maven to 3.5.0 (from 3.3.9). Unfortunately I get errors when
> the project's modules are resolved:
> {noformat}
> > mvn validate
> [FATAL] Non-resolvable parent POM for
> com.carrotsearch.lingo4g:lingo4g-public-bom:[unknown-version]: Could not find
> artifact com.carrotsearch.lingo4g:lingo4g-public:pom:1.6.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 5, column 11
> ...
> (and many follow).
> {noformat}
> This build has a correct pom parent-structure (a tree), but is fairly complex
> -- the submodule hierarchy is not aligned with parent-child pom hierarchy
> (it's best to look at the repro code to understand how it's structured).
> However, it's been working correctly with all prior Maven versions and I
> wonder if it's a regression bug or maybe underspecified Maven requirement
> (that should be enforced with a warning and not lead to this odd runtime
> message).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6533) ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in exception report
[
https://issues.apache.org/jira/browse/MNG-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782701#comment-16782701
]
Hudson commented on MNG-6533:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in
> exception report
>
>
> Key: MNG-6533
> URL: https://issues.apache.org/jira/browse/MNG-6533
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.5.4, 3.6.0
>Reporter: Mickael Istria
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To save a lot of CPU and RAM in Eclipse m2e, we're trying to use
> {{ProjectBuilder.build(List projects ...)}} instead of sequencing
> multiple {{Projectbuilder.build(File singleProject...)}}. This has a big
> positive impact on m2e.
> However, we noticed that when the operation is failing in some case because
> pom is incomplete (which is a pretty usual state in the IDE), the
> multi-projects method does not return the MavenProject in the
> {{ProjectBuildingException.getResults()}}, while the single-project method
> does.
> Adding MavenProject for the multi-project {{ProjectBuilder.build(...)}} would
> allow m2e to use this method and save ~75% RAM and CPU in many operations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6526) Upgrade to Wagon 3.3.1
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782694#comment-16782694 ] Hudson commented on MNG-6526: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Upgrade to Wagon 3.3.1 > -- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6593) track input location for super-pom
[ https://issues.apache.org/jira/browse/MNG-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782708#comment-16782708 ] Hudson commented on MNG-6593: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > track input location for super-pom > -- > > Key: MNG-6593 > URL: https://issues.apache.org/jira/browse/MNG-6593 > Project: Maven > Issue Type: Improvement > Components: Inheritance and Interpolation >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 3.6.1 > > > while working on MPH-160, found that input location from > [super-pom|https://maven.apache.org/ref/current/maven-model-builder/super-pom.html] > content is not tracked -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6573) Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI
[ https://issues.apache.org/jira/browse/MNG-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782703#comment-16782703 ] Hudson commented on MNG-6573: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI > -- > > Key: MNG-6573 > URL: https://issues.apache.org/jira/browse/MNG-6573 > Project: Maven > Issue Type: Task > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.6.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Maven Core Integration Test passed ok for Linux and Windows for Java 7, 8, > 11, 12-ea, 13-ea. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6529) ProjectBuilder.build(List projects, boolean, ProjectBuildingRequest) doesn't honor ProjectBuildingRequest.isResolveDependencies()
[
https://issues.apache.org/jira/browse/MNG-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782690#comment-16782690
]
Hudson commented on MNG-6529:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> ProjectBuilder.build(List projects, boolean, ProjectBuildingRequest)
> doesn't honor ProjectBuildingRequest.isResolveDependencies()
> ---
>
> Key: MNG-6529
> URL: https://issues.apache.org/jira/browse/MNG-6529
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.5.3
>Reporter: Mickael Istria
>Assignee: Robert Scholte
>Priority: Critical
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I'm willing to update Eclipse m2e to take advantage of the
> {{ProjectBuilder.build(List project, boolean, ProjectBuildingRequest)}}
> to avoid duplication of MavenProject in the IDE caused by
> {{ProjectBuilder.build(File singleFile, ProjectBuildingRequest)}}.
> It's already measured to have drastically good impact on the IDE, as
> explained in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=515668#c20] and
> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=515668#c38].
> However, using this cause regressions because the multi-projects entry-point
> method seems to totally ignore the
> {{ProjectBuildRequest.isResolveDependencies()}} flag and never returns a
> valid list of {{MavenProject.getArtifacts()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782704#comment-16782704
]
Hudson commented on MNG-6558:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6256) Maven script can break if "-f" path contains special characters
[
https://issues.apache.org/jira/browse/MNG-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782698#comment-16782698
]
Hudson commented on MNG-6256:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> Maven script can break if "-f" path contains special characters
>
>
> Key: MNG-6256
> URL: https://issues.apache.org/jira/browse/MNG-6256
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 10 with PowerShell
>Reporter: Christoph Etzel
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Executing maven on Windows using the {{\-f}} or {{--file}} parameter to
> specify an alternate POM file can break the script if the path contains
> special characters.
> It was originally discovered on a Windows Jenkins instance with working
> directory located under C:\Program Files (x86)\Jenkins..
> Example:
> {code:java}mvn -f "folderWithClosing)Bracket/pomFolder"{code}
> Command line output: {{"Bracket/pomFolder" kann syntaktisch an dieser Stelle
> nicht verarbeitet werden.}}
> Just for fun: Starting calc from maven script using {{\-f}}
> {code:java}mvn -f " ' & start calc"{code}
> Command line output: {{POM file '}} and a new calculator process
> The bug was introduced with commit
> https://github.com/apache/maven/commit/f8ab2a650f32d5d87126d341d9bbfccbf99fd0ca
> for issue MNG-5889.
> Workaround: Use maven 3.3.9 or below
> Possible fix: Escape {{%FILE_ARG%}} and {{%POM_DIR%}} with {{"}} in {{echo}}
> commands in {{maven.cmd}} (line 120 and 129).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6213) Maven doesn't check the validity of scope value
[
https://issues.apache.org/jira/browse/MNG-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782693#comment-16782693
]
Hudson commented on MNG-6213:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> Maven doesn't check the validity of scope value
> ---
>
> Key: MNG-6213
> URL: https://issues.apache.org/jira/browse/MNG-6213
> Project: Maven
> Issue Type: Improvement
> Components: POM
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T01:41:47+09:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.4", arch: "x86_64", family: "mac"
>Reporter: Jin Kwon
>Assignee: Michael Osipov
>Priority: Minor
> Labels: scope
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I accidentally put a wrong value into the {{scope}} tag.
> {code:xml}
>
>
>
> org.glassfish.jersey
> jersey-bom
> 2.26-b03
> pom
> include
>
>
>
> {code}
> And, of course, my dependency doesn't work.
> {code:xml}
>
>
> org.glassfish.jersey.core
> jersey-common
> test
>
>
> {code}
> {code}
> 'dependencies.dependency.version' for
> org.glassfish.jersey.core:jersey-common:jar is missing.
> {code}
> Maven should complains about the wrong value of {{include}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6520) Update assembly descriptors to 2.0.0
[ https://issues.apache.org/jira/browse/MNG-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782695#comment-16782695 ] Hudson commented on MNG-6520: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Update assembly descriptors to 2.0.0 > > > Key: MNG-6520 > URL: https://issues.apache.org/jira/browse/MNG-6520 > Project: Maven > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Update namespaces to the version compatible with 3.0+ maven-assembly-plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6495) ModelResolver cannot be null
[
https://issues.apache.org/jira/browse/MNG-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782707#comment-16782707
]
Hudson commented on MNG-6495:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> ModelResolver cannot be null
>
>
> Key: MNG-6495
> URL: https://issues.apache.org/jira/browse/MNG-6495
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap Build
>Affects Versions: 3.5.4
>Reporter: Elliotte Rusty Harold
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.1
>
>
> Got this exception stacktrace while writing some of my own code today:
> {noformat}
> Exception in thread "main" java.lang.NullPointerException:
> request.modelResolver cannot be null (parent POM
> com.google.guava:guava-parent:26.0-jre and POM
> com.google.guava:guava:[unknown-version])
> at org.apache.commons.lang3.Validate.notNull(Validate.java:225)
> at
> org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1046)
> at
> org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:830)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:332)
> at
> com.google.cloud.tools.opensource.dependencies.MetadataExplorer.main(MetadataExplorer.java:50)
> {noformat}
> No big deal except that the JavaDoc at
> [ModelBuildingRequest|http://maven.apache.org/ref/3.5.4/maven-model-builder/apidocs/org/apache/maven/model/building/ModelBuildingRequest.html]
> says "The model resolver to use, may be null."
> Not sure whether to update the docs or the code here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6544) Replace CacheUtils#{eq,hash} with Objects
[
https://issues.apache.org/jira/browse/MNG-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782692#comment-16782692
]
Hudson commented on MNG-6544:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> Replace CacheUtils#{eq,hash} with Objects
> -
>
> Key: MNG-6544
> URL: https://issues.apache.org/jira/browse/MNG-6544
> Project: Maven
> Issue Type: Task
> Components: core
>Affects Versions: 3.6.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.1
>
>
> {{Objects}} now sports idiot-safe {{equals}} and {{hashCode}} just like
> {{CacheUtils}}. We can swap out and deprecate/delete our code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6548) Lifecycle plugin version upgrades
[ https://issues.apache.org/jira/browse/MNG-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782696#comment-16782696 ] Hudson commented on MNG-6548: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Lifecycle plugin version upgrades > - > > Key: MNG-6548 > URL: https://issues.apache.org/jira/browse/MNG-6548 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.7.0-candidate > > > Regular plugin upgrades to absorb changes if plugin version is not specified > in the client POM. > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/lifecycles.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6571) Maven memory consumption issue
[ https://issues.apache.org/jira/browse/MNG-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782705#comment-16782705 ] Hudson commented on MNG-6571: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Maven memory consumption issue > -- > > Key: MNG-6571 > URL: https://issues.apache.org/jira/browse/MNG-6571 > Project: Maven > Issue Type: Wish >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 3.6.1 > > Attachments: Maven-Reactor-Dump-Patched.png, Maven-Reactor-Dump.png > > > as reported on Users list: > https://lists.apache.org/thread.html/7d75142448b3c234742bdfd3c743e2f62065fe8e0a313905cbbb2523@%3Cusers.maven.apache.org%3E > then with details on Dev list: > https://lists.apache.org/thread.html/34b64295238594e554f1f2f119848bce3b60d4e1e22e09f26aa64166@%3Cdev.maven.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6591) Upgrade to Wagon 3.3.2
[ https://issues.apache.org/jira/browse/MNG-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782706#comment-16782706 ] Hudson commented on MNG-6591: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Upgrade to Wagon 3.3.2 > -- > > Key: MNG-6591 > URL: https://issues.apache.org/jira/browse/MNG-6591 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Version 3.3.1 contains a regression which needed to be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782691#comment-16782691 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5995) Maven itself cannot run without maven-compat
[
https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782702#comment-16782702
]
Hudson commented on MNG-5995:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/
> Maven itself cannot run without maven-compat
>
>
> Key: MNG-5995
> URL: https://issues.apache.org/jira/browse/MNG-5995
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap Build, core
>Affects Versions: 3.3.9
>Reporter: Robert Scholte
>Assignee: Sylwester Lachiewicz
>Priority: Critical
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For all the 3.0 versions of the maven-plugins we require to not depend on
> maven-compat anymore. However, the Maven distribution still requires
> maven-compat. A simple proof: remove {{lib/maven-compat-3.x.y}} and execute
> {{mvn validate}}.
> You'll get the following exception:
> {noformat}[WARNING] Error injecting:
> org.apache.maven.project.DefaultProjectBuildingHelper
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> 1) No implementation for org.apache.maven.repository.RepositorySystem was
> bound.
> while locating
> org.apache.maven.project.DefaultProjectBuildingHelper{noformat}
> Reason: there's only one implementation: o.a.m.r.l.LegacyRepositorySystem,
> which is part of maven-compat.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6294) Convert MavenPluginValidator into a plexus component
[ https://issues.apache.org/jira/browse/MNG-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782709#comment-16782709 ] Hudson commented on MNG-6294: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/ > Convert MavenPluginValidator into a plexus component > > > Key: MNG-6294 > URL: https://issues.apache.org/jira/browse/MNG-6294 > Project: Maven > Issue Type: Improvement > Components: core >Reporter: Michael Simacek >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.6.x-candidate > > > [XMvn|https://github.com/fedora-java/xmvn] is a maven extension that helps > with creating RPM packages. In order to comply with packaging requirements, > it needs to relax some checks that maven does. One of those is plugin > validation done in MavenPluginValidator class. Currently, it overrides that > by shadowing the class on the classpath, which is a hack. It would help if > MavenPluginValidator was a plexus component and thus the implementation could > be selected by configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-581) critical error with non-ASCII charcters in directory name: cannot read Input length = 1
[
https://issues.apache.org/jira/browse/MJAVADOC-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782683#comment-16782683
]
Michael Osipov commented on MJAVADOC-581:
-
Please try MJAVADOC 3.1.0 from source. I think this issue has been already
addressed in MJAVADOC-544.
> critical error with non-ASCII charcters in directory name: cannot read Input
> length = 1
> ---
>
> Key: MJAVADOC-581
> URL: https://issues.apache.org/jira/browse/MJAVADOC-581
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.0.1
>Reporter: Garret Wilson
>Priority: Critical
>
> This is a critical bug that breaks the build. I originally posted this [on
> Stack Overflow|https://stackoverflow.com/q/53449049/421049] but got no
> response.
> I'm using OpenJDK 11 on Windows 10. I have a very simple POM, for a single
> Java file, that generates Javadocs. Here is an extract:
> {code:xml}
>
> UTF-8
> 11
> 11
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 3.0.1
>
>
>
> jar
>
>
>
>
>
>
> {code}
> Strangely just running {{mvn clean package}} causes an error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default) on project
> foobar: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - cannot read Input length = 1
> [ERROR]
> [ERROR] Command line was: C:\bin\jdk-11\bin\javadoc.exe @options @packages
> {noformat}
> In {{target/apidocs}} there are only three files: {{javadoc.bat}},
> {{options}}, and {{packages}}. The {{options}} file is the most interesting.
> It explicitly says {{UTF-8}} everywhere, as it should. But look at these
> lines:
> {noformat}
> -sourcepath
> C:/projects/li��o 1/src/main/java
> {noformat}
> This project is in {{C:\projects\lição 1}}. It appears that somewhere along
> the chain Java or Maven or the Javadoc plugin didn't correctly convert the
> directory name to UTF-8.
> Sure enough; when I renamed the directories in Windows to remove non-ASCII
> characters, {{mvn clean package}} worked just fine.
> This would seem like a blatant bug; once Maven starts, everything should be
> UTF-8 throughout.
> One [answer on Stack Overflow|https://stackoverflow.com/a/53528778/421049]
> gives you a hint of what's going wrong.
> In any case, I consider this to be a huge bug related to fundamental
> functioning. It absolutely must be fixed. Users can't suddenly see their
> build broken if their directory name has a non-ASCII character in it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #218: [SUREFIRE-1004] Support full gavtc format for dependenciesToScan
Tibor17 commented on issue #218: [SUREFIRE-1004] Support full gavtc format for dependenciesToScan URL: https://github.com/apache/maven-surefire/pull/218#issuecomment-469015594 @rehevkor5 @bindul Thx for your great work and contribution. Let's keeps such positive commits coming next time too.. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] eolivelli commented on issue #3: [MSCRIPTING-1] Squashed all commits from MSCRIPTING-1 branch
eolivelli commented on issue #3: [MSCRIPTING-1] Squashed all commits from MSCRIPTING-1 branch URL: https://github.com/apache/maven-scripting-plugin/pull/3#issuecomment-469012509 Sure. Will do tomorrow 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
