[GitHub] sormuras commented on issue #184: Donate current sources from junit-platform-surefire-provider
sormuras commented on issue #184: Donate current sources from junit-platform-surefire-provider URL: https://github.com/apache/maven-surefire/pull/184#issuecomment-388527807 No, didn't do it yet. Just wanted get the changes I made on gitbox-1330 to show up here as "Polishing". Will reset 1330 to this branch (github-184) and squash all commits into a single one there. This is an automated message from the Apache Git Service. To respond to the message, please log on 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] sormuras commented on issue #184: Donate current sources from junit-platform-surefire-provider
sormuras commented on issue #184: Donate current sources from junit-platform-surefire-provider URL: https://github.com/apache/maven-surefire/pull/184#issuecomment-388527807 No, didn't do it yet. Just wanted get the changes I made on bitbox-1330 to show up here as "Polishing". Will reset 1330 to this branch (github-184) and squash all commits into a single one there. This is an automated message from the Apache Git Service. To respond to the message, please log on 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] sormuras commented on issue #184: Donate current sources from junit-platform-surefire-provider
sormuras commented on issue #184: Donate current sources from junit-platform-surefire-provider URL: https://github.com/apache/maven-surefire/pull/184#issuecomment-388529278 What happend on the [`linux-jdk7-maven3.5.x`](https://builds.apache.org/job/maven-box/job/maven-surefire/job/1330/) build? ``` [linux-jdk7-maven3.5.x] Tests run: 58, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.858 sec [linux-jdk7-maven3.5.x] [linux-jdk7-maven3.5.x] Results : [linux-jdk7-maven3.5.x] [linux-jdk7-maven3.5.x] Tests run: 58, Failures: 0, Errors: 0, Skipped: 0 [linux-jdk7-maven3.5.x] [linux-jdk7-maven3.5.x] [INFO] [linux-jdk7-maven3.5.x] [INFO] --- maven-jar-plugin:3.0.0:jar (default-jar) @ surefire-booter --- [linux-jdk7-maven3.5.x] [INFO] Building jar: /home/jenkins/jenkins-slave/workspace/ven-box_maven-surefire_1330-TSMLOBV5ENRMCK6YV52ANAULUWOG4OYEMBRTFOGSINEWTK45IYLQ/surefire-booter/target/surefire-booter-3.0.0-SNAPSHOT.jar [linux-jdk7-maven3.5.x] [INFO] [linux-jdk7-maven3.5.x] [INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ surefire-booter --- [linux-jdk7-maven3.5.x] [INFO] [linux-jdk7-maven3.5.x] [INFO] --- maven-shade-plugin:3.1.0:shade (default) @ surefire-booter --- [linux-jdk7-maven3.5.x] [INFO] Excluding org.apache.maven.surefire:surefire-api:jar:3.0.0-SNAPSHOT from the shaded jar. [linux-jdk7-maven3.5.x] [INFO] Excluding org.apache.maven.surefire:surefire-logger-api:jar:3.0.0-SNAPSHOT from the shaded jar. [linux-jdk7-maven3.5.x] [INFO] Including org.apache.commons:commons-lang3:jar:3.5 in the shaded jar. [linux-jdk7-maven3.5.x] [INFO] Including commons-io:commons-io:jar:2.5 in the shaded jar. [linux-jdk7-maven3.5.x] [INFO] Minimizing jar org.apache.maven.surefire:surefire-booter:jar:3.0.0-SNAPSHOT [linux-jdk7-maven3.5.x] [INFO] [linux-jdk7-maven3.5.x] [INFO] Reactor Summary: [linux-jdk7-maven3.5.x] [INFO] [linux-jdk7-maven3.5.x] [INFO] Apache Maven Surefire .. SUCCESS [ 13.605 s] [linux-jdk7-maven3.5.x] [INFO] SureFire Logger API SUCCESS [ 3.933 s] [linux-jdk7-maven3.5.x] [INFO] SureFire API ... SUCCESS [ 12.695 s] [linux-jdk7-maven3.5.x] [INFO] ShadeFire JUnit3 Provider .. SUCCESS [ 1.921 s] [linux-jdk7-maven3.5.x] [INFO] SureFire Booter FAILURE [ 10.408 s] [linux-jdk7-maven3.5.x] [INFO] Maven Surefire Test-Grouping Support ... SKIPPED [...] ``` `windows-jdk7-maven3.5.x` build was doing fine. This is an automated message from the Apache Git Service. To respond to the message, please log on 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
[jira] [Commented] (MPIR-362) Dependency Management report doesn't exclude system scoped dependencies
[
https://issues.apache.org/jira/browse/MPIR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472801#comment-16472801
]
Hudson commented on MPIR-362:
-
Build failed in Jenkins: Maven TLP » maven-project-info-reports-plugin » master
#17
See
https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/17/
> Dependency Management report doesn't exclude system scoped dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.9
> Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161
>Reporter: Roberto Benedetti
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: MPIR-362.diff
>
>
> I have the same issue that was closed as "Cannot Reproduce". With this pom.xml
> {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
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> free.test
> system-scope-test
> 0.0.1-SNAPSHOT
> jar
> http://test.free/
>
> 1.8
>
> UTF-8
>
>
>
>
> netscape
> plugin
> ${java.version}
> system
>
> ${java.home}/lib/plugin.jar
>
>
>
>
>
>
>
>
> maven-compiler-plugin
> 3.3
>
> ${java.version}
> ${java.version}
>
>
>
>
>
>
>
>
>
> maven-project-info-reports-plugin
> 2.9
>
>
>
>
> dependency-management
>
>
>
>
>
>
>
> {code}
> running {{mvn site}} will give the following warning:
> {noformat}
> [INFO] Generating "Dependency Management" report---
> maven-project-info-reports-plugin:2.9
> [WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project
> artifact: Failure to find netscape:plugin:pom:1.8 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced for project netscape:plugin:pom:1.8
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:314)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:236)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:251)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:298)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
> (DependencyManagementRenderer.java:260)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
> (DependencyManagementRenderer.java:208)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
> (DependencyManagementRenderer.java:161)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
> (DependencyManagementRenderer.java:150)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
> (DependencyManagementRenderer.java:136)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:83)
> at
>
[jira] [Created] (MNG-6409) adding suuport of Big Endian for AARCH64 architecture in Snappy-java
puresoftware created MNG-6409: - Summary: adding suuport of Big Endian for AARCH64 architecture in Snappy-java Key: MNG-6409 URL: https://issues.apache.org/jira/browse/MNG-6409 Project: Maven Issue Type: New Feature Reporter: puresoftware -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MINVOKER-226) run goal failing on Windows + OracleJDK 8-144
[
https://issues.apache.org/jira/browse/MINVOKER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MINVOKER-226.
Resolution: Cannot Reproduce
> run goal failing on Windows + OracleJDK 8-144
> -
>
> Key: MINVOKER-226
> URL: https://issues.apache.org/jira/browse/MINVOKER-226
> Project: Maven Invoker Plugin
> Issue Type: Bug
> Environment: Windows 7 and Windows 8.1 (2 different machines)
> Oracle JDK 8-144
> Maven 3.5.0
> maven-invoker-plugin: from 2.0.0 to 3.0.1
>Reporter: Abel Salgado Romero
>Priority: Minor
> Attachments: logs.txt
>
>
> maven-invoker-plugin (version 2.0.0) run goal started failing on Windows 8.1
> and Windows 7 with OracleJDK 8.144. It worked fine previously.
> Runs OK on MacOS (JDK 8-133 and 8-144), and Ubuntu TraviCI and Windows
> AppVeyor.
> Though the issue started with invoker 2.0.0, I am fine to focus on 3.0.1
> since it's the current version. Also 2.0.0 and 3.0.0 show a different error.
> With 3.0.1 everything seems to run fine but the validation scripts fail
> because they cannot find the generated files of the plugin being tested (see
> this branch
> https://github.com/abelsromero/asciidoctor-maven-plugin/tree/it_test_fail_on_Windows_jdk8_144).
> That's true, the target directory does not hold the generated files but
> running with -X shows that the goals are apparently executed as seen by the
> line
> {{[DEBUG] Executing: cmd.exe /X /C
> "I:\babun\.babun\cygwin\home\abelsr\.sdkman\candidates\maven\3.5.0\bin\mvn.cmd
> -B -X -D maven.repo.local=C:\Users\abelsr\.m2\repository -s
> C:\Users\abelsr\AppData\Local\Temp\invoker-settings4165519454880719356.xml
> clean asciidoctor:process-asciidoc"}}
> Running the same command without the custom settings file in the it-tests
> directory works fine and generates the files.
> NOTE: even if you see in the paths of the attached log that files are in a
> Babun home, I run the command {{mvn clean verify -Prun-its -X}} from a
> standard cmd shell.
> Could it be, that the plugin runs the tests on another directory?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6409) adding suuport of Big Endian for AARCH64 architecture in Snappy-java
[ https://issues.apache.org/jira/browse/MNG-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] puresoftware updated MNG-6409: -- Description: Added the Support for handling the Big endian for AARCH64 which was missing in the existing source code. > adding suuport of Big Endian for AARCH64 architecture in Snappy-java > > > Key: MNG-6409 > URL: https://issues.apache.org/jira/browse/MNG-6409 > Project: Maven > Issue Type: New Feature >Reporter: puresoftware >Priority: Critical > Attachments: MNG-6409.patch > > > Added the Support for handling the Big endian for AARCH64 which was missing > in the existing source code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINVOKER-237) Upgrade to JDK 7 minimum.
[ https://issues.apache.org/jira/browse/MINVOKER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINVOKER-237: - Fix Version/s: (was: 3.1.0) 3.0.2 > Upgrade to JDK 7 minimum. > - > > Key: MINVOKER-237 > URL: https://issues.apache.org/jira/browse/MINVOKER-237 > Project: Maven Invoker Plugin > Issue Type: Task >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINVOKER-237) Upgrade to JDK 7 minimum.
Karl Heinz Marbaise created MINVOKER-237: Summary: Upgrade to JDK 7 minimum. Key: MINVOKER-237 URL: https://issues.apache.org/jira/browse/MINVOKER-237 Project: Maven Invoker Plugin Issue Type: Task Affects Versions: 3.0.2 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6409) adding suuport of Big Endian for AARCH64 architecture in Snappy-java
[ https://issues.apache.org/jira/browse/MNG-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] puresoftware updated MNG-6409: -- Attachment: MNG-6409.patch > adding suuport of Big Endian for AARCH64 architecture in Snappy-java > > > Key: MNG-6409 > URL: https://issues.apache.org/jira/browse/MNG-6409 > Project: Maven > Issue Type: New Feature >Reporter: puresoftware >Priority: Critical > Attachments: MNG-6409.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException
[
https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471570#comment-16471570
]
Dan Armbrust commented on MPLUGIN-336:
--
actually, it appears its already fixed upstream... plugin-plugin needs to be
rebuilt using up-to-date dependency chains rather than a version of asm
that is 4 years old.
This seems to work for now:
{code:java}
//
org.apache.maven.plugins
maven-plugin-plugin
${maven-plugin-plugin.version}
org.ow2.asm
asm
6.1.1
{code}
> broken in JDK 10 - IllegalArgumentException
> ---
>
> Key: MPLUGIN-336
> URL: https://issues.apache.org/jira/browse/MPLUGIN-336
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.5.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T14:39:06-05:00)
> Maven home: /mnt/STORAGE/Work/VetsEZ/Maven/apache-maven-3.5.0
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: /opt/java/jdk-10.0.1
>Reporter: Dan Armbrust
>Priority: Blocker
>
> I'm attempting to migrate some code to Java 10, and this is happening:
> {code:java}
> //
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor
> (default-descriptor) on project mojo: Execution default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.:
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor
> (default-descriptor) on project mojo: Execution default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:218)
> at
>
[GitHub] michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows
michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-388293992 Thanks for the PR, everything is fine now and merged. I plan to release soon. This is an automated message from the Apache Git Service. To respond to the message, please log on 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
[jira] [Commented] (SCM-714) mvn release:prepare fails if the command line is too long on windows
[ https://issues.apache.org/jira/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471637#comment-16471637 ] ASF GitHub Bot commented on SCM-714: michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-388293992 Thanks for the PR, everything is fine now and merged. I plan to release soon. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > mvn release:prepare fails if the command line is too long on windows > > > Key: SCM-714 > URL: https://issues.apache.org/jira/browse/SCM-714 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-gitexe >Affects Versions: 1.8.1 >Reporter: Felix Simmendinger >Assignee: Robert Scholte >Priority: Blocker > > The issue from SCM-697 does not solve the issue as the gitprovider is not > using the add command but the checkin command during a release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] murinrad commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows
murinrad commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-388293296 @michael-o Correct, however with the way I coded the fix previously that method was always receiving an empty filese, hence why it worked. Even without my changes, the else line seems redundant to me. This is an automated message from the Apache Git Service. To respond to the message, please log on 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
[jira] [Commented] (SCM-714) mvn release:prepare fails if the command line is too long on windows
[ https://issues.apache.org/jira/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471634#comment-16471634 ] ASF GitHub Bot commented on SCM-714: murinrad commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-388293296 @michael-o Correct, however with the way I coded the fix previously that method was always receiving an empty filese, hence why it worked. Even without my changes, the else line seems redundant to me. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > mvn release:prepare fails if the command line is too long on windows > > > Key: SCM-714 > URL: https://issues.apache.org/jira/browse/SCM-714 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-gitexe >Affects Versions: 1.8.1 >Reporter: Felix Simmendinger >Assignee: Robert Scholte >Priority: Blocker > > The issue from SCM-697 does not solve the issue as the gitprovider is not > using the add command but the checkin command during a release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException
Dan Armbrust created MPLUGIN-336:
Summary: broken in JDK 10 - IllegalArgumentException
Key: MPLUGIN-336
URL: https://issues.apache.org/jira/browse/MPLUGIN-336
Project: Maven Plugin Tools
Issue Type: Bug
Components: Plugin Plugin
Affects Versions: 3.5.1
Environment: Apache Maven 3.5.0
(ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T14:39:06-05:00)
Maven home: /mnt/STORAGE/Work/VetsEZ/Maven/apache-maven-3.5.0
Java version: 10.0.1, vendor: Oracle Corporation
Java home: /opt/java/jdk-10.0.1
Reporter: Dan Armbrust
I'm attempting to migrate some code to Java 10, and this is happening:
{code:java}
//
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor
(default-descriptor) on project mojo: Execution default-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.:
IllegalArgumentException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor
(default-descriptor) on project mojo: Execution default-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
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:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
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-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.IllegalArgumentException
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:218)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scanArchive(DefaultMojoAnnotationsScanner.java:145)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scan(DefaultMojoAnnotationsScanner.java:112)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scan(DefaultMojoAnnotationsScanner.java:79)
at
org.apache.maven.tools.plugin.extractor.annotations.JavaAnnotationsMojoDescriptorExtractor.scanAnnotations(JavaAnnotationsMojoDescriptorExtractor.java:124)
at
org.apache.maven.tools.plugin.extractor.annotations.JavaAnnotationsMojoDescriptorExtractor.execute(JavaAnnotationsMojoDescriptorExtractor.java:103)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
[jira] [Closed] (MINVOKER-235) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MINVOKER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINVOKER-235. Resolution: Done Done in [3ec5a7a3913fb5f01747bca1c109b4d1d07a9faa|https://gitbox.apache.org/repos/asf?p=maven-invoker-plugin.git;a=commitdiff;h=3ec5a7a3913fb5f01747bca1c109b4d1d07a9faa] > Upgrade plexus-utils 3.1.0 > -- > > Key: MINVOKER-235 > URL: https://issues.apache.org/jira/browse/MINVOKER-235 > Project: Maven Invoker Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-82:
--
Affects Version/s: 2.8
2.10
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4, 2.8, 2.10
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471815#comment-16471815
]
Hervé Boutemy commented on MDEP-82:
---
TL;DR = *Works with Maven 3.1.0+ and maven-dependency-plugin 3.3.0+, fails with
any Maven version or maven-dependency-plugin before*
If you have any issue, please precise which Maven and maven-dependency-plugin
versions you are using
Then detailed tests:
tested with attached pom.xml (dummy) and following settings.xml to provide a
clean local repository on each test (and locale repository manager for
efficiency):
{code:xml}
repo
{code}
then define explicitiely the maven-dependency-plugin version used for
{{go-offline}} to not depend on default version defined inside Maven:
{noformat}mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:2.8:go-offline{noformat}
And finally check if the build in offline mode works:
{noformat}mvn -V -s settings.xml verify -o{noformat}
Result: build works with *maven-dependency-plugin starting with version 3.0.0*
with recent Maven versions
On one line:
{noformat}\rm -rf repo ; mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:go-offline ; mvn -V -s
settings.xml verify -o{noformat}
works like a charm (tested with success also with 3.0.1, 3.0.2, 3.1.0)
The same test fails with 2.10 or anything before fails.
Tested with success with Maven 3.5.3, 3.3.9, 3.2.5, 3.1.0
But fails with Maven 3.0.5
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4, 2.8, 2.10
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-82:
--
Fix Version/s: 3.0.0
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4, 2.8, 2.10
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6408) adding suuport for AARCH64 architecture in Netty/Transport/Native/Epoll
[ https://issues.apache.org/jira/browse/MNG-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] puresoftware updated MNG-6408: -- Attachment: MNG-6408-netty-transport-native-epoll.patch > adding suuport for AARCH64 architecture in Netty/Transport/Native/Epoll > --- > > Key: MNG-6408 > URL: https://issues.apache.org/jira/browse/MNG-6408 > Project: Maven > Issue Type: New Feature >Reporter: puresoftware >Priority: Critical > Attachments: MNG-6408-netty-transport-native-epoll.patch > > > AARCH 64 architecture support is missing in the exiting Netty-epoll code. We > did some modification in the code level and add the support for AARCH64. Now > the Netty/Transport/Native/Epoll project can be used in aarch64 platform > also.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-595) Maven 3.5.2 introduces intermittent test-jar dependency failures in multi-module builds
[
https://issues.apache.org/jira/browse/MDEP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471691#comment-16471691
]
Beirtí Ó'Nunáin commented on MDEP-595:
--
Yeah, appreciate this is a pain. I don't know how the multi-threaded-module
build works,can you point me at any extra info outside of this
[https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3]
?
I think that the 'test-jar' dependency is confusing the execution graph
somehow, but that's pure speculation
> Maven 3.5.2 introduces intermittent test-jar dependency failures in
> multi-module builds
> ---
>
> Key: MDEP-595
> URL: https://issues.apache.org/jira/browse/MDEP-595
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
> Environment: Windows 7 / Server 2012
> Maven 3.5.2
> JDK 1.8
> maven-jar-plugin 2.6
> maven-dependency-plugin 2.10 & 3.0.2
>Reporter: Beirtí Ó'Nunáin
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> This issue never presented in 6 months of running a multi-module build on
> Maven 3.2.5. It began to present in Maven 3.5.2.
> As it's intermittent, will obviously be difficult to reproduce, but here is a
> knocked-down version of our project:
> * parent-aggregator
> ** project_a
> ** project_b
> *** builds jar and test-jar
> Project B has following pom snippet:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
> test-jar
>
>
>
>
> {code}
> Project A has a test-jar on Project B. The dependency
> declaration is as follows
> {code:java}
>
> mygroup
> projectB
> ${project.version}
> test-jar
> test
> {code}
> Using Maven 3.2.5, the dependency had been declared using
> tests and this worked fine. Following a
> recommendation on this page:
> https://stackoverflow.com/questions/1725476/maven-test-dependency-in-multi-module-project
> which refers to the previous editions of the guide suggesting classifier, I
> switched to '' but still have the same intermittent issue.
> This page suggests that using 'test-jar' is supported but not ideal:
> https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html
> Should we expect multi-module builds to work with test-jar dependencies or
> should we be using a separate 'tests' module instead?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MINVOKER-237) Upgrade to JDK 7 minimum.
[ https://issues.apache.org/jira/browse/MINVOKER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINVOKER-237. Resolution: Fixed Done in [a36000f33d91cd3e0a9acde2e0fe0170ce2d2374|https://gitbox.apache.org/repos/asf?p=maven-invoker-plugin.git;a=commitdiff;h=a36000f33d91cd3e0a9acde2e0fe0170ce2d2374] > Upgrade to JDK 7 minimum. > - > > Key: MINVOKER-237 > URL: https://issues.apache.org/jira/browse/MINVOKER-237 > Project: Maven Invoker Plugin > Issue Type: Task >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCM-868) gitexe add() does not return added files when invoked in subdir
[
https://issues.apache.org/jira/browse/SCM-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471717#comment-16471717
]
Ilya Basin commented on SCM-868:
If you run the "add" or "checkin" command on Windows with the current working
directory and the env. var. "TMP" being on different drive letters, then the
command result will be "zero files added" or "zero files checked in".
Unfortunately, the unit tests of maven-scm don't check this. This issue,
however, breaks WagonTestCase.testWagon() in maven-wagon when attempted to run
for gitexe.
> gitexe add() does not return added files when invoked in subdir
> ---
>
> Key: SCM-868
> URL: https://issues.apache.org/jira/browse/SCM-868
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5, 1.9.6
>Reporter: Ilya Basin
>Priority: Major
>
> I'm going to add a wagon-scm test suite for git. One of the test cases is
> calling the GitAddCommand command with:
> {code:java}
> repo:
> file:///C:/progs/maven/maven-wagon/wagon-providers/wagon-scm/target/test-classes/test-repo-git-test/
> fileSet: basedir =
> C:\Users\basin\AppData\Local\Temp\wagon-scm2020146470.checkout\file-list;
> files = [test-resource.txt]{code}
> After adding the files the command internally calls "git rev-parse
> --show-toplevel" which prints:
> {code:java}
> C:/Users/basin/AppData/Local/Temp/wagon-scm2020146470.checkout{code}
> And on the next line it tries to do (pseudo code):
> {code:java}
> ("file:/C:/Users/basin/AppData/Local/Temp/wagon-scm1144102340.checkout/file-list/").relativize(URI.create(
> "C:/Users/basin/AppData/Local/Temp/wagon-scm2020146470.checkout")){code}
> This is so wrong! What were those people from SCM-709 trying to get? A double
> dot ".."? The argument to the relativize() method MUST be a child, not a
> parent, otherwise the argument is returned unchanged.
> There are so many reasons why getting an absolute path from git is a bad
> idea: Symlinks, Windows paths.
> Nevertheless, there's a simple solution. The original problem was that "git
> status --porcelain" printed paths relative to the top level instead of
> relative to the base dir.
> So we should just call
> {code}
> git rev-parse --show-prefix
> {code} instead of "show-toplevel" and strip this prefix from the paths
> printed by "git status"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MNG-6407) adding suuport for AARCH64 architecture in jansi-native
[ https://issues.apache.org/jira/browse/MNG-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6407. --- Resolution: Not A Problem Not related to Maven. Request this from upstream. > adding suuport for AARCH64 architecture in jansi-native > --- > > Key: MNG-6407 > URL: https://issues.apache.org/jira/browse/MNG-6407 > Project: Maven > Issue Type: New Feature >Reporter: puresoftware >Priority: Major > > AARCH 64 architecture support is missing in the exiting jansi-native code. > Now we did some modification in the code level and add the support for > AARCH64. Now the jansi project can be used in AARCH64 platform also -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINVOKER-237) Upgrade to JDK 7 minimum.
[ https://issues.apache.org/jira/browse/MINVOKER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471714#comment-16471714 ] Hudson commented on MINVOKER-237: - Build succeeded in Jenkins: Maven TLP » maven-invoker-plugin » master #18 See https://builds.apache.org/job/maven-box/job/maven-invoker-plugin/job/master/18/ > Upgrade to JDK 7 minimum. > - > > Key: MINVOKER-237 > URL: https://issues.apache.org/jira/browse/MINVOKER-237 > Project: Maven Invoker Plugin > Issue Type: Task >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNG-6408) adding suuport for AARCH64 architecture in Netty/Transport/Native/Epoll
[ https://issues.apache.org/jira/browse/MNG-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6408. --- Resolution: Invalid Not related to Maven. > adding suuport for AARCH64 architecture in Netty/Transport/Native/Epoll > --- > > Key: MNG-6408 > URL: https://issues.apache.org/jira/browse/MNG-6408 > Project: Maven > Issue Type: New Feature >Reporter: puresoftware >Priority: Critical > Attachments: MNG-6408-netty-transport-native-epoll.patch > > > AARCH 64 architecture support is missing in the exiting Netty-epoll code. We > did some modification in the code level and add the support for AARCH64. Now > the Netty/Transport/Native/Epoll project can be used in aarch64 platform > also.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNG-6409) adding suuport of Big Endian for AARCH64 architecture in Snappy-java
[ https://issues.apache.org/jira/browse/MNG-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6409. --- Resolution: Invalid Not related to Maven. > adding suuport of Big Endian for AARCH64 architecture in Snappy-java > > > Key: MNG-6409 > URL: https://issues.apache.org/jira/browse/MNG-6409 > Project: Maven > Issue Type: New Feature >Reporter: puresoftware >Priority: Critical > Attachments: MNG-6409.patch > > > Added the Support for handling the Big endian for AARCH64 which was missing > in the existing source code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471815#comment-16471815
]
Hervé Boutemy edited comment on MDEP-82 at 5/11/18 12:18 PM:
-
TL;DR = *Works with Maven 3.1.0+ and maven-dependency-plugin 3.0.0+, fails with
any Maven version or maven-dependency-plugin before*
If you have any issue, please precise which Maven and maven-dependency-plugin
versions you are using
Then detailed tests:
tested with attached pom.xml (dummy) and following settings.xml to provide a
clean local repository on each test (and locale repository manager for
efficiency):
{code:xml}
repo
{code}
then define explicitiely the maven-dependency-plugin version used for
{{go-offline}} to not depend on default version defined inside Maven:
{noformat}mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:2.8:go-offline{noformat}
And finally check if the build in offline mode works:
{noformat}mvn -V -s settings.xml verify -o{noformat}
Result: build works with *maven-dependency-plugin starting with version 3.0.0*
with recent Maven versions
On one line:
{noformat}\rm -rf repo ; mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:go-offline ; mvn -V -s
settings.xml verify -o{noformat}
works like a charm (tested with success also with 3.0.1, 3.0.2, 3.1.0)
The same test fails with 2.10 or anything before fails.
Tested with success with Maven 3.5.3, 3.3.9, 3.2.5, 3.1.0
But fails with Maven 3.0.5
was (Author: hboutemy):
TL;DR = *Works with Maven 3.1.0+ and maven-dependency-plugin 3.3.0+, fails with
any Maven version or maven-dependency-plugin before*
If you have any issue, please precise which Maven and maven-dependency-plugin
versions you are using
Then detailed tests:
tested with attached pom.xml (dummy) and following settings.xml to provide a
clean local repository on each test (and locale repository manager for
efficiency):
{code:xml}
repo
{code}
then define explicitiely the maven-dependency-plugin version used for
{{go-offline}} to not depend on default version defined inside Maven:
{noformat}mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:2.8:go-offline{noformat}
And finally check if the build in offline mode works:
{noformat}mvn -V -s settings.xml verify -o{noformat}
Result: build works with *maven-dependency-plugin starting with version 3.0.0*
with recent Maven versions
On one line:
{noformat}\rm -rf repo ; mvn -s settings.xml
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:go-offline ; mvn -V -s
settings.xml verify -o{noformat}
works like a charm (tested with success also with 3.0.1, 3.0.2, 3.1.0)
The same test fails with 2.10 or anything before fails.
Tested with success with Maven 3.5.3, 3.3.9, 3.2.5, 3.1.0
But fails with Maven 3.0.5
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4, 2.8, 2.10
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472030#comment-16472030 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #16 See https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/16/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472032#comment-16472032 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-parent » master #69 See https://builds.apache.org/job/maven-box/job/maven-parent/job/master/69/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472064#comment-16472064 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-fluido-skin » master #16 See https://builds.apache.org/job/maven-box/job/maven-fluido-skin/job/master/16/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472038#comment-16472038 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-toolchains-plugin » master #10 See https://builds.apache.org/job/maven-box/job/maven-toolchains-plugin/job/master/10/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472059#comment-16472059 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-file-management » master #4 See https://builds.apache.org/job/maven-box/job/maven-file-management/job/master/4/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472072#comment-16472072 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-dist-tool » master #8 See https://builds.apache.org/job/maven-box/job/maven-dist-tool/job/master/8/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472011#comment-16472011 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-pdf-plugin » master #15 See https://builds.apache.org/job/maven-box/job/maven-pdf-plugin/job/master/15/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472027#comment-16472027 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-doxia-sitetools » master #33 See https://builds.apache.org/job/maven-box/job/maven-doxia-sitetools/job/master/33/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472058#comment-16472058 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-site-plugin » master #40 See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/40/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472047#comment-16472047 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-default-skin » master #6 See https://builds.apache.org/job/maven-box/job/maven-default-skin/job/master/6/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6410) When a reactor build fails on an artifactId which is not unique, Maven should provide the groupId when suggesting where build should restart from
[
https://issues.apache.org/jira/browse/MNG-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6410:
---
Summary: When a reactor build fails on an artifactId which is not unique,
Maven should provide the groupId when suggesting where build should restart
from (was: When a reactor build fails on an artifactId which is not unique,
Maven should provide the groupId when suggesting from where build should
restart from)
> When a reactor build fails on an artifactId which is not unique, Maven should
> provide the groupId when suggesting where build should restart from
> -
>
> Key: MNG-6410
> URL: https://issues.apache.org/jira/browse/MNG-6410
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.3
>Reporter: Łukasz Dywicki
>Priority: Minor
>
> In multi module builds same artifact id can be repeated with different group
> id. For example if project strategy is to use nesting of modules, instead of
> using long artifact names, {{ap}} or {{model}} module can occur multiple
> times with different group id.
> By default maven, upon failed build, prints out only {{-rf :artifactId}}.
> When developer will copy given suggestion and run build again then his build
> will be started from first module which have given artifact id.
> While severity of this bug is quite low, it affects productivity in bigger
> projects big time. To improve usability of returned message a Maven should
> return {{-rf groupId:artifactId}} once artifact id is not unique.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471887#comment-16471887 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-plugin-tools » master #24 See https://builds.apache.org/job/maven-box/job/maven-plugin-tools/job/master/24/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471931#comment-16471931 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-patch-plugin » master #3 See https://builds.apache.org/job/maven-box/job/maven-patch-plugin/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471930#comment-16471930 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-jmod-plugin » master #7 See https://builds.apache.org/job/maven-box/job/maven-jmod-plugin/job/master/7/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471928#comment-16471928 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-linkcheck-plugin » master #3 See https://builds.apache.org/job/maven-box/job/maven-linkcheck-plugin/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471962#comment-16471962 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-project-utils » master #2 See https://builds.apache.org/job/maven-box/job/maven-project-utils/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471858#comment-16471858 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-site » master #2 See https://builds.apache.org/job/maven-box/job/maven-site/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471882#comment-16471882 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-enforcer » master #18 See https://builds.apache.org/job/maven-box/job/maven-enforcer/job/master/18/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471896#comment-16471896 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-release » master #43 See https://builds.apache.org/job/maven-box/job/maven-release/job/master/43/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471895#comment-16471895 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-resolver-ant-tasks » master #10 See https://builds.apache.org/job/maven-box/job/maven-resolver-ant-tasks/job/master/10/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471904#comment-16471904 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-scm » master #16 See https://builds.apache.org/job/maven-box/job/maven-scm/job/master/16/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471927#comment-16471927 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-wagon » master #13 See https://builds.apache.org/job/maven-box/job/maven-wagon/job/master/13/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471925#comment-16471925 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-shared-utils » master #8 See https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/8/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471949#comment-16471949 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-common-artifact-filters » master #2 See https://builds.apache.org/job/maven-box/job/maven-common-artifact-filters/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471948#comment-16471948 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-artifact-resolver » master #3 See https://builds.apache.org/job/maven-box/job/maven-artifact-resolver/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471976#comment-16471976 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-verifier » master #7 See https://builds.apache.org/job/maven-box/job/maven-verifier/job/master/7/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471973#comment-16471973 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-shared-jar » master #2 See https://builds.apache.org/job/maven-box/job/maven-shared-jar/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471889#comment-16471889 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-changes-plugin » master #3 See https://builds.apache.org/job/maven-box/job/maven-changes-plugin/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471913#comment-16471913 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-jxr » master #9 See https://builds.apache.org/job/maven-box/job/maven-jxr/job/master/9/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471912#comment-16471912 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-doxia » master #23 See https://builds.apache.org/job/maven-box/job/maven-doxia/job/master/23/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471939#comment-16471939 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-repository-plugin » master #4 See https://builds.apache.org/job/maven-box/job/maven-repository-plugin/job/master/4/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471956#comment-16471956 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-dependency-analyzer » master #27 See https://builds.apache.org/job/maven-box/job/maven-dependency-analyzer/job/master/27/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471957#comment-16471957 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-jarsigner » master #2 See https://builds.apache.org/job/maven-box/job/maven-jarsigner/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471958#comment-16471958 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-filtering » master #6 See https://builds.apache.org/job/maven-box/job/maven-filtering/job/master/6/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471954#comment-16471954 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-dependency-tree » master #5 See https://builds.apache.org/job/maven-box/job/maven-dependency-tree/job/master/5/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471955#comment-16471955 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-downloader » master #2 See https://builds.apache.org/job/maven-box/job/maven-downloader/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6410) When a reactor build fails maven should provide clean suggestion from where build should start
Łukasz Dywicki created MNG-6410:
---
Summary: When a reactor build fails maven should provide clean
suggestion from where build should start
Key: MNG-6410
URL: https://issues.apache.org/jira/browse/MNG-6410
Project: Maven
Issue Type: Bug
Components: Command Line
Affects Versions: 3.5.3
Reporter: Łukasz Dywicki
In multi module builds same artifact id can be repeated with different group
id. For example if project strategy is to use nesting of modules, instead of
using long artifact names, {{ap}} or {{model}} module can occur multiple times
with different group id.
By default maven, upon failed build, prints out only {{-rf :artifactId}}. When
developer will copy given suggestion and run build again then his build will be
started from first module which have given artifact id.
While severity of this bug is quite low, it affects productivity in bigger
projects big time. To improve usability of returned message a Maven should
return {{-rf groupId:artifactId}} once artifact id is not unique.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException
[
https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471897#comment-16471897
]
Michael Osipov commented on MPLUGIN-336:
I will happily accept a PR for this.
> broken in JDK 10 - IllegalArgumentException
> ---
>
> Key: MPLUGIN-336
> URL: https://issues.apache.org/jira/browse/MPLUGIN-336
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.5.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T14:39:06-05:00)
> Maven home: /mnt/STORAGE/Work/VetsEZ/Maven/apache-maven-3.5.0
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: /opt/java/jdk-10.0.1
>Reporter: Dan Armbrust
>Priority: Blocker
>
> I'm attempting to migrate some code to Java 10, and this is happening:
> {code:java}
> //
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor
> (default-descriptor) on project mojo: Execution default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.:
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor
> (default-descriptor) on project mojo: Execution default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5.1:descriptor failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:218)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scanArchive(DefaultMojoAnnotationsScanner.java:145)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scan(DefaultMojoAnnotationsScanner.java:112)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scan(DefaultMojoAnnotationsScanner.java:79)
> at
>
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471898#comment-16471898 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-archiver » master #11 See https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/11/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471911#comment-16471911 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-doxia-linkcheck » master #9 See https://builds.apache.org/job/maven-box/job/maven-doxia-linkcheck/job/master/9/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6411) Improve readability of project list returned when resume from flag is invalid
Łukasz Dywicki created MNG-6411:
---
Summary: Improve readability of project list returned when resume
from flag is invalid
Key: MNG-6411
URL: https://issues.apache.org/jira/browse/MNG-6411
Project: Maven
Issue Type: Improvement
Affects Versions: 3.5.3
Reporter: Łukasz Dywicki
When value passed for {{-rf}} option is invalid a full list of details of all
projects in build is returned.
This list contains too much information. For every project it includes groupId,
artifactId, version and pom location. While it is useful for debugging purposes
many, if not most, developers are interested in specific coordinate
(groupId:artifactId) which should be passed to next execution, and which is
valid {{-rf}} optiona value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471917#comment-16471917 ] Hudson commented on MNGSITE-328: Build unstable in Jenkins: Maven TLP » maven-plugin-testing » master #2 See https://builds.apache.org/job/maven-box/job/maven-plugin-testing/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471936#comment-16471936 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #16 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/16/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471945#comment-16471945 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-scm-publish-plugin » master #15 See https://builds.apache.org/job/maven-box/job/maven-scm-publish-plugin/job/master/15/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471947#comment-16471947 ] Hudson commented on MNGSITE-328: Build unstable in Jenkins: Maven TLP » maven-remote-resources-plugin » master #6 See https://builds.apache.org/job/maven-box/job/maven-remote-resources-plugin/job/master/6/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471946#comment-16471946 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-stage-plugin » master #3 See https://builds.apache.org/job/maven-box/job/maven-stage-plugin/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471965#comment-16471965 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-reporting-exec » master #2 See https://builds.apache.org/job/maven-box/job/maven-reporting-exec/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471987#comment-16471987 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-archetypes » master #9 See https://builds.apache.org/job/maven-box/job/maven-archetypes/job/master/9/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471883#comment-16471883 ] Hudson commented on MNGSITE-328: Build failed in Jenkins: Maven TLP » maven-indexer » master #2 See https://builds.apache.org/job/maven-box/job/maven-indexer/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471884#comment-16471884 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-site » master #3 See https://builds.apache.org/job/maven-box/job/maven-site/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471901#comment-16471901 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-archetype » master #5 See https://builds.apache.org/job/maven-box/job/maven-archetype/job/master/5/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471906#comment-16471906 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-doxia-converter » master #4 See https://builds.apache.org/job/maven-box/job/maven-doxia-converter/job/master/4/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471907#comment-16471907 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-doxia-sitetools » master #32 See https://builds.apache.org/job/maven-box/job/maven-doxia-sitetools/job/master/32/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471924#comment-16471924 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-jarsigner-plugin » master #3 See https://builds.apache.org/job/maven-box/job/maven-jarsigner-plugin/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471923#comment-16471923 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-jdeprscan-plugin » master #4 See https://builds.apache.org/job/maven-box/job/maven-jdeprscan-plugin/job/master/4/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471922#comment-16471922 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-jdeps-plugin » master #13 See https://builds.apache.org/job/maven-box/job/maven-jdeps-plugin/job/master/13/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471960#comment-16471960 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-osgi » master #2 See https://builds.apache.org/job/maven-box/job/maven-osgi/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471959#comment-16471959 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-mapping » master #4 See https://builds.apache.org/job/maven-box/job/maven-mapping/job/master/4/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471961#comment-16471961 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-reporting-api » master #2 See https://builds.apache.org/job/maven-box/job/maven-reporting-api/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471975#comment-16471975 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-runtime » master #2 See https://builds.apache.org/job/maven-box/job/maven-runtime/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471972#comment-16471972 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-shared-incremental » master #2 See https://builds.apache.org/job/maven-box/job/maven-shared-incremental/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471974#comment-16471974 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-shared-resources » master #3 See https://builds.apache.org/job/maven-box/job/maven-shared-resources/job/master/3/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471971#comment-16471971 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-script-interpreter » master #2 See https://builds.apache.org/job/maven-box/job/maven-script-interpreter/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471970#comment-16471970 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-reporting-impl » master #2 See https://builds.apache.org/job/maven-box/job/maven-reporting-impl/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-328) How to get rid of .md5's in www.a.o/dist/ ?
[ https://issues.apache.org/jira/browse/MNGSITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471969#comment-16471969 ] Hudson commented on MNGSITE-328: Build succeeded in Jenkins: Maven TLP » maven-repository-builder » master #2 See https://builds.apache.org/job/maven-box/job/maven-repository-builder/job/master/2/ > How to get rid of .md5's in www.a.o/dist/ ? > --- > > Key: MNGSITE-328 > URL: https://issues.apache.org/jira/browse/MNGSITE-328 > Project: Maven Project Web Site > Issue Type: Wish >Reporter: Henk Penning >Priority: Major > > ASF policy (strongly) recommends not to publish .md5's in > [www.apache.org/dist/,|http://www.a.o/dist/,] > that is : [https://dist.apache.org/repos/dist/release/] > -- How can maven users achieve this ? > -- Is it possible (and sensible) to add something to maven, to make it easy > (or easier) ? > I must confess I don't know the first thing about maven etc ; hope my > question makes sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion
[
https://issues.apache.org/jira/browse/MNG-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6028:
---
Description:
Start multiproject build at root with mvn clean install
if module-a fails you currently get
{noformat}[ERROR] After correcting the problems, you can resume the build with
the command
[ERROR] mvn -rf :module-a{noformat}
to be able to easily copy-paste this it would be much nicer if the goals were
already filled in:
{noformat}[ERROR] After correcting the problems, you can resume the build with
the command
[ERROR] mvn clean install -rf :module-a{noformat}
was:
Start multiproject build at root with mvn clean install
if module-a fails you currently get
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :module-a
to be able to easily copy-paste this it would be much nicer if the goals were
already filled in:
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn clean install -rf :module-a
> When a reactor build fails maven should include current goals in resume
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn clean install -rf :module-a{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6410) When a reactor build fails on an artifactId which is not unique, Maven should provide the groupId when suggesting from where build should restart from
[
https://issues.apache.org/jira/browse/MNG-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6410:
---
Summary: When a reactor build fails on an artifactId which is not unique,
Maven should provide the groupId when suggesting from where build should
restart from (was: When a reactor build fails maven should provide clean
suggestion from where build should start)
> When a reactor build fails on an artifactId which is not unique, Maven should
> provide the groupId when suggesting from where build should restart from
> --
>
> Key: MNG-6410
> URL: https://issues.apache.org/jira/browse/MNG-6410
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.3
>Reporter: Łukasz Dywicki
>Priority: Minor
>
> In multi module builds same artifact id can be repeated with different group
> id. For example if project strategy is to use nesting of modules, instead of
> using long artifact names, {{ap}} or {{model}} module can occur multiple
> times with different group id.
> By default maven, upon failed build, prints out only {{-rf :artifactId}}.
> When developer will copy given suggestion and run build again then his build
> will be started from first module which have given artifact id.
> While severity of this bug is quite low, it affects productivity in bigger
> projects big time. To improve usability of returned message a Maven should
> return {{-rf groupId:artifactId}} once artifact id is not unique.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6408) adding suuport for AARCH64 architecture in Netty/Transport/Native/Epoll
puresoftware created MNG-6408: - Summary: adding suuport for AARCH64 architecture in Netty/Transport/Native/Epoll Key: MNG-6408 URL: https://issues.apache.org/jira/browse/MNG-6408 Project: Maven Issue Type: New Feature Reporter: puresoftware AARCH 64 architecture support is missing in the exiting Netty-epoll code. We did some modification in the code level and add the support for AARCH64. Now the Netty/Transport/Native/Epoll project can be used in aarch64 platform also.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] splatch opened a new pull request #165: [MNG-6028] Include current goals in resume suggestion
splatch opened a new pull request #165: [MNG-6028] Include current goals in resume suggestion URL: https://github.com/apache/maven/pull/165 This PR is small improvement which allows to simply pick up returned sugestion and restart the build. JIRA issue: https://issues.apache.org/jira/browse/MNG-6028. This is an automated message from the Apache Git Service. To respond to the message, please log on 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
[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion
[
https://issues.apache.org/jira/browse/MNG-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472359#comment-16472359
]
ASF GitHub Bot commented on MNG-6028:
-
splatch opened a new pull request #165: [MNG-6028] Include current goals in
resume suggestion
URL: https://github.com/apache/maven/pull/165
This PR is small improvement which allows to simply pick up returned
sugestion and restart the build.
JIRA issue: https://issues.apache.org/jira/browse/MNG-6028.
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> When a reactor build fails maven should include current goals in resume
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn clean install -rf :module-a{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6410) When a reactor build fails on an artifactId which is not unique, Maven should provide the groupId when suggesting where build should restart from
[
https://issues.apache.org/jira/browse/MNG-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472383#comment-16472383
]
ASF GitHub Bot commented on MNG-6410:
-
splatch opened a new pull request #166: [MNG-6410] Clean suggestion on build
resume.
URL: https://github.com/apache/maven/pull/166
Make sure that resume suggestion contains a valid value for restarting the
build, as same artifact name might occur in different places of multi-module
project, it is necessary to check if there is conflict in name.
By this way returned suggestion will always be correct and less experienced
developers will not get confused with it.
JIRA issue: https://issues.apache.org/jira/browse/MNG-6410.
A extra note, this pull request depends on another pull #165 - for MNG-6028,
which changes the same line, both commits are included in this PR.
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> When a reactor build fails on an artifactId which is not unique, Maven should
> provide the groupId when suggesting where build should restart from
> -
>
> Key: MNG-6410
> URL: https://issues.apache.org/jira/browse/MNG-6410
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.3
>Reporter: Łukasz Dywicki
>Priority: Minor
>
> In multi module builds same artifact id can be repeated with different group
> id. For example if project strategy is to use nesting of modules, instead of
> using long artifact names, {{ap}} or {{model}} module can occur multiple
> times with different group id.
> By default maven, upon failed build, prints out only {{-rf :artifactId}}.
> When developer will copy given suggestion and run build again then his build
> will be started from first module which have given artifact id.
> While severity of this bug is quite low, it affects productivity in bigger
> projects big time. To improve usability of returned message a Maven should
> return {{-rf groupId:artifactId}} once artifact id is not unique.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
