[jira] [Created] (MNGSITE-299) Download security flaw

[Warren MacEvoy (JIRA)]

 Warren MacEvoy created MNGSITE-299:
---

 Summary: Download security flaw
 Key: MNGSITE-299
 URL: https://issues.apache.org/jira/browse/MNGSITE-299
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: any - raspberry pi in particular
Reporter:  Warren MacEvoy


A quick search of how to install maven on a raspberry pi reveals the most 
effective way is a direct install from a download from your site.  I.e:

https://www.xianic.net/post/installing-maven-on-the-raspberry-pi/

I assume many of these users are new developers.  However the download link on 
your site refers to an INSECURE download,

http://www.mirrorservice.org/sites/ftp.apache.org/maven/maven-3/3.2.5/binaries/apache-maven-3.3.9-bin.tar.gz

 followed by the suggestion users should verify the download using md5 (!) or 
gpg.

Ignoring the terrible idea of having md5 hashes,  about four more steps later 
gives the following most unsatisfying gpg result:

gpg --verify apache-maven-3.3.9-bin.tar.gz.asc apache-maven-3.3.9-bin.tar.gz
gpg: Signature made Tue 10 Nov 2015 16:44:20 UTC using DSA key ID BB617866
gpg: Good signature from "Sarel Jason van Zyl "
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: FB11 D4BB 7B24 4678 337A  AD8B C7BF 26D0 BB61 7866

So

1. The CDN should ONLY ALLOW HTTPS.  Maven is a core project and allowing for 
simple injection at this level is irresponsible. 

2. Providing md5 checksums is irresponsible.  How about sha256?  This would 
allow us to skip all the gpg run-around to vacuous conclusion.

3. If gpg is the preferred route, then uploads should not be allowed that does 
not give a more satisfying answer than "there is no indication the signature 
belongs to the owner".  I think this falls below the md5 sum bar.

Thank you for providing support to this important project.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-5852) "mvn" script invokes /bin/sh but requires /bin/bash functions

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-5852:

Description: 
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.



  was:
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:

$ ./mvn
./mvn[200]: local: not found [No such file or directory]
./mvn[201]: local: not found [No such file or directory]
...

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.




> "mvn" script invokes /bin/sh but requires /bin/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: Christian Schulte
> Fix For: needing-scrub-3.4.0-fallout
>
>
> 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.4#6332)

[jira] [Commented] (MNG-5837) Syntax error in bin/mvn on Solaris SPARC

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833719#comment-15833719
 ] 

Michael Osipov commented on MNG-5837:
-

This is a regression introduced in newer script changed. Solaris' {{sh}} is 
notoriously not POSIX-compliant.

> Syntax error in bin/mvn on Solaris SPARC
> 
>
> Key: MNG-5837
> URL: https://issues.apache.org/jira/browse/MNG-5837
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.3.1
> Environment: Solaris 10
>Reporter: Erlend Birkedal
>Assignee: Michael Osipov
> Fix For: 3.5.0-candidate
>
>
> When running {{mvn}} on Solaris 10 we get the following error:
> {code:none}/opt/apache-maven-3.3.1/bin/mvn: syntax error at line 200: `(' 
> unexpected{code}
> Looks like similas issues as in MNG-5658



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6115) Add Jansi native library search path to our start scripts

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MNG-6115:
---
Description: By default Jansi extracts the native, shared library to temp 
which results in unnecessary file I/O and a huge amount of temp files when 
Maven is run very often. One can avoid that by adding 
{{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib/ext}} to the start script. The user 
has to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the 
overhead.  (was: By default Jansi extracts the native, shared library to temp 
which results in unnecessary file I/O and a huge amount of temp files when 
Maven is run very often. One can avoid that by adding 
{{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib}} to the start script. The user has 
to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the overhead.)

> Add Jansi native library search path to our start scripts
> -
>
> Key: MNG-6115
> URL: https://issues.apache.org/jira/browse/MNG-6115
> Project: Maven
>  Issue Type: Improvement
>  Components: Bootstrap & Build, Command Line
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
>
> By default Jansi extracts the native, shared library to temp which results in 
> unnecessary file I/O and a huge amount of temp files when Maven is run very 
> often. One can avoid that by adding 
> {{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib/ext}} to the start script. The 
> user has to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the 
> overhead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (MNG-5829) mvn shell script fails with syntax error on Solaris 10

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov reopened MNG-5829:
-
  Assignee: Michael Osipov

The shell on Solaris is not POSIX-compliant, therefore it does not support the 
{{$()}} construct, though this is highly preferred over backticks.

> 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
>
> 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.4#6332)

[jira] [Updated] (MNG-5829) mvn shell script fails with syntax error on Solaris 10

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-5829:

Summary: mvn shell script fails with syntax error on Solaris 10  (was: mvn 
on Solaris 10 fails with syntax error)

> 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
>Priority: Minor
>
> 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.4#6332)

[jira] [Closed] (MNG-6095) mvn script warns on Solaris

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6095.
---
Resolution: Duplicate

> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Assignee: Christian Schulte
>Priority: Minor
>  Labels: solaris
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh 
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation  SunOS 5.11  11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local: 
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local: 
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (MNG-6095) mvn script warns on Solaris

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov reopened MNG-6095:
-

> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Assignee: Christian Schulte
>Priority: Minor
>  Labels: solaris
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh 
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation  SunOS 5.11  11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local: 
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local: 
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-6095) mvn script warns on Solaris

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6095.
---
Resolution: Fixed

Dup of MNG-5852 because pure Bourne Shell does not support {{local}} construct. 
This a Bourne Again Shell function.

> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Assignee: Christian Schulte
>Priority: Minor
>  Labels: solaris
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh 
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation  SunOS 5.11  11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local: 
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local: 
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6095) mvn script warns on Solaris

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-6095:

Fix Version/s: (was: needing-scrub-3.4.0-fallout)

> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Assignee: Christian Schulte
>Priority: Minor
>  Labels: solaris
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh 
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation  SunOS 5.11  11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local: 
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local: 
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-5670) ConcurrentModificationException during DefaultMaven.newRepositorySession

[Christian Schulte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schulte updated MNG-5670:
---
Fix Version/s: (was: 3.5.0-candidate)
   3.5.0

> ConcurrentModificationException during DefaultMaven.newRepositorySession
> 
>
> Key: MNG-5670
> URL: https://issues.apache.org/jira/browse/MNG-5670
> Project: Maven
>  Issue Type: Bug
>  Components: Embedding
>Reporter: Igor Fedorenko
>Assignee: Guillaume Boué
> Fix For: 3.2.3, 3.5.0
>
>
> DefaultMaven.newRepositorySession will fail with 
> ConcurrentModificationException if System.properties is modified concurrently 
> by another thread. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=439227 
> for original bug report against m2e.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-6151) Force Push master from 737de43e392fc15a0ce366db98d70aa18b3f6c03

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6151.
---

> 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
>
>
> 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.4#6332)

[jira] [Closed] (MNG-6152) Add a Jenkinsfile so that builds.apache.org can use multibranch pipeline

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6152.
---

> 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
>
>
> 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.4#6332)

[jira] [Commented] (MNG-5954) Remove outdated maven-embedder/src/main/resources/META-INF/MANIFEST.MF

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833689#comment-15833689
 ] 

Hudson commented on MNG-5954:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1500 (See 
[https://builds.apache.org/job/maven-3.x/1500/])
[MNG-5954] Remove outdated (michaelo: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=deefd9342b13f1fec786ddb00ff3b39299e6e11a])
* (delete) maven-embedder/src/main/resources/META-INF/MANIFEST.MF


> 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
>
>
> File is outdated and not used anymore. Remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6138) Remove obsolete message_*.properties form maven-core

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833693#comment-15833693
 ] 

Hudson commented on MNG-6138:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1500 (See 
[https://builds.apache.org/job/maven-3.x/1500/])
[MNG-6138] Remove obsolete message_*.properties form maven-core (michaelo: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=8373c79a47ce4f12e549ae817a9c5f9eae950fb8])
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_fr.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_no.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_en.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_ja.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_zh_CN.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_nl.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_pl.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_ko.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_es.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_de.properties
* (delete) 
maven-core/src/main/resources/org/apache/maven/messages/messages_el.properties


> 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
>
>
> 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.4#6332)

[jira] [Commented] (MNG-5975) Use Java 7's SimpleDateFormat in CLIReportingUtils#formatTimestamp

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833690#comment-15833690
 ] 

Hudson commented on MNG-5975:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1500 (See 
[https://builds.apache.org/job/maven-3.x/1500/])
[MNG-5975] Use Java 7's SimpleDateFormat in (michaelo: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=355f4dff03cea8cab0d7bdcb00fffa4e43b2c10b])
* (edit) 
maven-embedder/src/main/java/org/apache/maven/cli/CLIReportingUtils.java


> 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
>
>
> 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.4#6332)

[jira] [Commented] (MNG-6081) Log refactoring - Method Invocation Replaced By Variable

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833692#comment-15833692
 ] 

Hudson commented on MNG-6081:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1500 (See 
[https://builds.apache.org/job/maven-3.x/1500/])
[MNG-6081] Log refactoring - Method Invocation Replaced By Variable (michaelo: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=a2358ba7bb9b5b8ccb4ca2b6ea66b637b88d6c09])
* (edit) 
maven-compat/src/main/java/org/apache/maven/artifact/resolver/DebugResolutionListener.java


> 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
>
> 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.4#6332)

[jira] [Commented] (MNG-6106) Remove maven.home default value setter from m2.conf

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833691#comment-15833691
 ] 

Hudson commented on MNG-6106:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1500 (See 
[https://builds.apache.org/job/maven-3.x/1500/])
[MNG-6106] Remove maven.home setter from m2.conf (michaelo: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=5053a628c0a4eb069ab5512ad7491494207cb996])
* (edit) apache-maven/src/bin/m2.conf


> 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
>
>
> 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.4#6332)

[jira] [Closed] (MNG-6138) Remove obsolete message_*.properties form maven-core

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6138.
---
Resolution: Fixed

Fixed with 
[8373c79a47ce4f12e549ae817a9c5f9eae950fb8|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8373c79a47ce4f12e549ae817a9c5f9eae950fb8].

> 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
>
>
> 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.4#6332)

[jira] [Closed] (MNG-6106) Remove maven.home default value setter from m2.conf

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6106.
---
Resolution: Fixed

Fixed with 
[5053a628c0a4eb069ab5512ad7491494207cb996|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=5053a628c0a4eb069ab5512ad7491494207cb996].

> 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
>
>
> 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.4#6332)

[jira] [Closed] (MNG-6081) Log refactoring - Method Invocation Replaced By Variable

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6081.
---
Resolution: Fixed

Fixed with 
[a2358ba7bb9b5b8ccb4ca2b6ea66b637b88d6c09|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=a2358ba7bb9b5b8ccb4ca2b6ea66b637b88d6c09].

> 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
>
> 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.4#6332)

[jira] [Comment Edited] (MNG-5975) Use Java 7's SimpleDateFormat in CLIReportingUtils#formatTimestamp

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833681#comment-15833681
 ] 

Michael Osipov edited comment on MNG-5975 at 1/22/17 8:41 PM:
--

Fixed with 
[355f4dff03cea8cab0d7bdcb00fffa4e43b2c10b|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=355f4dff03cea8cab0d7bdcb00fffa4e43b2c10b].


was (Author: michael-o):
Fixed with 
[deefd9342b13f1fec786ddb00ff3b39299e6e11a|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=deefd9342b13f1fec786ddb00ff3b39299e6e11a].

> 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
>
>
> 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.4#6332)

[jira] [Closed] (MNG-5954) Remove outdated maven-embedder/src/main/resources/META-INF/MANIFEST.MF

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-5954.
---
Resolution: Fixed

Fixed with 
[deefd9342b13f1fec786ddb00ff3b39299e6e11a|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=deefd9342b13f1fec786ddb00ff3b39299e6e11a].

> 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
>
>
> File is outdated and not used anymore. Remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-5975) Use Java 7's SimpleDateFormat in CLIReportingUtils#formatTimestamp

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-5975.
---
Resolution: Fixed

Fixed with 
[deefd9342b13f1fec786ddb00ff3b39299e6e11a|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=deefd9342b13f1fec786ddb00ff3b39299e6e11a].

> 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
>
>
> 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.4#6332)

[jira] [Reopened] (MNG-5670) ConcurrentModificationException during DefaultMaven.newRepositorySession

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov reopened MNG-5670:
-

Subsequent changes made by [~schulte77] need to be reapplied on 
{{post-reset-master}}.

> ConcurrentModificationException during DefaultMaven.newRepositorySession
> 
>
> Key: MNG-5670
> URL: https://issues.apache.org/jira/browse/MNG-5670
> Project: Maven
>  Issue Type: Bug
>  Components: Embedding
>Reporter: Igor Fedorenko
>Assignee: Guillaume Boué
> Fix For: 3.2.3, 3.5.0-candidate
>
>
> DefaultMaven.newRepositorySession will fail with 
> ConcurrentModificationException if System.properties is modified concurrently 
> by another thread. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=439227 
> for original bug report against m2e.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (MNG-5297) Site should tell 'prerequisites.maven is deprecated'

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov reopened MNG-5297:
-

{{950a90ececca385f60c336814fb8a48c3b42bb54}} is missing on 
{{post-reset-master}}.

> 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.3.9, 3.5.0-candidate
>
>
> MNG-4840 said 'enforcement of the build environment is left to the Maven 
> Enforcer Plugin'.
> http://jira.codehaus.org/browse/MNG-4840?focusedCommentId=253900=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.4#6332)

[jira] [Updated] (MSHARED-20) Extend Invoker API to support the needs of the Release Plugin

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MSHARED-20:
--
Fix Version/s: (was: maven-invoker-3.0.0)

> Extend Invoker API to support the needs of the Release Plugin
> -
>
> Key: MSHARED-20
> URL: https://issues.apache.org/jira/browse/MSHARED-20
> Project: Maven Shared Components
>  Issue Type: New Feature
>  Components: maven-invoker
>Reporter: Benjamin Bentmann
>
> We are happily maintaining (at least) two code bases to fork Maven: One in 
> the maven-invoker ({{Invoker}} and {{DefaultInvoker}}) and one in the 
> maven-release-manager ({{MavenExecutor}} and {{ForkedMavenExecutor}}). Some 
> far day in the future we might want to consolidate this stuff into a single 
> component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MNG-6160) Forking process not always aware of reactor projects

[Robert Scholte (JIRA)]

Robert Scholte created MNG-6160:
---

 Summary: Forking process not always aware of reactor projects
 Key: MNG-6160
 URL: https://issues.apache.org/jira/browse/MNG-6160
 Project: Maven
  Issue Type: Bug
  Components: Reactor and workspace
Affects Versions: 3.3.9
Reporter: Robert Scholte
 Attachments: mvn.log

While running {{mvn clean -e -Preporting site}} on the Maven Artifact Resolver 
1.0.3-SNAPSHOT I noticed downloads of files which should be part of the reactor.

{noformat}
[INFO] 
[INFO] Forking Maven Artifact Resolver SPI 1.0.3-SNAPSHOT
[INFO] 
Downloading: 
https://repository.apache.org/snapshots/org/apache/maven/resolver/maven-resolver-api/1.0.3-SNAPSHOT/maven-resolver-api-1.0.3-20170122.151134-3.pom
Downloaded: 
https://repository.apache.org/snapshots/org/apache/maven/resolver/maven-resolver-api/1.0.3-SNAPSHOT/maven-resolver-api-1.0.3-20170122.151134-3.pom
 (2 KB at 1.6 KB/sec)
{noformat}

There are 2 issues with this: 
- Maven is using other files than the expectd files from the reactor
- In case those files don't exist it'll fail.

See log file for complete evidence



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MRESOLVER-16) Site should contain links to the license

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MRESOLVER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833632#comment-15833632
 ] 

Hudson commented on MRESOLVER-16:
-

SUCCESS: Integrated in Jenkins build maven-resolver-demos #5 (See 
[https://builds.apache.org/job/maven-resolver-demos/5/])
[MRESOLVER-16] added standard license link and download page (hboutemy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-resolver-demos.git=commit=605937e49e81bb7c128ef521462b8c81b933a2c9])
* (add) src/site/xdoc/download.xml.vm
* (edit) src/site/site.xml
* (add) src/site/resources/download.cgi


> Site should contain links to the license
> 
>
> Key: MRESOLVER-16
> URL: https://issues.apache.org/jira/browse/MRESOLVER-16
> Project: Maven Resolver
>  Issue Type: Task
>  Components: ant tasks, demo, resolver
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Robert Scholte
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> On the base of Maven Artifact Resolver was a discussion regarding licensing. 
> Results are:
> - We can use Apache License, v2
> - We cannot use the name Aether
> - We can use the package {{org.eclipse.aether}} as long as needed, since 
> renaming would break APIs.
> The site should at least contain links to the license.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MRESOLVER-16) Site should contain links to the license

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MRESOLVER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833631#comment-15833631
 ] 

Hudson commented on MRESOLVER-16:
-

SUCCESS: Integrated in Jenkins build maven-resolver-ant-tasks #5 (See 
[https://builds.apache.org/job/maven-resolver-ant-tasks/5/])
[MRESOLVER-16] added standard license link and download page (hboutemy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-resolver-ant-tasks.git=commit=39e003d19c6f259a1b8941eb78784ca845ddf0d2])
* (edit) src/site/site.xml
* (add) src/site/resources/download.cgi
* (add) src/site/xdoc/download.xml.vm


> Site should contain links to the license
> 
>
> Key: MRESOLVER-16
> URL: https://issues.apache.org/jira/browse/MRESOLVER-16
> Project: Maven Resolver
>  Issue Type: Task
>  Components: ant tasks, demo, resolver
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Robert Scholte
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> On the base of Maven Artifact Resolver was a discussion regarding licensing. 
> Results are:
> - We can use Apache License, v2
> - We cannot use the name Aether
> - We can use the package {{org.eclipse.aether}} as long as needed, since 
> renaming would break APIs.
> The site should at least contain links to the license.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MRESOLVER-16) Site should contain links to the license

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MRESOLVER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833629#comment-15833629
 ] 

Hudson commented on MRESOLVER-16:
-

SUCCESS: Integrated in Jenkins build maven-resolver #36 (See 
[https://builds.apache.org/job/maven-resolver/36/])
[MRESOLVER-16] added standard license link and download page (hboutemy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git=commit=0cce625d127f6e1b23cabe69fd0cc95ad54b0f65])
* (add) src/site/resources/download.cgi
* (add) src/site/xdoc/download.xml.vm
* (edit) src/site/site.xml


> Site should contain links to the license
> 
>
> Key: MRESOLVER-16
> URL: https://issues.apache.org/jira/browse/MRESOLVER-16
> Project: Maven Resolver
>  Issue Type: Task
>  Components: ant tasks, demo, resolver
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Robert Scholte
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> On the base of Maven Artifact Resolver was a discussion regarding licensing. 
> Results are:
> - We can use Apache License, v2
> - We cannot use the name Aether
> - We can use the package {{org.eclipse.aether}} as long as needed, since 
> renaming would break APIs.
> The site should at least contain links to the license.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MRESOLVER-16) Site should contain links to the license

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MRESOLVER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MRESOLVER-16:
---
Component/s: demo
 ant tasks

> Site should contain links to the license
> 
>
> Key: MRESOLVER-16
> URL: https://issues.apache.org/jira/browse/MRESOLVER-16
> Project: Maven Resolver
>  Issue Type: Task
>  Components: ant tasks, demo, resolver
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Robert Scholte
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> On the base of Maven Artifact Resolver was a discussion regarding licensing. 
> Results are:
> - We can use Apache License, v2
> - We cannot use the name Aether
> - We can use the package {{org.eclipse.aether}} as long as needed, since 
> renaming would break APIs.
> The site should at least contain links to the license.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MRESOLVER-16) Site should contain links to the license

[JIRA]

[ 
https://issues.apache.org/jira/browse/MRESOLVER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833625#comment-15833625
 ] 

Hervé Boutemy commented on MRESOLVER-16:


a few years ago, we had some work to add license link + standard download 
source page: I'll add these to Maven Artifact Resolver (and demo + ant tasks)

> Site should contain links to the license
> 
>
> Key: MRESOLVER-16
> URL: https://issues.apache.org/jira/browse/MRESOLVER-16
> Project: Maven Resolver
>  Issue Type: Task
>  Components: ant tasks, demo, resolver
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Robert Scholte
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> On the base of Maven Artifact Resolver was a discussion regarding licensing. 
> Results are:
> - We can use Apache License, v2
> - We cannot use the name Aether
> - We can use the package {{org.eclipse.aether}} as long as needed, since 
> renaming would break APIs.
> The site should at least contain links to the license.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MRESOLVER-16) Site should contain links to the license

[Robert Scholte (JIRA)]

Robert Scholte created MRESOLVER-16:
---

 Summary: Site should contain links to the license
 Key: MRESOLVER-16
 URL: https://issues.apache.org/jira/browse/MRESOLVER-16
 Project: Maven Resolver
  Issue Type: Task
  Components: resolver
Affects Versions: Maven Artifact Resolver 1.0.3
Reporter: Robert Scholte
 Fix For: Maven Artifact Resolver 1.2.0


On the base of Maven Artifact Resolver was a discussion regarding licensing. 
Results are:
- We can use Apache License, v2
- We cannot use the name Aether
- We can use the package {{org.eclipse.aether}} as long as needed, since 
renaming would break APIs.

The site should at least contain links to the license.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-5904) Remove the whole Ant build

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MNG-5904:
---
Summary: Remove the whole Ant build  (was: Remove the whole Ant Build)

> 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-candidate
>
>
> 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.4#6332)

[jira] [Commented] (MNG-6088) after forked execution success, add an empty line

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833579#comment-15833579
 ] 

Hudson commented on MNG-6088:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1499 (See 
[https://builds.apache.org/job/maven-3.x/1499/])
[MNG-6088] add a newline after forked execution success message (hboutemy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=079f6b3ba3301035841e091cd237cd8295168741])
* (edit) 
maven-embedder/src/main/java/org/apache/maven/cli/event/ExecutionEventLogger.java


> 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
>
>
> 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.4#6332)

[jira] [Commented] (MNG-5836) logging config is overridden by $M2_HOME/lib/ext/*.jar

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833578#comment-15833578
 ] 

Hudson commented on MNG-5836:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1499 (See 
[https://builds.apache.org/job/maven-3.x/1499/])
[MNG-5836] put $maven.home/conf/logging first in classpath to avoid (hboutemy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=c516ef79aecdeef5297e44bb5e836e67ffa5336f])
* (edit) apache-maven/src/bin/m2.conf


> 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
>
>
> 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.4#6332)

[jira] [Closed] (MNG-5836) logging config is overridden by $M2_HOME/lib/ext/*.jar

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MNG-5836.
--
Resolution: Fixed

> 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
>
>
> 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.4#6332)

[jira] [Updated] (MNG-5836) logging config is overridden by $M2_HOME/lib/ext/*.jar

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MNG-5836:
---
Summary: logging config is overridden by $M2_HOME/lib/ext/*.jar  (was: 
logging config is overwritten by $M2_HOME/lib/ext/*.jar)

> 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
>
>
> 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.4#6332)

[jira] [Closed] (MNG-6088) after forked execution success, add an empty line

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MNG-6088.
--
Resolution: Fixed

> 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
>
>
> 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.4#6332)

[jira] [Created] (MPOM-159) Upgrade plexus-component-metadata to 1.7.1 to fix JDK 9 issues

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MPOM-159:


 Summary: Upgrade plexus-component-metadata to 1.7.1 to fix JDK 9 
issues
 Key: MPOM-159
 URL: https://issues.apache.org/jira/browse/MPOM-159
 Project: Maven POMs
  Issue Type: Improvement
  Components: maven
Affects Versions: MAVEN-30
Reporter: Karl Heinz Marbaise
 Fix For: MAVEN-31


Currently the plexus-component-metadata is on 1.6 which seemed to cause some 
issues with JDK 9...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-6043) Colorization is disabled too late in batch mode

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MNG-6043.
--
   Resolution: Fixed
Fix Version/s: (was: 3.5.0)

> Colorization is disabled too late in batch mode
> ---
>
> Key: MNG-6043
> URL: https://issues.apache.org/jira/browse/MNG-6043
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
>
> See 
> [discussion|https://mail-archives.apache.org/mod_mbox/maven-dev/201606.mbox/%3Cc3b896b1-db25-9861-6fc0-a1e25afad710%40apache.org%3E].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-6041) Option -l does not disable colorized output

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MNG-6041.
--
   Resolution: Fixed
Fix Version/s: (was: 3.5.0)

> Option -l does not disable colorized output
> ---
>
> Key: MNG-6041
> URL: https://issues.apache.org/jira/browse/MNG-6041
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Reporter: Karl Heinz Marbaise
>Assignee: Robert Scholte
>Priority: Minor
>
> Therefore the generated log file also contains escape sequences. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6043) Colorization is disabled too late in batch mode

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MNG-6043:
---
Affects Version/s: (was: needing-scrub-3.4.0-fallout)

> Colorization is disabled too late in batch mode
> ---
>
> Key: MNG-6043
> URL: https://issues.apache.org/jira/browse/MNG-6043
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
>
> See 
> [discussion|https://mail-archives.apache.org/mod_mbox/maven-dev/201606.mbox/%3Cc3b896b1-db25-9861-6fc0-a1e25afad710%40apache.org%3E].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6041) Option -l does not disable colorized output

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MNG-6041:
---
Affects Version/s: (was: needing-scrub-3.4.0-fallout)

> Option -l does not disable colorized output
> ---
>
> Key: MNG-6041
> URL: https://issues.apache.org/jira/browse/MNG-6041
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Reporter: Karl Heinz Marbaise
>Assignee: Robert Scholte
>Priority: Minor
>
> Therefore the generated log file also contains escape sequences. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-6115) Add Jansi native library search path to our start scripts

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MNG-6115.
--
   Resolution: Fixed
Fix Version/s: (was: 3.5.0)

> Add Jansi native library search path to our start scripts
> -
>
> Key: MNG-6115
> URL: https://issues.apache.org/jira/browse/MNG-6115
> Project: Maven
>  Issue Type: Improvement
>  Components: Bootstrap & Build, Command Line
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
>
> By default Jansi extracts the native, shared library to temp which results in 
> unnecessary file I/O and a huge amount of temp files when Maven is run very 
> often. One can avoid that by adding 
> {{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib}} to the start script. The user 
> has to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the 
> overhead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6046) upgrade JAnsi from 1.12 to 1.13

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MNG-6046:
---
Affects Version/s: (was: needing-scrub-3.4.0-fallout)

> upgrade JAnsi from 1.12 to 1.13
> ---
>
> Key: MNG-6046
> URL: https://issues.apache.org/jira/browse/MNG-6046
> Project: Maven
>  Issue Type: Improvement
>  Components: Logging
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> JAnsi 1.12 blows up when AnsiConsole.systemInstall() is called for a platform 
> where no native lib exists ( see 
> https://repo.maven.apache.org/maven2/org/fusesource/jansi/ for the list of 
> native libraries ) : then Maven becomes unusable for OpenBSD, FreeBSD, 
> Solaris, AIX, ...
> JAnsi 1.13 contains the critical fix: 
> https://github.com/fusesource/jansi/pull/54



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-6046) upgrade JAnsi from 1.12 to 1.13

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MNG-6046.
--
   Resolution: Fixed
Fix Version/s: (was: 3.5.0)

> upgrade JAnsi from 1.12 to 1.13
> ---
>
> Key: MNG-6046
> URL: https://issues.apache.org/jira/browse/MNG-6046
> Project: Maven
>  Issue Type: Improvement
>  Components: Logging
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> JAnsi 1.12 blows up when AnsiConsole.systemInstall() is called for a platform 
> where no native lib exists ( see 
> https://repo.maven.apache.org/maven2/org/fusesource/jansi/ for the list of 
> native libraries ) : then Maven becomes unusable for OpenBSD, FreeBSD, 
> Solaris, AIX, ...
> JAnsi 1.13 contains the critical fix: 
> https://github.com/fusesource/jansi/pull/54



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6115) Add Jansi native library search path to our start scripts

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MNG-6115:
---
Affects Version/s: (was: needing-scrub-3.4.0-fallout)

> Add Jansi native library search path to our start scripts
> -
>
> Key: MNG-6115
> URL: https://issues.apache.org/jira/browse/MNG-6115
> Project: Maven
>  Issue Type: Improvement
>  Components: Bootstrap & Build, Command Line
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
> Fix For: 3.5.0
>
>
> By default Jansi extracts the native, shared library to temp which results in 
> unnecessary file I/O and a huge amount of temp files when Maven is run very 
> often. One can avoid that by adding 
> {{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib}} to the start script. The user 
> has to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the 
> overhead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MINVOKER-216) Prepare for Java9 (requires Groovy upgrade)

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINVOKER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833559#comment-15833559
 ] 

Hudson commented on MINVOKER-216:
-

SUCCESS: Integrated in Jenkins build maven-plugins #8682 (See 
[https://builds.apache.org/job/maven-plugins/8682/])
[MINVOKER-216] Prepare for Java9 (requires Groovy upgrade) (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1779824])
* (edit) maven-invoker-plugin/pom.xml
* (edit) maven-invoker-plugin/src/it/invocation-multiple/pom.xml
* (edit) maven-invoker-plugin/src/it/invocation-multiple/src/it/project/pom.xml
* (edit) maven-invoker-plugin/src/it/settings-merge/invoker.properties
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+/invoker.properties
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+/pom.xml
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+/src
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+/src/it
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+/src/it/project
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+/src/it/project/pom.xml
* (add) 
maven-invoker-plugin/src/it/settings-merge_jdk9+/src/it/project/postbuild.groovy
* (add) maven-invoker-plugin/src/it/settings-merge_jdk9+/src/it/settings.xml


> Prepare for Java9 (requires Groovy upgrade)
> ---
>
> Key: MINVOKER-216
> URL: https://issues.apache.org/jira/browse/MINVOKER-216
> Project: Maven Invoker Plugin
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.0.0
>
>
> Running this plugin with Java9 works quite well, except there are issues with 
> groovy which is using some constructions which are not allowed anymore in 
> Java9.
> With Groovy these should all be fixed.
> ps. One of the ITs depends on gmaven-plugin, which is not maintained anymore 
> and won't work with Java9. This one needs to be rewritten.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MINVOKER-216) Prepare for Java9 (requires Groovy upgrade)

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINVOKER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MINVOKER-216.
---
Resolution: Fixed

Fixed in [r1779824|http://svn.apache.org/viewvc?rev=1779824=rev]

> Prepare for Java9 (requires Groovy upgrade)
> ---
>
> Key: MINVOKER-216
> URL: https://issues.apache.org/jira/browse/MINVOKER-216
> Project: Maven Invoker Plugin
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.0.0
>
>
> Running this plugin with Java9 works quite well, except there are issues with 
> groovy which is using some constructions which are not allowed anymore in 
> Java9.
> With Groovy these should all be fixed.
> ps. One of the ITs depends on gmaven-plugin, which is not maintained anymore 
> and won't work with Java9. This one needs to be rewritten.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MINVOKER-216) Prepare for Java9 (requires Groovy upgrade)

[Robert Scholte (JIRA)]

Robert Scholte created MINVOKER-216:
---

 Summary: Prepare for Java9 (requires Groovy upgrade)
 Key: MINVOKER-216
 URL: https://issues.apache.org/jira/browse/MINVOKER-216
 Project: Maven Invoker Plugin
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Robert Scholte
Assignee: Robert Scholte
 Fix For: 3.0.0


Running this plugin with Java9 works quite well, except there are issues with 
groovy which is using some constructions which are not allowed anymore in Java9.
With Groovy these should all be fixed.

ps. One of the ITs depends on gmaven-plugin, which is not maintained anymore 
and won't work with Java9. This one needs to be rewritten.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6008) Aether code import to git

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833526#comment-15833526
 ] 

Hudson commented on MNG-6008:
-

SUCCESS: Integrated in Jenkins build maven-resolver #34 (See 
[https://builds.apache.org/job/maven-resolver/34/])
[MNG-6008] git repository renamed to maven-resolver.git (hboutemy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git=commit=8bd8c539dbeb65937c766dcea2c4340f405e46a7])
* (edit) pom.xml


> Aether code import to git
> -
>
> Key: MNG-6008
> URL: https://issues.apache.org/jira/browse/MNG-6008
> Project: Maven
>  Issue Type: Sub-task
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> Need a temporary maven-aether.git repository to start working on license 
> headers etc... while defining if we can continue to use the Aether name
> If not, in the future, we'll need to rename the repo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6040) Create a JIRA project for Maven Artifact Resolver MRESOLVER

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833524#comment-15833524
 ] 

Hudson commented on MNG-6040:
-

SUCCESS: Integrated in Jenkins build maven-resolver #34 (See 
[https://builds.apache.org/job/maven-resolver/34/])
[MNG-6040] configured Jira project (hboutemy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git=commit=656749d8517bba43a47cf4d24333e4bc6213d0f9])
* (edit) pom.xml


> Create a JIRA project for Maven Artifact Resolver MRESOLVER
> ---
>
> Key: MNG-6040
> URL: https://issues.apache.org/jira/browse/MNG-6040
> Project: Maven
>  Issue Type: Sub-task
>Reporter: Karl Heinz Marbaise
>Assignee: Hervé Boutemy
>Priority: Blocker
>
> We need to have projekt in JIRA so we can track issues releated to Maven 
> Artifact Resolver



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MRESOLVER-1) Missing LICENSE and NOTICE files

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MRESOLVER-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MRESOLVER-1.
-
   Resolution: Won't Fix
Fix Version/s: (was: Maven Artifact Resolver 1.2.0)

as discussed on dev list 
https://lists.apache.org/thread.html/479ca401b57fbf78b57ebf95bed189d3381fb2f199f9178aee6a816e@%3Cdev.maven.apache.org%3E
 , these files with default content don't need to be hand-maintained in scm: 
they are provided in source release distribution package by 
apache-source-release-assembly-descriptor 
http://maven.apache.org/apache-resource-bundles/

> Missing LICENSE and NOTICE files
> 
>
> Key: MRESOLVER-1
> URL: https://issues.apache.org/jira/browse/MRESOLVER-1
> Project: Maven Resolver
>  Issue Type: Bug
>  Components: resolver
>Affects Versions: Maven Artifact Resolver 1.2.0
>Reporter: Mikolaj Izdebski
>
> LICENSE and NOTICE files are missing from git repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (MRESOLVER-1) Missing LICENSE and NOTICE files

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MRESOLVER-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy reopened MRESOLVER-1:
---
  Assignee: (was: Michael Osipov)

> Missing LICENSE and NOTICE files
> 
>
> Key: MRESOLVER-1
> URL: https://issues.apache.org/jira/browse/MRESOLVER-1
> Project: Maven Resolver
>  Issue Type: Bug
>  Components: resolver
>Affects Versions: Maven Artifact Resolver 1.2.0
>Reporter: Mikolaj Izdebski
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> LICENSE and NOTICE files are missing from git repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MNG-6029) Duplicate conditional and body in MetadataResolutionResult.java

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MNG-6029.
---
Resolution: Duplicate
  Assignee: (was: Michael Osipov)

Issue has been superseded.

> Duplicate conditional and body in MetadataResolutionResult.java
> ---
>
> Key: MNG-6029
> URL: https://issues.apache.org/jira/browse/MNG-6029
> Project: Maven
>  Issue Type: Bug
>  Components: Artifacts and Repositories
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>
> See PR: https://github.com/apache/maven/pull/79



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6029) Duplicate conditional and body in MetadataResolutionResult.java

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-6029:

Fix Version/s: (was: 3.5.0)

> Duplicate conditional and body in MetadataResolutionResult.java
> ---
>
> Key: MNG-6029
> URL: https://issues.apache.org/jira/browse/MNG-6029
> Project: Maven
>  Issue Type: Bug
>  Components: Artifacts and Repositories
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>
> See PR: https://github.com/apache/maven/pull/79



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-6147) MetadataResolutionResult#getGraph() contains duplicate if clause

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-6147:

Fix Version/s: (was: 3.3.9)

> 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
>
> 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.4#6332)

[jira] [Comment Edited] (MNG-6146) Several small stylistic improvements to code and documentation

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833511#comment-15833511
 ] 

Michael Osipov edited comment on MNG-6146 at 1/22/17 1:04 PM:
--

IT commit too {{c09aaa3554b0b67ebedabbfc7821c55d1aecb1da}}.


was (Author: michael-o):
IT commit too {c09aaa3554b0b67ebedabbfc7821c55d1aecb1da}.

> Several small stylistic 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: needing-scrub-3.4.0-fallout
>
>
> The following can easily be squashed:
> {noformat}
> 4f4690cb9ab2ed6e7ad421c28c05c27994e57800 Avoid implicit conversions of int to 
> long
> d99f9ef8c7ffe56966945d6f1b66f0280866ded5 Fix checkstyle error
> 1c9362be4328713386bd23b01f9e2c87674cb952 Use static final values instead of 
> literals
> 8d16c2256d591d0a567dbadec9cc933f15a53fcc Fix Checkstyle error
> 5a3332ca347628605bec7d3e9f9309081aaba46c Remove ancient Subversion keywords
> 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.4#6332)

[jira] [Commented] (MNG-6146) Several small stylistic improvements to code and documentation

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833511#comment-15833511
 ] 

Michael Osipov commented on MNG-6146:
-

IT commit too {c09aaa3554b0b67ebedabbfc7821c55d1aecb1da}.

> Several small stylistic 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: needing-scrub-3.4.0-fallout
>
>
> The following can easily be squashed:
> {noformat}
> 4f4690cb9ab2ed6e7ad421c28c05c27994e57800 Avoid implicit conversions of int to 
> long
> d99f9ef8c7ffe56966945d6f1b66f0280866ded5 Fix checkstyle error
> 1c9362be4328713386bd23b01f9e2c87674cb952 Use static final values instead of 
> literals
> 8d16c2256d591d0a567dbadec9cc933f15a53fcc Fix Checkstyle error
> 5a3332ca347628605bec7d3e9f9309081aaba46c Remove ancient Subversion keywords
> 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.4#6332)

[jira] [Commented] (MNG-6049) Add behavior to filter resolved version ranges of an artifact

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833508#comment-15833508
 ] 

Michael Osipov commented on MNG-6049:
-

IT in {pre-reset-master}:

{noformat}
commit 2066928943348aeae627994ad606d1380b8a5927
Author: Michael Osipov 
Date:   2016-06-25 19:37:43 +0200

[MNG-6049] Add behavior to filter resolved version ranges of an artifact

Disable tests for now because the extension dependency tree creates a
chicken-and-egg dependency problem on Maven 3.4.0. This can only be
resolved when 3.4.0 has been released.

{noformat}

> Add behavior to filter resolved version ranges of an artifact
> -
>
> Key: MNG-6049
> URL: https://issues.apache.org/jira/browse/MNG-6049
> Project: Maven
>  Issue Type: Improvement
>  Components: core, Dependencies
>Reporter: Uwe Barthel
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.6.0-candidate
>
>
> The discussion on issue MNG-3092 shows the seriously needs of different kinds 
> of version range resolving in Maven.
> This solution provides a hook for Maven extensions/plugins to change the list 
> of resolved version range results as required.
> The {{DefaultVersionRangeResolver}} will be extended with a filter for 
> version range results. A new interface {{VersionRangeResultFilter}} is added 
> and a non-filtering {{DefaultVersionRangeResultFilter}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MDEPLOY-214) retryFailedDeploymentCount=10 retries and fails immediately without a waiting time between retries

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MDEPLOY-214:
---
Assignee: (was: Michael Osipov)

> retryFailedDeploymentCount=10 retries and fails immediately without a waiting 
> time between retries
> --
>
> Key: MDEPLOY-214
> URL: https://issues.apache.org/jira/browse/MDEPLOY-214
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>  Components: deploy:deploy
>Affects Versions: 2.8.2
>Reporter: Pablo Alcaraz
>
> a pom.xml file with:
> {code:xml}
> 
> org.apache.maven.plugins
> maven-deploy-plugin
> 2.8.2
> 
> 
> 10
> 
> 
> {code}
> {code:html}
> [INFO] Uploading: 
> http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
> Sep 27, 2016 2:15:22 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing request 
> to {}->http://mvnrepository:8080: Connection reset
> Sep 27, 2016 2:15:22 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: Retrying request to {}->http://mvnrepository:8080
> [WARNING] Encountered issue during deployment: Failed to deploy artifacts: 
> Could not transfer artifact 
> com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to 
> ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect 
> to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
> [INFO] Retrying deployment attempt 2 of 10
> [INFO] Uploading: 
> http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
> [WARNING] Encountered issue during deployment: Failed to deploy artifacts: 
> Could not transfer artifact 
> com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to 
> ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect 
> to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
> [INFO] Retrying deployment attempt 3 of 10
> [INFO] Uploading: 
> http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
> [WARNING] Encountered issue during deployment: Failed to deploy artifacts: 
> Could not transfer artifact 
> com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to 
> ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect 
> to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
> [INFO] Retrying deployment attempt 4 of 10
> [INFO] Uploading: 
> http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
> [WARNING] Encountered issue during deployment: Failed to deploy artifacts: 
> Could not transfer artifact 
> com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to 
> ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect 
> to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
> [INFO] Retrying deployment attempt 5 of 10
> [INFO] Uploading: 
> http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
> [WARNING] Encountered issue during deployment: Failed to deploy artifacts: 
> Could not transfer artifact 
> com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to 
> ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect 
> to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
> [INFO] Retrying deployment attempt 6 of 10
> [INFO] Uploading: 
> http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
> [WARNING] Encountered issue during deployment: Failed to deploy artifacts: 
> Could not transfer artifact 
> com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to 
> ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect 
> to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
> [INFO] Retrying deployment attempt 7 of 10
> [INFO] Uploading: 
> 

[jira] [Updated] (MNG-6106) Remove maven.home default value setter from m2.conf

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-6106:

Issue Type: Task  (was: Bug)

> 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
>
>
> 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.4#6332)

[jira] [Updated] (MNG-6043) Colorization is disabled too late in batch mode

[Michael Osipov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-6043:

Assignee: Hervé Boutemy  (was: Michael Osipov)

> Colorization is disabled too late in batch mode
> ---
>
> Key: MNG-6043
> URL: https://issues.apache.org/jira/browse/MNG-6043
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: needing-scrub-3.4.0-fallout
>Reporter: Michael Osipov
>Assignee: Hervé Boutemy
> Fix For: 3.5.0
>
>
> See 
> [discussion|https://mail-archives.apache.org/mod_mbox/maven-dev/201606.mbox/%3Cc3b896b1-db25-9861-6fc0-a1e25afad710%40apache.org%3E].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MSHADE-240) support relocation pom.properties and pom.xml descriptors in shaded jars

[Thomas Mortagne (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHADE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833437#comment-15833437
 ] 

Thomas Mortagne commented on MSHADE-240:


IMO your use case is covered by what I suggested in the issue description:

bq. An alternative is to move them in some other place like 
/META-INF/shade/maven///* for example, so that you still 
keep information about what has been shaded.

As I said since the JAR does not contain what it's supposed to contain it 
should not screen to still being what it used to be. But in your use case you 
could look at both shaded and not shaded descriptors. In my case I have no way 
to know what kind of JAR it is (and I'm not even supposed to know what shade 
plugin is).

> support relocation pom.properties and pom.xml descriptors in shaded jars
> 
>
> Key: MSHADE-240
> URL: https://issues.apache.org/jira/browse/MSHADE-240
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4.3
>Reporter: Thomas Mortagne
>Assignee: Robert Scholte
> Fix For: 3.0.0
>
>
> When using shade plugin to embbed (and relocate to be safe) some dependency 
> the final jar ends up with the dependency 
> {{/META-INF/maven///*}} files.
> The problem is that in the final jars those files essentially become a lie 
> for any tools looking at those descriptors to find out what the jar contains 
> and you end up with false positive.
> Ideally they should be stripped when relocating a dependency since it means 
> the jar does not contain what is indicated in those files anymore, only 
> something that happen to have the same feature but with completely different 
> packages (so unusable). An alternative is to move them in some other place 
> like {{/META-INF/shade/maven///*}} for example, so that 
> you still keep information about what has been shaded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)