from:"Larry West \(Jira\)"

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-15 Thread Larry West (Jira)



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

Larry West commented on MNG-7697:
-

[~cstamas] Sorry for the delay, but I see the problem IS successfully resolved 
in my example POMs, using {{apache-maven-3.9.1-20230314.155245-42-bin}} from 
the 
[3.9.1-SNAPSHOT|https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven/3.9.1-SNAPSHOT/]
 repo, with (Corretto) Java 8, 17, and 19 on MacOS 13.2.1.
{quote}Apache Maven 3.9.1-SNAPSHOT (79100c6b35d29f0b74951b7f7486f259d90f8e97)
{quote}
(An earlier 3.9.1 SNAPSHOT also succeeded).

> Cannot parse POM that contains an emoji in a comment
> 
>
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0, 4.0.0-alpha-4
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0-alpha-5, 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Updated] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-15 Thread Larry West (Jira)



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

Larry West updated MNG-7697:

Attachment: (was: image-2023-03-15-21-25-38-647.png)

> Cannot parse POM that contains an emoji in a comment
> 
>
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0, 4.0.0-alpha-4
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0-alpha-5, 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Updated] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-15 Thread Larry West (Jira)



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

Larry West updated MNG-7697:

Attachment: image-2023-03-15-21-25-38-647.png

> Cannot parse POM that contains an emoji in a comment
> 
>
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0, 4.0.0-alpha-4
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0-alpha-5, 3.9.1
>
> Attachments: image-2023-03-15-21-25-38-647.png, pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-13 Thread Larry West (Jira)



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

Larry West commented on MNG-7697:
-

Thanks, [~cstamas]! I'll try 3.9.x tonight.

> Cannot parse POM that contains an emoji in a comment
> 
>
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-13 Thread Larry West (Jira)



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

Larry West edited comment on MNG-7697 at 3/13/23 7:16 PM:
--

Any update on this?   Lots of people (at my work) have to stay with 
{{{}3.8.x{}}}, waiting for {{3.9.1}} to fix this issue so they can work with 
long-standing and perfectly valid POMs, including for dependencies (which 
causes the application being built to omit required transitive dependencies).

IOW, this is impactful.


was (Author: larry_west):
Any update on this?   Lots of people are waiting for {{3.9.1}} to fix this 
issue so they can work with long-standing and perfectly valid POMs, including 
for dependencies (which causes the application being built to omit required 
transitive dependencies).

IOW, this is very impactful.

> Cannot parse POM that contains an emoji in a comment
> 
>
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-13 Thread Larry West (Jira)



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

Larry West commented on MNG-7697:
-

Any update on this?   Lots of people are waiting for {{3.9.1}} to fix this 
issue so they can work with long-standing and perfectly valid POMs, including 
for dependencies (which causes the application being built to omit required 
transitive dependencies).

IOW, this is very impactful.

> Cannot parse POM that contains an emoji in a comment
> 
>
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-02 Thread Larry West (Jira)



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

Larry West edited comment on MNG-7697 at 3/3/23 2:59 AM:
-

_Update: I missed Michael Osipov's "Confirmed" comment until after submitting._

_And now I see that 
[plexus-utils-3.5.1|https://github.com/codehaus-plexus/plexus-utils/releases/tag/plexus-utils-3.5.1]
 appears to have a fix (MNG-7710) — thanks [~gnodet]!_

Here's another example with {{f0 9f a4 94}} (U+1F914: "thinking face") in the 
comment: [^pom.xml].
{code:xml}

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0

G
A
1

{code}
I can't find an XML tool that says this is *not* well-formed. Nor {{xmllint}} 
on MacOS.
h3. Maven 3.9.0

As noted in the description, Maven 3.9.0 incorrectly complains about the UTF-8 
character:
{noformat}
$ mvn390 -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
⋮
$ mvn390 dependency:tree
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /Users/lwest/test/MNG-7696/pom.xml: Illegal character 
0xd83e found in comment (position: END_TAG seen ...\n
G
A
1

{code}
I can't find an XML tool that says this is *not* well-formed. Nor {{xmllint}} 
on MacOS.
h3. Maven 3.9.0

As noted in the description, Maven 3.9.0 incorrectly complains about the UTF-8 
character:
{noformat}
$ mvn390 -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
⋮
$ mvn390 dependency:tree
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /Users/lwest/test/MNG-7696/pom.xml: Illegal character 
0xd83e found in comment (position: END_TAG seen ...\n
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-02 Thread Larry West (Jira)



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

Larry West edited comment on MNG-7697 at 3/3/23 2:53 AM:
-

_Update: I missed Michael Osipov's "Confirmed" comment until after submitting._

_And now I see that 
[plexus-utils-3.5.1|https://github.com/codehaus-plexus/plexus-utils/releases/tag/plexus-utils-3.5.1]
 appears to have a fix._

Here's another example with {{f0 9f a4 94}} (U+1F914: "thinking face") in the 
comment: [^pom.xml].
{code:xml}

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0

G
A
1

{code}
I can't find an XML tool that says this is *not* well-formed. Nor {{xmllint}} 
on MacOS.
h3. Maven 3.9.0

As noted in the description, Maven 3.9.0 incorrectly complains about the UTF-8 
character:
{noformat}
$ mvn390 -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
⋮
$ mvn390 dependency:tree
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /Users/lwest/test/MNG-7696/pom.xml: Illegal character 
0xd83e found in comment (position: END_TAG seen ...\n
G
A
1

{code}
I can't find an XML tool that says this is *not* well-formed. Nor {{xmllint}} 
on MacOS.
h3. Maven 3.9.0

As noted in the description, Maven 3.9.0 incorrectly complains about the UTF-8 
character:
{noformat}
$ mvn390 -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
⋮
$ mvn390 dependency:tree
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /Users/lwest/test/MNG-7696/pom.xml: Illegal character 
0xd83e found in comment (position: END_TAG seen ...\n
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-02 Thread Larry West (Jira)



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

Larry West edited comment on MNG-7697 at 3/3/23 2:44 AM:
-

_Update: I missed Michael Osipov's "Confirmed" comment until after submitting._

Here's another example with {{f0 9f a4 94}} (U+1F914: "thinking face") in the 
comment: [^pom.xml].
{code:xml}

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0

G
A
1

{code}
I can't find an XML tool that says this is *not* well-formed. Nor {{xmllint}} 
on MacOS.
h3. Maven 3.9.0

As noted in the description, Maven 3.9.0 incorrectly complains about the UTF-8 
character:
{noformat}
$ mvn390 -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
⋮
$ mvn390 dependency:tree
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /Users/lwest/test/MNG-7696/pom.xml: Illegal character 
0xd83e found in comment (position: END_TAG seen ...\n
G
A
1

{code}
I can't find an XML tool that says this is *not* well-formed. Nor {{xmllint}} 
on MacOS.
h3. Maven 3.9.0

As noted in the description, Maven 3.9.0 incorrectly complains about the UTF-8 
character:
{noformat}
$ mvn390 -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
⋮
$ mvn390 dependency:tree
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /Users/lwest/test/MNG-7696/pom.xml: Illegal character 
0xd83e found in comment (position: END_TAG seen ...\n
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-02 Thread Larry West (Jira)



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

Larry West commented on MNG-7697:
-

Here's another example with {{f0 9f a4 94}} (U+1F914: "thinking face") in the 
comment: [^pom.xml].
{code:xml}

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0

G
A
1

{code}
I can't find an XML tool that says this is *not* well-formed. Nor {{xmllint}} 
on MacOS.
h3. Maven 3.9.0

As noted in the description, Maven 3.9.0 incorrectly complains about the UTF-8 
character:
{noformat}
$ mvn390 -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
⋮
$ mvn390 dependency:tree
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /Users/lwest/test/MNG-7696/pom.xml: Illegal character 
0xd83e found in comment (position: END_TAG seen ...\n
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Updated] (MNG-7697) Cannot parse POM that contains an emoji in a comment

2023-03-02 Thread Larry West (Jira)



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

Larry West updated MNG-7697:

Attachment: pom-1.xml

> Cannot parse POM that contains an emoji in a comment
> 
>
> Key: MNG-7697
> URL: https://issues.apache.org/jira/browse/MNG-7697
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.9.0
> Environment: MacOS 13.2.1
> OpenJDK Runtime Environment Temurin-17.0.4+8 
>Reporter: Andrew Rosenberg
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.1
>
> Attachments: pom-1.xml, pom.xml
>
>
> {noformat}
>  mvn -e  clean install                            
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-parseable POM 
> /Users/andrew.rosenberg/.m2/repository/com/verygood/security/base-pom-17/0.2.47/base-pom-17-0.2.47.pom:
>  Illegal character 0xd83d found in comment (position: START_TAG seen 
> ...\n

[jira] [Updated] (MDEP-660) Obsolete example of -Dverbose on web page

2019-08-21 Thread Larry West (Jira)



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

Larry West updated MDEP-660:

Description: 
The 
[examples/resolving-conflicts-using-the-dependency-tree|https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html]
 page offers hope that John Lin has worked on MDEP-644:



{quote}
h2. Resolving conflicts using the dependency tree

A project's dependency tree can be expanded to display dependency conflicts. 
For example, to find out why Commons Collections 2.0 is being used by the Maven 
Dependency Plugin, we can execute the following in the project's directory:
  # mvn dependency:tree -Dverbose -Dincludes=commons-collections
The {{verbose}} flag instructs the dependency tree to display conflicting 
dependencies that were omitted from the resolved dependency tree. In this case, 
the goal outputs:

... 

{quote}

 

Alas, it is not so, as MDEP-374 explains.

That page should perhaps be deleted.

  was:
The 
[[examples/resolving-conflicts-using-the-dependency-tree|https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html]|[https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html]]
 page offers hope that John Lin has worked on MDEP-644:



{quote}
h2. Resolving conflicts using the dependency tree

A project's dependency tree can be expanded to display dependency conflicts. 
For example, to find out why Commons Collections 2.0 is being used by the Maven 
Dependency Plugin, we can execute the following in the project's directory:
  # mvn dependency:tree -Dverbose -Dincludes=commons-collections
The {{verbose}} flag instructs the dependency tree to display conflicting 
dependencies that were omitted from the resolved dependency tree. In this case, 
the goal outputs:

... 

{quote}

 

Alas, it is not so, as MDEP-374 explains.

That page should perhaps be deleted.


> Obsolete example of -Dverbose on web page
> -
>
> Key: MDEP-660
> URL: https://issues.apache.org/jira/browse/MDEP-660
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: tree
>Affects Versions: 3.1.1
> Environment: Web - Chrome
>Reporter: Larry West
>Priority: Minor
>  Labels: documentation
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The 
> [examples/resolving-conflicts-using-the-dependency-tree|https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html]
>  page offers hope that John Lin has worked on MDEP-644:
> 
> {quote}
> h2. Resolving conflicts using the dependency tree
> A project's dependency tree can be expanded to display dependency conflicts. 
> For example, to find out why Commons Collections 2.0 is being used by the 
> Maven Dependency Plugin, we can execute the following in the project's 
> directory:
>   # mvn dependency:tree -Dverbose -Dincludes=commons-collections
> The {{verbose}} flag instructs the dependency tree to display conflicting 
> dependencies that were omitted from the resolved dependency tree. In this 
> case, the goal outputs:
> ... 
> {quote}
> 
>  
> Alas, it is not so, as MDEP-374 explains.
> That page should perhaps be deleted.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (MDEP-660) Obsolete example of -Dverbose on web page

2019-08-21 Thread Larry West (Jira)

Larry West created MDEP-660:
---

 Summary: Obsolete example of -Dverbose on web page
 Key: MDEP-660
 URL: https://issues.apache.org/jira/browse/MDEP-660
 Project: Maven Dependency Plugin
  Issue Type: Bug
  Components: tree
Affects Versions: 3.1.1
 Environment: Web - Chrome
Reporter: Larry West


The 
[[examples/resolving-conflicts-using-the-dependency-tree|https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html]|[https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html]]
 page offers hope that John Lin has worked on MDEP-644:



{quote}
h2. Resolving conflicts using the dependency tree

A project's dependency tree can be expanded to display dependency conflicts. 
For example, to find out why Commons Collections 2.0 is being used by the Maven 
Dependency Plugin, we can execute the following in the project's directory:
  # mvn dependency:tree -Dverbose -Dincludes=commons-collections
The {{verbose}} flag instructs the dependency tree to display conflicting 
dependencies that were omitted from the resolved dependency tree. In this case, 
the goal outputs:

... 

{quote}

 

Alas, it is not so, as MDEP-374 explains.

That page should perhaps be deleted.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X

2018-03-19 Thread Larry West (JIRA)


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

Larry West commented on SUREFIRE-1502:
--

[~tibor17] I cloned from the 
[https://github.com/apache/maven-surefire/tree/SUREFIRE-1422] branch 
({{27f68718}}⋮) and stopped setting {{reuseForks=false}}, but get the same 
problem (twice) :( :

{noformat}
. . .
[ERROR] Process Exit Code: 0
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
. . .
{noformat}

I didn't try debugging it... let me know if there's more info or something else 
to try. 

> Forking fails on OS/X
> -
>
> Key: SUREFIRE-1502
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1, 2.21.0
> Environment: OS/X 10.13.3
> Java 1.8.0_162
>Reporter: Larry West
>Assignee: Tibor Digana
>Priority: Major
> Attachments: surefire3972773662020453876tmp, 
> surefire_06790995305937656848tmp
>
>
> This is very similar to SUREFIRE-1422, but is still present _intermittently_ 
> on version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.
> The symptom is that all tests run fine (the reports are there), but as soon 
> as they do, there is an error:
> {noformat}
> The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
>  ...
> Process Exit Code: 0
> {noformat}
> This of course fails the build.
> This occurs on roughly half the builds (with 2.21.0, at least).
> Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
> h5. Selected output from mvn -X
> {noformat}
> [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> {noformat}
> ... then, after all the tests have run, successfully, it reports failure:
> {noformat}
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> Process Exit Code: 0
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:671)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:533)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:278)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:244)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
> (AbstractSurefireMojo.java:1148)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
>  (AbstractSurefireMojo.java:977)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
> (AbstractSurefireMojo.java:853)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExec

[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West commented on SUREFIRE-1502:
--

I just tried setting {{reuseForks=false}} and was able to build successfully 
seven times in a row.  It might have been slower, but going back to earlier 
versions presents other problems for us.

>From the {{mvn -X}} output on the *original, failing* build:

{noformat}
[INFO] --- maven-surefire-plugin:2.21.0:test (default-test) @ jsk-cc ---
[DEBUG] Using mirror central-mirror 
(http://nexus-proxy/nexus/content/groups/public) for snapshots 
(http://snapshots.maven.codehaus.org/maven2).
[DEBUG] Using mirror central-mirror 
(http://nexus-proxy/nexus/content/groups/public) for central 
(http://repo1.maven.org/maven2).
[DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=313522, 
ConflictMarker.markTime=102477, ConflictMarker.nodeCount=114, 
ConflictIdSorter.graphTime=171914, ConflictIdSorter.topsortTime=41866, 
ConflictIdSorter.conflictIdCount=37, ConflictIdSorter.conflictIdCycleCount=0, 
ConflictResolver.totalTime=1118242, ConflictResolver.conflictItemCount=79, 
DefaultDependencyCollector.collectTime=50282293, 
DefaultDependencyCollector.transformTime=1773104}
[DEBUG] org.apache.maven.plugins:maven-surefire-plugin:jar:2.21.0:
[DEBUG]org.apache.maven.surefire:maven-surefire-common:jar:2.21.0:compile
[DEBUG]   org.apache.maven:maven-plugin-api:jar:2.2.1:compile
[DEBUG]   
org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.5:compile
[DEBUG]   org.apache.maven.surefire:surefire-api:jar:2.21.0:compile
[DEBUG]  
org.apache.maven.surefire:surefire-logger-api:jar:2.21.0:compile
[DEBUG]   org.apache.maven.surefire:surefire-booter:jar:2.21.0:compile
[DEBUG]   org.apache.maven:maven-artifact:jar:2.2.1:compile
[DEBUG]  org.codehaus.plexus:plexus-utils:jar:1.5.15:compile
[DEBUG]   org.apache.maven:maven-plugin-descriptor:jar:2.2.1:compile
[DEBUG]  
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG] junit:junit:jar:4.12:compile
[DEBUG]org.hamcrest:hamcrest-core:jar:1.3:compile
[DEBUG]   org.apache.maven:maven-project:jar:2.2.1:compile
[DEBUG]  org.apache.maven:maven-settings:jar:2.2.1:compile
[DEBUG]  org.apache.maven:maven-profile:jar:2.2.1:compile
[DEBUG]  org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
[DEBUG] 
backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
[DEBUG]  org.apache.maven:maven-plugin-registry:jar:2.2.1:compile
[DEBUG]  org.codehaus.plexus:plexus-interpolation:jar:1.11:compile
[DEBUG]   org.apache.maven:maven-model:jar:2.2.1:compile
[DEBUG]   org.apache.maven:maven-core:jar:2.2.1:compile
[DEBUG]  
org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.1:compile
[DEBUG]  org.slf4j:slf4j-jdk14:jar:1.5.6:runtime
[DEBUG] org.slf4j:slf4j-api:jar:1.5.6:runtime
[DEBUG]  org.slf4j:jcl-over-slf4j:jar:1.5.6:runtime
[DEBUG]  org.apache.maven.reporting:maven-reporting-api:jar:3.0:compile
[DEBUG]  org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
[DEBUG]  org.apache.maven:maven-error-diagnostics:jar:2.2.1:compile
[DEBUG]  org.apache.maven:maven-monitor:jar:2.2.1:compile
[DEBUG]  classworlds:classworlds:jar:1.1:compile
[DEBUG]  org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile
[DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.4:compile
[DEBUG]   org.apache.maven:maven-toolchain:jar:2.2.1:compile
[DEBUG]   org.codehaus.plexus:plexus-java:jar:0.9.3:compile
[DEBUG]  org.ow2.asm:asm:jar:6.0_BETA:compile
[DEBUG]  com.thoughtworks.qdox:qdox:jar:2.0-M7:compile
[DEBUG] Created new class realm 
plugin>org.apache.maven.plugins:maven-surefire-plugin:2.21.0
[DEBUG] Importing foreign packages into class realm 
plugin>org.apache.maven.plugins:maven-surefire-plugin:2.21.0
[DEBUG]   Imported:  < maven.api
[DEBUG] Populating class realm 
plugin>org.apache.maven.plugins:maven-surefire-plugin:2.21.0
[DEBUG]   Included: org.apache.maven.plugins:maven-surefire-plugin:jar:2.21.0
[DEBUG]   Included: org.apache.maven.surefire:maven-surefire-common:jar:2.21.0
[DEBUG]   Included: 
org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.5
[DEBUG]   Included: org.apache.maven.surefire:surefire-api:jar:2.21.0
[DEBUG]   Included: org.apache.maven.surefire:surefire-logger-api:jar:2.21.0
[DEBUG]   Included: org.apache.maven.surefire:surefire-booter:jar:2.21.0
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.15
[DEBUG]   Included: junit:junit:jar:4.12
[DEBUG]   Included: org.hamcrest:hamcrest-core:jar:1.3
[DEBUG]   Included: backport-util-concurrent:backport-util-concurrent:jar:3.1
[DEBUG]   Included: org.codehaus.plexus:

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Description: 
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

The symptom is that all tests run fine (the reports are there), but as soon as 
they do, there is an error:
{noformat}
The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
 ...
Process Exit Code: 0
{noformat}
This of course fails the build.

This occurs on roughly half the builds (with 2.21.0, at least).

Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
h5. Selected output from mvn -X
{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
{noformat}
... then, after all the tests have run, successfully, it reports failure:
{noformat}
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
Process Exit Code: 0
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:671)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:278)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:244)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
(AbstractSurefireMojo.java:1148)
at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
 (AbstractSurefireMojo.java:977)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
(AbstractSurefireMojo.java:853)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
{noformat}
There are no "[date]-jvmRun[N].dump", "[date].dumpstream" or 
"[date]-jvmRun[N].dumpstream" files.
h5. Addendum

One detail that is perhaps not relevant is that our projects always use 
{{file.encoding=UTF-8}}, but I see that ForkStarter has hard-coded 
{{ISO_8859_1}} as the StreamCharset param to executeCommandLineAsCallable().

  was:
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

The symptom is that all tests run fine (the reports a

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Description: 
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

The symptom is that all tests run fine (the reports are there), but as soon as 
they do, there is an error:
{noformat}
The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
 ...
Process Exit Code: 0
{noformat}
This of course fails the build.

This occurs roughly half the builds (with 2.21.0, at least).

Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
h5. Selected output from mvn -X
{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
{noformat}
... then, after all the tests have run, successfully, it reports failure:
{noformat}
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
Process Exit Code: 0
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:671)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:278)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:244)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
(AbstractSurefireMojo.java:1148)
at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
 (AbstractSurefireMojo.java:977)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
(AbstractSurefireMojo.java:853)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
{noformat}
There are no "[date]-jvmRun[N].dump", "[date].dumpstream" or 
"[date]-jvmRun[N].dumpstream" files.
h5. Addendum

One detail that is perhaps not relevant is that our projects always use 
{{file.encoding=UTF-8}}, but I see that ForkStarter has hard-coded 
{{ISO_8859_1}} as the StreamCharset param to executeCommandLineAsCallable().

  was:
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

The symptom is that all tests run fine (the reports are

[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West commented on SUREFIRE-1502:
--

(I'm unable to edit the "Fix Version/s" field — this is not fixed in 
2.21.0)

> Forking fails on OS/X
> -
>
> Key: SUREFIRE-1502
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1, 2.21.0
> Environment: OS/X 10.13.3
> Java 1.8.0_162
>Reporter: Larry West
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
> Attachments: surefire3972773662020453876tmp, 
> surefire_06790995305937656848tmp
>
>
> This is very similar to SUREFIRE-1422, but is still present _intermittently_ 
> on version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.
> The symptom is that all tests run fine (the reports are there), but as soon 
> as they do, there is an error:
> {noformat}
> The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
>  ...
> Process Exit Code: 0
> {noformat}
> This of course fails the build.
> Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
> h5. Selected output from mvn -X
> {noformat}
> [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> {noformat}
> ... then, after all the tests have run, successfully, it reports failure:
> {noformat}
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> Process Exit Code: 0
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:671)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:533)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:278)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:244)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
> (AbstractSurefireMojo.java:1148)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
>  (AbstractSurefireMojo.java:977)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
> (AbstractSurefireMojo.java:853)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 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.c

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Description: 
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

The symptom is that all tests run fine (the reports are there), but as soon as 
they do, there is an error:

{noformat}
The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
 ...
Process Exit Code: 0
{noformat}

This of course fails the build.

Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.

h5. Selected output from mvn -X

{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
{noformat}

... then, after all the tests have run, successfully, it reports failure:

{noformat}
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
Process Exit Code: 0
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:671)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:278)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:244)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
(AbstractSurefireMojo.java:1148)
at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
 (AbstractSurefireMojo.java:977)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
(AbstractSurefireMojo.java:853)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
{noformat}

There are no "[date]-jvmRun[N].dump", "[date].dumpstream" or 
"[date]-jvmRun[N].dumpstream" files.

h5. Addendum

One detail that is perhaps not relevant is that our projects always use 
{{file.encoding=UTF-8}}, but I see that ForkStarter has hard-coded 
{{ISO_8859_1}} as the StreamCharset param to executeCommandLineAsCallable().

  was:
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
h5. Selected output from mvn -X
{noformat}
[DEBUG] Forking

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Attachment: surefire3972773662020453876tmp

> Forking fails on OS/X
> -
>
> Key: SUREFIRE-1502
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1, 2.21.0
> Environment: OS/X 10.13.3
> Java 1.8.0_162
>Reporter: Larry West
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
> Attachments: surefire3972773662020453876tmp, 
> surefire_06790995305937656848tmp
>
>
> This is very similar to SUREFIRE-1422, but is still present _intermittently_ 
> on version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.
> Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
> h5. Selected output from mvn -X
> {noformat}
> [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> {noformat}
> ... then, after all the tests have run, successfully, it reports failure:
> {noformat}
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> Process Exit Code: 0
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:671)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:533)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:278)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:244)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
> (AbstractSurefireMojo.java:1148)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
>  (AbstractSurefireMojo.java:977)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
> (AbstractSurefireMojo.java:853)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:356)
> {noformat}
> There are no "[date]-jvmRun[N].dump", "[date].dumpstream" or 
> "[date]-jvmRun[N].dumpstream" files.
> h5. Add

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Attachment: surefire3972773662020453876tmp
surefire_06790995305937656848tmp

> Forking fails on OS/X
> -
>
> Key: SUREFIRE-1502
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1, 2.21.0
> Environment: OS/X 10.13.3
> Java 1.8.0_162
>Reporter: Larry West
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
> Attachments: surefire_06790995305937656848tmp
>
>
> This is very similar to SUREFIRE-1422, but is still present _intermittently_ 
> on version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.
> Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
> h5. Selected output from mvn -X
> {noformat}
> [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> {noformat}
> ... then, after all the tests have run, successfully, it reports failure:
> {noformat}
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> Process Exit Code: 0
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:671)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:533)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:278)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:244)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
> (AbstractSurefireMojo.java:1148)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
>  (AbstractSurefireMojo.java:977)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
> (AbstractSurefireMojo.java:853)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:356)
> {noformat}
> There are no "[date]-jvmRun[N].dump", "[date].dumpstream" or 
> "[date]-jvmRun[N].dumpstream" fi

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Attachment: (was: surefire3972773662020453876tmp)

> Forking fails on OS/X
> -
>
> Key: SUREFIRE-1502
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1, 2.21.0
> Environment: OS/X 10.13.3
> Java 1.8.0_162
>Reporter: Larry West
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
> Attachments: surefire_06790995305937656848tmp
>
>
> This is very similar to SUREFIRE-1422, but is still present _intermittently_ 
> on version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.
> Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
> h5. Selected output from mvn -X
> {noformat}
> [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> {noformat}
> ... then, after all the tests have run, successfully, it reports failure:
> {noformat}
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
> -jar 
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
>  /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> Process Exit Code: 0
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:671)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
> (ForkStarter.java:533)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:278)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
> (ForkStarter.java:244)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
> (AbstractSurefireMojo.java:1148)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
>  (AbstractSurefireMojo.java:977)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
> (AbstractSurefireMojo.java:853)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:356)
> {noformat}
> There are no "[date]-jvmRun[N].dump", "[date].dumpstream" or 
> "[date]-jvmRun[N].dumpstream" files.
> h5. Addendum
> One detail that

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Description: 
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
h5. Selected output from mvn -X
{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
{noformat}
... then, after all the tests have run, successfully, it reports failure:
{noformat}
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
Process Exit Code: 0
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:671)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:278)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:244)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
(AbstractSurefireMojo.java:1148)
at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
 (AbstractSurefireMojo.java:977)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
(AbstractSurefireMojo.java:853)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
{noformat}

There are no "[date]-jvmRun[N].dump", "[date].dumpstream" or 
"[date]-jvmRun[N].dumpstream" files.
h5. Addendum

One detail that is perhaps not relevant is that our projects always use 
{{file.encoding=UTF-8}}, but I see that ForkStarter has hard-coded 
{{ISO_8859_1}} as the StreamCharset param to executeCommandLineAsCallable().

  was:
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
h5. Selected output from mvn -X
{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T1

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Description: 
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
h5. Selected output from mvn -X
{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
{noformat}
... then, after all the tests have run, successfully...
{noformat}
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
Process Exit Code: 0
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:671)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:278)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:244)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
(AbstractSurefireMojo.java:1148)
at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
 (AbstractSurefireMojo.java:977)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
(AbstractSurefireMojo.java:853)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
{noformat}
h5. Addendum

One detail that is perhaps not relevant is that our projects always use 
{{file.encoding=UTF-8}}, but I see that ForkStarter has hard-coded 
{{ISO_8859_1}} as the StreamCharset param to executeCommandLineAsCallable().

  was:
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

Maven version 3.5.3.  Java 1.8.0_162.  OS/X 10.13.3.

h5. Selected output from mvn -X

{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
{noformat}
...
{noformat}
Cau

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Environment: 
OS/X 10.13.3
Java 1.8.0_162

  was:Linux (Debian 9 with OpenJDK 8)

Description: 
This is very similar to SUREFIRE-1422, but is still present _intermittently_ on 
version 2.21.0 as well as 2.20.1.  It was not present on 2.19.1.

Maven version 3.5.3.  Java 1.8.0_162.  OS/X 10.13.3.

h5. Selected output from mvn -X

{noformat}
[DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
{noformat}
...
{noformat}
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
 /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 
surefire3972773662020453876tmp surefire_06790995305937656848tmp
Process Exit Code: 0
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:671)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork 
(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:278)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run 
(ForkStarter.java:244)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider 
(AbstractSurefireMojo.java:1148)
at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
 (AbstractSurefireMojo.java:977)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute 
(AbstractSurefireMojo.java:853)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
{noformat}

h5. Addendum

One detail that is perhaps not relevant is that our projects always use 
{{file.encoding=UTF-8}}, but I see that ForkStarter has hard-coded 
{{ISO_8859_1}} as the StreamCharset param to executeCommandLineAsCallable().

  was:
Hi,

With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure on 
Linux when the fork mode is enabled:

{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project foo: There are test failures.
[ERROR]
[ERROR] Please refer to /foo/target/surefire-reports for the individual test 
results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
{code}

I traced the issue

[jira] [Created] (SUREFIRE-1502) CLONE - Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)

Larry West created SUREFIRE-1502:


 Summary: CLONE - Forking fails on OS/X
 Key: SUREFIRE-1502
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
 Project: Maven Surefire
  Issue Type: Bug
  Components: process forking
Affects Versions: 2.20.1
 Environment: Linux (Debian 9 with OpenJDK 8)
Reporter: Larry West
Assignee: Tibor Digana
 Fix For: 2.21.0


Hi,

With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure on 
Linux when the fork mode is enabled:

{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project foo: There are test failures.
[ERROR]
[ERROR] Please refer to /foo/target/surefire-reports for the individual test 
results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
{code}

I traced the issue back to the PpidChecker class, the code assumes that 
{{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
trimmed down containers commonly used for continuous integration).

It would be nice to have a fallback mechanism when ps isn't available, or at 
least check its existence and display an explicit message stating that it must 
be installed.



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

[jira] [Updated] (SUREFIRE-1502) CLONE - Forking fails on OS/X

2018-03-16 Thread Larry West (JIRA)


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

Larry West updated SUREFIRE-1502:
-
Affects Version/s: 2.21.0

> CLONE - Forking fails on OS/X
> -
>
> Key: SUREFIRE-1502
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1, 2.21.0
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Larry West
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure 
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test 
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that 
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at 
> least check its existence and display an explicit message stating that it 
> must be installed.



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

[jira] [Comment Edited] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

2018-03-16 Thread Larry West (JIRA)


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

Larry West edited comment on SUREFIRE-1422 at 3/16/18 10:59 PM:


For anyone searching: this also happens on Mac OS/X (10.13.3).

Does *not* occur with version 2.19.1.


was (Author: larry_west):
For anyone searching: this also happens on Mac OS/X (10.13.3).

Does *not* occur with version 2.19.1 or 2.21.0: thanks for fixing.

> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure 
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test 
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that 
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at 
> least check its existence and display an explicit message stating that it 
> must be installed.



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

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

2018-03-16 Thread Larry West (JIRA)


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

Larry West commented on SUREFIRE-1422:
--

For anyone searching: this also happens on Mac OS/X (10.13.3).

Does *not* occur with version 2.19.1 or 2.21.0: thanks for fixing.

> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure 
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test 
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that 
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on 
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at 
> least check its existence and display an explicit message stating that it 
> must be installed.



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

[jira] Created: (MNGSITE-141) Maven properties are not like Ant properties

2011-09-09 Thread Larry West (JIRA)

Maven properties are not like Ant properties


 Key: MNGSITE-141
 URL: https://jira.codehaus.org/browse/MNGSITE-141
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: http://maven.apache.org/settings.html#Properties
Reporter: Larry West
Priority: Minor


The text says "Maven properties are value placeholder, like properties in Ant." 
 This is incorrect.  Ant properties generally cannot be changed.   Maven 
documentation is oddly silent on this crucial point -- I cannot imagine how 
many hours have been wasted by this -- but in my tests, Maven 3 does change the 
value of properties.

It's a huge difference in functionality, and a surprise to anyone coming from 
Ant, and that line exacerbates the problem.

The fix: append this text: ", except that Maven properties are NOT immutable, 
which is to say attempts to change (user-defined) properties will succeed."

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Updated] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Updated] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Comment Edited] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Commented] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Updated] (MNG-7697) Cannot parse POM that contains an emoji in a comment

[jira] [Updated] (MDEP-660) Obsolete example of -Dverbose on web page

[jira] [Created] (MDEP-660) Obsolete example of -Dverbose on web page

[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) Forking fails on OS/X

[jira] [Created] (SUREFIRE-1502) CLONE - Forking fails on OS/X

[jira] [Updated] (SUREFIRE-1502) CLONE - Forking fails on OS/X

[jira] [Comment Edited] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available

[jira] Created: (MNGSITE-141) Maven properties are not like Ant properties

30 matches

Site Navigation

Mail list logo

Footer information