[Commented] (SUREFIRE-1431) @{argLine} not replaced if undefined

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Commented] (SUREFIRE-1431) @{argLine} not replaced if undefined

JIRA jira@apache.org

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

Michal Domagala commented on SUREFIRE-1431:

[~tibor17], could clarify your answer?
I understand that:
# I can setup argument line with *$*, but I have to know final settings before I call Maven. It is problem because the settings is decided by jacoco plugin during build
#  To solve that issue *@* was introduced, but it fails without Jacoco plugin

As a solution I expect hint how to configure surefire to work without Jacoco plugin but at the same time "consume" argLine produced by Jacoco (if jacoco plugin is part of build)

> @{argLine} not replaced if undefined
> ------------------------------------
>                 Key: SUREFIRE-1431
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1431
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.21.1
>         Environment: Maven 3.5.0
>            Reporter: Matthieu Fillon
>            Assignee: Tibor Digana
>         Attachments: maven.log
> I need to specify argLine for my tests. I also need it to work with Java agent Jacoco when a certain Maven profile is activated.
> So I added `@{argLine}` to my argLine property and it works fine when running with Jacoco agent activated.
> When running the tests without profile that activates Jacoco agent, the surefire plugin fails with following line (relevant maven logs attached) :
> {color:red}Error: Could not find or load main class @\{argLine} {color}
> I guess @{argLine} is only replaced if an argLine has been defined before by another plugin but if not it is not replaced at all.
> Should'nt it be replaced in any case and if none defined, just replace with empty value?

This message was sent by Atlassian JIRA