[jira] [Created] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
Guy created MNG-6558:
Summary: ToolchainsBuildingResult event is not sent on EventSpy
Key: MNG-6558
URL: https://issues.apache.org/jira/browse/MNG-6558
Project: Maven
Issue Type: Bug
Affects Versions: 3.6.0
Reporter: Guy
On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
the {{ToolchainsBuildingResult}} is not sent. The problem is
[here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
where the {{ToolchainsBuildingRequest}} event is sent twice to the
{{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6557) Add Surefire and Failsafe 3.0.0-M3 in default-bindings.xml
Tibor Digana created MNG-6557: - Summary: Add Surefire and Failsafe 3.0.0-M3 in default-bindings.xml Key: MNG-6557 URL: https://issues.apache.org/jira/browse/MNG-6557 Project: Maven Issue Type: Improvement Components: core Reporter: Tibor Digana Fix For: 3.6.x-candidate https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739096#comment-16739096 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-6065 #17 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6065/17/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739094#comment-16739094 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-6065 #17 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6065/17/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739093#comment-16739093 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-6065 #17 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6065/17/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739095#comment-16739095 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-6065 #17 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6065/17/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739092#comment-16739092 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-6065 #17 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6065/17/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739080#comment-16739080 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MAVEN-3.6/MNG-6399 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MAVEN-3.6%252FMNG-6399/19/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739087#comment-16739087 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-6071 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/6/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739086#comment-16739086 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-6071 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/6/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739088#comment-16739088 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-6071 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/6/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739090#comment-16739090 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-6071 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/6/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739089#comment-16739089 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-6071 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/6/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739082#comment-16739082 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MAVEN-3.6/MNG-6399 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MAVEN-3.6%252FMNG-6399/19/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739081#comment-16739081 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MAVEN-3.6/MNG-6399 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MAVEN-3.6%252FMNG-6399/19/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739079#comment-16739079 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MAVEN-3.6/MNG-6399 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MAVEN-3.6%252FMNG-6399/19/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739078#comment-16739078 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MAVEN-3.6/MNG-6399 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MAVEN-3.6%252FMNG-6399/19/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739043#comment-16739043 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/19/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739070#comment-16739070 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-5666 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5666/12/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739073#comment-16739073 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-5666 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5666/12/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739071#comment-16739071 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-5666 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5666/12/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739064#comment-16739064 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-5995 #7 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5995/7/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739074#comment-16739074 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-5666 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5666/12/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739072#comment-16739072 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-5666 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5666/12/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739065#comment-16739065 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-5995 #7 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5995/7/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739063#comment-16739063 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-5995 #7 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5995/7/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739062#comment-16739062 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-5995 #7 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5995/7/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739061#comment-16739061 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-5995 #7 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5995/7/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739055#comment-16739055 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/19/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739057#comment-16739057 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/19/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739059#comment-16739059 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/19/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739058#comment-16739058 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/19/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739056#comment-16739056 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/19/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739041#comment-16739041 ] Hudson commented on MNG-3372: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5527 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5527/3/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739037#comment-16739037 ] Hudson commented on MNG-6513: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5527 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5527/3/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739053#comment-16739053 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-6311-regression #5 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6311-regression/5/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739051#comment-16739051 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-6311-regression #5 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6311-regression/5/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739054#comment-16739054 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-6311-regression #5 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6311-regression/5/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739050#comment-16739050 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-6311-regression #5 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6311-regression/5/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739052#comment-16739052 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-6311-regression #5 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6311-regression/5/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739047#comment-16739047 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/19/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739044#comment-16739044 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/19/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739048#comment-16739048 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/19/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739045#comment-16739045 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/19/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739039#comment-16739039 ] Hudson commented on MNG-6265: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5527 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5527/3/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739040#comment-16739040 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5527 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5527/3/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739042#comment-16739042 ] Hudson commented on MNG-6555: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5527 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5527/3/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739030#comment-16739030 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5600 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5600/4/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739032#comment-16739032 ] Hudson commented on MNG-6555: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5600 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5600/4/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739031#comment-16739031 ] Hudson commented on MNG-3372: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5600 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5600/4/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739029#comment-16739029 ] Hudson commented on MNG-6265: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5600 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5600/4/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739028#comment-16739028 ] Hudson commented on MNG-6513: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5600 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5600/4/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739023#comment-16739023 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-6294 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/6/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739013#comment-16739013 ] Hudson commented on MNG-6265: - Build failed in Jenkins: Maven TLP » maven » MNG-6533-2 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533-2/6/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739021#comment-16739021 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-6294 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/6/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739019#comment-16739019 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-6294 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/6/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739020#comment-16739020 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-6294 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/6/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739022#comment-16739022 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-6294 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/6/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739016#comment-16739016 ] Hudson commented on MNG-6555: - Build failed in Jenkins: Maven TLP » maven » MNG-6533-2 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533-2/6/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739014#comment-16739014 ] Hudson commented on MNG-5965: - Build failed in Jenkins: Maven TLP » maven » MNG-6533-2 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533-2/6/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739015#comment-16739015 ] Hudson commented on MNG-3372: - Build failed in Jenkins: Maven TLP » maven » MNG-6533-2 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533-2/6/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739012#comment-16739012 ] Hudson commented on MNG-6513: - Build failed in Jenkins: Maven TLP » maven » MNG-6533-2 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533-2/6/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738999#comment-16738999 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6405 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6405/2/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738995#comment-16738995 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6526 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6526/2/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739003#comment-16739003 ] Hudson commented on MNG-6513: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6543 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6543/3/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739004#comment-16739004 ] Hudson commented on MNG-6265: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6543 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6543/3/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739006#comment-16739006 ] Hudson commented on MNG-3372: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6543 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6543/3/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739005#comment-16739005 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6543 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6543/3/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739007#comment-16739007 ] Hudson commented on MNG-6555: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6543 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6543/3/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739001#comment-16739001 ] Hudson commented on MNG-6555: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6405 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6405/2/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738998#comment-16738998 ] Hudson commented on MNG-6265: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6405 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6405/2/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739000#comment-16739000 ] Hudson commented on MNG-3372: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6405 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6405/2/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738994#comment-16738994 ] Hudson commented on MNG-6265: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6526 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6526/2/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738996#comment-16738996 ] Hudson commented on MNG-3372: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6526 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6526/2/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738997#comment-16738997 ] Hudson commented on MNG-6555: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6526 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6526/2/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738986#comment-16738986 ] Hudson commented on MNG-6265: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/4/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738987#comment-16738987 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/4/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738989#comment-16738989 ] Hudson commented on MNG-6555: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/4/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738988#comment-16738988 ] Hudson commented on MNG-3372: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/4/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738982#comment-16738982 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/6/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738983#comment-16738983 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/6/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738985#comment-16738985 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/6/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738984#comment-16738984 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/6/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738978#comment-16738978 ] Hudson commented on MNG-5965: - Build unstable in Jenkins: Maven TLP » maven » MNG-6533 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533/6/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738977#comment-16738977 ] Hudson commented on MNG-6265: - Build unstable in Jenkins: Maven TLP » maven » MNG-6533 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533/6/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738976#comment-16738976 ] Hudson commented on MNG-6513: - Build unstable in Jenkins: Maven TLP » maven » MNG-6533 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533/6/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738979#comment-16738979 ] Hudson commented on MNG-3372: - Build unstable in Jenkins: Maven TLP » maven » MNG-6533 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533/6/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738980#comment-16738980 ] Hudson commented on MNG-6555: - Build unstable in Jenkins: Maven TLP » maven » MNG-6533 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6533/6/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] slachiewicz commented on issue #153: [MNG-6069] Migrate to non deprecated parts of Commons CLI
slachiewicz commented on issue #153: [MNG-6069] Migrate to non deprecated parts of Commons CLI URL: https://github.com/apache/maven/pull/153#issuecomment-452921857 Finally, I manage to not potentially break class compatibility (see #226) and char public variables will stay. 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-5965) Parallel build multiplies work if multiple goals are given
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738837#comment-16738837 ] Hudson commented on MNG-5965: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6069 #24 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/24/ > Parallel build multiplies work if multiple goals are given > -- > > Key: MNG-5965 > URL: https://issues.apache.org/jira/browse/MNG-5965 > Project: Maven > Issue Type: Bug > Components: Bootstrap Build >Affects Versions: 3.3.9 > Environment: Windows 7 64bit >Reporter: Matthias Schmalz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > Attachments: parallel.test.zip > > Time Spent: 20m > Remaining Estimate: 0h > > When I run a parallel build which invokes multiple goals Maven multiplies the > work e.g. when I run > install sonar:sonar > Every phase is executed once as expected. However when I run > install sonar:sonar -T 4 > Every phase is executed twice. > The problem can be reproduced with a single simple Java project (of course > parallel builds are useless with a single module). Debugging showed that > every Mojo is really called twice per project. > Find attached a simple project and two build outputs, where you can see that > the parallel build is doing everything twice (you can ignore that Sonar fails > in the end, due to no server is up). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3372) dependency:tree throws exception
[ https://issues.apache.org/jira/browse/MNG-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738838#comment-16738838 ] Hudson commented on MNG-3372: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6069 #24 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/24/ > dependency:tree throws exception > > > Key: MNG-3372 > URL: https://issues.apache.org/jira/browse/MNG-3372 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Simon Kitching >Assignee: Brian Fox >Priority: Major > Attachments: pom.xml > > > Running >mvn -Papache > org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > on a pom containing the following entry throws an exception, unless an > exclusion is applied as shown below. > > jasperreports > jasperreports > 2.0.0 > compile > > > > commons-digester > > commons-digester > > > xml-apis > xml-apis > > > eclipse > jdtcore > > > > > commons-digester > commons-digester > 1.8 > compile > > Exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.flushDependencyManagement(DependencyTreeResolutionListener.java:524) > at > org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.omitForNearer(DependencyTreeResolutionListener.java:209) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:487) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:462) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:234) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:370) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102) > at > org.apache.maven.plugin.dependency.TreeMojo.execute(TreeMojo.java:218) > My uneducated guess is that for that particular version of the dependency, > neither the dependency's pom nor any parent pom defines a version for > commons-digester. > PS: dependency:tree rocks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6265) Controlling reactor order of modules
[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738836#comment-16738836 ] Hudson commented on MNG-6265: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6069 #24 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/24/ > Controlling reactor order of modules > > > Key: MNG-6265 > URL: https://issues.apache.org/jira/browse/MNG-6265 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.5.0 >Reporter: August Shi >Priority: Major > Attachments: p.patch > > Time Spent: 10m > Remaining Estimate: 0h > > We have a use case for controlling the reactor order in Maven, specifically > for running tests on Travis. The common pattern is to run "mvn install > -DskipTests; mvn test". After modules are installed (in the default order), > the modules can be run in any order during testing, e.g., running the failed > modules first, as in -Dsurefire.runOrder=failedfirst for Surefire. > Would this feature be useful for others? I am attaching a *draft* patch that > implements this feature by modifying DefaultMaven.java. I see no clean way of > implementing this feature through an extension, unless some new callback, > e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to > improve this draft? > One can test the feature by applying the patch, building Maven, and running > tests with the modules in a random order like this: > $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean > install -DskipTests > $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d > maven* | shuf) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6069) Migrate to non deprecated parts of Commons CLI
[
https://issues.apache.org/jira/browse/MNG-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738834#comment-16738834
]
Hudson commented on MNG-6069:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6069 #24
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/24/
> Migrate to non deprecated parts of Commons CLI
> --
>
> Key: MNG-6069
> URL: https://issues.apache.org/jira/browse/MNG-6069
> Project: Maven
> Issue Type: Improvement
> Components: Embedding
>Affects Versions: 3.3.9, 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0
>Reporter: Karl Heinz Marbaise
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.6.1
>
>
> At the moment all parts of {{OptionBuilder...}} are marked deprecated in
> {{CLIManager}}. They should be migrated to:
> {code:java}
> Option.builder( HELP ).longOpt( "help" ).desc( "Display help information"
> ).build()
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6513) Replace depreated Plexus javadoc tags with annotations in ITs
[ https://issues.apache.org/jira/browse/MNG-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738835#comment-16738835 ] Hudson commented on MNG-6513: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6069 #24 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/24/ > Replace depreated Plexus javadoc tags with annotations in ITs > -- > > Key: MNG-6513 > URL: https://issues.apache.org/jira/browse/MNG-6513 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.1 > > > Remove Javadoc Plexus tags @plexus.component and replace with standard Java > annotations from plexus-component-annotations in Integration Tests > Guide: > [https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html] > As effect - remove Javadoc generation warning about Taglets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6555) Packaging 'rar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738839#comment-16738839 ] Hudson commented on MNG-6555: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6069 #24 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/24/ > Packaging 'rar' binding plugin upgrades > --- > > Key: MNG-6555 > URL: https://issues.apache.org/jira/browse/MNG-6555 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0-candidate > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_rar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.1.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.0| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6489) Upgrade Maven Resolver to 1.3.0
[ https://issues.apache.org/jira/browse/MNG-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738778#comment-16738778 ] Hudson commented on MNG-6489: - Build failed in Jenkins: Maven TLP » maven » MNG-6069 #23 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/23/ > Upgrade Maven Resolver to 1.3.0 > --- > > Key: MNG-6489 > URL: https://issues.apache.org/jira/browse/MNG-6489 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.5.4 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.0 > > > Release Notes - Maven Resolver - Version 1.3.0 > Bug > * MRESOLVER-45 - Git repo is gone/moved > * MRESOLVER-50 - Source repository coordinates incorrect > New Feature > * MRESOLVER-46 - Add support InputStream/OutputStream transformers > Improvement > * MRESOLVER-31 - Use the Felix Bundle Plugin to generate OSGi metadata > * MRESOLVER-35 - Move dependency collector and friends to subpackage in > maven-resolver-impl > * MRESOLVER-36 - SLFJ - remove LoggerFactory from dependency injection > * MRESOLVER-42 - Use pre-compiled pattern in DefaultArtifact constructor > * MRESOLVER-47 - Link to older Aether Wiki in Eclipse on front page > * MRESOLVER-48 - Add default Travis CI configuration for Java 7, 8, 10 > Task > * MRESOLVER-44 - switch from Git-WIP to Gitbox -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6481) Allow to compile and test Maven with Java 11
[ https://issues.apache.org/jira/browse/MNG-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738788#comment-16738788 ] Hudson commented on MNG-6481: - Build failed in Jenkins: Maven TLP » maven » MNG-6069 #23 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/23/ > Allow to compile and test Maven with Java 11 > > > Key: MNG-6481 > URL: https://issues.apache.org/jira/browse/MNG-6481 > Project: Maven > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.6.1 > > > Java 11 is coming closer, let's prepare to use it for the development of > Maven. > A minimal requirement to run Maven - still Java 7. > * compile and pass Maven's tests with Java 11 > * adjust ITs to run under Java 11 > Do we need compile and to pass all tests with Java 9, 10 and 11? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6544) Replace CacheUtils#{eq,hash} with Objects
[
https://issues.apache.org/jira/browse/MNG-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738793#comment-16738793
]
Hudson commented on MNG-6544:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6069 #23
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/23/
> Replace CacheUtils#{eq,hash} with Objects
> -
>
> Key: MNG-6544
> URL: https://issues.apache.org/jira/browse/MNG-6544
> Project: Maven
> Issue Type: Task
> Components: core
>Affects Versions: 3.6.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.1
>
>
> {{Objects}} now sports idiot-safe {{equals}} and {{hashCode}} just like
> {{CacheUtils}}. We can swap out and deprecate/delete our code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6505) child.(x.y).inherit.append.path value should be inherited
[ https://issues.apache.org/jira/browse/MNG-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738786#comment-16738786 ] Hudson commented on MNG-6505: - Build failed in Jenkins: Maven TLP » maven » MNG-6069 #23 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/23/ > child.(x.y).inherit.append.path value should be inherited > - > > Key: MNG-6505 > URL: https://issues.apache.org/jira/browse/MNG-6505 > Project: Maven > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Critical > Fix For: 3.6.1 > > > in Maven 3.6.0, values of child.inherit.append.path are not inherited: they > have to be explicitely defined in every child pom of they switch to default > "true" value > these values should be inherited: once defined in a parent pom, every child > should inherit from the value (and of course be able to override) > Note: this seems to have been part of the MNG-6059 implementation that was > done for Maven dropped 3.4.0 version but was forgotten during Maven 3.6.0 > merge... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6059) Important use cases not covered, as child.inherit.append.path affects all children
[
https://issues.apache.org/jira/browse/MNG-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738785#comment-16738785
]
Hudson commented on MNG-6059:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6069 #23
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069/23/
> Important use cases not covered, as child.inherit.append.path affects all
> children
> --
>
> Key: MNG-6059
> URL: https://issues.apache.org/jira/browse/MNG-6059
> Project: Maven
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 3.6.0
> Environment: Apache Maven 3.4.0-SNAPSHOT
> (227085283b6379038ec16f4cf9ad2e8869cef694; 2016-07-06T21:29:12+02:00)
>Reporter: Andreas Sewe
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.6.1
>
>
> The {{child.inherit.append.path}} attribute introduced with MNG-5951
> unfortunately does not support the use case where the children of the element
> with the attribute should follow different inheritance rules. Take a typical
> configuration for Github, for example (taken from
> <[http://central.sonatype.org/pages/requirements.html]>):
> {noformat}
>
>
> scm:git:git://github.com/simpligility/ossrh-demo.git
>
> scm:git:ssh://github.com:simpligility/ossrh-demo.git
> http://github.com/simpligility/ossrh-demo/tree/master
>
> {noformat}
> If the {{ossrh-demo.git}} repository contains a child module called
> {{some-module}}, then that child’s {{scm/url}} should become
> {{[http://github.com/simpligility/ossrh-demo/tree/master/some-module]}} as
> per the normal inheritance rules, but both the {{scm/connection}} and
> {{scm/developerConnection}} URLs should remain unchanged.
> Unfortunately, this is not possible with {{*child*.inherit.append.path}},
> which acts on all children simultaneously.
> IMHO, this is a conceptual problem. In particular, setting
> {{child.inherit.append.path}} on the *root* element to just control a single
> child ({{project/url}}) feels wrong, as the attribute is in all likelihood
> not even located close to the {{}} element it controls.
> h1. Implemented Solution
> {code:xml}
> ...
> child.scm.developerConnection.inherit.append.path="false"
>child.scm.url.inherit.append.path="false">
> ...
> ...
> ...
>
>
>
> ...
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
