[jira] [Updated] (MJAVADOC-520) Upgrade plexus-utils/qdox/plexus-archiver/

[JIRA]

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

Hervé Boutemy updated MJAVADOC-520:
---
Description: 
* plexus-utils to 3.1.0
* qdox to 2.0-M8
* plexus-archiver 3.5, 3.6.0
* plexus-utils-3.1.0
* maven-archiver 3.2.0
* plexus-interactivity-api 1.0-alpha-6

  was:
* plexus-utils to 3.1.0
* qdox to 2.0-M8
* plexus-archiver 3.5
* plexus-utils-3.1.0
* maven-archiver 3.2.0
* plexus-interactivity-api 1.0-alpha-6


> Upgrade plexus-utils/qdox/plexus-archiver/
> --
>
> Key: MJAVADOC-520
> URL: https://issues.apache.org/jira/browse/MJAVADOC-520
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> * plexus-utils to 3.1.0
> * qdox to 2.0-M8
> * plexus-archiver 3.5, 3.6.0
> * plexus-utils-3.1.0
> * maven-archiver 3.2.0
> * plexus-interactivity-api 1.0-alpha-6



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

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

hboutemy commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389396383
 
 
   in fact, the more I think to it, the more I'm convinced we should just 
update "\" to "\" because we can't create something 
really accurate
   and end user just use their keyboard to scroll up: what is important is that 
the new "-rf \" is easy to get and copy
   and it's even easier if we don't try to expand "\"


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[GitHub] hboutemy commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

hboutemy commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389396383
 
 
   in fact, the more I think to it, the more I'm convinced we should just 
update "" to "" because we can't create something 
really accurate
   and end user just use their keyboard to scroll up: what is important is that 
the new "-rf " is easy to get and copy
   and it's even easier if we don't try to expand ""


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] hboutemy commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

hboutemy commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389396383
 
 
   in fact, the more I think to it, the more I'm convinced we should just 
update "\" to "\" because we can't create something 
really accurate
   and end user just use their keyboard to scroll up: what is important is that 
the new "-rf \" is easy to get and copy
   and it's even easier if we don't try to expand "\"


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

hboutemy commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389396383
 
 
   in fact, the more I think to it, the more I'm convinced we should just 
update "" to "" because we can't create something 
really accurate
   and end user just use their keyboard to scroll up: what is important is that 
the new "-rf " is easy to get and copy
   and it's even easier if we don't try to expand ""


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[jira] [Comment Edited] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone

[Marcelo Riss (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476702#comment-16476702
 ] 

Marcelo Riss edited comment on MCHANGES-388 at 5/16/18 1:29 AM:


I already have a solution at this commit at a fork in my github account: 
[https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584].
 Just ignore the changes at the pom.xml file, which I needed to change in order 
to make an specific deployment for testing. I also haven't implemented any 
integration test.


was (Author: mriss):
I already have a solution at this commit at a fork in my github account: 
[https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584].
 Just ignore the changes at the pom.xml file, which I need to change to do an 
specific deployment for testing. I also haven't implemented any integration 
test.

> Add option to include issues using the -SNAPSHOT suffix for version/milestone
> -
>
> Key: MCHANGES-388
> URL: https://issues.apache.org/jira/browse/MCHANGES-388
> Project: Maven Changes Plugin
>  Issue Type: Wish
>  Components: github
>Reporter: Marcelo Riss
>Priority: Minor
> Attachments: pom.xml
>
>
> I have a use case where the version id/name at the issue tracking system 
> (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue 
> tracking system and the parameter 
> *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]*
>  to true, the -SNAPSHOT suffix is removed when filtering the issues. My 
> suggestion is to add a configuration parameter allowing to consider or not 
> the -SNAPSHOT suffix as the version id/name when searching for issues. 



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

[jira] [Comment Edited] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone

[Marcelo Riss (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476702#comment-16476702
 ] 

Marcelo Riss edited comment on MCHANGES-388 at 5/16/18 1:28 AM:


I already have a solution at this commit at a fork in my github account: 
[https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584].
 Just ignore the changes at the pom.xml file, which I need to change to do an 
specific deployment for testing. I also haven't implemented any integration 
test.


was (Author: mriss):
I already have a solution at this commit at a fork in my github account: 
[https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584.]
 Just ignore the changes at the pom.xml file, which I need to change to do an 
specific deployment for testing. I also haven't implemented any integration 
test.

> Add option to include issues using the -SNAPSHOT suffix for version/milestone
> -
>
> Key: MCHANGES-388
> URL: https://issues.apache.org/jira/browse/MCHANGES-388
> Project: Maven Changes Plugin
>  Issue Type: Wish
>  Components: github
>Reporter: Marcelo Riss
>Priority: Minor
> Attachments: pom.xml
>
>
> I have a use case where the version id/name at the issue tracking system 
> (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue 
> tracking system and the parameter 
> *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]*
>  to true, the -SNAPSHOT suffix is removed when filtering the issues. My 
> suggestion is to add a configuration parameter allowing to consider or not 
> the -SNAPSHOT suffix as the version id/name when searching for issues. 



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

[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone

[Marcelo Riss (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476702#comment-16476702
 ] 

Marcelo Riss commented on MCHANGES-388:
---

I already have a solution at this commit at a fork in my github account: 
[https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584.]
 Just ignore the changes at the pom.xml file, which I need to change to do an 
specific deployment for testing. I also haven't implemented any integration 
test.

> Add option to include issues using the -SNAPSHOT suffix for version/milestone
> -
>
> Key: MCHANGES-388
> URL: https://issues.apache.org/jira/browse/MCHANGES-388
> Project: Maven Changes Plugin
>  Issue Type: Wish
>  Components: github
>Reporter: Marcelo Riss
>Priority: Minor
> Attachments: pom.xml
>
>
> I have a use case where the version id/name at the issue tracking system 
> (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue 
> tracking system and the parameter 
> *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]*
>  to true, the -SNAPSHOT suffix is removed when filtering the issues. My 
> suggestion is to add a configuration parameter allowing to consider or not 
> the -SNAPSHOT suffix as the version id/name when searching for issues. 



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

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389346403
 
 
   I updated commit to use `StringUtils` from plexus utils available in imports.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[GitHub] splatch commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389346403
 
 
   I updated to use `StringUtils` from plexus utils available in imports.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] splatch commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389346403
 
 
   I updated commit to use `StringUtils` from plexus utils available in imports.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389346403
 
 
   I updated to use `StringUtils` from plexus utils available in imports.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389343208
 
 
   @hboutemy not really, it just includes goals and -rf flag. No other params 
are added. Shall we include them too?
   There are several other switches such -o, -nsu and -P which can be added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389343208
 
 
   @hboutemy not really, it just includes goals and -rf flag. No other params 
are added. Shall we include them too?
   There are several other switches such -o, -nsu and -P to name few which can 
be added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[GitHub] splatch commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389343208
 
 
   @hboutemy not really, it just includes goals and -rf flag. No other params 
are added. Shall we include them too?
   There are several other switches such -o, -nsu and -P to name few which can 
be added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] splatch commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389343208
 
 
   @hboutemy not really, it just includes goals and -rf flag. No other params 
are added. Shall we include them too?
   There are several other switches such -o, -nsu and -P which can be added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389343208
 
 
   @hboutemy not really, it just includes goals and -rf flag. No other params 
are added. Shall we include them too?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[GitHub] splatch commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

splatch commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389343208
 
 
   @hboutemy not really, it just includes goals and -rf flag. No other params 
are added. Shall we include them too?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MNG-6411) Improve readability of project list returned when resume from flag is invalid

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6411:
-

splatch commented on a change in pull request #164: [MNG-6411] Improve 
readability of project list for resume option.
URL: https://github.com/apache/maven/pull/164#discussion_r188462651
 
 

 ##
 File path: 
maven-core/src/main/java/org/apache/maven/graph/DefaultGraphBuilder.java
 ##
 @@ -311,13 +311,29 @@ else if ( StringUtils.isNotEmpty( 
request.getMakeBehavior() ) )
 if ( !resumed )
 {
 throw new MavenExecutionException( "Could not find project to 
resume reactor build from: " + selector
-+ " vs " + projects, request.getPom() );
++ " vs " + formatProjects( projects ), request.getPom() );
 }
 }
 
 return result;
 }
 
+private String formatProjects( List projects )
+{
+StringBuilder projectNames = new StringBuilder();
+for ( int index = 0, size = projects.size(); index < size; index++ )
+{
+MavenProject project = projects.get( index );
 
 Review comment:
   @slachiewicz @michael-o I checked it and `StringUtils` would allow me to 
glue collection easily but still I need to custom formatting of elements. Whole 
idea is to return proper input for `-rf` option. 
   
   For now I switch to iterator without `StringUtils`.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve readability of project list returned when resume from flag is invalid
> -
>
> Key: MNG-6411
> URL: https://issues.apache.org/jira/browse/MNG-6411
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.5.3
>Reporter: Łukasz Dywicki
>Priority: Minor
> Fix For: 3.5.4-candidate
>
>
> When value passed for {{-rf}} option is invalid a full list of details of all 
> projects in build is returned.
> This list contains too much information. For every project it includes 
> groupId, artifactId, version and pom location. While it is useful for 
> debugging purposes many, if not most, developers are interested in specific 
> coordinate (groupId:artifactId) which should be passed to next execution, and 
> which is valid {{-rf}} optiona value.
> Note tat below outputs contain new lines for ease of read. This could be also 
> added to exception message to make it more readable.
> Assuming, that I've passed -rf :x Current output in case of failure:
> {noformat}
> ERROR] Could not find project to resume reactor build from: :x vs [
>   MavenProject: com.example:foobar:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/pom.xml,
>   MavenProject: com.example.foobar:parent:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/parent/pom.xml,
>   MavenProject: com.example.foobar:api:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/api/pom.xml,
>   MavenProject: com.example.foobar:model:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/model/pom.xml,
>   MavenProject: com.example.foobar:csv:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/csv/pom.xml,
>   MavenProject: com.example.foobar.csv:model:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/csv/model/pom.xml,
>   MavenProject: com.example.foobar.csv:api:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/csv/api/pom.xml,
>   MavenProject: com.example.foobar:json:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/json/pom.xml,
>   MavenProject: com.example.foobar.json:model:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/json/model/pom.xml,
>   MavenProject: com.example.foobar.json:api:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/json/api/pom.xml,
>   MavenProject: com.example.foobar.json:core:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/json/core/pom.xml,
>   MavenProject: com.example.foobar:fax:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/fax/pom.xml,
>   MavenProject: com.example.foobar.fax:api:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/fax/api/pom.xml,
>   MavenProject: com.example.foobar.fax:model:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/fax/model/pom.xml,
>   MavenProject: com.example.foobar.fax:web:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/fax/web/pom.xml,
>   MavenProject: com.example.foobar.fax.web:api:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/fax/web/api/pom.xml,
>   MavenProject: com.example.foobar.fax.web:core:1.0.0-SNAPSHOT @ 
> ~/sources/foobar/fax/web/core/pom.xml] -> [Help 1]
> {noformat}
> Additional information about pom locations is irrelevant from message point 
> of view, because valid input for -rf option is presented below:
> {noformat}

[GitHub] splatch commented on a change in pull request #164: [MNG-6411] Improve readability of project list for resume option.

[GitBox]

splatch commented on a change in pull request #164: [MNG-6411] Improve 
readability of project list for resume option.
URL: https://github.com/apache/maven/pull/164#discussion_r188462651
 
 

 ##
 File path: 
maven-core/src/main/java/org/apache/maven/graph/DefaultGraphBuilder.java
 ##
 @@ -311,13 +311,29 @@ else if ( StringUtils.isNotEmpty( 
request.getMakeBehavior() ) )
 if ( !resumed )
 {
 throw new MavenExecutionException( "Could not find project to 
resume reactor build from: " + selector
-+ " vs " + projects, request.getPom() );
++ " vs " + formatProjects( projects ), request.getPom() );
 }
 }
 
 return result;
 }
 
+private String formatProjects( List projects )
+{
+StringBuilder projectNames = new StringBuilder();
+for ( int index = 0, size = projects.size(); index < size; index++ )
+{
+MavenProject project = projects.get( index );
 
 Review comment:
   @slachiewicz @michael-o I checked it and `StringUtils` would allow me to 
glue collection easily but still I need to custom formatting of elements. Whole 
idea is to return proper input for `-rf` option. 
   
   For now I switch to iterator without `StringUtils`.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (SCM-886) Tests with checkin rely on global git config

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SCM-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476540#comment-16476540
 ] 

ASF GitHub Bot commented on SCM-886:


asfgit closed pull request #73: [SCM-886] introduce helper class to configure 
git commit user
URL: https://github.com/apache/maven-scm/pull/73
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
index 5781edc0e..99011dbd0 100644
--- 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
+++ 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
@@ -25,6 +25,7 @@
 import org.apache.maven.scm.command.add.AddScmResult;
 import org.apache.maven.scm.command.checkin.CheckInScmResult;
 import org.apache.maven.scm.command.checkout.CheckOutScmResult;
+import org.apache.maven.scm.provider.git.GitScmTestUtils;
 import org.apache.maven.scm.repository.ScmRepository;
 import org.codehaus.plexus.util.FileUtils;
 
@@ -61,7 +62,12 @@ public void testCheckinNoBranch()
 FileUtils.copyDirectoryStructure( repo_orig, repo );
 
 ScmRepository scmRepository = getScmManager().makeScmRepository( 
"scm:git:file:///" + repo.getAbsolutePath() );
+
 CheckOutScmResult checkOutScmResult = checkoutRepo( scmRepository );
+
+// Add a default user to the config
+GitScmTestUtils.setDefaultUser(workingDirectory);
+
 assertEquals( 0, checkOutScmResult.getCheckedOutFiles().size() );
 
 File f = new File( workingDirectory.getAbsolutePath() + File.separator 
+ "pom.xml" );
diff --git 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
index 50093dbd5..a34796a55 100644
--- 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
+++ 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
@@ -98,6 +98,9 @@ public void testCheckinAfterRename() throws Exception {
 ScmRepository scmRepository = getScmManager().makeScmRepository( 
"scm:git:file://" + repo.getAbsolutePath() );
 checkoutRepoInto(checkedOutRepo, scmRepository);
 
+// Add a default user to the config
+GitScmTestUtils.setDefaultUser(checkedOutRepo);
+
 // Creating foo/bar/wine.xml
 File fooDir = new File( checkedOutRepo.getAbsolutePath() + 
File.separator + "foo" );
 fooDir.mkdir();
diff --git 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
index 4ba272bf6..c62458fd7 100644
--- 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
+++ 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
@@ -29,6 +29,7 @@
 import org.codehaus.plexus.util.cli.Commandline;
 
 import java.io.File;
+import java.io.FileWriter;
 import java.io.IOException;
 
 /**
@@ -136,4 +137,38 @@ public static void deleteAllDirectories( File 
startDirectory, String pattern )
 }
 }
 
+public static void setDefaultUser( File repositoryRootFile )
+{
+File gitConfigFile = new File( new File( repositoryRootFile, ".git" ), 
"config" );
+
+FileWriter fw = null;
+try
+{
+fw = new FileWriter( gitConfigFile , true );
+fw.append( "[user]\n" );
+fw.append( "\tname = John Doe\n" );
+fw.append( "\temail = john@nowhere.com\n" );
+fw.flush();
+   

[jira] [Closed] (SCM-886) Tests with checkin rely on global git config

[Michael Osipov (JIRA)]

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

Michael Osipov closed SCM-886.
--
Resolution: Fixed

Fixed with 
[7719468daf9432e88c34005ca6054f6c07d3f4b3|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=7719468daf9432e88c34005ca6054f6c07d3f4b3].

> Tests with checkin rely on global git config
> 
>
> Key: SCM-886
> URL: https://issues.apache.org/jira/browse/SCM-886
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Matthieu Brouillard
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> Inside maven-scm-provider-gitexe project, the two following tests 
> `GitCheckInCommandNoBranchTest.testCheckinNoBranch` and 
> `GitCheckInCommandTest.testCheckinAfterRename` expect a global user.name and 
> user.email to be set.
> On installations where .gitconfig contains the following:
> {{[user]}}
> {{useConfigOnly = true}}
> The tests will fail.
> It would be better after repository creation to configure a user name & email 
> at project level.



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

[GitHub] asfgit closed pull request #73: [SCM-886] introduce helper class to configure git commit user

[GitBox]

asfgit closed pull request #73: [SCM-886] introduce helper class to configure 
git commit user
URL: https://github.com/apache/maven-scm/pull/73
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
index 5781edc0e..99011dbd0 100644
--- 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
+++ 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandNoBranchTest.java
@@ -25,6 +25,7 @@
 import org.apache.maven.scm.command.add.AddScmResult;
 import org.apache.maven.scm.command.checkin.CheckInScmResult;
 import org.apache.maven.scm.command.checkout.CheckOutScmResult;
+import org.apache.maven.scm.provider.git.GitScmTestUtils;
 import org.apache.maven.scm.repository.ScmRepository;
 import org.codehaus.plexus.util.FileUtils;
 
@@ -61,7 +62,12 @@ public void testCheckinNoBranch()
 FileUtils.copyDirectoryStructure( repo_orig, repo );
 
 ScmRepository scmRepository = getScmManager().makeScmRepository( 
"scm:git:file:///" + repo.getAbsolutePath() );
+
 CheckOutScmResult checkOutScmResult = checkoutRepo( scmRepository );
+
+// Add a default user to the config
+GitScmTestUtils.setDefaultUser(workingDirectory);
+
 assertEquals( 0, checkOutScmResult.getCheckedOutFiles().size() );
 
 File f = new File( workingDirectory.getAbsolutePath() + File.separator 
+ "pom.xml" );
diff --git 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
index 50093dbd5..a34796a55 100644
--- 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
+++ 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommandTest.java
@@ -98,6 +98,9 @@ public void testCheckinAfterRename() throws Exception {
 ScmRepository scmRepository = getScmManager().makeScmRepository( 
"scm:git:file://" + repo.getAbsolutePath() );
 checkoutRepoInto(checkedOutRepo, scmRepository);
 
+// Add a default user to the config
+GitScmTestUtils.setDefaultUser(checkedOutRepo);
+
 // Creating foo/bar/wine.xml
 File fooDir = new File( checkedOutRepo.getAbsolutePath() + 
File.separator + "foo" );
 fooDir.mkdir();
diff --git 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
index 4ba272bf6..c62458fd7 100644
--- 
a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
+++ 
b/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gittest/src/main/java/org/apache/maven/scm/provider/git/GitScmTestUtils.java
@@ -29,6 +29,7 @@
 import org.codehaus.plexus.util.cli.Commandline;
 
 import java.io.File;
+import java.io.FileWriter;
 import java.io.IOException;
 
 /**
@@ -136,4 +137,38 @@ public static void deleteAllDirectories( File 
startDirectory, String pattern )
 }
 }
 
+public static void setDefaultUser( File repositoryRootFile )
+{
+File gitConfigFile = new File( new File( repositoryRootFile, ".git" ), 
"config" );
+
+FileWriter fw = null;
+try
+{
+fw = new FileWriter( gitConfigFile , true );
+fw.append( "[user]\n" );
+fw.append( "\tname = John Doe\n" );
+fw.append( "\temail = john@nowhere.com\n" );
+fw.flush();
+fw.close();
+}
+catch ( IOException e )
+{
+System.err.println( "cannot setup a default user for tests purpose 
inside " + gitConfigFile );
+e.printStackTrace();
+}

[jira] [Issue Comment Deleted] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[JIRA]

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

Hervé Boutemy updated MNG-6028:
---
Comment: was deleted

(was: question: if the initial command contained something like 
"-Dparam=value", does the generated command contain it?)

> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[JIRA]

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

Hervé Boutemy commented on MNG-6028:


question: if the initial command contained something like "-Dparam=value", does 
the generated command contain it?

> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MNG-6028:
-

hboutemy commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389318965
 
 
   question: if the initial command contained something like "-Dparam=value", 
does the generated command contain it?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a reactor build fails maven should include current goals in resume 
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn  -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were 
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build 
> with the command
> [ERROR]   mvn clean install -rf :module-a{noformat}



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

[GitHub] hboutemy commented on issue #165: [MNG-6028] Include current goals in resume suggestion

[GitBox]

hboutemy commented on issue #165: [MNG-6028] Include current goals in resume 
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-389318965
 
 
   question: if the initial command contained something like "-Dparam=value", 
does the generated command contain it?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (MDEP-613) Analyze failed: Unsupported class file major version 55

[Mincong Huang (JIRA)]

Mincong Huang created MDEP-613:
--

 Summary: Analyze failed: Unsupported class file major version 55
 Key: MDEP-613
 URL: https://issues.apache.org/jira/browse/MDEP-613
 Project: Maven Dependency Plugin
  Issue Type: Bug
  Components: analyze
Affects Versions: 3.1.0
Reporter: Mincong Huang
 Attachments: log.txt

Class file of major version 55 (Java 11) is not yet supported by Maven 
Dependency Plugin. So when running command {{mvn dependency:analysis}} on 
classes created by Java 11, il failed. See {{log.txt}} for the full log trace.

This is caused by ASM, which does not support major version 55 (Java 11) yet. 
However, their HEAD contains already the solution, so using the SNAPSHOT 
version will work. This support will be included in the next release 6.2.



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

[jira] [Assigned] (SCM-886) Tests with checkin rely on global git config

[Michael Osipov (JIRA)]

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

Michael Osipov reassigned SCM-886:
--

Assignee: Michael Osipov

> Tests with checkin rely on global git config
> 
>
> Key: SCM-886
> URL: https://issues.apache.org/jira/browse/SCM-886
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Matthieu Brouillard
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> Inside maven-scm-provider-gitexe project, the two following tests 
> `GitCheckInCommandNoBranchTest.testCheckinNoBranch` and 
> `GitCheckInCommandTest.testCheckinAfterRename` expect a global user.name and 
> user.email to be set.
> On installations where .gitconfig contains the following:
> {{[user]}}
> {{useConfigOnly = true}}
> The tests will fail.
> It would be better after repository creation to configure a user name & email 
> at project level.



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

[jira] [Updated] (SCM-886) Tests with checkin rely on global git config

[Michael Osipov (JIRA)]

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

Michael Osipov updated SCM-886:
---
Fix Version/s: 1.9.6

> Tests with checkin rely on global git config
> 
>
> Key: SCM-886
> URL: https://issues.apache.org/jira/browse/SCM-886
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Matthieu Brouillard
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> Inside maven-scm-provider-gitexe project, the two following tests 
> `GitCheckInCommandNoBranchTest.testCheckinNoBranch` and 
> `GitCheckInCommandTest.testCheckinAfterRename` expect a global user.name and 
> user.email to be set.
> On installations where .gitconfig contains the following:
> {{[user]}}
> {{useConfigOnly = true}}
> The tests will fail.
> It would be better after repository creation to configure a user name & email 
> at project level.



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

[jira] [Closed] (SCM-888) Changelog generation fails on Windows with Mercurial SCM

[Michael Osipov (JIRA)]

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

Michael Osipov closed SCM-888.
--
Resolution: Fixed

Fixed with 
[e25e6bf3d9da6ba015eee274422fd5a0b864e481|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=e25e6bf3d9da6ba015eee274422fd5a0b864e481].

> Changelog generation fails on Windows with Mercurial SCM
> 
>
> Key: SCM-888
> URL: https://issues.apache.org/jira/browse/SCM-888
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-mercurial (hg)
>Affects Versions: 1.9.5
> Environment: Windows
>Reporter: Tim Vail
>Assignee: Michael Osipov
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.9.6
>
>
> When you do 'mvn scm:changelog' on Windows with a project that is backed by 
> mercurial it only finds revision -1 because literal newline in the Mercurial 
> template is terminating the command for cmd.exe.
> There is a fix for this in my github pull request:
> https://github.com/apache/maven-scm/pull/43



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

[GitHub] asfgit closed pull request #43: Fix for Windows by changing literal newlines to backslash followed by n.

[GitBox]

asfgit closed pull request #43: Fix for Windows by changing literal newlines to 
backslash followed by n.
URL: https://github.com/apache/maven-scm/pull/43
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/maven-scm-providers/maven-scm-provider-hg/src/main/java/org/apache/maven/scm/provider/hg/command/HgCommandConstants.java
 
b/maven-scm-providers/maven-scm-provider-hg/src/main/java/org/apache/maven/scm/provider/hg/command/HgCommandConstants.java
index 9029856ed..e98f283fc 100644
--- 
a/maven-scm-providers/maven-scm-provider-hg/src/main/java/org/apache/maven/scm/provider/hg/command/HgCommandConstants.java
+++ 
b/maven-scm-providers/maven-scm-provider-hg/src/main/java/org/apache/maven/scm/provider/hg/command/HgCommandConstants.java
@@ -164,7 +164,6 @@ private HgCommandConstants()
  * verbose format for log command.
  */
 public static final String TEMPLATE_FORMAT =
-"changeset:   {rev}:{node|short}\nbranch:  {branch}\nuser:
{author}\ndate:{date|isodatesec}"
-+ "\ntag: {tags}\nfiles:   
{files}\ndescription:\n{desc}\n";
-
+"changeset:   {rev}:{node|short}\\nbranch:  {branch}\\nuser:   
 {author}\\n" 
++ "date:{date|isodatesec}\\ntag: {tags}\\nfiles:   
{files}\\ndescription:\\n{desc}\\n";
 }


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Updated] (MSHARED-718) Upgrade asm to most recent version 6.1.1

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MSHARED-718:

Issue Type: Dependency upgrade  (was: Task)

> Upgrade asm to most recent version 6.1.1
> 
>
> Key: MSHARED-718
> URL: https://issues.apache.org/jira/browse/MSHARED-718
> Project: Maven Shared Components
>  Issue Type: Dependency upgrade
>Affects Versions: maven-dependency-analyzer-1.9
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-dependency-analyzer-1.10
>
>
> Based on the upgrade of asm to 6.1.1 it is also required to upgrade 
> commons-lang3 to version 3.7 which requires a JDK minimum upgrade to 7.



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

[jira] [Updated] (SCM-888) Changelog generation fails on Windows with Mercurial SCM

[Michael Osipov (JIRA)]

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

Michael Osipov updated SCM-888:
---
Fix Version/s: 1.9.6

> Changelog generation fails on Windows with Mercurial SCM
> 
>
> Key: SCM-888
> URL: https://issues.apache.org/jira/browse/SCM-888
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-mercurial (hg)
>Affects Versions: 1.9.5
> Environment: Windows
>Reporter: Tim Vail
>Assignee: Michael Osipov
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.9.6
>
>
> When you do 'mvn scm:changelog' on Windows with a project that is backed by 
> mercurial it only finds revision -1 because literal newline in the Mercurial 
> template is terminating the command for cmd.exe.
> There is a fix for this in my github pull request:
> https://github.com/apache/maven-scm/pull/43



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

[jira] [Assigned] (SCM-888) Changelog generation fails on Windows with Mercurial SCM

[Michael Osipov (JIRA)]

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

Michael Osipov reassigned SCM-888:
--

Assignee: Michael Osipov

> Changelog generation fails on Windows with Mercurial SCM
> 
>
> Key: SCM-888
> URL: https://issues.apache.org/jira/browse/SCM-888
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-mercurial (hg)
>Affects Versions: 1.9.5
> Environment: Windows
>Reporter: Tim Vail
>Assignee: Michael Osipov
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.9.6
>
>
> When you do 'mvn scm:changelog' on Windows with a project that is backed by 
> mercurial it only finds revision -1 because literal newline in the Mercurial 
> template is terminating the command for cmd.exe.
> There is a fix for this in my github pull request:
> https://github.com/apache/maven-scm/pull/43



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

[jira] [Commented] (SCM-888) Changelog generation fails on Windows with Mercurial SCM

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/SCM-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476335#comment-16476335
 ] 

Michael Osipov commented on SCM-888:


I like the label you added to this ticket.

> Changelog generation fails on Windows with Mercurial SCM
> 
>
> Key: SCM-888
> URL: https://issues.apache.org/jira/browse/SCM-888
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-mercurial (hg)
>Affects Versions: 1.9.5
> Environment: Windows
>Reporter: Tim Vail
>Assignee: Michael Osipov
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.9.6
>
>
> When you do 'mvn scm:changelog' on Windows with a project that is backed by 
> mercurial it only finds revision -1 because literal newline in the Mercurial 
> template is terminating the command for cmd.exe.
> There is a fix for this in my github pull request:
> https://github.com/apache/maven-scm/pull/43



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

[jira] [Commented] (MASSEMBLY-874) maven-assembly plugin always downloads dependencies from net

[Donatien RIVIERE (JIRA)]

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

Donatien RIVIERE commented on MASSEMBLY-874:


Same issue here, when using a  tag in assembly descriptor.

> maven-assembly plugin always downloads dependencies from net
> 
>
> Key: MASSEMBLY-874
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-874
> Project: Maven Assembly Plugin
>  Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Multi-Module build
>Reporter: Roland Schäuble
>Priority: Major
> Attachments: make.log
>
>
> The maven-assembly-plugin always loads it own dependencies from the internet, 
> although the required dependencies are available in the local m2 repositiory. 
> The local repository is updated with the dependencies but during the next 
> build, the files are downloaded from the internet again instead of getting 
> them from the local repo.
> In the attached log, near the end, the unnecessary downloads begin with 
> "Downloading from central: 
> [https://repo.maven.apache.org/maven2/com/lowagie/itext/2.1.7.js5/itext-2.1.7.js5.pom.;|https://repo.maven.apache.org/maven2/com/lowagie/itext/2.1.7.js5/itext-2.1.7.js5.pom.]
> The files are definitely available in my local repository under 
> ~/.m2/repository/com/...



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

[jira] [Commented] (SUREFIRE-1330) JUnit 5 surefire-provider code donation

[Tibor Digana (JIRA)]

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

Tibor Digana commented on SUREFIRE-1330:


I was fixing Surefire1295AttributeJvmCrashesToTestsIT in past. I have no
idea why the text is not in the logs.
Start the build again.

On Tue, May 15, 2018 at 9:19 AM, Christian Stein (JIRA) 



> JUnit 5 surefire-provider code donation
> ---
>
> Key: SUREFIRE-1330
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1330
> Project: Maven Surefire
>  Issue Type: New Feature
>Reporter: Benedikt Ritter
>Assignee: Tibor Digana
>Priority: Major
>  Labels: junit5
> Fix For: 2.22.0
>
> Attachments: junit-platform-surefire-provider.zip
>
>
> The JUnit team wishes to contribute their surefire provider implementation 
> for JUnit 5 to the Maven team.
> The code is currently located at GitHub: 
> https://github.com/junit-team/junit5/tree/master/junit-platform-surefire-provider
> They have recently relicensed the code under terms of Apache License 2.0: 
> https://github.com/junit-team/junit5/issues/541



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

[jira] [Commented] (MCOMPILER-342) Unsupported class file major version 55

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475881#comment-16475881
 ] 

Michael Osipov commented on MCOMPILER-342:
--

We will leave this open until upstream is resolved.

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
> Attachments: log.txt
>
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Created] (MASSEMBLY-886) Support for mappers in assembly

[JIRA]

Arnaud Bourrée created MASSEMBLY-886:


 Summary: Support for mappers in assembly
 Key: MASSEMBLY-886
 URL: https://issues.apache.org/jira/browse/MASSEMBLY-886
 Project: Maven Assembly Plugin
  Issue Type: Improvement
Affects Versions: 3.1.0
Reporter: Arnaud Bourrée


Share Maven component 
[file-management|http://maven.apache.org/shared/file-management/] supports 
[mapper in fileSet|http://maven.apache.org/shared/file-management/fileset.html].

It will be great that assembly file format support it too.





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

[jira] [Comment Edited] (SUREFIRE-1520) ClassNotFoundException with forkCount>1 and junit5

[JIRA]

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

Jens Teglhus Møller edited comment on SUREFIRE-1520 at 5/15/18 1:32 PM:


I see the same error when using 
{code:xml}
  false
{code}
I was able to work around it by adding a regular project dependency:
{code:xml}


  org.apache.maven.surefire
  surefire-logger-api
  ${surefire.version}
  test

{code}
It did not work when I added the dependency to the surefire plugin.


was (Author: djarnis73):
I see the same error when using 
{code:xml}
  false
{code}
I was able to work around it by adding a regular project dependency:
{code:xml}


  org.apache.maven.surefire
  surefire-logger-api
  ${surefire.version}
  test

{code}

> ClassNotFoundException with forkCount>1 and junit5
> --
>
> Key: SUREFIRE-1520
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1520
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 2.21.0
>Reporter: Stefan Küttner
>Priority: Major
>
> maven-version: 3.2.5 / 3.3.9
> OS: Windows 7
> Java 8 (compiler level & runtime)
> {code:xml|title=pom.xml (effective-pom)|collapse=true}
>   
> maven-surefire-plugin
> 2.21.0
> 
>   
> default-test
> test
> 
>   test
> 
> 
>   
> **/*IntegrationTest.java
>   
>   false
>   2
>   true
>   
> 3600
>   
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
>   alphabetical
>   
> **/*Test.java
>   
> 
>   
> 
> 
>   
> org.junit.platform
> junit-platform-surefire-provider
> 1.2.0
> compile
>   
>   
> org.junit.vintage
> junit-vintage-engine
> 5.2.0
> compile
>   
>   
> org.junit.jupiter
> junit-jupiter-engine
> 5.2.0
> compile
>   
> 
> 
>   2
>   true
>   3600
>   
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
>   alphabetical
>   false
>   
> **/*Test.java
>   
>   
> **/*PerfTest.java
> **/*IntegrationTest.java
>   
> 
>   
> {code}
> result is 
> {code:java|title=java.lang.ClassNotFoundException: 
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger|collapse=true}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test (default-test) on 
> project mts.ctsm: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed: 
> java.lang.ClassNotFoundException: 
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test 
> (default-test) on project mts.ctsm: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed: 
> java.lang.ClassNotFoundException: 
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> 

[jira] [Commented] (SUREFIRE-1520) ClassNotFoundException with forkCount>1 and junit5

[JIRA]

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

Jens Teglhus Møller commented on SUREFIRE-1520:
---

I see the same error when using 
{code:xml}
  false
{code}
I was able to work around it by adding a regular project dependency:
{code:xml}


  org.apache.maven.surefire
  surefire-logger-api
  ${surefire.version}
  test

{code}

> ClassNotFoundException with forkCount>1 and junit5
> --
>
> Key: SUREFIRE-1520
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1520
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 2.21.0
>Reporter: Stefan Küttner
>Priority: Major
>
> maven-version: 3.2.5 / 3.3.9
> OS: Windows 7
> Java 8 (compiler level & runtime)
> {code:xml|title=pom.xml (effective-pom)|collapse=true}
>   
> maven-surefire-plugin
> 2.21.0
> 
>   
> default-test
> test
> 
>   test
> 
> 
>   
> **/*IntegrationTest.java
>   
>   false
>   2
>   true
>   
> 3600
>   
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
>   alphabetical
>   
> **/*Test.java
>   
> 
>   
> 
> 
>   
> org.junit.platform
> junit-platform-surefire-provider
> 1.2.0
> compile
>   
>   
> org.junit.vintage
> junit-vintage-engine
> 5.2.0
> compile
>   
>   
> org.junit.jupiter
> junit-jupiter-engine
> 5.2.0
> compile
>   
> 
> 
>   2
>   true
>   3600
>   
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
>   alphabetical
>   false
>   
> **/*Test.java
>   
>   
> **/*PerfTest.java
> **/*IntegrationTest.java
>   
> 
>   
> {code}
> result is 
> {code:java|title=java.lang.ClassNotFoundException: 
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger|collapse=true}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test (default-test) on 
> project mts.ctsm: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed: 
> java.lang.ClassNotFoundException: 
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test 
> (default-test) on project mts.ctsm: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed: 
> java.lang.ClassNotFoundException: 
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> 

[jira] [Commented] (MCOMPILER-342) Unsupported class file major version 55

[Mincong Huang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475721#comment-16475721
 ] 

Mincong Huang commented on MCOMPILER-342:
-

Thanks Michael for your quick analysis, I opened an issue for ASM: 
https://gitlab.ow2.org/asm/asm/issues/317830. I'm not sure if this ticket 
should remain opened. I'll let you decide.

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
> Attachments: log.txt
>
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Commented] (MINVOKER-224) Unable to set cloneProjectsTo to null

[Tomer Cohen (JIRA)]

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

Tomer Cohen commented on MINVOKER-224:
--

[~olamy] Is there an ETA for when the version (which I see right now is stamped 
as 3.1.0) is to be released? Thanks!

> Unable to set cloneProjectsTo to null
> -
>
> Key: MINVOKER-224
> URL: https://issues.apache.org/jira/browse/MINVOKER-224
> Project: Maven Invoker Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Phillip Webb
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Major
> Fix For: 3.1.0
>
>
> [MINVOKER-219|https://issues.apache.org/jira/browse/MINVOKER-219] changed the 
> default value of {{cloneProjectsTo}} to {{target/its}}. This change 
> unfortunately now makes it impossible to have a {{null}} value, meaning that 
> in-place invocation is no longer supported. From the Javadoc:
> {quote}Directory to which projects should be cloned prior to execution. If 
> set to null, each integration test will be run in the directory in which the 
> corresponding IT POM was found. In this case, you most likely want to 
> configure your SCM to ignore target and build.log in the test's base 
> directory.{quote}
> Is it possible to revert this change, or to provide a alternative property to 
> allow cloning to be skipped?



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

[jira] [Commented] (MCOMPILER-342) Unsupported class file major version 55

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475680#comment-16475680
 ] 

Michael Osipov commented on MCOMPILER-342:
--

[Here|https://github.com/spotbugs/spotbugs-maven-plugin/issues/47#issuecomment-388326400]
 is your answer. ASM is to blame.

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
> Attachments: log.txt
>
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Comment Edited] (MCOMPILER-342) Unsupported class file major version 55

[Mincong Huang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475635#comment-16475635
 ] 

Mincong Huang edited comment on MCOMPILER-342 at 5/15/18 10:28 AM:
---

Full trace log is uploaded, see {{log.txt}}. This is done via command lines:

{noformat}
$ java -version
java version "11-ea" 2018-09-25
Java(TM) SE Runtime Environment 18.9 (build 11-ea+13)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+13, mixed mode)
$ git clone https://github.com/mincong-h/MCOMPILER-342.git
$ cd MCOMPILER-342
$ mvn clean compile -Dmaven.compiler.source=11 -Dmaven.compiler.target=11 -X
{noformat}


was (Author: mincong):
Full trace log is uploaded, see {{log.txt}}. This is done via command lines:

{noformat}
$ git clone https://github.com/mincong-h/MCOMPILER-342.git
$ cd MCOMPILER-342
$ mvn clean compile -Dmaven.compiler.source=11 -Dmaven.compiler.target=11 -X
{noformat}

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
> Attachments: log.txt
>
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Commented] (MCOMPILER-342) Unsupported class file major version 55

[Mincong Huang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475635#comment-16475635
 ] 

Mincong Huang commented on MCOMPILER-342:
-

Full trace log is uploaded, see {{log.txt}}. This is done via command lines:

{noformat}
$ git clone https://github.com/mincong-h/MCOMPILER-342.git
$ cd MCOMPILER-342
$ mvn clean compile -Dmaven.compiler.source=11 -Dmaven.compiler.target=11 -X
{noformat}

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
> Attachments: log.txt
>
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Updated] (MCOMPILER-342) Unsupported class file major version 55

[Mincong Huang (JIRA)]

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

Mincong Huang updated MCOMPILER-342:

Attachment: log.txt

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
> Attachments: log.txt
>
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

Re: [GitHub] michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows

[Vishal Kumar Gupta]

Please unsubscribe me from this mailing list.

On Tue, May 15, 2018 at 2:06 PM, GitBox  wrote:

> michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare
> fails if the command line is too long on windows
> URL: https://github.com/apache/maven-scm/pull/30#issuecomment-389088832
>
>
>You can always build from source and change dependency versions.
>
> 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on GitHub and use the
> URL above to go to the specific comment.
>
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
>
>
> With regards,
> Apache Git Services
>

[jira] [Commented] (MCOMPILER-342) Unsupported class file major version 55

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475557#comment-16475557
 ] 

Michael Osipov commented on MCOMPILER-342:
--

Please provide a full trace log.

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Closed] (MNG-6382) JANSI fails frequently with NumberFormatException when building in parallel

[JIRA]

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

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

https://gitbox.apache.org/repos/asf?p=maven.git=commit=3c3a5901f35783289d502b67bfc520b8e6936ed8

> JANSI fails frequently with NumberFormatException when building in parallel
> ---
>
> Key: MNG-6382
> URL: https://issues.apache.org/jira/browse/MNG-6382
> Project: Maven
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3 
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: C:\Develop\_tools\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Develop\_tools\jdk-10.0.0
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Falko Modler
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.5.4
>
>
> After upgrading from 3.3.9 to 3.5.4 my parallel Maven build fail frequently 
> with:
> {noformat}
> java.lang.NumberFormatException: For input string: "34m"
> at 
> java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.base/java.lang.Integer.parseInt(Integer.java:652)
> at java.base/java.lang.Integer.(Integer.java:1096)
> at 
> org.fusesource.jansi.AnsiPrintStream.filter(AnsiPrintStream.java:129)
> at 
> org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:97)
> at 
> org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:107)
> at 
> org.fusesource.jansi.FilterPrintStream.print(FilterPrintStream.java:161)
> at 
> org.slf4j.impl.MavenSimpleLogger.writeThrowable(MavenSimpleLogger.java:81)
> at org.slf4j.impl.SimpleLogger.write(SimpleLogger.java:319)
> at org.slf4j.impl.SimpleLogger.log(SimpleLogger.java:295)
> at org.slf4j.impl.SimpleLogger.error(SimpleLogger.java:593)
> at 
> org.apache.maven.cli.CLIReportingUtils.showError(CLIReportingUtils.java:138)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:309)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {noformat}
> This seems to have been [fixed in JANSI master 
> branch|https://github.com/fusesource/jansi/commit/e45e4665538ba9234f5ee5d7b06d78d6a03deda3]
>  but it has not yet been released. There is already a request for a bugfix 
> release, see [issue 114 ("Need 1.17.1 
> release")|https://github.com/fusesource/jansi/issues/114].
> Maven 3.5.4 should therefore upgrade to JANSI 1.17.1.



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

[jira] [Closed] (MNG-6372) On Windows Maven can output spurious ANSI escapes such as [0m [0m

[JIRA]

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

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

https://gitbox.apache.org/repos/asf?p=maven.git=commit=3c3a5901f35783289d502b67bfc520b8e6936ed8

> On Windows Maven can output spurious ANSI escapes such as [0m [0m
> -
>
> Key: MNG-6372
> URL: https://issues.apache.org/jira/browse/MNG-6372
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
>Reporter: Stephen Connolly
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.5.4
>
>
> Found during the release vote of Maven 3.5.3 on Windows spurious ANSI partial 
> escape codes such as [0m
> A regression introduced by the upgrade of JAnsi to 1.17. Tracked in Jansi as 
> issue #107 https://github.com/fusesource/jansi/issues/107, will be fixed in 
> 1.17.1 
> notice: another issue from Jansi 1.17 exists, which is failure when run in 
> parallel build with NumberFormatException = see MNG-6382 for details



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

[jira] [Commented] (SCM-886) Tests with checkin rely on global git config

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SCM-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475534#comment-16475534
 ] 

ASF GitHub Bot commented on SCM-886:


McFoggy opened a new pull request #73: [SCM-886] introduce helper class to 
configure git commit user
URL: https://github.com/apache/maven-scm/pull/73
 
 
   in every tests performing some modifications in git repository (commits, ...)
   a defaut user (name & email) is configured so that git commands succeed if 
no global user exists
   
   fixes #SCM-886
   
   Signed-off-by: Matthieu Brouillard 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Tests with checkin rely on global git config
> 
>
> Key: SCM-886
> URL: https://issues.apache.org/jira/browse/SCM-886
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Matthieu Brouillard
>Priority: Major
>
> Inside maven-scm-provider-gitexe project, the two following tests 
> `GitCheckInCommandNoBranchTest.testCheckinNoBranch` and 
> `GitCheckInCommandTest.testCheckinAfterRename` expect a global user.name and 
> user.email to be set.
> On installations where .gitconfig contains the following:
> {{[user]}}
> {{useConfigOnly = true}}
> The tests will fail.
> It would be better after repository creation to configure a user name & email 
> at project level.



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

[GitHub] McFoggy opened a new pull request #73: [SCM-886] introduce helper class to configure git commit user

[GitBox]

McFoggy opened a new pull request #73: [SCM-886] introduce helper class to 
configure git commit user
URL: https://github.com/apache/maven-scm/pull/73
 
 
   in every tests performing some modifications in git repository (commits, ...)
   a defaut user (name & email) is configured so that git commands succeed if 
no global user exists
   
   fixes #SCM-886
   
   Signed-off-by: Matthieu Brouillard 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows

[GitBox]

michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if 
the command line is too long on windows
URL: https://github.com/apache/maven-scm/pull/30#issuecomment-389088832
 
 
   You can always build from source and change dependency versions.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (SCM-714) mvn release:prepare fails if the command line is too long on windows

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475495#comment-16475495
 ] 

ASF GitHub Bot commented on SCM-714:


michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if 
the command line is too long on windows
URL: https://github.com/apache/maven-scm/pull/30#issuecomment-389088832
 
 
   You can always build from source and change dependency versions.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> mvn release:prepare fails if the command line is too long on windows
> 
>
> Key: SCM-714
> URL: https://issues.apache.org/jira/browse/SCM-714
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.8.1
>Reporter: Felix Simmendinger
>Assignee: Robert Scholte
>Priority: Blocker
>
> The issue from SCM-697 does not solve the issue as the gitprovider is not 
> using the add command but the checkin command during a release.



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

[jira] [Commented] (MCOMPILER-342) Unsupported class file major version 55

[Mincong Huang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCOMPILER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475425#comment-16475425
 ] 

Mincong Huang commented on MCOMPILER-342:
-

I'd like to contribute a patch if somebody help me to understand the codebase :)

> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Updated] (MCOMPILER-342) Unsupported class file major version 55

[Mincong Huang (JIRA)]

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

Mincong Huang updated MCOMPILER-342:

Description: 
Maven compiler plugin does not support classes created by JDK 11 (major version 
55). If you have classes created by JDK 11 in your classpath when using Maven 
Compiler, you've the following errors:

{quote}
Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) 
on project java-examples-dev-core: Execution default-compile of goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
Unsupported class file major version 55 -> [Help 1]
{quote}

See https://github.com/mincong-h/MCOMPILER-342 for reproduction

  was:
Maven compiler plugin does not support classes created by JDK 11 (major version 
55). If you have classes created by JDK 11 in your classpath when using Maven 
Compiler, you've the following errors:

{quote}
Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) 
on project java-examples-dev-core: Execution default-compile of goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
Unsupported class file major version 55 -> [Help 1]
{quote}


> Unsupported class file major version 55
> ---
>
> Key: MCOMPILER-342
> URL: https://issues.apache.org/jira/browse/MCOMPILER-342
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Mincong Huang
>Priority: Blocker
>
> Maven compiler plugin does not support classes created by JDK 11 (major 
> version 55). If you have classes created by JDK 11 in your classpath when 
> using Maven Compiler, you've the following errors:
> {quote}
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project java-examples-dev-core: Execution 
> default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
> Unsupported class file major version 55 -> [Help 1]
> {quote}
> See https://github.com/mincong-h/MCOMPILER-342 for reproduction



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

[jira] [Created] (MCOMPILER-342) Unsupported class file major version 55

[Mincong Huang (JIRA)]

Mincong Huang created MCOMPILER-342:
---

 Summary: Unsupported class file major version 55
 Key: MCOMPILER-342
 URL: https://issues.apache.org/jira/browse/MCOMPILER-342
 Project: Maven Compiler Plugin
  Issue Type: Bug
Affects Versions: 3.7.0
Reporter: Mincong Huang


Maven compiler plugin does not support classes created by JDK 11 (major version 
55). If you have classes created by JDK 11 in your classpath when using Maven 
Compiler, you've the following errors:

{quote}
Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) 
on project java-examples-dev-core: Execution default-compile of goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: 
Unsupported class file major version 55 -> [Help 1]
{quote}



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

[jira] [Commented] (SUREFIRE-1330) JUnit 5 surefire-provider code donation

[Christian Stein (JIRA)]

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

Christian Stein commented on SUREFIRE-1330:
---

Build #17 failed on linux-jdk8-maven3.5.x only (jdk 7, 9 and 10 are fine) with:
  
{quote}[linux-jdk8-maven3.5.x] Running 
org.apache.maven.surefire.its.jiras.Surefire1295AttributeJvmCrashesToTestsIT 
[linux-jdk8-maven3.5.x] Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time 
elapsed: 45.493 sec <<< FAILURE! [linux-jdk8-maven3.5.x] 
test[2](org.apache.maven.surefire.its.jiras.Surefire1295AttributeJvmCrashesToTestsIT)
 Time elapsed: 0.002 sec <<< ERROR! [linux-jdk8-maven3.5.x] 
org.apache.maven.surefire.its.fixture.SurefireVerifierException: 
org.apache.maven.it.VerificationException: Text not found in log: Crashed 
tests: [linux-jdk8-maven3.5.x] at 
org.apache.maven.surefire.its.fixture.OutputValidator.verifyTextInLog(OutputValidator.java:60)
 [linux-jdk8-maven3.5.x] at 
org.apache.maven.surefire.its.jiras.Surefire1295AttributeJvmCrashesToTestsIT.checkCrash(Surefire1295AttributeJvmCrashesToTestsIT.java:126)
 [linux-jdk8-maven3.5.x] at 
org.apache.maven.surefire.its.jiras.Surefire1295AttributeJvmCrashesToTestsIT.test(Surefire1295AttributeJvmCrashesToTestsIT.java:116)
{quote}
 

Will a restart help?

 

[~tibor17] What do you think about the documentation?

> JUnit 5 surefire-provider code donation
> ---
>
> Key: SUREFIRE-1330
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1330
> Project: Maven Surefire
>  Issue Type: New Feature
>Reporter: Benedikt Ritter
>Assignee: Tibor Digana
>Priority: Major
>  Labels: junit5
> Fix For: 2.22.0
>
> Attachments: junit-platform-surefire-provider.zip
>
>
> The JUnit team wishes to contribute their surefire provider implementation 
> for JUnit 5 to the Maven team.
> The code is currently located at GitHub: 
> https://github.com/junit-team/junit5/tree/master/junit-platform-surefire-provider
> They have recently relicensed the code under terms of Apache License 2.0: 
> https://github.com/junit-team/junit5/issues/541



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

[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report

[Heiko Wentzke (JIRA)]

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

Heiko Wentzke commented on SUREFIRE-1480:
-

Updated to Surefire v2.21.0 - still the same result in Jenkins :(

> parallel tests may produce invalid .xml report
> --
>
> Key: SUREFIRE-1480
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1480
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin, 
> Maven Surefire Plugin
>Affects Versions: 2.20.1
>Reporter: Mark Lehky
>Priority: Major
> Attachments: FailedXMLReport.txt, Stacktrace_failedTest.txt
>
>
> Relevant software:
>  * Jenkins 2.108
>  * Maven 3.??
>  * JUnit 4.12
>  * maven-failsafe-plugin 2.20.1 (I have seen this issue with surefire as well)
> I have a testsuite (one JUnit class) that contains multiple tests (multiple 
> JUnit methods), which are all run in parallel. Some of the tests may be 
> ignore using JUnit {{Assume}}.
> On occasion (not 100% reproducible), the resulting report will contain an 
> entry like:
> {noformat}
> < message="Skip test!">
> {noformat}
> The correct entry, as is produced most of the time, should be:
> {noformat}
> 
> {noformat}
> The invalid formatted XML, when run in Jenkins, results in the test being 
> flagged as failed, and Jenkins simply has the message: 
> "TEST-xml.[failed-to-read]" (the dots are replaced with the correct 
> filename!).



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