[
https://jira.codehaus.org/browse/SUREFIRE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354227#comment-354227
]
Andreas Gudian edited comment on SUREFIRE-1104 at 10/11/14 2:41 PM:
--------------------------------------------------------------------
You're right. I guess my problem was that I passed "-T 2" as one argument to
the process (by using our MavenLauncher.addGoal(..) method). Changing the test
to use {{.addGoal( "-T" ).addGoal( "2" )}} would have done the trick as well,
as it would correctly pass the to parts as separate arguments, just as it would
be when calling {{mvn test -T 2}} on the command line.
was (Author: agudian):
You're right. I guess my problem was that I passed "-T 2" as one argument to
the process (by using our MavenLauncher.addGoal(..) method). Chaining the test
to use {{.addGoal( "-T" ).addGoal( "2" )}} would have done the trick as well,
as it would correctly pass the to parts as separate arguments, just as it would
be when calling {{mvn test -T 2}} on the command line.
> Internal Maven Surefire IT tests fail with Maven 3.2.x
> ------------------------------------------------------
>
> Key: SUREFIRE-1104
> URL: https://jira.codehaus.org/browse/SUREFIRE-1104
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: Backlog
> Environment: Maven dist 3.2.x
> Reporter: Tibor Digana
> Assignee: Andreas Gudian
> Priority: Minor
> Fix For: 2.18
>
>
> The IT tests in maven-surefire project which work with Maven 3.2.x and forked
> processes fail with thrown NumberFormatException.
> As a root cause, surefire cannot decode the process id " 2" as a String to
> the number.
> It looks like the fault is Maven Core side however the IT tests fail on our
> side. it seems that Maven backwards compatibility is broken.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
