[jira] [Commented] (ARCHETYPE-519) archetype:generate with specified remote archetypeCatalog falls back to internal catalog
[
https://issues.apache.org/jira/browse/ARCHETYPE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880216#comment-15880216
]
Ate Douma commented on ARCHETYPE-519:
-
I agree, this is a really problematic change.
It is causing problems for new users getting started with our [Hippo
CMS|https://www.onehippo.org/] product, for which we don't have the archetype
on Maven Central, and neither intend to move it there.
As a workaround we had to update our documentation to make sure our users use
archetype 2.4 explicitly, but that is rather 'backwards' IMO.
I definitely think these changes in archetype 3.0 should be made optional or at
least optionally be turned off.
> archetype:generate with specified remote archetypeCatalog falls back to
> internal catalog
>
>
> Key: ARCHETYPE-519
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-519
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 3.0.0
> Environment: Mac OS X 10.11.6, Apache Maven 3.2.3
>Reporter: Philip Mundt
>Assignee: Robert Scholte
> Fix For: 3.0.1
>
>
> We were surprised to find out that our archetype was "suddenly" not working
> anymore. It turns out it was the release of
> {{org.apache.maven.plugins:maven-archetype-plugin:3.0.0}} from 12/Feb/17 that
> was the culprit.
> When running:
> {{mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.0:generate
> -DarchetypeCatalog=}} we end up with the
> plugin falling back to the internal catalog:
> {code}
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
>
> [INFO]
> [INFO] >>> maven-archetype-plugin:3.0.0:generate (default-cli) >
> generate-sources @ standalone-pom >>>
> [INFO]
> [INFO] <<< maven-archetype-plugin:3.0.0:generate (default-cli) <
> generate-sources @ standalone-pom <<<
> [INFO]
> [INFO] --- maven-archetype-plugin:3.0.0:generate (default-cli) @
> standalone-pom ---
> [INFO] Generating project in Interactive mode
> [INFO] No catalog defined. Using internal catalog
> [INFO] No archetype defined. Using maven-archetype-quickstart
> (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
> Choose archetype:
> 1: internal -> org.apache.maven.archetypes:maven-archetype-archetype (An
> archetype which contains a sample archetype.)
> 2: internal -> org.apache.maven.archetypes:maven-archetype-j2ee-simple (An
> archetype which contains a simplifed sample J2EE application.)
> 3: internal -> org.apache.maven.archetypes:maven-archetype-plugin (An
> archetype which contains a sample Maven plugin.)
> 4: internal -> org.apache.maven.archetypes:maven-archetype-plugin-site (An
> archetype which contains a sample Maven plugin site.
> This archetype can be layered upon an existing Maven plugin project.)
> 5: internal -> org.apache.maven.archetypes:maven-archetype-portlet (An
> archetype which contains a sample JSR-268 Portlet.)
> 6: internal -> org.apache.maven.archetypes:maven-archetype-profiles ()
> 7: internal -> org.apache.maven.archetypes:maven-archetype-quickstart (An
> archetype which contains a sample Maven project.)
> 8: internal -> org.apache.maven.archetypes:maven-archetype-site (An archetype
> which contains a sample Maven site which demonstrates
> some of the supported document types like APT, XDoc, and FML and
> demonstrates how
> to i18n your site. This archetype can be layered upon an existing Maven
> project.)
> 9: internal -> org.apache.maven.archetypes:maven-archetype-site-simple (An
> archetype which contains a sample Maven site.)
> 10: internal -> org.apache.maven.archetypes:maven-archetype-webapp (An
> archetype which contains a sample Maven Webapp project.)
> Choose a number or apply filter (format: [groupId:]artifactId, case sensitive
> contains):
> {code}
> Version 2.4 works as expected (the archetype catalog exists under given URL
> and can be downloaded).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6078) Can't overwrite properties which have been defined in .mvn/maven.config
[
https://issues.apache.org/jira/browse/MNG-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880382#comment-15880382
]
Hudson commented on MNG-6078:
-
FAILURE: Integrated in Jenkins build maven-3.x #1553 (See
[https://builds.apache.org/job/maven-3.x/1553/])
[MNG-6078] Undo the order reversal hack (stephen.alan.connolly:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=5885e70e24a69914da892eb343906658d5463bfa])
* (edit) maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java
* (edit) maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java
[MNG-6078] Perform a proper merge of the two sources of command line
(stephen.alan.connolly:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=dc9c4db4494b62e2231bb67b39678decf6329852])
* (edit) maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java
* (edit) maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java
* (add) maven-embedder/src/main/java/org/apache/maven/cli/MergedCommandLine.java
> Can't overwrite properties which have been defined in .mvn/maven.config
> ---
>
> Key: MNG-6078
> URL: https://issues.apache.org/jira/browse/MNG-6078
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.5.0
>
>
> Currently properties which have been defined in {{.mvn/maven.config}} can't
> be overwritten via command line. This should be made possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly reassigned MNG-6172:
-
Assignee: Stephen Connolly
> Precedence of command-line system property options has changed
> --
>
> Key: MNG-6172
> URL: https://issues.apache.org/jira/browse/MNG-6172
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0-candidate
>
>
> The current state of master (what will eventually become 3.5.0) has reversed
> the precedence of command-line system property options compared to previous
> releases of Maven.
> For example, running this command with a basic project:
> {code}
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> {code}
> using current master will cause {{/tmp/aaa}} to be created (first-one-wins),
> whereas for all previous releases of Maven {{/tmp/zzz}} would have been
> created (last-one-wins)
> This has the potential to break CI builds which relied on the previous
> last-one-wins behaviour.
> This was introduced by the fix for MNG-6078
> https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
> - by reversing the whole array the precedence between options on the same
> command line has been reversed, not just the relationship between
> .mvn/maven.config options and command line options.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly resolved MNG-6172.
---
Resolution: Fixed
Fix Version/s: (was: 3.5.0-candidate)
3.5.0
Fixed with dc9c4db4494b62e2231bb67b39678decf6329852 in maven-core
> Precedence of command-line system property options has changed
> --
>
> Key: MNG-6172
> URL: https://issues.apache.org/jira/browse/MNG-6172
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0
>
>
> The current state of master (what will eventually become 3.5.0) has reversed
> the precedence of command-line system property options compared to previous
> releases of Maven.
> For example, running this command with a basic project:
> {code}
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> {code}
> using current master will cause {{/tmp/aaa}} to be created (first-one-wins),
> whereas for all previous releases of Maven {{/tmp/zzz}} would have been
> created (last-one-wins)
> This has the potential to break CI builds which relied on the previous
> last-one-wins behaviour.
> This was introduced by the fix for MNG-6078
> https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
> - by reversing the whole array the precedence between options on the same
> command line has been reversed, not just the relationship between
> .mvn/maven.config options and command line options.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MNG-6172.
-
> Precedence of command-line system property options has changed
> --
>
> Key: MNG-6172
> URL: https://issues.apache.org/jira/browse/MNG-6172
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0
>
>
> The current state of master (what will eventually become 3.5.0) has reversed
> the precedence of command-line system property options compared to previous
> releases of Maven.
> For example, running this command with a basic project:
> {code}
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> {code}
> using current master will cause {{/tmp/aaa}} to be created (first-one-wins),
> whereas for all previous releases of Maven {{/tmp/zzz}} would have been
> created (last-one-wins)
> This has the potential to break CI builds which relied on the previous
> last-one-wins behaviour.
> This was introduced by the fix for MNG-6078
> https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
> - by reversing the whole array the precedence between options on the same
> command line has been reversed, not just the relationship between
> .mvn/maven.config options and command line options.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5967) Dependency updates
[ https://issues.apache.org/jira/browse/MNG-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5967: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Dependency updates > -- > > Key: MNG-5967 > URL: https://issues.apache.org/jira/browse/MNG-5967 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Trivial > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5889) .mvn directory should be picked when using --file
[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5889:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> .mvn directory should be picked when using --file
> -
>
> Key: MNG-5889
> URL: https://issues.apache.org/jira/browse/MNG-5889
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.3.3
>Reporter: Daniel Spilker
>Assignee: Tibor Digana
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> The {{.mvn}} directory is not picked up when using the {{--file}} switch to
> build a project from outside of the multi-module root.
> Example:
> * the module root is {{/foo/bar}}
> * {{.mvn}} is located at {{/foo/bar/.mvn}}
> * current directory is {{/foo}}
> * Maven is invoked with {{mvn --file bar/module/pom.xml}}
> I would expect the {{.mvn}} directory detection to start at the directory of
> the POM selected by {{--file}} and then go through the parent directories.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6092) warn if prerequisites.maven is used for non-plugin projects
[ https://issues.apache.org/jira/browse/MNG-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6092: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > warn if prerequisites.maven is used for non-plugin projects > --- > > Key: MNG-6092 > URL: https://issues.apache.org/jira/browse/MNG-6092 > Project: Maven > Issue Type: Wish > Components: core >Affects Versions: 3.3.9 >Reporter: Hervé Boutemy >Assignee: Karl Heinz Marbaise > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > as seen in MNG'4840 and documented in MNG-5297, in Maven 3, > prerequisites.maven has a meaning for plugin projects: defining this for > non-plugins projects makes feel that it will be checked like it was done in > Maven 2, but this is not the case. > Adding a warning could help people avoid this habit taken with Maven 2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6032) WARNING during build based on absolute path in assembly-descriptor.
[ https://issues.apache.org/jira/browse/MNG-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6032: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > WARNING during build based on absolute path in assembly-descriptor. > --- > > Key: MNG-6032 > URL: https://issues.apache.org/jira/browse/MNG-6032 > Project: Maven > Issue Type: Improvement > Components: Deployment >Affects Versions: needing-scrub-3.4.0-fallout >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6117) ${session.parallel} not correctly set
[
https://issues.apache.org/jira/browse/MNG-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6117:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> ${session.parallel} not correctly set
> -
>
> Key: MNG-6117
> URL: https://issues.apache.org/jira/browse/MNG-6117
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Richard Raumberger
>Assignee: Guillaume Boué
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Running {{mvn help:evaluate -T 3}} and resolving the property
> {{session.parallel}} returns {{true}} when run with Maven 3.0.5.
> When running it with 3.3.9, this property resolves to {{false}}.
> {code}
> mvn help:evaluate -T 3
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the MultiThreadedBuilder implementation with a thread count of 3
> [INFO]
> [INFO]
>
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
>
> [INFO]
> [INFO] --- maven-help-plugin:2.2:evaluate (default-cli) @ standalone-pom ---
> [INFO] No artifact parameter specified, using
> 'org.apache.maven:standalone-pom:pom:1' as project.
> [INFO] Enter the Maven expression i.e. ${project.groupId} or 0 to exit?:
> ${session.parallel}
> [INFO]
> false
> {code}
> E.g. Surefire
> [relies|https://github.com/apache/maven-surefire/blob/fb9b699e27dae905393a5bc4d5c6ae39606c3172/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L658]
> on this property, to check whether Maven is running in parallel mode, as
> mentioned in the comments of
> [SUREFIRE-1301|https://issues.apache.org/jira/browse/SUREFIRE-1301].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5829) mvn shell script fails with syntax error on Solaris 10
[
https://issues.apache.org/jira/browse/MNG-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5829:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> mvn shell script fails with syntax error on Solaris 10
> --
>
> Key: MNG-5829
> URL: https://issues.apache.org/jira/browse/MNG-5829
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.3
> Environment: Solaris 10
>Reporter: Zac Thompson
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> The {{$(cmd)}} idiom is used extensively in bin/mvn from lines 199-220, but
> this is not supported by older incarnations of /bin/sh (used on the shebang
> line). The {{`cmd`}} idiom is slightly more portable, and looks like it can
> probably be directly substituted.
> {noformat}
> find_maven_basedir() {
> local basedir=$(pwd)
> local wdir=$(pwd)
> while [ "$wdir" != '/' ] ; do
> wdir=$(cd "$wdir/.."; pwd)
> if [ -d "$wdir"/.mvn ] ; then
> basedir=$wdir
> break
> fi
> done
> echo "${basedir}"
> }
> # concatenates all lines of a file
> concat_lines() {
> if [ -f "$1" ]; then
> echo "$(tr -s '\n' ' ' < "$1")"
> fi
> }
> export MAVEN_PROJECTBASEDIR=${MAVEN_BASEDIR:-$(find_maven_basedir)}
> MAVEN_OPTS="$(concat_lines "$MAVEN_PROJECTBASEDIR/.mvn/jvm.config")
> $MAVEN_OPTS"
> {noformat}
> See MNG-5658 for an earlier case of a similar problem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Precedence of command-line system property options has changed
> --
>
> Key: MNG-6172
> URL: https://issues.apache.org/jira/browse/MNG-6172
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> The current state of master (what will eventually become 3.5.0) has reversed
> the precedence of command-line system property options compared to previous
> releases of Maven.
> For example, running this command with a basic project:
> {code}
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> {code}
> using current master will cause {{/tmp/aaa}} to be created (first-one-wins),
> whereas for all previous releases of Maven {{/tmp/zzz}} would have been
> created (last-one-wins)
> This has the potential to break CI builds which relied on the previous
> last-one-wins behaviour.
> This was introduced by the fix for MNG-6078
> https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
> - by reversing the whole array the precedence between options on the same
> command line has been reversed, not just the relationship between
> .mvn/maven.config options and command line options.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6138) Remove obsolete message_*.properties form maven-core
[
https://issues.apache.org/jira/browse/MNG-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6138:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Remove obsolete message_*.properties form maven-core
>
>
> Key: MNG-6138
> URL: https://issues.apache.org/jira/browse/MNG-6138
> Project: Maven
> Issue Type: Task
> Components: core
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> The folowing files are not used in the entire project tree:
> {noformat}
> $ find . -name '*.properties'
> ./src/main/resources/org/apache/maven/messages/messages.properties
> ./src/main/resources/org/apache/maven/messages/messages_de.properties
> ./src/main/resources/org/apache/maven/messages/messages_el.properties
> ./src/main/resources/org/apache/maven/messages/messages_en.properties
> ./src/main/resources/org/apache/maven/messages/messages_es.properties
> ./src/main/resources/org/apache/maven/messages/messages_fr.properties
> ./src/main/resources/org/apache/maven/messages/messages_ja.properties
> ./src/main/resources/org/apache/maven/messages/messages_ko.properties
> ./src/main/resources/org/apache/maven/messages/messages_nl.properties
> ./src/main/resources/org/apache/maven/messages/messages_no.properties
> ./src/main/resources/org/apache/maven/messages/messages_pl.properties
> ./src/main/resources/org/apache/maven/messages/messages_zh_CN.properties
> {noformat}
> The have been added years ago, but never used. Since we do not strive for any
> i18n, they are safe to be removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5579) Unify error output/check logic from shell and batch scripts
[
https://issues.apache.org/jira/browse/MNG-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5579:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Unify error output/check logic from shell and batch scripts
> ---
>
> Key: MNG-5579
> URL: https://issues.apache.org/jira/browse/MNG-5579
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.1.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Currently,
> both output two different messages.
> Shell:
> {quote}
> Error: JAVA_HOME is not defined correctly.
>We cannot execute $JAVACMD
> {quote}
> while batch says:
> {quote}
> Error: JAVA_HOME not found in your environment.
> Please set the JAVA_HOME variable in your environment to match the
> location of your Java installation.
> {quote}
> Same applies for {{M2_HOME}}. Additionally, testing for the Java command is
> handled different in both scripts. The batch script relies on JAVA_HOME while
> the shell script can ignore it. Both should require {{JAVA_HOME}} or warn
> about and use {{which java}}, respectively {{java}} in {{PATH}} ({{for %%X
> in (java.exe) do (set JAVACMD=%%~$PATH:X)}}) on Windows. After that should
> proceed to checking {{M2_HOME}}.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5946) Fix links etc. in README.txt which is part of the delivery
[ https://issues.apache.org/jira/browse/MNG-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5946: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Fix links etc. in README.txt which is part of the delivery > -- > > Key: MNG-5946 > URL: https://issues.apache.org/jira/browse/MNG-5946 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > Fixed the README.txt file which is packaged into the apache-maven binary > artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6106) Remove maven.home default value setter from m2.conf
[
https://issues.apache.org/jira/browse/MNG-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6106:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Remove maven.home default value setter from m2.conf
> ---
>
> Key: MNG-6106
> URL: https://issues.apache.org/jira/browse/MNG-6106
> Project: Maven
> Issue Type: Task
> Components: Bootstrap & Build, core
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> The {{set maven.home default ${user.home\}/m2}} seems to be a relic from
> ancient times: {{maven.home}} property is always defined by {{mvn}} launch
> script
> Even if it would be used, it wouldn't work because {{user.home}} never
> contains Maven's installation files. (?)
> This line can safely be removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6078) Can't overwrite properties which have been defined in .mvn/maven.config
[
https://issues.apache.org/jira/browse/MNG-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6078:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Can't overwrite properties which have been defined in .mvn/maven.config
> ---
>
> Key: MNG-6078
> URL: https://issues.apache.org/jira/browse/MNG-6078
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Currently properties which have been defined in {{.mvn/maven.config}} can't
> be overwritten via command line. This should be made possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6014) Removing ArtifactHandler for ejb3
[ https://issues.apache.org/jira/browse/MNG-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6014: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Removing ArtifactHandler for ejb3 > - > > Key: MNG-6014 > URL: https://issues.apache.org/jira/browse/MNG-6014 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > Remove the ejb3 ArtifactHandler cause we don't have any bounded life cycle > since Maven 3.3.9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5954) Remove outdated maven-embedder/src/main/resources/META-INF/MANIFEST.MF
[ https://issues.apache.org/jira/browse/MNG-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5954: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Remove outdated maven-embedder/src/main/resources/META-INF/MANIFEST.MF > -- > > Key: MNG-5954 > URL: https://issues.apache.org/jira/browse/MNG-5954 > Project: Maven > Issue Type: Task > Components: Embedding >Affects Versions: 3.3.9 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > File is outdated and not used anymore. Remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5993) Confusing error message in case of missing/empty artifactId and version in pluginManagement
[
https://issues.apache.org/jira/browse/MNG-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5993:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Confusing error message in case of missing/empty artifactId and version in
> pluginManagement
> ---
>
> Key: MNG-5993
> URL: https://issues.apache.org/jira/browse/MNG-5993
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
>Affects Versions: 3.3.9
>Reporter: Konrad Windszus
>Assignee: Karl Heinz Marbaise
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Executing any goals/phases on this pom.xml leads to a weird error
> {code}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> com.example.group
> testinvalidpom
> 0.0.1-SNAPSHOT
>
>
>
>
>
>
>
>
>
>
>
> {code}
> The error being emitted is
> {code}
> [ERROR] Error resolving version for plugin ':null' from the repositories
> [local (), nexus ()]: Plugin not found in
> any plugin repository -> [Help 1]
> {code}
> Even with debug you only see something like this
> {code}
> [ERROR] Error resolving version for plugin ':null' from the repositories
> [...]: Plugin not found in any plugin repository -> [Help 1]
> org.apache.maven.plugin.version.PluginVersionResolutionException: Error
> resolving version for plugin ':null' from the repositories [local
> (/Users/konradwindszus/.m2/repository), nexus
> (https://repo.int.netcentric.biz/nexus/content/groups/public/)]: Plugin not
> found in any plugin repository
> at
> org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.selectVersion(DefaultPluginVersionResolver.java:236)
> at
> org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.resolveFromRepository(DefaultPluginVersionResolver.java:148)
> at
> org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.resolve(DefaultPluginVersionResolver.java:96)
> at
> org.apache.maven.lifecycle.internal.LifecyclePluginResolver.resolveMissingPluginVersions(LifecyclePluginResolver.java:89)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:135)
> at
> org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan(BuilderCommon.java:97)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:109)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
> In this example the error is easy to spot, but for bigger pom.xmls with more
> complex hierarchies it is very hard.
> Some basic validation should take place that on the merged pom.xml all of
> groupId, artifactId and version is available and if that is not the case, the
> line number of the pom.xml together with the filename should be given out,
> where the according information is missing.
> A similar error is emitted in case the groupId element is missing as well or
> t
[jira] [Updated] (MNG-6140) update documentation's dependency graph with resolver + resolver-provider + slf4j-provider
[ https://issues.apache.org/jira/browse/MNG-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6140: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > update documentation's dependency graph with resolver + resolver-provider + > slf4j-provider > -- > > Key: MNG-6140 > URL: https://issues.apache.org/jira/browse/MNG-6140 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > http://maven.apache.org/ref/3-LATEST/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6001) Replace %HOME% with %USERPROFILE% in mvn.cmd
[
https://issues.apache.org/jira/browse/MNG-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6001:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Replace %HOME% with %USERPROFILE% in mvn.cmd
>
>
> Key: MNG-6001
> URL: https://issues.apache.org/jira/browse/MNG-6001
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Setting {{HOME=%HOMEDRIVE%%HOMEPATH%}} is a relic from Windows NT times. The
> preferred way is to use {{%USERPROFILE%}} which is already done in Java 8
> internally.
> Let's use it to load the {{mavenrc}} scripts.
> Some references:
> * http://stackoverflow.com/a/36392591/696632
> * http://stackoverflow.com/a/21599376/696632
> * http://bugs.java.com/view_bug.do?bug_id=4787931
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6109) PluginDescriptor doesn't read since value of parameter
[
https://issues.apache.org/jira/browse/MNG-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6109:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> PluginDescriptor doesn't read since value of parameter
> --
>
> Key: MNG-6109
> URL: https://issues.apache.org/jira/browse/MNG-6109
> Project: Maven
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.3.9
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> This causes missing information for code manipulating plugins "normally"
> through PluginDescriptor read by Maven core from
> {{META-INF/maven/plugin.xml}}.
> For example MPLUGIN-319, which parses code to create PluginDescriptor then
> generate {{META-INF/maven/plugin.xml}}, but gets truncated info when getting
> back PluginDescriptor as read by Maven core...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5975) Use Java 7's SimpleDateFormat in CLIReportingUtils#formatTimestamp
[ https://issues.apache.org/jira/browse/MNG-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5975: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Use Java 7's SimpleDateFormat in CLIReportingUtils#formatTimestamp > -- > > Key: MNG-5975 > URL: https://issues.apache.org/jira/browse/MNG-5975 > Project: Maven > Issue Type: Improvement > Components: Embedding >Affects Versions: 3.3.9 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > The current code manually formats the timestamp because Commons Lang 3 was > not in the dependencies list. Now there is, drop custom code and use builtin > features. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6147) MetadataResolutionResult#getGraph() contains duplicate if clause
[ https://issues.apache.org/jira/browse/MNG-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6147: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > MetadataResolutionResult#getGraph() contains duplicate if clause > > > Key: MNG-6147 > URL: https://issues.apache.org/jira/browse/MNG-6147 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.3.9 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > There is an duplicate if clause from lines 110 to 125 which can safely be > removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6136) Upgrade Maven Wagon from 2.10 to 2.12
[ https://issues.apache.org/jira/browse/MNG-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6136: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Upgrade Maven Wagon from 2.10 to 2.12 > - > > Key: MNG-6136 > URL: https://issues.apache.org/jira/browse/MNG-6136 > Project: Maven > Issue Type: Task > Components: Deployment >Affects Versions: 3.3.9 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > Let's absorb latest improvements to Wagon into Maven. > Release Notes - Maven Wagon - Version 2.11 > Release Notes - Maven Wagon - Version 2.12 > ** Bug > * [WAGON-408] - ITs for #testSecuredGet() fail with Windows > * [WAGON-426] - Fingerprints loss in known_hosts > * [WAGON-439] - Jsch issue in java 1.7 and Kerberos-enabled ssh servers > * [WAGON-449] - CLIENT not changed after setting > PoolingHttpClientConnectionManager > * [WAGON-469] - wagon-http does not enable Expect-Continue by default > * [WAGON-475] - TransferEvent GET used instead of PUT and vice versa > * [WAGON-476] - HTTP Provider follows redirects on PUT and may change > request method > * [WAGON-479] - Preemptive auth with HTTP Provider may fail because > BasicScheme is added as completed=true to the AuthCache > * [WAGON-480] - Non-threadsafe HttpClientContext is shared between > threaded use of HttpClientWagon > * [WAGON-481] - Sensitive (auth) information is not cleared when > HttpClientWagon is disconnected > * [WAGON-485] - ScpWagon parses file size to int causing overflow for > large files > ** Improvement > * [WAGON-455] - Upgrade of 'plexus-utils' to version 3.0.23. > * [WAGON-458] - Implementation for FTPS > * [WAGON-460] - Upgrade plexus-utils to 3.0.24 > * [WAGON-464] - Upgrade jsch dependency to 0.1.51 or newer to support > ECDSA host key typess > * [WAGON-465] - wagon-ssh: add API option to check for remote exit code > * [WAGON-466] - wagon-ssh: Better error message when ssh account is locked > * [WAGON-467] - wagon-ssh: options to configure hostKeyChecking and > PreferredAuthentications > * [WAGON-472] - Upgrade Commons IO to 2.5 > * [WAGON-484] - Update WebDAV Provider naming > ** Task > * [WAGON-389] - Incorrect versions on gh-pages > * [WAGON-447] - Remove Commons Lang 2 for a few cases > * [WAGON-457] - Wagon tests fail on Windows because Subversion crashes on > a test repo > * [WAGON-470] - Update TLS certificates for HTTPS tests > * [WAGON-471] - Clean up dependency mess (reported by dependency:analyze) > * [WAGON-473] - Don't abuse IllegalArgumentException to intercept null > input > * [WAGON-474] - Upgrade and revise all tests for Jetty 8 > * [WAGON-483] - Upgrade SLF4J to 1.7.22 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6150) Javadoc improvements for 3.5.0
[ https://issues.apache.org/jira/browse/MNG-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6150: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Javadoc improvements for 3.5.0 > -- > > Key: MNG-6150 > URL: https://issues.apache.org/jira/browse/MNG-6150 > Project: Maven > Issue Type: Improvement > Components: core >Reporter: Stephen Connolly >Assignee: Michael Osipov >Priority: Trivial > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > Catch all for Javadoc improvements -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5852) mvn shell script invokes /bin/sh but requires Bash functions
[
https://issues.apache.org/jira/browse/MNG-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5852:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> mvn shell script invokes /bin/sh but requires Bash functions
>
>
> Key: MNG-5852
> URL: https://issues.apache.org/jira/browse/MNG-5852
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.3
> Environment: Solaris 11
>Reporter: Jeffrey Alexander
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> The bin/mvn script uses the "local" command which is a shell builtin of bash
> and similar shells, but is not required for POSIX-compliance in sh. When I
> attempt to run mvn on my Solaris system, I see the following output:
> {noformat}
> $ ./mvn
> ./mvn[200]: local: not found [No such file or directory]
> ./mvn[201]: local: not found [No such file or directory]
> ...
> {noformat}
> Lines 200 and 201 invoke "local" to make local variables to the function.
> According to "man bash", this is a shell builtin. However, bin/mvn is
> invoked as:
> #!/bin/sh
> On most flavors of linux, this resolves to bash or dash which probably runs
> in a restricted environment after checking to see that its $0 is sh. But on
> Solaris's /bin/sh is actually ksh93 for backwards compatibility.
> Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a
> script that is invoked with /bin/sh is a bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5977) Improve output readability of our MavenTransferListener implementations
[
https://issues.apache.org/jira/browse/MNG-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5977:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Improve output readability of our MavenTransferListener implementations
> ---
>
> Key: MNG-5977
> URL: https://issues.apache.org/jira/browse/MNG-5977
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Embedding
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
> Attachments: current.zip, improved-debug.zip, improved.zip
>
>
> The current output of Downloading/Downladed/Uploading/Uploaded transfer
> notification has some flaws:
> 1. It does not scale numbers between 1 and 1000 with appropriate units
> 2. It should use correct size ({{kB}}, {{MB}}, {{GB}} and time units ({{s}})
> but doesn't. (see https://en.wikipedia.org/wiki/Binary_prefix and
> https://en.wikipedia.org/wiki/Metric_prefix)
> 3. When Aether downloads in parallel (which applies for non-POM files) the
> progress interleaves due to race conditions to {{System.out}} and you do not
> know to which resource a progress belongs to.
> Let's use an improved version of MPIR {{DependenciesRenderer}}'s
> [{{FileDecimalFormat}}|https://github.com/apache/maven-plugins/blob/trunk/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/dependencies/renderer/DependenciesRenderer.java#L1583]
> for it.
> concrete examples:
> before
> {noformat}191/191 KB 27/48 KB 48/119 KB 80/87 KB 13/13 KB {noformat}
> after:
> {noformat}Progress (4): 500/800 B | 40/45 kB | 193 kB/315 kB | 1.3/9.0 MB |
> 12/30 MB{noformat}
> if total size is unavailable or the file has already been downloaded but not
> removed from the list, the output will be:
> {noformat}Progress (4): 800 B | 40/45 kB | 193 kB | 9.0 MB | 12 MB{noformat}
> or in debug mode:
> {noformat}Progress (5): xml-apis-1.3.04.jar () |
> maven-shared-utils-0.6.jar () | xercesImpl-2.9.1.jar () |
> commons-digester-1.6.jar () | maven-reporting-impl-2.3.jar
> (){noformat}
> If the scale is between 1 and 10, one decimal place will be printed out. If
> it is between 10 and 1000+, it will be an integer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6017) Removing ArtifactHandler for par LifeCycle
[ https://issues.apache.org/jira/browse/MNG-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6017: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Removing ArtifactHandler for par LifeCycle > -- > > Key: MNG-6017 > URL: https://issues.apache.org/jira/browse/MNG-6017 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > Remove the ArtifactHandler definition for par lifecycle which has been > [removed in Maven 3.3.9|MNG-5892] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6171) REGRESSION: WARNING about usage of a non threadsafe marked plugin is not showed anymore
[
https://issues.apache.org/jira/browse/MNG-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6171:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> REGRESSION: WARNING about usage of a non threadsafe marked plugin is not
> showed anymore
> ---
>
> Key: MNG-6171
> URL: https://issues.apache.org/jira/browse/MNG-6171
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.1, 3.2.5, 3.3.9
>Reporter: Karl Heinz Marbaise
>Assignee: Hervé Boutemy
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> If you call Maven via command line like this:
> {{mvn -T 5 versions:set -DnewVersion=...}} in Maven 3.0.5, 3.1.1 you will get
> a message like this:
> {code}
> [INFO] Building with 20 threads
> [INFO]
> [INFO]
>
> [INFO] Building reactor-parent 1.0-SNAPSHOT
> [INFO]
>
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in reactor-parent:
> [WARNING] org.codehaus.mojo:versions-maven-plugin:2.3
> [WARNING] *
> [INFO]
> [INFO] --- versions-maven-plugin:2.3:set (default-cli) @ reactor-parent ---
> [INFO] Searching for local aggregator root...
> [INFO] Local aggregation root:
> /Users/kama/ws-git-soebes/maven-memory-problem/test-project/reactor
> [INFO] Processing change of org.test.parent:reactor-parent:1.0-SNAPSHOT ->
> 1.0-SNAPSHOT
> [INFO]
>
> {code}
> Starting with Maven 3.2.5 and above you don't get the WARNING anymore. Also
> for [current Master of
> Maven|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=0284dda81beb43b54116326f9a6efd439d40c922]
> it will not beed showed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6030) ReactorModelCache do not used effectively after maven version 3.0.5 which cause a large memory footprint
[
https://issues.apache.org/jira/browse/MNG-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6030:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> ReactorModelCache do not used effectively after maven version 3.0.5 which
> cause a large memory footprint
>
>
> Key: MNG-6030
> URL: https://issues.apache.org/jira/browse/MNG-6030
> Project: Maven
> Issue Type: Improvement
> Components: Embedding
>Affects Versions: 3.1.1, 3.2.5, 3.3.3, 3.3.9
>Reporter: Andriy
>Assignee: Karl Heinz Marbaise
> Labels: memory, performance
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
> Attachments: generate.heavy.parent.pom.and.deep.hierarchy.groovy,
> generate.heavy.parent.pom.groovy, screenshot-maven-3.0.5.png,
> screenshot-maven-3.3.9-details.png, screenshot-maven-3.3.9.png
>
>
> after version 3.0.5 we found a very big memory consumption with maven. needed
> for build memory grows from 1G to 5G
> According to current implementation there were change with commit
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=e778ea67121f17232a7dced3fb4f0a205ffa64af
>
> https://issues.apache.org/jira/browse/MNG-5312
> {code}
> private ModelBuildingRequest getModelBuildingRequest( InternalConfig config )
> {
> @@ -256,7 +256,7 @@ public class DefaultProjectBuilder
> request.setUserProperties( configuration.getUserProperties() );
> request.setBuildStartTime( configuration.getBuildStartTime() );
> request.setModelResolver( resolver );
> -request.setModelCache( config.modelCache );
> +request.setModelCache( new ReactorModelCache() );
> return request;
> }
> {code}
> and as result new ReactorModelCache created for each ModelBuildingRequest
> which is created new to parse each pom.xml included in the build as module.
> so if there is a big projects with a lot of modules ModelBuildingRequest is
> created for each of them and parse result is not reused between modules. and
> if all this modules has the same parent pom it parsed each time and stored as
> many times as many ModelBuildingRequest was created. As parent pom often
> contains dependencies, dependencyManagement and common information for all
> modules it cause a larger memory footprint then was before. In version 3.0.5
> and earlier ReactorModelCache was single and was reused between
> ModelBuildingRequest.
> in our cause footprint grew from 1g to 5g.
> it will be better to reuse result of parsing pom files between
> ModelBuildingRequests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5607) Don't use M2_HOME in mvn shell/command scripts anymore
[
https://issues.apache.org/jira/browse/MNG-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5607:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Don't use M2_HOME in mvn shell/command scripts anymore
> --
>
> Key: MNG-5607
> URL: https://issues.apache.org/jira/browse/MNG-5607
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.2.1
> Environment: all
>Reporter: Karl Heinz Marbaise
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Currently the {{mvn}} shell script and the {{mvn.bat}} using {{M2_HOME}}.
> This should be changed either to {{MAVEN_HOME}} or {{M3_HOME}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6068) Document default scope compile in pom XSD and reference documentation
[
https://issues.apache.org/jira/browse/MNG-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6068:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Document default scope compile in pom XSD and reference documentation
> -
>
> Key: MNG-6068
> URL: https://issues.apache.org/jira/browse/MNG-6068
> Project: Maven
> Issue Type: Improvement
> Components: core, POM
>Affects Versions: 3.3.9
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Many people referencing the XSD of the POM file as reference and missing
> information in there.
> So adding the information about the default scope which is {{compile}}:
> http://maven.apache.org/ref/3.3.9/maven-model/maven.html#class_dependency
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6152) Add a Jenkinsfile so that builds.apache.org can use multibranch pipeline
[ https://issues.apache.org/jira/browse/MNG-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6152: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Add a Jenkinsfile so that builds.apache.org can use multibranch pipeline > > > Key: MNG-6152 > URL: https://issues.apache.org/jira/browse/MNG-6152 > Project: Maven > Issue Type: Task > Components: core >Reporter: Stephen Connolly >Assignee: Stephen Connolly > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > We want to enable multibranch pipeline support on our CI infrastructure so > that all branches can get integration test verification -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6102) Introduce ${maven.conf} in m2.conf
[
https://issues.apache.org/jira/browse/MNG-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6102:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Introduce ${maven.conf} in m2.conf
> --
>
> Key: MNG-6102
> URL: https://issues.apache.org/jira/browse/MNG-6102
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build, core, Settings, Toolchains
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Package maintainers always try to fit a product into the file hierarchy
> given/mandated by the OS/distribution. They separate the application from the
> configuration to have one common place for every bit. Currently, Maven does
> not properly support his. {{conf/}} is tightly coupled with {{maven.home}}
> property and cannot be changed unless the Java code changes. Impossible for a
> maintainer to stick to
> [FHS|https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard] or
> [{{heir(7)}}|https://www.freebsd.org/cgi/man.cgi?query=hier&sourceid=opensearch].
> By introducing a {{maven.conf}} property in {{m2.conf}}, a maintainer can
> easily move the configuration files to {{/usr/local/etc/maven3}}, decouple it
> from the installation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6003) Drastically reduce JAVA_HOME discovery code
[
https://issues.apache.org/jira/browse/MNG-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6003:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Drastically reduce JAVA_HOME discovery code
> ---
>
> Key: MNG-6003
> URL: https://issues.apache.org/jira/browse/MNG-6003
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Our [installation documentation|https://maven.apache.org/install.html]
> several times requires that {{JAVA_HOME}} is set and points to a valid JDK.
> Though, tens of lines in {{mvn}} and {{mvn.cmd}} perform some magic to
> discover it when it is not set. This completely contradicts our requirement
> that {{JAVA_HOME}} must be set.
> We can drastically reduce this code by checking if {{JAVA_HOME}} is set and
> use it, if not perform {{which java}} and use that to run Maven. Not adhering
> to our requirements is deemed to undefined behavior. A developer must be able
> to set this simple env var properly. In most cases on Unix/Linux OpenJDK is
> installed anyway which means that {{which java}} points to a JDK anyway. For
> instance, the {{JAVA_HOME}} discovery on FreeBSD competely fails and sets it
> to {{/usr/local}} because {{/usr/local/bin/java}} is actually a wrapper
> script.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6053) Unsafe System Properties copy in MavenRepositorySystemUtils, causing NPEs
[
https://issues.apache.org/jira/browse/MNG-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6053:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Unsafe System Properties copy in MavenRepositorySystemUtils, causing NPEs
> -
>
> Key: MNG-6053
> URL: https://issues.apache.org/jira/browse/MNG-6053
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
> Environment: Eclipse m2e 1.7
>Reporter: Fred Bricon
>Assignee: Guillaume Boué
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> This bug has been reported in m2e
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=493871:
> {quote}
> I'm occasionally, not 100% reliably reproducible, but regularly enough (like
> it occurs every now and then, not just once) seeing the error below, in the
> Error Log of Eclipse during workspace rebuilds. This is with M2E 1.7.0. --
> I'm not sure if this is just "annoying" or actually prevents M2E from
> correctly configuring projects (?). Either way, perhaps it would be possible
> to "harden" respective code to prevent this?
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at
> org.apache.maven.repository.internal.MavenRepositorySystemUtils.newSession(MavenRepositorySystemUtils.java:133)
> at
> org.apache.maven.internal.aether.DefaultRepositorySystemSessionFactory.newRepositorySession(DefaultRepositorySystemSessionFactory.java:98)
> at
> org.apache.maven.DefaultMaven.newRepositorySession(DefaultMaven.java:352)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.createRepositorySession(MavenImpl.java:309)
> {quote}
> Looking at
> https://github.com/apache/maven/blob/86b656167923923e2e416def4a48303b4e6248fa/maven-aether-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java#L132,
> it seems some system property is null (maybe due to some concurrency issue),
> and given that Hashtable doesn't support null values, then it throws an NPE
> on the put() call
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6110) Upgrade Aether to Maven Resolver
[ https://issues.apache.org/jira/browse/MNG-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6110: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Upgrade Aether to Maven Resolver > > > Key: MNG-6110 > URL: https://issues.apache.org/jira/browse/MNG-6110 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.3.9 >Reporter: Harald Wellmann >Assignee: Hervé Boutemy > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > Replace Aether by Maven Resolver to make use of the latest bugfixes and > enhancements related to dependency collection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6146) Several small stylistic and spelling improvements to code and documentation
[
https://issues.apache.org/jira/browse/MNG-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6146:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Several small stylistic and spelling improvements to code and documentation
> ---
>
> Key: MNG-6146
> URL: https://issues.apache.org/jira/browse/MNG-6146
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> The following can easily be squashed:
> {noformat}
> d99f9ef8c7ffe56966945d6f1b66f0280866ded5 Fix checkstyle error
> 1c9362be4328713386bd23b01f9e2c87674cb952 Use static final values instead of
> literals
> 52945a679ec8f3f571d77658eda2fce06d637aa7 Use proper spelling of "e.g."
> a26cc1b9636e19c28cd32ed1c844fec64dec55b6 Use the proper term for char U+002D
> (-) hyphen(-minus) instead of dash
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6093) create a slf4j-simple provider extension that supports level color rendering
[ https://issues.apache.org/jira/browse/MNG-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6093: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > create a slf4j-simple provider extension that supports level color rendering > > > Key: MNG-6093 > URL: https://issues.apache.org/jira/browse/MNG-6093 > Project: Maven > Issue Type: New Feature > Components: Logging >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > With color support, core Maven and plugins do general message colorization > (or more high-level "message styling" through maven-shared-utils) > slf4j provider however has to add color: > - for log level output (DEBUG/INFO/WARNING/ERROR) > - for stacktrace rendering > That's why we use Gossip slf4j provider: it has sufficient little extension > points to add this, with just a little bit of code (see > http://maven.apache.org/ref/3-LATEST/maven-embedder/apidocs/org/apache/maven/cli/logging/impl/gossip/package-summary.html > ) and configuration > The issue with switching to Gossip slf4j provider is that people don't know > it and it does not have the same features as slf4j-simple (missing relative > timestamps and configuration with CLI: see > http://mail-archives.apache.org/mod_mbox/maven-dev/201607.mbox/%3CCAK8jvqxYNK4weM2Frp4Brg3J7EybyjBiCsSRdGuNMQhYAG728Q%40mail.gmail.com%3E > ), the configuration file is not the same (name nor content). > But the extension points are not that big: if slf4j-simple provider just made > a few methods protected instread of private, it would be extensible > What if we just copy slf4j-simple to change the signatures and create small > extension classes? The license permits it, we can try it and eventually see > with slf4j if the modification can go into official release -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6145) Remove non-existent m2 include in component.xml
[
https://issues.apache.org/jira/browse/MNG-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6145:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Remove non-existent m2 include in component.xml
>
>
> Key: MNG-6145
> URL: https://issues.apache.org/jira/browse/MNG-6145
> Project: Maven
> Issue Type: Improvement
> Components: Deployment
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Trivial
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> {{apache-maven/src/main/assembly/component.xml}} defines an include a file
> {{m2}} which does not exist anymore. It is safe to remove this include.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5963) mvn.cmd does not return ERROR_CODE
[ https://issues.apache.org/jira/browse/MNG-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5963: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > mvn.cmd does not return ERROR_CODE > -- > > Key: MNG-5963 > URL: https://issues.apache.org/jira/browse/MNG-5963 > Project: Maven > Issue Type: Bug >Affects Versions: 3.3.9 > Environment: Windows 10 >Reporter: Larry Singer >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > mvn.cmd does not return an ERROR_CODE value to an enclosing script in > WIndows. Running this script: > @ECHO OFF > CALL mvn clean install > echo "%ERROR_CODE%" > Now shows "". Previously it showed "0" for success and "1" for error. > It appears that there is an @endlocal missing. A possible fix is to add > @endlocal & set ERROR_CODE=%ERROR_CODE% > before > exit /B %ERROR_CODE% -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6081) Log refactoring - Method Invocation Replaced By Variable
[
https://issues.apache.org/jira/browse/MNG-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6081:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Log refactoring - Method Invocation Replaced By Variable
>
>
> Key: MNG-6081
> URL: https://issues.apache.org/jira/browse/MNG-6081
> Project: Maven
> Issue Type: Improvement
> Components: core
>Affects Versions: 3.3.9
>Reporter: Nemo Chen
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
> Attachments: MNG-6081.patch
>
>
> *Method Invocation Replaced By Variable*
> In file:
> apache-maven-3.3.9/maven-compat/src/main/java/org/apache/maven/artifact/resolver/DebugResolutionListener.java
> from line 70:
> {code}
> String keptVersion = kept.getVersion();
> if ( omittedVersion != null ? !omittedVersion.equals( keptVersion ) :
> keptVersion != null )
> {
> logger.debug( indent + omitted + " (removed - nearer found: " +
> kept.getVersion() + ")" );
> }
> {code}
> the "kept.getVersion()" can be replaced with "keptVersion" for the sake of
> simplicity and readability.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6088) after forked execution success, add an empty line
[ https://issues.apache.org/jira/browse/MNG-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6088: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > after forked execution success, add an empty line > - > > Key: MNG-6088 > URL: https://issues.apache.org/jira/browse/MNG-6088 > Project: Maven > Issue Type: Wish > Components: Embedding >Affects Versions: 3.3.9 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > while working on MSHARED-589 to improve maven-site-plugin output when forking > executions for reports preparation, I found that since start of forked > execution adds a newline before starting, end of the execution should add an > empty line also for better rendering > such newline can easily be added in maven-reporting-exec, but it seems more > logical to add it in Maven core instead -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5878) add support for module name != artifactId in every calculated URLs (project, SCM, site): special project.directory property
[
https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5878:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> add support for module name != artifactId in every calculated URLs (project,
> SCM, site): special project.directory property
> ---
>
> Key: MNG-5878
> URL: https://issues.apache.org/jira/browse/MNG-5878
> Project: Maven
> Issue Type: New Feature
> Components: Inheritance and Interpolation
>Affects Versions: 3.3.3
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Say you have this project structure:
> {noformat}
> /
> |-- module1
> |-- module2
> {noformat}
> and artifactIds are named:
> {noformat}
> my-parent
> |-- my-module1
> |-- my-module2
> {noformat}
> Prefix {{my-}} is omitted for brevity in module names. For instance, Jersey
> does that.
> When the SCM report is built, the artifactId is always used for path
> composition which leads to incorrect URLs. You can of course set the
> parameter {{checkoutDirectoryName}} but this would be extremely tedious for
> all modules down the tree.
> The code should obtain the module name and use it for URL composition.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5368) UnsupportedOperationException thrown when version range is not correct in dependencyManagement definitions
[
https://issues.apache.org/jira/browse/MNG-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5368:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> UnsupportedOperationException thrown when version range is not correct in
> dependencyManagement definitions
> --
>
> Key: MNG-5368
> URL: https://issues.apache.org/jira/browse/MNG-5368
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4
> Environment: MacOS 10.7.5 Darwin Kernel Version 11.4.2:
> xnu-1699.32.7~1/RELEASE_X86_64 x86_64
>Reporter: Andrew Haines
>Assignee: Christian Schulte
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> When specifying a non valid version range in a dependencyManagement tag,
> instead of a descriptive error message we get a UnsupportedOperationException
> thrown. The code at fault in
> org.apache.maven.project.MavenProject#getManagedVersionMap is:
> {code}
> map = new HashMap();
> for ( Iterator i =
> dependencyManagement.getDependencies().iterator(); i.hasNext(); )
> {
> Dependency d = i.next();
> Artifact artifact =
> repositorySystem.createDependencyArtifact( d );
> if ( artifact == null )
> {
> map = Collections.emptyMap();
> }
> map.put( d.getManagementKey(), artifact );
> {code}
> When the artifact is null, the map is set to an immutable map and then the
> null artifact is then attempted to be put into it. This will always fail.
> This particular problem originates from code further down the stack in
> org.apache.maven.repository.legacy.LegacyRepositorySystem:
> {code}
>public Artifact createDependencyArtifact( Dependency d )
> {
> VersionRange versionRange;
> try
> {
> versionRange = VersionRange.createFromVersionSpec( d.getVersion()
> );
> }
> catch ( InvalidVersionSpecificationException e )
> {
> return null;
> }
> {code}
> Instead of signalling appropriately that an error has occurred, this
> exception is consumed and thus causes the erroneous behaviour mentioned in
> the first code snippet
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5931) Fixing documentation
[ https://issues.apache.org/jira/browse/MNG-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5931: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Fixing documentation > - > > Key: MNG-5931 > URL: https://issues.apache.org/jira/browse/MNG-5931 > Project: Maven > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > We need to fix the docs on the following page > http://maven.apache.org/ref/3.3.9/maven-core/default-bindings.html cause we > have removed maven-ejb-plugin and par lifecycle... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5962) mvn.cmd fails when the current directory has spaces in between
[
https://issues.apache.org/jira/browse/MNG-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5962:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> mvn.cmd fails when the current directory has spaces in between
> --
>
> Key: MNG-5962
> URL: https://issues.apache.org/jira/browse/MNG-5962
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.3, 3.3.9
> Environment: Windows 7
>Reporter: Miriam Lee
>Assignee: Michael Osipov
>Priority: Minor
> Labels: easyfix, newbie
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
> Attachments: MNG-5962-apache-maven.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Executing {{mvn.cmd}} when the current directory has spaces in between
> outputs {{The system cannot find the path specified.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6144) DefaultWagonManagerTest#testGetMissingJarForced() passed incorrect value
[
https://issues.apache.org/jira/browse/MNG-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6144:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> DefaultWagonManagerTest#testGetMissingJarForced() passed incorrect value
>
>
> Key: MNG-6144
> URL: https://issues.apache.org/jira/browse/MNG-6144
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.3.9
>Reporter: August Shi
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> {{DefaultWagonManagerTest#testGetMissingJarForced()}} passes {{false}}, but
> method name requires {{true}} to be passed to the {{WagonManager}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5823) mvnDebug doesn't work with M2_HOME with spaces - missing quotes
[
https://issues.apache.org/jira/browse/MNG-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5823:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> mvnDebug doesn't work with M2_HOME with spaces - missing quotes
> ---
>
> Key: MNG-5823
> URL: https://issues.apache.org/jira/browse/MNG-5823
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.1
> Environment: Windows, Cygwin
>Reporter: Tobias Oberlies
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> When calling {{mvnDebug}} in a Cygwin shell, I get the following error
> {noformat}
> Preparing to Execute Maven in Debug Mode
> dirname: extra operand `Files/Maven/apache-maven-3.3.1/bin/mvnDebug'
> Try `dirname --help' for more information.
> env: /mvn: No such file or directory
> {noformat}
> The root cause are missing quotes in and around the dirname call. The script
> currently calls
> {noformat}
> env MAVEN_OPTS="$MAVEN_OPTS $MAVEN_DEBUG_OPTS" $(dirname $0)/mvn "$@"
> {noformat}
> but the call should be
> {noformat}
> env MAVEN_OPTS="$MAVEN_OPTS $MAVEN_DEBUG_OPTS" "$(dirname "$0")/mvn" "$@"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5958) java.lang.String cannot be cast to org.apache.maven.lifecycle.mapping.LifecyclePhase
[
https://issues.apache.org/jira/browse/MNG-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5958:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
>
>
> Key: MNG-5958
> URL: https://issues.apache.org/jira/browse/MNG-5958
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.3.9
> Environment: win 8.1
>Reporter: Meytal Genah
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Our app uses flex mojo.
> We upgraded from Maven 3.3.3 to Maven 3.3.9 and when building we get:
> {noformat}[ERROR] Internal error: java.lang.ClassCastException:
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhas
> e
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:119)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:64)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:451)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:421)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:620)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:411)
> at
> org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> ... 11 more{noformat}
> I didn’t see anyone encountering the same problem. Maybe it is related to the
> fix of https://issues.apache.org/jira/browse/MNG-5805.
> Also, according to the stack trace, the invalid casting is in this line:
> {code:java}LifecyclePhase goals =
> goalsForLifecyclePhase.getValue();{code}
> this is the content of the pom.xml:
> {code:xml}http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
>com.myapp.plugin
> GUI
> trunk
>
> myapp-war
> 1.0
> war
> Plugin GUI WAR
>
>
[jira] [Updated] (MNG-6137) Clean up duplicate dependencies caused by incomplete Wagon HTTP Provider exclusions
[
https://issues.apache.org/jira/browse/MNG-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6137:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Clean up duplicate dependencies caused by incomplete Wagon HTTP Provider
> exclusions
> ---
>
> Key: MNG-6137
> URL: https://issues.apache.org/jira/browse/MNG-6137
> Project: Maven
> Issue Type: Task
> Components: Deployment
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Some dependencies are duplicated in {{$\{maven.home}/lib}} because not all
> shaded dependencies of Wagon HTTP Provider are excluded. This can easily be
> cleaned up when Wagon 2.12 is merged.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5836) logging config is overridden by $M2_HOME/lib/ext/*.jar
[
https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5836:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> logging config is overridden by $M2_HOME/lib/ext/*.jar
> --
>
> Key: MNG-5836
> URL: https://issues.apache.org/jira/browse/MNG-5836
> Project: Maven
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: Hervé Boutemy
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> If one of the jars in {{$M2_HOME/lib/ext/*.jar}} happens to have
> {{simplelogger.properties}}, that configuration file masks logging
> configuration under {{$M2_HOME/conf/logging}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5297) Site should tell 'prerequisites.maven is deprecated'
[ https://issues.apache.org/jira/browse/MNG-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5297: -- Fix Version/s: (was: 3.3.9) 3.5.0-alpha-2 3.5.0-alpha-1 > Site should tell 'prerequisites.maven is deprecated' > > > Key: MNG-5297 > URL: https://issues.apache.org/jira/browse/MNG-5297 > Project: Maven > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 3.0.4 >Reporter: Kengo TODA >Assignee: Jason van Zyl >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > MNG-4840 said 'enforcement of the build environment is left to the Maven > Enforcer Plugin'. > http://jira.codehaus.org/browse/MNG-4840?focusedCommentId=253900&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-253900 > But currently, there is no 'deprecated' mark at Maven site. > http://maven.apache.org/ref/3.0.4/maven-model/maven.html#prerequisites > I think site should has 'deprecated' mark like 'reports' element. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5904) Remove the whole Ant build
[ https://issues.apache.org/jira/browse/MNG-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5904: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Remove the whole Ant build > -- > > Key: MNG-5904 > URL: https://issues.apache.org/jira/browse/MNG-5904 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: needing-scrub-3.4.0-fallout >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > We should remove the whole Ant build cause we have a large number of Maven > versions which could be used to start building Maven itself. > So i don't see any usefulness in it anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5961) Maven possibly not aware of log4j2
[
https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5961:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Maven possibly not aware of log4j2
> --
>
> Key: MNG-5961
> URL: https://issues.apache.org/jira/browse/MNG-5961
> Project: Maven
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.3.9
>Reporter: Mike Drob
>Assignee: Arnaud HERITIER
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Using a fresh install of maven 3.3.9 I followed the steps at
> https://garygregory.wordpress.com/2015/03/23/watch-maven-in-color to add
> color highlighting to my output. Everything works as expected, however on all
> usages I would get the warning:
> {noformat}
> [WARN] The SLF4J binding actually used is not supported by Maven:
> org.apache.logging.slf4j.Log4jLoggerFactory
> [WARN] Maven supported bindings are:
> [WARN] (from
> jar:file:/opt/apache-maven-3.3.9/lib/maven-embedder-3.3.9.jar!/META-INF/maven/slf4j-configuration.properties)
> - ch.qos.logback.classic.LoggerContext
> - org.slf4j.helpers.Log4jLoggerFactory
> - org.slf4j.impl.SimpleLoggerFactory
> {noformat}
> This looks pretty harmless, and I was able to suppress it by manually adding
> the line
> {code}
> org.apache.logging.slf4j.Log4jLoggerFactory
> org.apache.maven.cli.logging.impl.Log4j2Configuration
> {code}
> to {{/META-INF/maven/slf4j-configuration.properties}} in
> {{maven-embedder-3.3.9.jar}}.
> I'm not sure that this is a "correct" solution, and I'm not even confident I
> could explain what effect it has, hence not posting a patch, but somebody
> with more knowledge might be able to triage this better. Or offer an
> "official" way to do colorized output.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5968) Default plugin version updates
[ https://issues.apache.org/jira/browse/MNG-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5968: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Default plugin version updates > -- > > Key: MNG-5968 > URL: https://issues.apache.org/jira/browse/MNG-5968 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6166) mvn dependency:go-offline fails due to missing transitive dependency jdom:jdom:jar:1.1
[ https://issues.apache.org/jira/browse/MNG-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6166: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > mvn dependency:go-offline fails due to missing transitive dependency > jdom:jdom:jar:1.1 > -- > > Key: MNG-6166 > URL: https://issues.apache.org/jira/browse/MNG-6166 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Archimedes Trajano >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > When running mvn dependency:go-offline it reports that > Failed to execute goal > org.apache.maven.plugins:maven-dependency-plugin:2.8:resolve-plugins > (resolve-plugins) on project maven-artifact: Nested: Could not find artifact > jdom:jdom:jar:1.1 in central (http://repo.maven.apache.org/maven2) > It is likely in one of the external dependencies because I don't see it on > the code base itself. > https://travis-ci.org/trajano/maven/builds/198102606 > Just an FYI there is no jdom:jdom:jar:1.1 in central it is a POM project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6165) Deprecate and replace incorrectly spelled public API
[ https://issues.apache.org/jira/browse/MNG-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6165: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Deprecate and replace incorrectly spelled public API > > > Key: MNG-6165 > URL: https://issues.apache.org/jira/browse/MNG-6165 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.3.9 >Reporter: Josh Soref >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > According to [PR #101|https://github.com/apache/maven/pull/101] some of the > public API methods are incorrectly spelled. Let's clean that up by > deprecating and adding a correctly spelled version. The old version will > simply call the new one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5883) Silence unnecessary legacy local repository warning
[
https://issues.apache.org/jira/browse/MNG-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5883:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Silence unnecessary legacy local repository warning
> ---
>
> Key: MNG-5883
> URL: https://issues.apache.org/jira/browse/MNG-5883
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.2.5, 3.3.3
>Reporter: Ben Caradoc-Davies
>Assignee: Christian Schulte
>Priority: Trivial
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Having been burned on several occasions by the new local repository
> behaviour, which in effect scopes artifacts by their origin (when first
> stored in the local repository), I was delighted by the introduction of the
> -llr command line option in 3.0.3. I now use this behaviour for all builds to
> avoid the build instability caused by remote repository migration. This
> avoids the need to start each build with:
> {code}
> find ~/.m2/repository -name "_*.repositories" -exec rm -f {} \;
> {code}
> Given that users of -llr have made an informed choice to do so, please remove
> the (in my view unnecessary) warning that it generates:
> {code}
> [WARNING] Disabling enhanced local repository: using legacy is strongly
> discouraged to ensure build reproducibility.
> {code}
> Kind regards,
> Ben.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6105) properties.internal.SystemProperties.addSystemProperties() is not really thread-safe
[
https://issues.apache.org/jira/browse/MNG-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6105:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> properties.internal.SystemProperties.addSystemProperties() is not really
> thread-safe
>
>
> Key: MNG-6105
> URL: https://issues.apache.org/jira/browse/MNG-6105
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /usr/maven/default
> Java version: 1.8.0_102, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_102/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-431.29.2.el6.x86_64", arch: "amd64",
> family: "unix"
>Reporter: Falko Modler
>Assignee: Guillaume Boué
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> We got a rather large Maven project with a couble of modules that execute
> {{maven-assembly-plugin}}. Our build runs in parallel mode via {{-Tx}}.
> From time to time we are seeing following exception causing the respective
> build to fail:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip) on
> project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip)
> on project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at
> org.apache.maven.properties.internal.SystemProperties.addSystemProperties(SystemProperties.java:38)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.getSystemProperties(MavenMetadataSource.java:756)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:574)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:190)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:532)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:584)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.collect(DefaultLegacyArtifactCollector.java:144)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:493)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveWithExceptions(DefaultArtifactResolver.java:348)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:342)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:321)
> at
> org.a
[jira] [Updated] (MNG-5934) String handling issues identified by PMD
[ https://issues.apache.org/jira/browse/MNG-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5934: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > String handling issues identified by PMD > > > Key: MNG-5934 > URL: https://issues.apache.org/jira/browse/MNG-5934 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.3.9 >Reporter: Alex Henrie >Assignee: Michael Osipov >Priority: Minor > Labels: easyfix, newbie, patch, performance > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > Attachments: > 0001-Prefer-StringBuilder.append-char-to-StringBuilder.ap.patch, > 0002-Prefer-String.indexOf-char-to-String.indexOf-String.patch, > 0003-Combine-string-literals-instead-of-calling-String.ap.patch, > 0004-Construct-StringBuffers-with-enough-space-to-begin-w.patch > > > The code linting tool [PMD|http://pmd.sourceforge.net/pmd-5.2.0/] identified > numerous places where Maven's string handling is inefficient. I've prepared a > set of patches that should help speed things up. > The command I used was `pmd -d . -R java-strings` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6163) Introduce CLASSWORLDS_JAR in shell startup scripts
[
https://issues.apache.org/jira/browse/MNG-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6163:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> Introduce CLASSWORLDS_JAR in shell startup scripts
> --
>
> Key: MNG-6163
> URL: https://issues.apache.org/jira/browse/MNG-6163
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> MNG-5538 introduced {{CLASSWORLDS_JAR}}, but the issue was dropped due to
> reproducibility, however {{mvn.cmd}} has also a {{CLASSWORLDS_JAR}} variable.
> Both scripts shall behave the same way.
> Reapply commits from MNG-5538 as this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
issues@maven.apache.org
[
https://issues.apache.org/jira/browse/MNG-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6022:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> mvn.cmd fails if directory contains an ampersand (&)
>
>
> Key: MNG-6022
> URL: https://issues.apache.org/jira/browse/MNG-6022
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> Checkout a fresh version of MASSEMBLY trunk, run {{mvn clean install
> -Prun-its}} and see the IT {{projects\basic-features\this & that}}. Go to the
> {{target}} directory of this IT and run Maven again. It says:
> {noformat}
> D:\Entwicklung\Projekte\maven-assembly-plugin\target\it\projects\basic-features\this
> & that>mvn compile
> Der Befehl "that" ist entweder falsch geschrieben oder
> konnte nicht gefunden werden.
> Das System kann den angegebenen Pfad nicht finden.
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.060 s
> [INFO] Finished at: 2016-05-15T00:37:27+02:00
> [INFO] Final Memory: 6M/241M
> [INFO]
>
> [ERROR] The goal you specified requires a project to execute but there is no
> POM in this directory (D:\). Please verify you invoked Maven from the correct
> directory. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException
> D:\Entwicklung\Projekte\maven-assembly-plugin\target\it\projects\basic-features\this
> & that>
> {noformat}
> {{EXEC_DIR}} and friends aren't quoted and therefore the ampersand toolks for
> {{that}} command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
issues@maven.apache.org
[
https://issues.apache.org/jira/browse/MNG-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5815:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> "mvn.cmd" does not indicate failure properly when using "&&"
>
>
> Key: MNG-5815
> URL: https://issues.apache.org/jira/browse/MNG-5815
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.1
> Environment: Windows 8.1 Pro 64-bit
>Reporter: Peter Kjær Guldbæk
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> I recently upgraded from Maven 3.0.4 to 3.3.1. It seems as if "mvn.cmd" no
> longer indicates failure properly when using "&&".
> Invoking "mvn foo && echo SUCCESS!" using Maven 3.0.4 on Windows causes the
> following output (notice no trace of "SUCCESS!" as "mvn" fails):
> {noformat}
> c:\Temp>mvn foo && echo SUCCESS!
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.061s
> [INFO] Finished at: Tue Apr 28 14:08:27 CEST 2015
> [INFO] Final Memory: 10M/491M
> [INFO]
>
> [ERROR] The goal you specified requires a project to execute but there is no
> POM in this directory (c:\Temp). Please verify you invoked Maven from the
> correct directory. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException
> {noformat}
> Invoking "mvn foo && echo SUCCESS!" using Maven 3.3.1 on Windows causes the
> following output (notice "SUCCESS!" is echoed even though "mvn" fails):
> {noformat}
> c:\Temp>mvn foo && echo SUCCESS!
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.053 s
> [INFO] Finished at: 2015-04-28T14:09:19+02:00
> [INFO] Final Memory: 13M/491M
> [INFO]
>
> [ERROR] The goal you specified requires a project to execute but there is no
> POM in this directory (c:\Temp). Please verify you invoked Maven from the
> correct directory. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException
> SUCCESS!
> {noformat}
> It is a little strange that it does not work in Maven 3.3.1 as invoking "mvn
> foo" actually causes "%ERRORLEVEL%" to be set to "1":
> {noformat}
> c:\Temp>mvn foo
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.052 s
> [INFO] Finished at: 2015-04-28T14:09:41+02:00
> [INFO] Final Memory: 13M/491M
> [INFO]
>
> [ERROR] The goal you specified requires a project to execute but there is no
> POM in this directory (c:\Temp). Please verify you invoked Maven from the
> correct directory. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException
> c:\Temp>echo %ERRORLEVEL%
> 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6151) Force Push master from 737de43e392fc15a0ce366db98d70aa18b3f6c03
[ https://issues.apache.org/jira/browse/MNG-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6151: -- Fix Version/s: 3.5.0-alpha-2 3.5.0-alpha-1 > Force Push master from 737de43e392fc15a0ce366db98d70aa18b3f6c03 > --- > > Key: MNG-6151 > URL: https://issues.apache.org/jira/browse/MNG-6151 > Project: Maven > Issue Type: Task > Components: core >Reporter: Stephen Connolly >Assignee: Stephen Connolly > Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2 > > > See > https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5368) UnsupportedOperationException thrown when version range is not correct in dependencyManagement definitions
[
https://issues.apache.org/jira/browse/MNG-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5368:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> UnsupportedOperationException thrown when version range is not correct in
> dependencyManagement definitions
> --
>
> Key: MNG-5368
> URL: https://issues.apache.org/jira/browse/MNG-5368
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4
> Environment: MacOS 10.7.5 Darwin Kernel Version 11.4.2:
> xnu-1699.32.7~1/RELEASE_X86_64 x86_64
>Reporter: Andrew Haines
>Assignee: Christian Schulte
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> When specifying a non valid version range in a dependencyManagement tag,
> instead of a descriptive error message we get a UnsupportedOperationException
> thrown. The code at fault in
> org.apache.maven.project.MavenProject#getManagedVersionMap is:
> {code}
> map = new HashMap();
> for ( Iterator i =
> dependencyManagement.getDependencies().iterator(); i.hasNext(); )
> {
> Dependency d = i.next();
> Artifact artifact =
> repositorySystem.createDependencyArtifact( d );
> if ( artifact == null )
> {
> map = Collections.emptyMap();
> }
> map.put( d.getManagementKey(), artifact );
> {code}
> When the artifact is null, the map is set to an immutable map and then the
> null artifact is then attempted to be put into it. This will always fail.
> This particular problem originates from code further down the stack in
> org.apache.maven.repository.legacy.LegacyRepositorySystem:
> {code}
>public Artifact createDependencyArtifact( Dependency d )
> {
> VersionRange versionRange;
> try
> {
> versionRange = VersionRange.createFromVersionSpec( d.getVersion()
> );
> }
> catch ( InvalidVersionSpecificationException e )
> {
> return null;
> }
> {code}
> Instead of signalling appropriately that an error has occurred, this
> exception is consumed and thus causes the erroneous behaviour mentioned in
> the first code snippet
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6137) Clean up duplicate dependencies caused by incomplete Wagon HTTP Provider exclusions
[
https://issues.apache.org/jira/browse/MNG-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6137:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Clean up duplicate dependencies caused by incomplete Wagon HTTP Provider
> exclusions
> ---
>
> Key: MNG-6137
> URL: https://issues.apache.org/jira/browse/MNG-6137
> Project: Maven
> Issue Type: Task
> Components: Deployment
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Some dependencies are duplicated in {{$\{maven.home}/lib}} because not all
> shaded dependencies of Wagon HTTP Provider are excluded. This can easily be
> cleaned up when Wagon 2.12 is merged.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Precedence of command-line system property options has changed
> --
>
> Key: MNG-6172
> URL: https://issues.apache.org/jira/browse/MNG-6172
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> The current state of master (what will eventually become 3.5.0) has reversed
> the precedence of command-line system property options compared to previous
> releases of Maven.
> For example, running this command with a basic project:
> {code}
> mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
> {code}
> using current master will cause {{/tmp/aaa}} to be created (first-one-wins),
> whereas for all previous releases of Maven {{/tmp/zzz}} would have been
> created (last-one-wins)
> This has the potential to break CI builds which relied on the previous
> last-one-wins behaviour.
> This was introduced by the fix for MNG-6078
> https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28
> - by reversing the whole array the precedence between options on the same
> command line has been reversed, not just the relationship between
> .mvn/maven.config options and command line options.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6117) ${session.parallel} not correctly set
[
https://issues.apache.org/jira/browse/MNG-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6117:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> ${session.parallel} not correctly set
> -
>
> Key: MNG-6117
> URL: https://issues.apache.org/jira/browse/MNG-6117
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Richard Raumberger
>Assignee: Guillaume Boué
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Running {{mvn help:evaluate -T 3}} and resolving the property
> {{session.parallel}} returns {{true}} when run with Maven 3.0.5.
> When running it with 3.3.9, this property resolves to {{false}}.
> {code}
> mvn help:evaluate -T 3
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the MultiThreadedBuilder implementation with a thread count of 3
> [INFO]
> [INFO]
>
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
>
> [INFO]
> [INFO] --- maven-help-plugin:2.2:evaluate (default-cli) @ standalone-pom ---
> [INFO] No artifact parameter specified, using
> 'org.apache.maven:standalone-pom:pom:1' as project.
> [INFO] Enter the Maven expression i.e. ${project.groupId} or 0 to exit?:
> ${session.parallel}
> [INFO]
> false
> {code}
> E.g. Surefire
> [relies|https://github.com/apache/maven-surefire/blob/fb9b699e27dae905393a5bc4d5c6ae39606c3172/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L658]
> on this property, to check whether Maven is running in parallel mode, as
> mentioned in the comments of
> [SUREFIRE-1301|https://issues.apache.org/jira/browse/SUREFIRE-1301].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6017) Removing ArtifactHandler for par LifeCycle
[ https://issues.apache.org/jira/browse/MNG-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6017: -- Fix Version/s: (was: 3.5.0-alpha-2) > Removing ArtifactHandler for par LifeCycle > -- > > Key: MNG-6017 > URL: https://issues.apache.org/jira/browse/MNG-6017 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1 > > > Remove the ArtifactHandler definition for par lifecycle which has been > [removed in Maven 3.3.9|MNG-5892] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5889) .mvn directory should be picked when using --file
[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5889:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> .mvn directory should be picked when using --file
> -
>
> Key: MNG-5889
> URL: https://issues.apache.org/jira/browse/MNG-5889
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.3.3
>Reporter: Daniel Spilker
>Assignee: Tibor Digana
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> The {{.mvn}} directory is not picked up when using the {{--file}} switch to
> build a project from outside of the multi-module root.
> Example:
> * the module root is {{/foo/bar}}
> * {{.mvn}} is located at {{/foo/bar/.mvn}}
> * current directory is {{/foo}}
> * Maven is invoked with {{mvn --file bar/module/pom.xml}}
> I would expect the {{.mvn}} directory detection to start at the directory of
> the POM selected by {{--file}} and then go through the parent directories.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6078) Can't overwrite properties which have been defined in .mvn/maven.config
[
https://issues.apache.org/jira/browse/MNG-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6078:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Can't overwrite properties which have been defined in .mvn/maven.config
> ---
>
> Key: MNG-6078
> URL: https://issues.apache.org/jira/browse/MNG-6078
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Currently properties which have been defined in {{.mvn/maven.config}} can't
> be overwritten via command line. This should be made possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5968) Default plugin version updates
[ https://issues.apache.org/jira/browse/MNG-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5968: -- Fix Version/s: (was: 3.5.0-alpha-2) > Default plugin version updates > -- > > Key: MNG-5968 > URL: https://issues.apache.org/jira/browse/MNG-5968 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6152) Add a Jenkinsfile so that builds.apache.org can use multibranch pipeline
[ https://issues.apache.org/jira/browse/MNG-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6152: -- Fix Version/s: (was: 3.5.0-alpha-2) > Add a Jenkinsfile so that builds.apache.org can use multibranch pipeline > > > Key: MNG-6152 > URL: https://issues.apache.org/jira/browse/MNG-6152 > Project: Maven > Issue Type: Task > Components: core >Reporter: Stephen Connolly >Assignee: Stephen Connolly > Fix For: 3.5.0, 3.5.0-alpha-1 > > > We want to enable multibranch pipeline support on our CI infrastructure so > that all branches can get integration test verification -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5963) mvn.cmd does not return ERROR_CODE
[ https://issues.apache.org/jira/browse/MNG-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5963: -- Fix Version/s: (was: 3.5.0-alpha-2) > mvn.cmd does not return ERROR_CODE > -- > > Key: MNG-5963 > URL: https://issues.apache.org/jira/browse/MNG-5963 > Project: Maven > Issue Type: Bug >Affects Versions: 3.3.9 > Environment: Windows 10 >Reporter: Larry Singer >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1 > > > mvn.cmd does not return an ERROR_CODE value to an enclosing script in > WIndows. Running this script: > @ECHO OFF > CALL mvn clean install > echo "%ERROR_CODE%" > Now shows "". Previously it showed "0" for success and "1" for error. > It appears that there is an @endlocal missing. A possible fix is to add > @endlocal & set ERROR_CODE=%ERROR_CODE% > before > exit /B %ERROR_CODE% -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5993) Confusing error message in case of missing/empty artifactId and version in pluginManagement
[
https://issues.apache.org/jira/browse/MNG-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5993:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Confusing error message in case of missing/empty artifactId and version in
> pluginManagement
> ---
>
> Key: MNG-5993
> URL: https://issues.apache.org/jira/browse/MNG-5993
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
>Affects Versions: 3.3.9
>Reporter: Konrad Windszus
>Assignee: Karl Heinz Marbaise
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Executing any goals/phases on this pom.xml leads to a weird error
> {code}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> com.example.group
> testinvalidpom
> 0.0.1-SNAPSHOT
>
>
>
>
>
>
>
>
>
>
>
> {code}
> The error being emitted is
> {code}
> [ERROR] Error resolving version for plugin ':null' from the repositories
> [local (), nexus ()]: Plugin not found in
> any plugin repository -> [Help 1]
> {code}
> Even with debug you only see something like this
> {code}
> [ERROR] Error resolving version for plugin ':null' from the repositories
> [...]: Plugin not found in any plugin repository -> [Help 1]
> org.apache.maven.plugin.version.PluginVersionResolutionException: Error
> resolving version for plugin ':null' from the repositories [local
> (/Users/konradwindszus/.m2/repository), nexus
> (https://repo.int.netcentric.biz/nexus/content/groups/public/)]: Plugin not
> found in any plugin repository
> at
> org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.selectVersion(DefaultPluginVersionResolver.java:236)
> at
> org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.resolveFromRepository(DefaultPluginVersionResolver.java:148)
> at
> org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.resolve(DefaultPluginVersionResolver.java:96)
> at
> org.apache.maven.lifecycle.internal.LifecyclePluginResolver.resolveMissingPluginVersions(LifecyclePluginResolver.java:89)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:135)
> at
> org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan(BuilderCommon.java:97)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:109)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
> In this example the error is easy to spot, but for bigger pom.xmls with more
> complex hierarchies it is very hard.
> Some basic validation should take place that on the merged pom.xml all of
> groupId, artifactId and version is available and if that is not the case, the
> line number of the pom.xml together with the filename should be given out,
> where the according information is missing.
> A similar error is emitted in case the groupId element is missing as well or
> there is an empty artifactId.
--
Th
[jira] [Updated] (MNG-5823) mvnDebug doesn't work with M2_HOME with spaces - missing quotes
[
https://issues.apache.org/jira/browse/MNG-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5823:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> mvnDebug doesn't work with M2_HOME with spaces - missing quotes
> ---
>
> Key: MNG-5823
> URL: https://issues.apache.org/jira/browse/MNG-5823
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.1
> Environment: Windows, Cygwin
>Reporter: Tobias Oberlies
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> When calling {{mvnDebug}} in a Cygwin shell, I get the following error
> {noformat}
> Preparing to Execute Maven in Debug Mode
> dirname: extra operand `Files/Maven/apache-maven-3.3.1/bin/mvnDebug'
> Try `dirname --help' for more information.
> env: /mvn: No such file or directory
> {noformat}
> The root cause are missing quotes in and around the dirname call. The script
> currently calls
> {noformat}
> env MAVEN_OPTS="$MAVEN_OPTS $MAVEN_DEBUG_OPTS" $(dirname $0)/mvn "$@"
> {noformat}
> but the call should be
> {noformat}
> env MAVEN_OPTS="$MAVEN_OPTS $MAVEN_DEBUG_OPTS" "$(dirname "$0")/mvn" "$@"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5579) Unify error output/check logic from shell and batch scripts
[
https://issues.apache.org/jira/browse/MNG-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5579:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Unify error output/check logic from shell and batch scripts
> ---
>
> Key: MNG-5579
> URL: https://issues.apache.org/jira/browse/MNG-5579
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.1.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Currently,
> both output two different messages.
> Shell:
> {quote}
> Error: JAVA_HOME is not defined correctly.
>We cannot execute $JAVACMD
> {quote}
> while batch says:
> {quote}
> Error: JAVA_HOME not found in your environment.
> Please set the JAVA_HOME variable in your environment to match the
> location of your Java installation.
> {quote}
> Same applies for {{M2_HOME}}. Additionally, testing for the Java command is
> handled different in both scripts. The batch script relies on JAVA_HOME while
> the shell script can ignore it. Both should require {{JAVA_HOME}} or warn
> about and use {{which java}}, respectively {{java}} in {{PATH}} ({{for %%X
> in (java.exe) do (set JAVACMD=%%~$PATH:X)}}) on Windows. After that should
> proceed to checking {{M2_HOME}}.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6068) Document default scope compile in pom XSD and reference documentation
[
https://issues.apache.org/jira/browse/MNG-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6068:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Document default scope compile in pom XSD and reference documentation
> -
>
> Key: MNG-6068
> URL: https://issues.apache.org/jira/browse/MNG-6068
> Project: Maven
> Issue Type: Improvement
> Components: core, POM
>Affects Versions: 3.3.9
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Many people referencing the XSD of the POM file as reference and missing
> information in there.
> So adding the information about the default scope which is {{compile}}:
> http://maven.apache.org/ref/3.3.9/maven-model/maven.html#class_dependency
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5883) Silence unnecessary legacy local repository warning
[
https://issues.apache.org/jira/browse/MNG-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5883:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Silence unnecessary legacy local repository warning
> ---
>
> Key: MNG-5883
> URL: https://issues.apache.org/jira/browse/MNG-5883
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.2.5, 3.3.3
>Reporter: Ben Caradoc-Davies
>Assignee: Christian Schulte
>Priority: Trivial
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Having been burned on several occasions by the new local repository
> behaviour, which in effect scopes artifacts by their origin (when first
> stored in the local repository), I was delighted by the introduction of the
> -llr command line option in 3.0.3. I now use this behaviour for all builds to
> avoid the build instability caused by remote repository migration. This
> avoids the need to start each build with:
> {code}
> find ~/.m2/repository -name "_*.repositories" -exec rm -f {} \;
> {code}
> Given that users of -llr have made an informed choice to do so, please remove
> the (in my view unnecessary) warning that it generates:
> {code}
> [WARNING] Disabling enhanced local repository: using legacy is strongly
> discouraged to ensure build reproducibility.
> {code}
> Kind regards,
> Ben.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5878) add support for module name != artifactId in every calculated URLs (project, SCM, site): special project.directory property
[
https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5878:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> add support for module name != artifactId in every calculated URLs (project,
> SCM, site): special project.directory property
> ---
>
> Key: MNG-5878
> URL: https://issues.apache.org/jira/browse/MNG-5878
> Project: Maven
> Issue Type: New Feature
> Components: Inheritance and Interpolation
>Affects Versions: 3.3.3
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Say you have this project structure:
> {noformat}
> /
> |-- module1
> |-- module2
> {noformat}
> and artifactIds are named:
> {noformat}
> my-parent
> |-- my-module1
> |-- my-module2
> {noformat}
> Prefix {{my-}} is omitted for brevity in module names. For instance, Jersey
> does that.
> When the SCM report is built, the artifactId is always used for path
> composition which leads to incorrect URLs. You can of course set the
> parameter {{checkoutDirectoryName}} but this would be extremely tedious for
> all modules down the tree.
> The code should obtain the module name and use it for URL composition.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6053) Unsafe System Properties copy in MavenRepositorySystemUtils, causing NPEs
[
https://issues.apache.org/jira/browse/MNG-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6053:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Unsafe System Properties copy in MavenRepositorySystemUtils, causing NPEs
> -
>
> Key: MNG-6053
> URL: https://issues.apache.org/jira/browse/MNG-6053
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
> Environment: Eclipse m2e 1.7
>Reporter: Fred Bricon
>Assignee: Guillaume Boué
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> This bug has been reported in m2e
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=493871:
> {quote}
> I'm occasionally, not 100% reliably reproducible, but regularly enough (like
> it occurs every now and then, not just once) seeing the error below, in the
> Error Log of Eclipse during workspace rebuilds. This is with M2E 1.7.0. --
> I'm not sure if this is just "annoying" or actually prevents M2E from
> correctly configuring projects (?). Either way, perhaps it would be possible
> to "harden" respective code to prevent this?
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at
> org.apache.maven.repository.internal.MavenRepositorySystemUtils.newSession(MavenRepositorySystemUtils.java:133)
> at
> org.apache.maven.internal.aether.DefaultRepositorySystemSessionFactory.newRepositorySession(DefaultRepositorySystemSessionFactory.java:98)
> at
> org.apache.maven.DefaultMaven.newRepositorySession(DefaultMaven.java:352)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.createRepositorySession(MavenImpl.java:309)
> {quote}
> Looking at
> https://github.com/apache/maven/blob/86b656167923923e2e416def4a48303b4e6248fa/maven-aether-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java#L132,
> it seems some system property is null (maybe due to some concurrency issue),
> and given that Hashtable doesn't support null values, then it throws an NPE
> on the put() call
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6092) warn if prerequisites.maven is used for non-plugin projects
[ https://issues.apache.org/jira/browse/MNG-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6092: -- Fix Version/s: (was: 3.5.0-alpha-2) > warn if prerequisites.maven is used for non-plugin projects > --- > > Key: MNG-6092 > URL: https://issues.apache.org/jira/browse/MNG-6092 > Project: Maven > Issue Type: Wish > Components: core >Affects Versions: 3.3.9 >Reporter: Hervé Boutemy >Assignee: Karl Heinz Marbaise > Fix For: 3.5.0, 3.5.0-alpha-1 > > > as seen in MNG'4840 and documented in MNG-5297, in Maven 3, > prerequisites.maven has a meaning for plugin projects: defining this for > non-plugins projects makes feel that it will be checked like it was done in > Maven 2, but this is not the case. > Adding a warning could help people avoid this habit taken with Maven 2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6171) REGRESSION: WARNING about usage of a non threadsafe marked plugin is not showed anymore
[
https://issues.apache.org/jira/browse/MNG-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6171:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> REGRESSION: WARNING about usage of a non threadsafe marked plugin is not
> showed anymore
> ---
>
> Key: MNG-6171
> URL: https://issues.apache.org/jira/browse/MNG-6171
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.1, 3.2.5, 3.3.9
>Reporter: Karl Heinz Marbaise
>Assignee: Hervé Boutemy
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> If you call Maven via command line like this:
> {{mvn -T 5 versions:set -DnewVersion=...}} in Maven 3.0.5, 3.1.1 you will get
> a message like this:
> {code}
> [INFO] Building with 20 threads
> [INFO]
> [INFO]
>
> [INFO] Building reactor-parent 1.0-SNAPSHOT
> [INFO]
>
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in reactor-parent:
> [WARNING] org.codehaus.mojo:versions-maven-plugin:2.3
> [WARNING] *
> [INFO]
> [INFO] --- versions-maven-plugin:2.3:set (default-cli) @ reactor-parent ---
> [INFO] Searching for local aggregator root...
> [INFO] Local aggregation root:
> /Users/kama/ws-git-soebes/maven-memory-problem/test-project/reactor
> [INFO] Processing change of org.test.parent:reactor-parent:1.0-SNAPSHOT ->
> 1.0-SNAPSHOT
> [INFO]
>
> {code}
> Starting with Maven 3.2.5 and above you don't get the WARNING anymore. Also
> for [current Master of
> Maven|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=0284dda81beb43b54116326f9a6efd439d40c922]
> it will not beed showed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5962) mvn.cmd fails when the current directory has spaces in between
[
https://issues.apache.org/jira/browse/MNG-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5962:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> mvn.cmd fails when the current directory has spaces in between
> --
>
> Key: MNG-5962
> URL: https://issues.apache.org/jira/browse/MNG-5962
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.3, 3.3.9
> Environment: Windows 7
>Reporter: Miriam Lee
>Assignee: Michael Osipov
>Priority: Minor
> Labels: easyfix, newbie
> Fix For: 3.5.0, 3.5.0-alpha-1
>
> Attachments: MNG-5962-apache-maven.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Executing {{mvn.cmd}} when the current directory has spaces in between
> outputs {{The system cannot find the path specified.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6032) WARNING during build based on absolute path in assembly-descriptor.
[ https://issues.apache.org/jira/browse/MNG-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6032: -- Fix Version/s: (was: 3.5.0-alpha-2) > WARNING during build based on absolute path in assembly-descriptor. > --- > > Key: MNG-6032 > URL: https://issues.apache.org/jira/browse/MNG-6032 > Project: Maven > Issue Type: Improvement > Components: Deployment >Affects Versions: needing-scrub-3.4.0-fallout >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5297) Site should tell 'prerequisites.maven is deprecated'
[ https://issues.apache.org/jira/browse/MNG-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5297: -- Fix Version/s: (was: 3.5.0-alpha-2) > Site should tell 'prerequisites.maven is deprecated' > > > Key: MNG-5297 > URL: https://issues.apache.org/jira/browse/MNG-5297 > Project: Maven > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 3.0.4 >Reporter: Kengo TODA >Assignee: Jason van Zyl >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1 > > > MNG-4840 said 'enforcement of the build environment is left to the Maven > Enforcer Plugin'. > http://jira.codehaus.org/browse/MNG-4840?focusedCommentId=253900&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-253900 > But currently, there is no 'deprecated' mark at Maven site. > http://maven.apache.org/ref/3.0.4/maven-model/maven.html#prerequisites > I think site should has 'deprecated' mark like 'reports' element. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5904) Remove the whole Ant build
[ https://issues.apache.org/jira/browse/MNG-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5904: -- Fix Version/s: (was: 3.5.0-alpha-2) > Remove the whole Ant build > -- > > Key: MNG-5904 > URL: https://issues.apache.org/jira/browse/MNG-5904 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: needing-scrub-3.4.0-fallout >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1 > > > We should remove the whole Ant build cause we have a large number of Maven > versions which could be used to start building Maven itself. > So i don't see any usefulness in it anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5977) Improve output readability of our MavenTransferListener implementations
[
https://issues.apache.org/jira/browse/MNG-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-5977:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Improve output readability of our MavenTransferListener implementations
> ---
>
> Key: MNG-5977
> URL: https://issues.apache.org/jira/browse/MNG-5977
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Embedding
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1
>
> Attachments: current.zip, improved-debug.zip, improved.zip
>
>
> The current output of Downloading/Downladed/Uploading/Uploaded transfer
> notification has some flaws:
> 1. It does not scale numbers between 1 and 1000 with appropriate units
> 2. It should use correct size ({{kB}}, {{MB}}, {{GB}} and time units ({{s}})
> but doesn't. (see https://en.wikipedia.org/wiki/Binary_prefix and
> https://en.wikipedia.org/wiki/Metric_prefix)
> 3. When Aether downloads in parallel (which applies for non-POM files) the
> progress interleaves due to race conditions to {{System.out}} and you do not
> know to which resource a progress belongs to.
> Let's use an improved version of MPIR {{DependenciesRenderer}}'s
> [{{FileDecimalFormat}}|https://github.com/apache/maven-plugins/blob/trunk/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/dependencies/renderer/DependenciesRenderer.java#L1583]
> for it.
> concrete examples:
> before
> {noformat}191/191 KB 27/48 KB 48/119 KB 80/87 KB 13/13 KB {noformat}
> after:
> {noformat}Progress (4): 500/800 B | 40/45 kB | 193 kB/315 kB | 1.3/9.0 MB |
> 12/30 MB{noformat}
> if total size is unavailable or the file has already been downloaded but not
> removed from the list, the output will be:
> {noformat}Progress (4): 800 B | 40/45 kB | 193 kB | 9.0 MB | 12 MB{noformat}
> or in debug mode:
> {noformat}Progress (5): xml-apis-1.3.04.jar () |
> maven-shared-utils-0.6.jar () | xercesImpl-2.9.1.jar () |
> commons-digester-1.6.jar () | maven-reporting-impl-2.3.jar
> (){noformat}
> If the scale is between 1 and 10, one decimal place will be printed out. If
> it is between 10 and 1000+, it will be an integer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6151) Force Push master from 737de43e392fc15a0ce366db98d70aa18b3f6c03
[ https://issues.apache.org/jira/browse/MNG-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6151: -- Fix Version/s: (was: 3.5.0-alpha-2) > Force Push master from 737de43e392fc15a0ce366db98d70aa18b3f6c03 > --- > > Key: MNG-6151 > URL: https://issues.apache.org/jira/browse/MNG-6151 > Project: Maven > Issue Type: Task > Components: core >Reporter: Stephen Connolly >Assignee: Stephen Connolly > Fix For: 3.5.0, 3.5.0-alpha-1 > > > See > https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5946) Fix links etc. in README.txt which is part of the delivery
[ https://issues.apache.org/jira/browse/MNG-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5946: -- Fix Version/s: (was: 3.5.0-alpha-2) > Fix links etc. in README.txt which is part of the delivery > -- > > Key: MNG-5946 > URL: https://issues.apache.org/jira/browse/MNG-5946 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.0, 3.5.0-alpha-1 > > > Fixed the README.txt file which is packaged into the apache-maven binary > artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5975) Use Java 7's SimpleDateFormat in CLIReportingUtils#formatTimestamp
[ https://issues.apache.org/jira/browse/MNG-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5975: -- Fix Version/s: (was: 3.5.0-alpha-2) > Use Java 7's SimpleDateFormat in CLIReportingUtils#formatTimestamp > -- > > Key: MNG-5975 > URL: https://issues.apache.org/jira/browse/MNG-5975 > Project: Maven > Issue Type: Improvement > Components: Embedding >Affects Versions: 3.3.9 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1 > > > The current code manually formats the timestamp because Commons Lang 3 was > not in the dependencies list. Now there is, drop custom code and use builtin > features. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6110) Upgrade Aether to Maven Resolver
[ https://issues.apache.org/jira/browse/MNG-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6110: -- Fix Version/s: (was: 3.5.0-alpha-2) > Upgrade Aether to Maven Resolver > > > Key: MNG-6110 > URL: https://issues.apache.org/jira/browse/MNG-6110 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.3.9 >Reporter: Harald Wellmann >Assignee: Hervé Boutemy > Fix For: 3.5.0, 3.5.0-alpha-1 > > > Replace Aether by Maven Resolver to make use of the latest bugfixes and > enhancements related to dependency collection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6001) Replace %HOME% with %USERPROFILE% in mvn.cmd
[
https://issues.apache.org/jira/browse/MNG-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6001:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Replace %HOME% with %USERPROFILE% in mvn.cmd
>
>
> Key: MNG-6001
> URL: https://issues.apache.org/jira/browse/MNG-6001
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> Setting {{HOME=%HOMEDRIVE%%HOMEPATH%}} is a relic from Windows NT times. The
> preferred way is to use {{%USERPROFILE%}} which is already done in Java 8
> internally.
> Let's use it to load the {{mavenrc}} scripts.
> Some references:
> * http://stackoverflow.com/a/36392591/696632
> * http://stackoverflow.com/a/21599376/696632
> * http://bugs.java.com/view_bug.do?bug_id=4787931
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6147) MetadataResolutionResult#getGraph() contains duplicate if clause
[ https://issues.apache.org/jira/browse/MNG-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-6147: -- Fix Version/s: (was: 3.5.0-alpha-2) > MetadataResolutionResult#getGraph() contains duplicate if clause > > > Key: MNG-6147 > URL: https://issues.apache.org/jira/browse/MNG-6147 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.3.9 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1 > > > There is an duplicate if clause from lines 110 to 125 which can safely be > removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6106) Remove maven.home default value setter from m2.conf
[
https://issues.apache.org/jira/browse/MNG-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6106:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Remove maven.home default value setter from m2.conf
> ---
>
> Key: MNG-6106
> URL: https://issues.apache.org/jira/browse/MNG-6106
> Project: Maven
> Issue Type: Task
> Components: Bootstrap & Build, core
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> The {{set maven.home default ${user.home\}/m2}} seems to be a relic from
> ancient times: {{maven.home}} property is always defined by {{mvn}} launch
> script
> Even if it would be used, it wouldn't work because {{user.home}} never
> contains Maven's installation files. (?)
> This line can safely be removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-5954) Remove outdated maven-embedder/src/main/resources/META-INF/MANIFEST.MF
[ https://issues.apache.org/jira/browse/MNG-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5954: -- Fix Version/s: (was: 3.5.0-alpha-2) > Remove outdated maven-embedder/src/main/resources/META-INF/MANIFEST.MF > -- > > Key: MNG-5954 > URL: https://issues.apache.org/jira/browse/MNG-5954 > Project: Maven > Issue Type: Task > Components: Embedding >Affects Versions: 3.3.9 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.5.0, 3.5.0-alpha-1 > > > File is outdated and not used anymore. Remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6163) Introduce CLASSWORLDS_JAR in shell startup scripts
[
https://issues.apache.org/jira/browse/MNG-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6163:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> Introduce CLASSWORLDS_JAR in shell startup scripts
> --
>
> Key: MNG-6163
> URL: https://issues.apache.org/jira/browse/MNG-6163
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> MNG-5538 introduced {{CLASSWORLDS_JAR}}, but the issue was dropped due to
> reproducibility, however {{mvn.cmd}} has also a {{CLASSWORLDS_JAR}} variable.
> Both scripts shall behave the same way.
> Reapply commits from MNG-5538 as this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
