date:20180210

[jira] [Updated] (MNG-6188) Console color not properly reset when interrupting build process

2018-02-10 Thread JIRA


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

Hervé Boutemy updated MNG-6188:
---
Fix Version/s: (was: 3.5.x-candidate)
   3.5.3

> Console color not properly reset when interrupting build process
> 
>
> Key: MNG-6188
> URL: https://issues.apache.org/jira/browse/MNG-6188
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.0-alpha-1
>Reporter: Robert Scholte
>Priority: Major
> Fix For: 3.5.3
>
> Attachments: jansi-bug.PNG
>
>
> When interrupting the build process for some reason, it could happen that 
> console has still a color assigned.
> For a possible result, see the attachment (most of mint should have been 
> white)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6328) kura bulding by using maven

2018-02-10 Thread JIRA


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

Hervé Boutemy closed MNG-6328.
--
Resolution: Invalid

> kura bulding by using maven
> ---
>
> Key: MNG-6328
> URL: https://issues.apache.org/jira/browse/MNG-6328
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.1.0
>Reporter: gopal
>Priority: Major
> Attachments: maven.png, maven1.png
>
>
> I am New to maven,I try to build all the kura source, am Downloaded in the 
> given link:-git clone -b develop https://github.com/eclipse/kura.git
> I am trying to build my kura source by useing maven, I gave command mvn clean 
> install,  in the path :- /home/gopal/kura_git/kura/kura but I got these errors



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MNG-6353) Upgrade maven-shared-utils to 3.2.1

2018-02-10 Thread JIRA


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

Hervé Boutemy updated MNG-6353:
---
Fix Version/s: (was: 3.5.3-candidate)
   3.5.3

> Upgrade maven-shared-utils to 3.2.1
> ---
>
> Key: MNG-6353
> URL: https://issues.apache.org/jira/browse/MNG-6353
> Project: Maven
>  Issue Type: Dependency upgrade
>Reporter: Robert Scholte
>Priority: Major
> Fix For: 3.5.3
>
>
> This version contains 
> \{{o.a.m.s.u.logging.MessageUtils.registerShutdownHook()}} which should 
> prevent ANSI from staying active when killing an active process.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MNG-6215) 'mvn --encrypt-password' doesn't prompt in Git Bash

2018-02-10 Thread JIRA


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

Hervé Boutemy updated MNG-6215:
---
Fix Version/s: 3.5.x-candidate

> 'mvn --encrypt-password' doesn't prompt in Git Bash
> ---
>
> Key: MNG-6215
> URL: https://issues.apache.org/jira/browse/MNG-6215
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.3.9
> Environment: git version 2.12.2.windows.2
> jdk 8u111
> windows 7 pro
>Reporter: Alex Pintilie
>Priority: Major
> Fix For: 3.5.x-candidate
>
> Attachments: screenshot.jpg
>
>
> When I try to encrypt a password with {{mvn --encrypt-password}} in the Git 
> Bash, I get no prompt like in the windows command prompt. Instead I get some 
> empty curly braces {} (see screenshot).
> {{git version 2.12.2.windows.2}}
> Regards,
> Alex



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Moved] (MSHARED-681) Maven-Shared: Java7Support silently fails overwriting symlinks

2018-02-10 Thread JIRA


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

Hervé Boutemy moved MNG-6048 to MSHARED-681:


Component/s: (was: Errors)
 maven-shared-utils
Key: MSHARED-681  (was: MNG-6048)
Project: Maven Shared Components  (was: Maven)

> Maven-Shared: Java7Support silently fails overwriting symlinks
> --
>
> Key: MSHARED-681
> URL: https://issues.apache.org/jira/browse/MSHARED-681
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-shared-utils
>Reporter: Markus Karg
>Priority: Critical
>
> When A is an existing symlink to B, then createSymbolicLink(A,C) does
> neither overwrite A->B by A->C (as expected in analogy to the behavior
> of copy(A,C)) nor does it throw an exception nor does it return A->B to
> indicate the failure, but it actually "silently fails", i. e. it returns
> A->C!
> This certainly is heavily problematic, unsymmetric to what
> copy(File,File) and Files.createSymbolicLink(Path,Path) do, and
> certainly unwanted and buggy behavior.
> The solution is to delete any existing target before creating the
> symlic, hence copying the behavior of copy(File,File).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MASSEMBLY-875) Maven 3.x is about 10x slower than 2.6

2018-02-10 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/MASSEMBLY-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359631#comment-16359631
 ] 

Karl Heinz Marbaise commented on MASSEMBLY-875:
---

Sorry the profiler is only available in version 0.1.0 from central (Doc 
issue)...

> Maven 3.x is about 10x slower than 2.6
> --
>
> Key: MASSEMBLY-875
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-875
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Reporter: Stu
>Priority: Minor
>
> In all our java projects, we have a fairly basic assembly configuration, 
> something like this:
> {code:java}
> 
> maven-assembly-plugin
> 2.6
> 
> 
> 
> org.x.x.x
> 
> 
> 
> jar-with-dependencies
> 
> 
> 
> 
> make-assembly
> package
> 
> single
> 
> 
> 
> {code}
> They all take about 10x longer with any 3.x.x version of the maven assembly 
> plugin than the 2.6 version.
> This has been noticed by others:
> [https://stackoverflow.com/questions/9009232/what-sort-of-configuration-issues-or-problems-might-make-maven-assembly-plugin-g/24519615#24519615]
> But not reported as a bug that I could find.
> Although I could only justify "Minor" for the priority, this is really is a 
> blocker for us moving to 3.x.x
> The upgrade is just not worth taking your build from < 10 sec to > 50 sec.
> (For this particular build, it went from about ~ 7 sec to ~ 57 sec.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MASSEMBLY-876) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MASSEMBLY-876.
-
Resolution: Fixed

Done in 
[e80c195a714b821fb00d8c72d00236414aea2153|https://gitbox.apache.org/repos/asf?p=maven-assembly-plugin.git;a=commitdiff;h=e80c195a714b821fb00d8c72d00236414aea2153]

> Upgrade parent to 31
> 
>
> Key: MASSEMBLY-876
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-876
> Project: Maven Assembly Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MCLEAN-81) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MCLEAN-81.
-
Resolution: Fixed

Done in 
[05512afff435506feb74713742956b5d0cd4ab88|https://gitbox.apache.org/repos/asf?p=maven-clean-plugin.git;a=commitdiff;h=05512afff435506feb74713742956b5d0cd4ab88]

> Upgrade parent to 31
> 
>
> Key: MCLEAN-81
> URL: https://issues.apache.org/jira/browse/MCLEAN-81
> Project: Maven Clean Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MCLEAN-81) Upgrade parent to 31

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MCLEAN-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359628#comment-16359628
 ] 

Hudson commented on MCLEAN-81:
--

Build succeeded in Jenkins: Maven TLP » maven-clean-plugin » master #3

See https://builds.apache.org/job/maven-box/job/maven-clean-plugin/job/master/3/

> Upgrade parent to 31
> 
>
> Key: MCLEAN-81
> URL: https://issues.apache.org/jira/browse/MCLEAN-81
> Project: Maven Clean Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-5378) Use maven-shared-utils in Maven core to replace plexus-utils

2018-02-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on MNG-5378:
-

GitHub user slachiewicz opened a pull request:

https://github.com/apache/maven/pull/155

[MNG-5378] Replace plexus-util StringUtils with commons-lang3



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/slachiewicz/maven fix/MNG-5378

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/155.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #155


commit 6c57ccb33ef97170dba63b835200a0fd84de6a68
Author: Sylwester Lachiewicz 
Date:   2018-02-10T18:05:53Z

[MNG-5378] Replace plexus-utils with commons-lang3




> Use maven-shared-utils in Maven core to replace plexus-utils
> 
>
> Key: MNG-5378
> URL: https://issues.apache.org/jira/browse/MNG-5378
> Project: Maven
>  Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Kristian Rosenvold
>Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> see http://maven.apache.org/shared/maven-shared-utils/ for the rationale



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MASSEMBLY-876) Upgrade parent to 31

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MASSEMBLY-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359561#comment-16359561
 ] 

Hudson commented on MASSEMBLY-876:
--

Build succeeded in Jenkins: Maven TLP » maven-assembly-plugin » master #3

See 
https://builds.apache.org/job/maven-box/job/maven-assembly-plugin/job/master/3/

> Upgrade parent to 31
> 
>
> Key: MASSEMBLY-876
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-876
> Project: Maven Assembly Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MCLEAN-81) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MCLEAN-81:
-

 Summary: Upgrade parent to 31
 Key: MCLEAN-81
 URL: https://issues.apache.org/jira/browse/MCLEAN-81
 Project: Maven Clean Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1475) PpidChecker.windows() assumes wmic is on the path

2018-02-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359558#comment-16359558
 ] 

ASF GitHub Bot commented on SUREFIRE-1475:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/174
  
Of course you should push only single commit in PR.
`git commit --amend`
and the title must be 
`[SUREFIRE-1475] ...here is title as in Jira...`


> PpidChecker.windows() assumes wmic is on the path
> -
>
> Key: SUREFIRE-1475
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1475
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows
>Reporter: Anders Wallgren
>Priority: Major
>
>  
> {{PpidChecker.windows()}} assumes that the wmic executable is on the path, 
> which isn't always the case.
> A better approach would probably be to use 
> {{%SystemRoot%\System32\Wbem\wmic}}.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #174: https://issues.apache.org/jira/browse/SUREFIRE-14...

2018-02-10 Thread Tibor17

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/174
  
Of course you should push only single commit in PR.
`git commit --amend`
and the title must be 
`[SUREFIRE-1475] ...here is title as in Jira...`


---

[GitHub] maven-surefire issue #174: https://issues.apache.org/jira/browse/SUREFIRE-14...

2018-02-10 Thread Tibor17

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/174
  
First of all do it similar like we do in *NIX.
Resolve `%SystemRoot%\System32\Wbem\wmic.exe` in Java and check that the 
file exists.
If it exists use it, otherwise do it as we did before.


---

[jira] [Closed] (MACR-42) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MACR-42.
---
Resolution: Fixed

Done in 
[5f2d3e037f4ad6b6827f02c162df2da182d10897|https://gitbox.apache.org/repos/asf?p=maven-acr-plugin.git;a=commitdiff;h=5f2d3e037f4ad6b6827f02c162df2da182d10897]

> Upgrade parent to 31
> 
>
> Key: MACR-42
> URL: https://issues.apache.org/jira/browse/MACR-42
> Project: Maven ACR Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MACR-42) Upgrade parent to 31

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MACR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359555#comment-16359555
 ] 

Hudson commented on MACR-42:


Build succeeded in Jenkins: Maven TLP » maven-acr-plugin » master #3

See https://builds.apache.org/job/maven-box/job/maven-acr-plugin/job/master/3/

> Upgrade parent to 31
> 
>
> Key: MACR-42
> URL: https://issues.apache.org/jira/browse/MACR-42
> Project: Maven ACR Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6215) 'mvn --encrypt-password' doesn't prompt in Git Bash

2018-02-10 Thread Sylwester Lachiewicz (JIRA)


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

Sylwester Lachiewicz commented on MNG-6215:
---

The same with latest maven Apache Maven 3.5.3-SNAPSHOT 
(61f0166bce265fe1edaf4e20a3c5c9b67972d30e; 2018-02-10T16:17:10+01:00) (Windows 
10) 

{{$ mvn --encrypt-master-password}}
{{[..]}}

{{[DEBUG] Populating class realm maven.api}}
{{[INFO] Error stacktraces are turned on.}}
{{[DEBUG] Message scheme: color}}
{{[DEBUG] Message styles: debug info warning error success failure strong mojo 
project}}
{{[DEBUG] Reading global settings from 
C:\programs\apache-maven-3.5.0\conf\settings.xml}}
{{[DEBUG] Reading user settings from C:\Users\slachiewicz\.m2\settings.xml}}
{{[DEBUG] Reading global toolchains from 
C:\programs\apache-maven-3.5.0\conf\toolchains.xml}}
{{[DEBUG] Reading user toolchains from C:\Users\slachiewicz\.m2\toolchains.xml}}
{{{}}}

{{git version 2.14.1.windows.1}}

 

 

> 'mvn --encrypt-password' doesn't prompt in Git Bash
> ---
>
> Key: MNG-6215
> URL: https://issues.apache.org/jira/browse/MNG-6215
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.3.9
> Environment: git version 2.12.2.windows.2
> jdk 8u111
> windows 7 pro
>Reporter: Alex Pintilie
>Priority: Major
> Attachments: screenshot.jpg
>
>
> When I try to encrypt a password with {{mvn --encrypt-password}} in the Git 
> Bash, I get no prompt like in the windows command prompt. Instead I get some 
> empty curly braces {} (see screenshot).
> {{git version 2.12.2.windows.2}}
> Regards,
> Alex



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRESOLVER-39) deadlock during multithreaded dependency resolution

2018-02-10 Thread Henrik Lundahl (JIRA)


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

Henrik Lundahl commented on MRESOLVER-39:
-

Can possibly 1.1.1 be released so that MNG-6323 can be resolved?

> deadlock during multithreaded dependency resolution
> ---
>
> Key: MRESOLVER-39
> URL: https://issues.apache.org/jira/browse/MRESOLVER-39
> Project: Maven Resolver
>  Issue Type: Bug
>Reporter: Zoltan Haindrich
>Assignee: Robert Scholte
>Priority: Major
> Fix For: Maven Artifact Resolver 1.1.1
>
> Attachments: MRESOLVER-39.tar.gz
>
>
> narrowed down a resolution problem to the commit ad50215 ; which belongs to  
> MRESOLVER-13
> Probably the changes in PartialFile might be the most relevant wrt to this 
> problem.
> for stack traces, see MNG-6323, MNG-6324



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6323) Deadlock in multithreaded dependency resolution

2018-02-10 Thread Henrik Lundahl (JIRA)


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

Henrik Lundahl commented on MNG-6323:
-

MRESOLVER-39 has been fixed now, but Maven Resolver 1.1.1 has not yet been 
released.

> Deadlock in multithreaded dependency resolution
> ---
>
> Key: MNG-6323
> URL: https://issues.apache.org/jira/browse/MNG-6323
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.2
>Reporter: Ben Caradoc-Davies
>Priority: Major
> Attachments: geoserver-community-maven-hang-jstack-2.txt, 
> geoserver-community-maven-hang-jstack.txt
>
>
> Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven 
> 3.5.0.
> To reproduce the issue, clone GeoServer:
> {noformat}
> git clone https://github.com/geoserver/geoserver.git
> cd geoserver
> {noformat}
> Build GeoServer community modules with:
> {noformat}
> mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease 
> -DskipTests clean install
> {noformat}
> Builds that normally take 2-4 minutes instead experience long hangs. 
> {{jstack}} output (attached) suggests a deadlock (two different hangs 
> attached). Some of the locks are in {{TIME_WAIT}} and eventually the build 
> completes after 30-45 minutes, but this is enough to cause builds on Travis 
> to be killed for their failure to output for ten minutes. (Travis upgraded to 
> Maven 3.5.2 a week ago.)
> I have only seen the failures with -U. The hang does not occur in 
> single-threaded builds. There are no "*.lock" files in the local repository 
> during the hang so the deadlocks are not mediated by the filesystem. CPU 
> utilisation is zero suggesting a deadlock not a livelock.
> See also discussion on the geoserver-devel mailing list: 
> http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRELEASE-726) mvn release:prepare-with-pom not honouring the commitByProject parameter.

2018-02-10 Thread Robert Scholte (JIRA)


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

Robert Scholte closed MRELEASE-726.
---
Resolution: Pending Closed
  Assignee: Robert Scholte

Git support has been improved with 2.5.x.

Based on no activity I assume this one can be closed by now.

> mvn release:prepare-with-pom not honouring the commitByProject parameter.
> -
>
> Key: MRELEASE-726
> URL: https://issues.apache.org/jira/browse/MRELEASE-726
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: Git, prepare-with-pom
>Affects Versions: 2.2.2
> Environment: Linux 64bit (Ubuntu).
>Reporter: Dave Fennell
>Assignee: Robert Scholte
>Priority: Blocker
> Attachments: MNG-726-maven-release-manager.patch, 
> MNG-726-maven-scm-provider-gitexe.patch, bug-726-scenario.zip, 
> patched_output.txt, pre_patched_output.txt
>
>
> Using this in my pom file:
> {code:xml}
>   
>   org.apache.maven.plugins
>   maven-release-plugin
>   2.2.2
>   
>   deploy
>   false
>   true
>   true
>   
>   
> {code}
> Running this command:
> {{mvn release:prepare}}
> Correctly goes into each directory to make changes, e.g. 
> {noformat}
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd /usr/local/src/whitelabel && git add -- 
> pom.xml
> [INFO] Working directory: /usr/local/src/whitelabel
> [INFO] Executing: /bin/sh -c cd /usr/local/src/whitelabel && git status
> [INFO] Working directory: /usr/local/src/whitelabel
> [INFO] Executing: /bin/sh -c cd /usr/local/src/whitelabel && git commit 
> --verbose -F /tmp/maven-scm-561169862.commit pom.xml
> [INFO] Working directory: /usr/local/src/whitelabel
> [INFO] Executing: /bin/sh -c cd /usr/local/src/whitelabel/foundation && git 
> add -- pom.xml
> [INFO] Working directory: /usr/local/src/whitelabel/foundation
> [INFO] Executing: /bin/sh -c cd /usr/local/src/whitelabel/foundation && git 
> status
> [INFO] Working directory: /usr/local/src/whitelabel/foundation
> [INFO] Executing: /bin/sh -c cd /usr/local/src/whitelabel/foundation && git 
> commit --verbose -F /tmp/maven-scm-2018482909.commit pom.xml
> {noformat}
> etc ...
> However running this command:
> {{mvn release:prepare-with-pom}}
> So that I can generate a release-pom.xml file errors because it attempts to 
> do all the checkins on one line:
> {noformat}
> [INFO] Executing: /bin/sh -c cd /usr/local/src/whitelabel && git add -- 
> release-pom.xml foundation/release-pom.xml module/release-pom.xml 
> module/advertising/release-pom.xml module/buttonconfig/release-pom.xml 
> module/core/release-pom.xml module/film/release-pom.xml 
> module/profile/release-pom.xml module/proxy/release-pom.xml 
> module/rental/release-pom.xml module/service/release-pom.xml 
> module/smartcard/release-pom.xml module/telephony/release-pom.xml 
> module/terminalui/release-pom.xml module/tv/release-pom.xml 
> module/upsell/release-pom.xml module/urlconfig/release-pom.xml 
> mule/release-pom.xml mule/advertising/release-pom.xml 
> mule/button-config/release-pom.xml mule/film/release-pom.xml 
> mule/hospediacard/release-pom.xml mule/location/release-pom.xml 
> mule/profile/release-pom.xml mule/proxy/release-pom.xml 
> mule/rental/release-pom.xml mule/service/release-pom.xml 
> mule/smartcard/release-pom.xml mule/startup/release-pom.xml 
> mule/terminaluimenu/release-pom.xml mule/tv/release-pom.xml 
> mule/upsell/release-pom.xml mule/urlconfig/release-pom.xml
> {noformat}
> This doesn't work for my setup because each directory is a git submodule so 
> must be run separately, it looks to me like it's simply ignoring the 
> {{commitByProject}} setting, but the docs 
> (http://maven.apache.org/plugins/maven-release-plugin/prepare-with-pom-mojo.html)
>  list it as being a supported property since {{2.0-beta5}}.  I've marked this 
> as a blocker because I wanted to use the release-pom.xml and I have no way to 
> generate them now (since the {{-DgenerateReleasePoms}} option on the 
> {{release:prepare}} goal seems to have been deprecated).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRELEASE-900) release:prepare goal uses parent directory of real repository location

2018-02-10 Thread Robert Scholte (JIRA)


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

Robert Scholte closed MRELEASE-900.
---
Resolution: Pending Closed
  Assignee: Robert Scholte

> release:prepare goal uses parent directory of real repository location
> --
>
> Key: MRELEASE-900
> URL: https://issues.apache.org/jira/browse/MRELEASE-900
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Affects Versions: 2.5.1
>Reporter: Jens Rabe
>Assignee: Robert Scholte
>Priority: Blocker
>
> I have this in my pom.xml:
> {code:xml}
> 
> 
> scm:git:http://my-git-server.example.com/git/somebody/my-project.git
> 
> ssh://g...@my-git-server.example.com:10022/somebody/my-project.git
> http://my-git-server.example.com/git/somebody/my-project
> 
> {code}
> When I do a mvn release:prepare, it tries to push the tag to 
> ssh://g...@my-git-server.example.com:10022/somebody/ instead of 
> ssh://g...@my-git-server.example.com:10022/somebody/my-project.git, causing 
> the release prepare to fail with "Access denied".
> When I add a "fake file" at the end, like:
> {code:xml}
> 
> 
> scm:git:http://my-git-server.example.com/git/somebody/my-project.git/.git
> 
> ssh://g...@my-git-server.example.com:10022/somebody/my-project.gi/.gitt
> http://my-git-server.example.com/git/somebody/my-project
> 
> {code}
> the release:prepare works, but release:perform fails because it is using the 
> URL as-is.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRELEASE-923) mvn release:prepare-with-pom doesn't replace SNAPSHOTs defined in a SNAPSHOT parent

2018-02-10 Thread Robert Scholte (JIRA)


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

Robert Scholte closed MRELEASE-923.
---
Resolution: Not A Problem
  Assignee: Robert Scholte

> mvn release:prepare-with-pom doesn't replace SNAPSHOTs defined in a SNAPSHOT 
> parent
> ---
>
> Key: MRELEASE-923
> URL: https://issues.apache.org/jira/browse/MRELEASE-923
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare-with-pom
>Affects Versions: 2.5.2, 2.5.3
>Reporter: Andreas Schaller
>Assignee: Robert Scholte
>Priority: Blocker
>
> If I use a SNAPSHOT version of a plugin within a parent pom that is also a 
> SNAPSHOT, the mvn release:prepare-with-pom can't replace it with its released 
> version.
> I'm asked:
> {noformat}
> There are still some remaining snapshot dependencies.
> : Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project 
> Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : 
> Dependency 'my.group:my.dependency' is a snapshot (1.0.0-SNAPSHOT)
> : Which release version should it be set to? 1.0.0: : 
> What version should the dependency be reset to for development? 1.0.0: : 
> 1.0.1-SNAPSHOT
> Dependency 'my.group:my.parent' is a snapshot (1.0.0-SNAPSHOT)
> : Which release version should it be set to? 1.0.0: : 
> What version should the dependency be reset to for development? 1.0.0: : 
> 1.0.1-SNAPSHOT
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 40.211s
> [INFO] Finished at: Wed Sep 23 13:35:33 CEST 2015
> [INFO] Final Memory: 17M/157M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare-with-pom 
> (default-cli) on project my.project: Can't release project due to non 
> released dependencies :
> [ERROR] my.group:my.maven.plugin:maven-plugin:1.0.0-SNAPSHOT:runtime
> {noformat}
> Example parent pom:
> {code:xml}
> 
> my.group
> my.parent
> 1.0.0-SNAPSHOT
> pom
> 
> 
> java-packaging-tools
> 
> true
> 
> 
> 
> 
> my.group
> my.maven.plugin
> 1.0.0-SNAPSHOT
> 
> 
> 
> 
> 
> 
> {code}
> Example project pom:
> {code:xml}
> 
> my.group
> my.project
> 1.0.0-SNAPSHOT
> 
> 
> my.group
> my.dependency
> 1.0.0-SNAPSHOT
> 
> 
> 
> {code}
> So first of all, why are the transitive dependencies resolved before the 
> parent?
> And now the issue: in the released version of my.parent (1.0.0) there is also 
> the released version of my.maven.plugin (1.0.0) so why is the 
> relase:prepare-with-pom failing?
> If I manually set the parent version to 1.0.0 before I run mvn 
> relase:prepare-with-pom everything works fine as expected.
> Also I when use the option "Dependency type to resolve,: specify the 
> selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 
> 4:Extensions ): (0/1/2/3) 1: : 0" I'm asked for the relese version of the 
> my.maven.plugin and can perform the release as expected.
> And a last question: why is the default answer for the "What version should 
> the dependency be reset to for development?" question always the released 
> version and not the next SNAPSHOT version?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MASSEMBLY-876) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MASSEMBLY-876:
-

 Summary: Upgrade parent to 31
 Key: MASSEMBLY-876
 URL: https://issues.apache.org/jira/browse/MASSEMBLY-876
 Project: Maven Assembly Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.1.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.1.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRELEASE-998) Add ability to create custom phases

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRELEASE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359496#comment-16359496
 ] 

Hudson commented on MRELEASE-998:
-

Build succeeded in Jenkins: Maven TLP » maven-release » master #34

See https://builds.apache.org/job/maven-box/job/maven-release/job/master/34/

> Add ability to create custom phases
> ---
>
> Key: MRELEASE-998
> URL: https://issues.apache.org/jira/browse/MRELEASE-998
> Project: Maven Release Plugin
>  Issue Type: New Feature
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0
>
>
> With the implementation of strategies it should also be possible to create 
> custom phases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRELEASE-601) The Maven 2 release plugin modifies CDATA elements in pom.xml files.

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRELEASE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359495#comment-16359495
 ] 

Hudson commented on MRELEASE-601:
-

Build succeeded in Jenkins: Maven TLP » maven-release » master #34

See https://builds.apache.org/job/maven-box/job/maven-release/job/master/34/

> The Maven 2 release plugin modifies CDATA elements in pom.xml files.
> 
>
> Key: MRELEASE-601
> URL: https://issues.apache.org/jira/browse/MRELEASE-601
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Affects Versions: 2.0-beta-7
>Reporter: Brandon Enochs
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: pom.xml
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRELEASE-998) Add ability to create custom phases

2018-02-10 Thread Robert Scholte (JIRA)


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

Robert Scholte closed MRELEASE-998.
---
Resolution: Fixed

Fixed in 
[419114d796c3dea8718f51606ff0482232184487|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=419114d796c3dea8718f51606ff0482232184487]

> Add ability to create custom phases
> ---
>
> Key: MRELEASE-998
> URL: https://issues.apache.org/jira/browse/MRELEASE-998
> Project: Maven Release Plugin
>  Issue Type: New Feature
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0
>
>
> With the implementation of strategies it should also be possible to create 
> custom phases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MACR-42) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MACR-42:
---

 Summary: Upgrade parent to 31
 Key: MACR-42
 URL: https://issues.apache.org/jira/browse/MACR-42
 Project: Maven ACR Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6204) Exception when parsing

2018-02-10 Thread Sylwester Lachiewicz (JIRA)


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

Sylwester Lachiewicz commented on MNG-6204:
---

The plexus-utils 3.1 was relased in May 2017 - could you verify if yours issue 
is still valid?

> Exception when parsing  
>
> Key: MNG-6204
> URL: https://issues.apache.org/jira/browse/MNG-6204
> Project: Maven
>  Issue Type: Bug
>  Components: Bootstrap  Build
>Affects Versions: 3.3.9, 3.5.0-alpha-1, 3.5.0-beta-1
> Environment: Windows 7
>Reporter: Robert Kleinschmager
>Priority: Major
> Attachments: debug.log, pom.xml
>
>
> Parsing large pom.xml  (>8kb), which contains  * Steps
> ** use given !pom.xml!
> ** execute {{mvn validate}}
> * Expected
> ** pass
> * Actual
> ** {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 10106
>   at 
> org.codehaus.plexus.util.xml.pull.MXParser.parsePI(MXParser.java:2502)
> {code}
> ** see !debug.log!
> * this is caused by [plexus-utils issue no 
> 22|https://github.com/codehaus-plexus/plexus-utils/issues/22]
> ** PR must be merged 
> [PR#23|https://github.com/codehaus-plexus/plexus-utils/pull/23]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MENFORCER-297) Upgrade parent to 31

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MENFORCER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359472#comment-16359472
 ] 

Hudson commented on MENFORCER-297:
--

Build succeeded in Jenkins: Maven TLP » maven-enforcer » master #15

See https://builds.apache.org/job/maven-box/job/maven-enforcer/job/master/15/

> Upgrade parent to 31
> 
>
> Key: MENFORCER-297
> URL: https://issues.apache.org/jira/browse/MENFORCER-297
> Project: Maven Enforcer Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-M1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MRELEASE-998) Add ability to create custom phases

2018-02-10 Thread Robert Scholte (JIRA)

Robert Scholte created MRELEASE-998:
---

 Summary: Add ability to create custom phases
 Key: MRELEASE-998
 URL: https://issues.apache.org/jira/browse/MRELEASE-998
 Project: Maven Release Plugin
  Issue Type: New Feature
Reporter: Robert Scholte
Assignee: Robert Scholte
 Fix For: 3.0.0


With the implementation of strategies it should also be possible to create 
custom phases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MDEPLOY-230) Upgrade parent to 31

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEPLOY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359470#comment-16359470
 ] 

Hudson commented on MDEPLOY-230:


Build succeeded in Jenkins: Maven TLP » maven-deploy-plugin » master #3

See 
https://builds.apache.org/job/maven-box/job/maven-deploy-plugin/job/master/3/

> Upgrade parent to 31
> 
>
> Key: MDEPLOY-230
> URL: https://issues.apache.org/jira/browse/MDEPLOY-230
> Project: Maven Deploy Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MENFORCER-297) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MENFORCER-297.
-
Resolution: Fixed

Done in 
[05b35e8ac7f752fa765cfaa56982fdc0f29a98bf|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commitdiff;h=05b35e8ac7f752fa765cfaa56982fdc0f29a98bf]

> Upgrade parent to 31
> 
>
> Key: MENFORCER-297
> URL: https://issues.apache.org/jira/browse/MENFORCER-297
> Project: Maven Enforcer Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-M1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINSTALL-142) Upgrade parent to 31

2018-02-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MINSTALL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359468#comment-16359468
 ] 

Hudson commented on MINSTALL-142:
-

Build succeeded in Jenkins: Maven TLP » maven-install-plugin » master #7

See 
https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/master/7/

> Upgrade parent to 31
> 
>
> Key: MINSTALL-142
> URL: https://issues.apache.org/jira/browse/MINSTALL-142
> Project: Maven Install Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MDEPLOY-230) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MDEPLOY-230.
---
Resolution: Fixed

Done in 
[8ca9666c9ddd6b9db4fdd9c94f1ae52f25f173c6|https://gitbox.apache.org/repos/asf?p=maven-deploy-plugin.git;a=commitdiff;h=8ca9666c9ddd6b9db4fdd9c94f1ae52f25f173c6]

> Upgrade parent to 31
> 
>
> Key: MDEPLOY-230
> URL: https://issues.apache.org/jira/browse/MDEPLOY-230
> Project: Maven Deploy Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MINSTALL-142) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MINSTALL-142.

Resolution: Fixed

Done in 
[9d47c7a616415c321df27acd3e0457b95f0ecc28|https://gitbox.apache.org/repos/asf?p=maven-install-plugin.git;a=commitdiff;h=9d47c7a616415c321df27acd3e0457b95f0ecc28]]

> Upgrade parent to 31
> 
>
> Key: MINSTALL-142
> URL: https://issues.apache.org/jira/browse/MINSTALL-142
> Project: Maven Install Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MDEPLOY-230) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MDEPLOY-230:
---

 Summary: Upgrade parent to 31
 Key: MDEPLOY-230
 URL: https://issues.apache.org/jira/browse/MDEPLOY-230
 Project: Maven Deploy Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MINSTALL-142) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MINSTALL-142:


 Summary: Upgrade parent to 31
 Key: MINSTALL-142
 URL: https://issues.apache.org/jira/browse/MINSTALL-142
 Project: Maven Install Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MENFORCER-297) Upgrade parent to 31

2018-02-10 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MENFORCER-297:
-

 Summary: Upgrade parent to 31
 Key: MENFORCER-297
 URL: https://issues.apache.org/jira/browse/MENFORCER-297
 Project: Maven Enforcer Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.0.0-M1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6311) Maven intolerably slow when import scope used heavily in large project

2018-02-10 Thread Sylwester Lachiewicz (JIRA)


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

Sylwester Lachiewicz commented on MNG-6311:
---

In the maven-resolver project there is a fix that introduces parallel artifact 
retrieval, but I think that yours patch has a much greater impact on performance

> Maven intolerably slow when import scope used heavily in large project
> --
>
> Key: MNG-6311
> URL: https://issues.apache.org/jira/browse/MNG-6311
> Project: Maven
>  Issue Type: Bug
>  Components: core, Performance
>Affects Versions: 3.5.0, 3.5.2
>Reporter: David Churcher
>Priority: Major
>  Labels: performance
> Attachments: anon-hierarchy-maven-output.zip, modelcachefix.diff
>
>
> I have a build performance problem that is identical to MNG-5312, and has 
> appeared since MNG-6030 in Maven v3.5.0 reversed the patch for MNG-5312, 
> removing the ModelCache from some of the overloads for 
> DefaultProjectBuilder.build. 
> As in MNG-5312 the problem is in a large proprietary project. It uses up to 8 
> levels of parent POMs, many of which use the import scope and have large 
> dependency-management sections, and has hundreds of dependencies that also 
> use the same parent POM hierarchy. Adding some logging shows that Maven does 
> over 800,000 uncached reads of parent POM files, which takes about half an 
> hour. With model caching this goes down to a few seconds.
> I've attached a patch that fixes this by using a class-level ModelCache in 
> DefaultProjectBuilder. This does not suffer from the memory usage problems 
> reported in MNG-6030.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6239) jansi messes up System.err and System.out

2018-02-10 Thread Sylwester Lachiewicz (JIRA)


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

Sylwester Lachiewicz commented on MNG-6239:
---

Verified on the latest version of maven 3.5.3-SNAPSHOT and jansi 1.17 and the 
problem still occurs

> jansi messes up System.err and System.out
> -
>
> Key: MNG-6239
> URL: https://issues.apache.org/jira/browse/MNG-6239
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.5.0
> Environment: Java 1.8.0_131, Ubuntu 17.04
>Reporter: Simone Bordet
>Priority: Blocker
> Attachments: mvn-jansi.tgz
>
>
> I use the Maven Exec Plugin to run a class that asks for interactive input 
> from the user. This was working in 3.3.9, but does not work in 3.5.0.
> Anything printed on {{System.err}} or {{System.out}} without a newline is not 
> printed immediately on the terminal window.
> Example:
> {code:java}
> BufferedReader console = new BufferedReader(new InputStreamReader(System.in));
> System.err.printf("listen port: ");
> String value = console.readLine().trim();
> {code}
> The example above would not print {{listen port:}} on the terminal.
> Attached you can find a project that reproduces this issue.
> Unpack the project and then run:
> {noformat}
> $ mvn install && mvn exec:exec
> {noformat}
> The expected output of the reproducer would be:
> {noformat}
> err.println
> out.println
> err.printerr.printfout.printout.printf
> {noformat}
> instead I get:
> {noformat}
> err.println
> out.println
> {noformat}
> Removing {{jansi-1.13.jar}} from {{$MAVEN/lib/}} fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6353) Upgrade maven-shared-utils to 3.2.1

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6353:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6353 #2

See https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6353/2/

> Upgrade maven-shared-utils to 3.2.1
> ---
>
> Key: MNG-6353
> URL: https://issues.apache.org/jira/browse/MNG-6353
> Project: Maven
>  Issue Type: Dependency upgrade
>Reporter: Robert Scholte
>Priority: Major
> Fix For: 3.5.3-candidate
>
>
> This version contains 
> \{{o.a.m.s.u.logging.MessageUtils.registerShutdownHook()}} which should 
> prevent ANSI from staying active when killing an active process.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6069) Migrate to non deprecated parts of Commons CLI

2018-02-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on MNG-6069:
-

Github user slachiewicz commented on a diff in the pull request:

https://github.com/apache/maven/pull/153#discussion_r167400525
  
--- Diff: maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java 
---
@@ -1620,14 +1620,18 @@ static void populateProperties( CommandLine 
commandLine, Properties systemProper
 
 if ( commandLine.hasOption( CLIManager.SET_SYSTEM_PROPERTY ) )
 {
-String[] defStrs = commandLine.getOptionValues( 
CLIManager.SET_SYSTEM_PROPERTY );
-
-if ( defStrs != null )
+Properties lineOptionProperties = 
commandLine.getOptionProperties( CLIManager.SET_SYSTEM_PROPERTY );
+
+for ( String defStr : 
lineOptionProperties.stringPropertyNames( ) )
 {
-for ( String defStr : defStrs )
-{
-setCliProperty( defStr, userProperties );
-}
+String optValue = lineOptionProperties.getProperty( defStr 
);
+userProperties.setProperty( defStr, optValue );
+
+// 
--
+// I'm leaving the setting of system properties here as 
not to break
+// the SystemPropertyProfileActivator. This won't harm 
embedding. jvz.
+// 
--
+   System.setProperty( defStr, optValue );
--- End diff --

System properties will stay, new commons-cli just simplified setCliProperty.


> Migrate to non deprecated parts of Commons CLI
> --
>
> Key: MNG-6069
> URL: https://issues.apache.org/jira/browse/MNG-6069
> Project: Maven
>  Issue Type: Improvement
>  Components: Embedding
>Affects Versions: 3.3.9, 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.5.x-candidate
>
>
> At the moment all parts of {{OptionBuilder...}} are marked deprecated in 
> {{CLIManager}}. They should be migrated to:
> {code:java}
> Option.builder( HELP ).longOpt( "help" ).desc( "Display help information" 
> ).build()
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-5967) Dependency updates

2018-02-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on MNG-5967:
-

Github user slachiewicz closed the pull request at:

https://github.com/apache/maven/pull/154


> 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-alpha-1, 3.5.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6335) Update test framework Mockito from 1.10 to 2.12

2018-02-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on MNG-6335:
-

Github user slachiewicz closed the pull request at:

https://github.com/apache/maven/pull/150


> Update test framework Mockito from 1.10 to 2.12
> ---
>
> Key: MNG-6335
> URL: https://issues.apache.org/jira/browse/MNG-6335
> Project: Maven
>  Issue Type: Dependency upgrade
>Affects Versions: 3.5.2
>Reporter: Sylwester Lachiewicz
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6320) Apparently wrong encoding of non-ascii java class filename in error messages in the maven log

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6320:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6352-print-version #3

See 
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6352-print-version/3/

> Apparently wrong encoding of non-ascii java class filename in error messages 
> in the maven log
> -
>
> Key: MNG-6320
> URL: https://issues.apache.org/jira/browse/MNG-6320
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.2
> Environment: Windows 10
>Reporter: Eugene Pliskin
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.3
>
> Attachments: maven.3.3.9.log, maven.3.5.2.log
>
>
> Attached please find two build logs, one from maven version 3.3.9, and 
> another from maven version 3.5.2. Both log files were made for the same Java 
> project on Windows 10 machine, with "mvn compile > log" command. Java 
> platform default encoding is UTF-8.
> One Java source file contains intentional error, which is reported in lines 
> 433-435 of file "maven.3.3.9.log", and in lines 437-439 of file 
> "maven.3.5.2.log". 
> Class name is non-ascii and version 3.3.9 log appears right. But in version 
> 3.5.2 this same filename appears unreadable in the error message in the maven 
> log.
> Notice that if I view the file "maven.3.5.2.log" with different encoding 
> (cp866), then this error message becomes readable. It looks like this 
> non-ascii filename gets inserted into UTF-8 encoded log file in wrong "cp866" 
> encoding, in maven version 3.5.2.
> Still, version 3.3.9 of maven does the right thing, and the error message is 
> readable in UTF-8 log.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6282) Console output has no colors in shell (both Git Bash and Cygwin) [regression in Jansi 1.16 / Maven 3.5.1]

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6282:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6352-print-version #3

See 
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6352-print-version/3/

> Console output has no colors in shell (both Git Bash and Cygwin) [regression 
> in Jansi 1.16 / Maven 3.5.1]
> -
>
> Key: MNG-6282
> URL: https://issues.apache.org/jira/browse/MNG-6282
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.2
>Reporter: Dejan Stojadinović
>Assignee: Hervé Boutemy
>Priority: Major
>  Labels: regression, windows
> Fix For: 3.5.3
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, 
> screenshot-4.png, screenshot-5-Cygwin.png, screenshot-6.png, screenshot-7.png
>
>
> See 
> [screenshot|https://issues.apache.org/jira/secure/attachment/12886398/screenshot-1.png]
>  for more details.
> _*Environment:*_
> * Windows 10, 64 bit
> * Oracle Java, version: *1.8.0_144*
> * Git Bash shell (MINGW64), Cygwin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6352) Printout version information at the end of the build

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6352:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6352-print-version #3

See 
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6352-print-version/3/

> Printout version information at the end of the build
> 
>
> Key: MNG-6352
> URL: https://issues.apache.org/jira/browse/MNG-6352
> Project: Maven
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 3.5.2
>Reporter: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.5.3
>
>
> At the end of the buid in particular of a mutli module build we should print 
> the information about the versions of modules (in case of aggregators) or 
> only a single version in case of a multi module build as an information for 
> the user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6255) Maven script cannot parse jvm.config with CRLF

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6255:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6352-print-version #3

See 
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6352-print-version/3/

> Maven script cannot parse jvm.config with CRLF
> --
>
> Key: MNG-6255
> URL: https://issues.apache.org/jira/browse/MNG-6255
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 7 with MINGW64 environment via Git for Windows 
> 0.1.1 including GNU coreutils and bash 4.4.12
>Reporter: Andrew Kennedy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.5.3
>
>
> A project with a {{.mvn/jvm.config}} file that has *CRLF* line endings will 
> not parse it correctly. The script uses the {{tr}} command to change *LF* to 
> space, but this leaves *CR* behind. For example, with the {{jvm.config}} file 
> containing the text {{-Xmx1024m -Xms512m}} followed by *CRLF*, the following 
> error message is printed:
> {code}
> $ mvn install
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Invalid initial heap size: -Xms512m
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6335) Update test framework Mockito from 1.10 to 2.12

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6335:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6352-print-version #3

See 
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6352-print-version/3/

> Update test framework Mockito from 1.10 to 2.12
> ---
>
> Key: MNG-6335
> URL: https://issues.apache.org/jira/browse/MNG-6335
> Project: Maven
>  Issue Type: Dependency upgrade
>Affects Versions: 3.5.2
>Reporter: Sylwester Lachiewicz
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-5992) Git passwords are exposed as the Super POM still uses Maven Release Plugin 2.3.2

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-5992:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6352-print-version #3

See 
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6352-print-version/3/

> Git passwords are exposed as the Super POM still uses Maven Release Plugin 
> 2.3.2
> 
>
> Key: MNG-5992
> URL: https://issues.apache.org/jira/browse/MNG-5992
> Project: Maven
>  Issue Type: Improvement
>  Components: Bootstrap  Build, Plugins and Lifecycle, POM
>Affects Versions: 3.3.3, 3.3.9
> Environment: All
>Reporter: Ryan J. McDonough
>Assignee: Hervé Boutemy
>Priority: Critical
>  Labels: security
> Fix For: 3.5.3
>
>
> The super POM defines version 2.3.2 of the Maven Release plugin. When using 
> HTTP/HTTPS Git SCM URIs, Maven will printout the password in the logs. Thus, 
> any CI system such as Jenkins, TravisCI, etc. will have the passwords exposed 
> in the logs and in the console output. In the case of TravisCI, this will be 
> publicly visible. 
> The [Maven Release Plugin fixed this issue in 
> MRELEASE-846|https://issues.apache.org/jira/browse/MRELEASE-846], but Maven 
> core is still pointing at an exposed version of the Maven Release plugin. I 
> have a test case that demonstrates the issue here:
> https://github.com/damnhandy/maven-publish-issue
> If you run the same build and explicitly define 2.5.3, the password is no 
> longer displayed. This should be the default. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6255) Maven script cannot parse jvm.config with CRLF

2018-02-10 Thread JIRA


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

Hervé Boutemy closed MNG-6255.
--
   Resolution: Fixed
 Assignee: Hervé Boutemy
Fix Version/s: (was: 3.5.3-candidate)
   3.5.3

PR merged, thank you
https://git-wip-us.apache.org/repos/asf?p=maven.git=commit=867e5d50be0bca17b1ba23c78e8c7c6d74c6aecd

> Maven script cannot parse jvm.config with CRLF
> --
>
> Key: MNG-6255
> URL: https://issues.apache.org/jira/browse/MNG-6255
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 7 with MINGW64 environment via Git for Windows 
> 0.1.1 including GNU coreutils and bash 4.4.12
>Reporter: Andrew Kennedy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.5.3
>
>
> A project with a {{.mvn/jvm.config}} file that has *CRLF* line endings will 
> not parse it correctly. The script uses the {{tr}} command to change *LF* to 
> space, but this leaves *CR* behind. For example, with the {{jvm.config}} file 
> containing the text {{-Xmx1024m -Xms512m}} followed by *CRLF*, the following 
> error message is printed:
> {code}
> $ mvn install
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Invalid initial heap size: -Xms512m
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6335) Update test framework Mockito from 1.10 to 2.12

2018-02-10 Thread JIRA


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

Hervé Boutemy closed MNG-6335.
--
   Resolution: Fixed
Fix Version/s: (was: 3.5.3-candidate)
   3.5.3

PR merged, thank you
https://git-wip-us.apache.org/repos/asf?p=maven.git=commit=a03489b67d04a4b014ff5d1c151b331a39bf100b

> Update test framework Mockito from 1.10 to 2.12
> ---
>
> Key: MNG-6335
> URL: https://issues.apache.org/jira/browse/MNG-6335
> Project: Maven
>  Issue Type: Dependency upgrade
>Affects Versions: 3.5.2
>Reporter: Sylwester Lachiewicz
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (MNG-6335) Update test framework Mockito from 1.10 to 2.12

2018-02-10 Thread JIRA


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

Hervé Boutemy reassigned MNG-6335:
--

Assignee: Hervé Boutemy

> Update test framework Mockito from 1.10 to 2.12
> ---
>
> Key: MNG-6335
> URL: https://issues.apache.org/jira/browse/MNG-6335
> Project: Maven
>  Issue Type: Dependency upgrade
>Affects Versions: 3.5.2
>Reporter: Sylwester Lachiewicz
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.3-candidate
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6282) Console output has no colors in shell (both Git Bash and Cygwin) [regression in Jansi 1.16 / Maven 3.5.1]

2018-02-10 Thread JIRA


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

Hervé Boutemy closed MNG-6282.
--
   Resolution: Fixed
 Assignee: Hervé Boutemy
Fix Version/s: 3.5.3

Jansi upgrade done 
https://git-wip-us.apache.org/repos/asf?p=maven.git=commit=916839528cfc26719cb85dc74e3165095447bc97
 to benefit from https://github.com/fusesource/jansi-native/issues/11

and Maven workaround removed 
https://git-wip-us.apache.org/repos/asf?p=maven.git=commit=e2bc17b5087067398cf17c009f74cfb493ace7ca

> Console output has no colors in shell (both Git Bash and Cygwin) [regression 
> in Jansi 1.16 / Maven 3.5.1]
> -
>
> Key: MNG-6282
> URL: https://issues.apache.org/jira/browse/MNG-6282
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.2
>Reporter: Dejan Stojadinović
>Assignee: Hervé Boutemy
>Priority: Major
>  Labels: regression, windows
> Fix For: 3.5.3
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, 
> screenshot-4.png, screenshot-5-Cygwin.png, screenshot-6.png, screenshot-7.png
>
>
> See 
> [screenshot|https://issues.apache.org/jira/secure/attachment/12886398/screenshot-1.png]
>  for more details.
> _*Environment:*_
> * Windows 10, 64 bit
> * Oracle Java, version: *1.8.0_144*
> * Git Bash shell (MINGW64), Cygwin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6320) Apparently wrong encoding of non-ascii java class filename in error messages in the maven log

2018-02-10 Thread JIRA


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

Hervé Boutemy commented on MNG-6320:


Jansi upgrade done to benefit from https://github.com/fusesource/jansi/pull/95
https://git-wip-us.apache.org/repos/asf?p=maven.git=commit=916839528cfc26719cb85dc74e3165095447bc97

> Apparently wrong encoding of non-ascii java class filename in error messages 
> in the maven log
> -
>
> Key: MNG-6320
> URL: https://issues.apache.org/jira/browse/MNG-6320
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.2
> Environment: Windows 10
>Reporter: Eugene Pliskin
>Priority: Minor
> Fix For: 3.5.3
>
> Attachments: maven.3.3.9.log, maven.3.5.2.log
>
>
> Attached please find two build logs, one from maven version 3.3.9, and 
> another from maven version 3.5.2. Both log files were made for the same Java 
> project on Windows 10 machine, with "mvn compile > log" command. Java 
> platform default encoding is UTF-8.
> One Java source file contains intentional error, which is reported in lines 
> 433-435 of file "maven.3.3.9.log", and in lines 437-439 of file 
> "maven.3.5.2.log". 
> Class name is non-ascii and version 3.3.9 log appears right. But in version 
> 3.5.2 this same filename appears unreadable in the error message in the maven 
> log.
> Notice that if I view the file "maven.3.5.2.log" with different encoding 
> (cp866), then this error message becomes readable. It looks like this 
> non-ascii filename gets inserted into UTF-8 encoded log file in wrong "cp866" 
> encoding, in maven version 3.5.2.
> Still, version 3.3.9 of maven does the right thing, and the error message is 
> readable in UTF-8 log.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6320) Apparently wrong encoding of non-ascii java class filename in error messages in the maven log

2018-02-10 Thread JIRA


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

Hervé Boutemy closed MNG-6320.
--
   Resolution: Fixed
 Assignee: Hervé Boutemy
Fix Version/s: (was: 3.5.3-candidate)
   3.5.3

> Apparently wrong encoding of non-ascii java class filename in error messages 
> in the maven log
> -
>
> Key: MNG-6320
> URL: https://issues.apache.org/jira/browse/MNG-6320
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.2
> Environment: Windows 10
>Reporter: Eugene Pliskin
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.3
>
> Attachments: maven.3.3.9.log, maven.3.5.2.log
>
>
> Attached please find two build logs, one from maven version 3.3.9, and 
> another from maven version 3.5.2. Both log files were made for the same Java 
> project on Windows 10 machine, with "mvn compile > log" command. Java 
> platform default encoding is UTF-8.
> One Java source file contains intentional error, which is reported in lines 
> 433-435 of file "maven.3.3.9.log", and in lines 437-439 of file 
> "maven.3.5.2.log". 
> Class name is non-ascii and version 3.3.9 log appears right. But in version 
> 3.5.2 this same filename appears unreadable in the error message in the maven 
> log.
> Notice that if I view the file "maven.3.5.2.log" with different encoding 
> (cp866), then this error message becomes readable. It looks like this 
> non-ascii filename gets inserted into UTF-8 encoded log file in wrong "cp866" 
> encoding, in maven version 3.5.2.
> Still, version 3.3.9 of maven does the right thing, and the error message is 
> readable in UTF-8 log.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRELEASE-935) Support for expression in 'version' tag

2018-02-10 Thread Robert Scholte (JIRA)


[ 
https://issues.apache.org/jira/browse/MRELEASE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359384#comment-16359384
 ] 

Robert Scholte commented on MRELEASE-935:
-

This should be implemented as a new 
[VersionPolicy|https://maven.apache.org/maven-release/maven-release-api/apidocs/index.html].
 That's the preferred way to solve this. Something like {{KeepVersionPolicy}} 
(or some better name...)

Also be aware there are more special placeholders, not just ${revision}

> Support for expression in 'version' tag
> ---
>
> Key: MRELEASE-935
> URL: https://issues.apache.org/jira/browse/MRELEASE-935
> Project: Maven Release Plugin
>  Issue Type: New Feature
>Affects Versions: 2.5.3
>Reporter: Andrea Scarpino
>Priority: Critical
> Attachments: support_for_revision_in_version.patch
>
>
> The release plugin doesn't support a version value that points to a property 
> which define the version.
> Everytime I use the plugin, the version in the current POM loose the 
> expression. Maybe it could work using the property to which it points?
> {noformat}
> $ grep '' pom.xml
> ${parent.project.version}
> $ grep '' pom.xml
> 0.0.1-SNAPSHOT
> {noformat}
> Could you please implement this or point me to the files that handle this?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6255) Maven script cannot parse jvm.config with CRLF

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6255:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » master #34

See https://builds.apache.org/job/maven-wip/job/maven/job/master/34/

> Maven script cannot parse jvm.config with CRLF
> --
>
> Key: MNG-6255
> URL: https://issues.apache.org/jira/browse/MNG-6255
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 7 with MINGW64 environment via Git for Windows 
> 0.1.1 including GNU coreutils and bash 4.4.12
>Reporter: Andrew Kennedy
>Priority: Major
> Fix For: 3.5.3-candidate
>
>
> A project with a {{.mvn/jvm.config}} file that has *CRLF* line endings will 
> not parse it correctly. The script uses the {{tr}} command to change *LF* to 
> space, but this leaves *CR* behind. For example, with the {{jvm.config}} file 
> containing the text {{-Xmx1024m -Xms512m}} followed by *CRLF*, the following 
> error message is printed:
> {code}
> $ mvn install
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Invalid initial heap size: -Xms512m
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6320) Apparently wrong encoding of non-ascii java class filename in error messages in the maven log

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6320:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » master #34

See https://builds.apache.org/job/maven-wip/job/maven/job/master/34/

> Apparently wrong encoding of non-ascii java class filename in error messages 
> in the maven log
> -
>
> Key: MNG-6320
> URL: https://issues.apache.org/jira/browse/MNG-6320
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.2
> Environment: Windows 10
>Reporter: Eugene Pliskin
>Priority: Minor
> Fix For: 3.5.3-candidate
>
> Attachments: maven.3.3.9.log, maven.3.5.2.log
>
>
> Attached please find two build logs, one from maven version 3.3.9, and 
> another from maven version 3.5.2. Both log files were made for the same Java 
> project on Windows 10 machine, with "mvn compile > log" command. Java 
> platform default encoding is UTF-8.
> One Java source file contains intentional error, which is reported in lines 
> 433-435 of file "maven.3.3.9.log", and in lines 437-439 of file 
> "maven.3.5.2.log". 
> Class name is non-ascii and version 3.3.9 log appears right. But in version 
> 3.5.2 this same filename appears unreadable in the error message in the maven 
> log.
> Notice that if I view the file "maven.3.5.2.log" with different encoding 
> (cp866), then this error message becomes readable. It looks like this 
> non-ascii filename gets inserted into UTF-8 encoded log file in wrong "cp866" 
> encoding, in maven version 3.5.2.
> Still, version 3.3.9 of maven does the right thing, and the error message is 
> readable in UTF-8 log.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6127:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » master #34

See https://builds.apache.org/job/maven-wip/job/maven/job/master/34/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6282) Console output has no colors in shell (both Git Bash and Cygwin) [regression in Jansi 1.16 / Maven 3.5.1]

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6282:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » master #34

See https://builds.apache.org/job/maven-wip/job/maven/job/master/34/

> Console output has no colors in shell (both Git Bash and Cygwin) [regression 
> in Jansi 1.16 / Maven 3.5.1]
> -
>
> Key: MNG-6282
> URL: https://issues.apache.org/jira/browse/MNG-6282
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.2
>Reporter: Dejan Stojadinović
>Priority: Major
>  Labels: regression, windows
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, 
> screenshot-4.png, screenshot-5-Cygwin.png, screenshot-6.png, screenshot-7.png
>
>
> See 
> [screenshot|https://issues.apache.org/jira/secure/attachment/12886398/screenshot-1.png]
>  for more details.
> _*Environment:*_
> * Windows 10, 64 bit
> * Oracle Java, version: *1.8.0_144*
> * Git Bash shell (MINGW64), Cygwin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6335) Update test framework Mockito from 1.10 to 2.12

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-6335:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » master #34

See https://builds.apache.org/job/maven-wip/job/maven/job/master/34/

> Update test framework Mockito from 1.10 to 2.12
> ---
>
> Key: MNG-6335
> URL: https://issues.apache.org/jira/browse/MNG-6335
> Project: Maven
>  Issue Type: Dependency upgrade
>Affects Versions: 3.5.2
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.5.3-candidate
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-5753) Allow plugin implementors to choose how they want the configuration created for a particular MojoExecution

2018-02-10 Thread Hudson (JIRA)


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

Hudson commented on MNG-5753:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » master #34

See https://builds.apache.org/job/maven-wip/job/maven/job/master/34/

> Allow plugin implementors to choose how they want the configuration created 
> for a particular MojoExecution
> --
>
> Key: MNG-5753
> URL: https://issues.apache.org/jira/browse/MNG-5753
> Project: Maven
>  Issue Type: New Feature
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>Priority: Minor
> Fix For: 3.3.1
>
>
> Provide finer grained control over how a  is processed before 
> handing a final mojo configuration over the Configurator which takes the 
> configuration and applies it to the Mojo. My specific use case is that I want 
> to allow many mojos to be configured clearly by scoping the configuration for 
> a Mojo by Mojo name.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSHADE-272) Option to preserve source timestamps

2018-02-10 Thread Philip Aston (JIRA)

Philip Aston created MSHADE-272:
---

 Summary: Option to preserve source timestamps
 Key: MSHADE-272
 URL: https://issues.apache.org/jira/browse/MSHADE-272
 Project: Maven Shade Plugin
  Issue Type: Wish
Affects Versions: 3.1.0
Reporter: Philip Aston


Please add an option to preserve the source timestamps of files.

Not doing so causes a significant issue when packaging Clojure projects, since 
Clojure uses the timestamps to determine whether to dynamically recompile code. 
See:

- 
[http://mail-archives.apache.org/mod_mbox/maven-users/201310.mbox/%3ccaaub-epb4cdpuymgepu7thsb2bqcujmgmnm1b4h1ucmyr+u...@mail.gmail.com%3E]

- [https://groups.google.com/d/msg/clojure/12BOjg1KsWA/8DIobmb2EwAJ]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1004) Enhance pattern/wildcard capabilities for dependenciesToScan to GAVT

2018-02-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359359#comment-16359359
 ] 

ASF GitHub Bot commented on SUREFIRE-1004:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/173
  
Thx for your work. I will get back to you soon. Right now I am working on
branch SUREFIRE-1463 which contains few fixes. I plan to finish this,
including build script, and then I would push my changes. I will make a
code review in this PR as I do in every other before accepting. Please wait
for me meanwhile.

On Sat, Feb 10, 2018 at 1:42 AM, Bindul Bhowmik 
wrote:

> @Tibor17 
>
> I have reviewed the Maven Coordinates documentation you mentioned, and I
> can switch the order of elements in the parameter easily. However, I think
> I would disagree with requiring the version to be last element in the
> coordinates in this use case. As the functionality stands, the
> dependenciesToScan configuration does not add additional dependencies to
> the test scope of the project, it filters dependencies already added to 
the
> test scope in the project to allow for scanning test classes to run. If
> someone wants to add say a classfier or a type/packaging, requiring them
> them to also mention the version of the dependency would just make
> maintainers life harder by having another location to keep the version of
> the dependency in sync.
>
> As such I propose, we keep the version as optional and support the
> following variations of dependencies to scan:
>
>- groupId:artifactId
>- groupId:artifactId:packaging/type
>- groupId:artifactId:packaging/type::version
>- groupId:artifactId:packaging/type:classifier
>- groupId:artifactId::classifier
>- groupId:artifactId::classifier:version
>- groupId:artifactId:packaging/type:classifier:version
>
> It still maintains the same order of elements as the Maven Coordinates
> documentation in the POM, just makes the version not required to be the
> last element, or rather makes version optional.
>
> Thoughts?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> 
,
> or mute the thread
> 

> .
>



-- 
Cheers
Tibor



> Enhance pattern/wildcard capabilities for dependenciesToScan to GAVT
> 
>
> Key: SUREFIRE-1004
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1004
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.15
>Reporter: Andreas Gudian
>Priority: Major
>
> * Enhance what has been built with SUREFIRE-569 to support patterns as in 
> maven-shade-plugin. Use maven-common-artifact-filters for that.
> * Add/Adapt documentation and examples.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #173: [SUREFIRE-1004] Support full gavtc format for dep...

2018-02-10 Thread Tibor17

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/173
  
Thx for your work. I will get back to you soon. Right now I am working on
branch SUREFIRE-1463 which contains few fixes. I plan to finish this,
including build script, and then I would push my changes. I will make a
code review in this PR as I do in every other before accepting. Please wait
for me meanwhile.

On Sat, Feb 10, 2018 at 1:42 AM, Bindul Bhowmik 
wrote:

> @Tibor17 
>
> I have reviewed the Maven Coordinates documentation you mentioned, and I
> can switch the order of elements in the parameter easily. However, I think
> I would disagree with requiring the version to be last element in the
> coordinates in this use case. As the functionality stands, the
> dependenciesToScan configuration does not add additional dependencies to
> the test scope of the project, it filters dependencies already added to 
the
> test scope in the project to allow for scanning test classes to run. If
> someone wants to add say a classfier or a type/packaging, requiring them
> them to also mention the version of the dependency would just make
> maintainers life harder by having another location to keep the version of
> the dependency in sync.
>
> As such I propose, we keep the version as optional and support the
> following variations of dependencies to scan:
>
>- groupId:artifactId
>- groupId:artifactId:packaging/type
>- groupId:artifactId:packaging/type::version
>- groupId:artifactId:packaging/type:classifier
>- groupId:artifactId::classifier
>- groupId:artifactId::classifier:version
>- groupId:artifactId:packaging/type:classifier:version
>
> It still maintains the same order of elements as the Maven Coordinates
> documentation in the POM, just makes the version not required to be the
> last element, or rather makes version optional.
>
> Thoughts?
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> 
,
> or mute the thread
> 

> .
>



-- 
Cheers
Tibor



---

[jira] [Commented] (SUREFIRE-1475) PpidChecker.windows() assumes wmic is on the path

2018-02-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359356#comment-16359356
 ] 

ASF GitHub Bot commented on SUREFIRE-1475:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/174
  
Logging errors can be added to the dump file, but right now please add the 
Microsoft link, as you said 'yes'.


> PpidChecker.windows() assumes wmic is on the path
> -
>
> Key: SUREFIRE-1475
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1475
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows
>Reporter: Anders Wallgren
>Priority: Major
>
>  
> {{PpidChecker.windows()}} assumes that the wmic executable is on the path, 
> which isn't always the case.
> A better approach would probably be to use 
> {{%SystemRoot%\System32\Wbem\wmic}}.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #174: https://issues.apache.org/jira/browse/SUREFIRE-14...

2018-02-10 Thread Tibor17

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/174
  
Logging errors can be added to the dump file, but right now please add the 
Microsoft link, as you said 'yes'.


---

69 matches

Mail list logo