Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@{argLine} is not recognized in the "VM arguments" of JUnit "Run configuration" #1417

Closed
psybases opened this issue Nov 27, 2024 · 2 comments
Labels
for: eclipse something that is specific for Eclipse status: declined type: bug

Comments

@psybases
Copy link

Describe the bug
Run configuration for JUnit tests, copies automatically the configuration from pom.xml plugin
"maven-surefire-plugin" to "VM arguments".
But if the configuration contains "@{argLine}",
(as described at https://maven.apache.org/surefire-archives/surefire-3.2.2/maven-surefire-plugin/test-mojo.html#argline)
the Junit execution fails with the following message
Error: could not open `{argLine}'

To Reproduce
Have a pom.xml with a maven-surefire-plugin configuration containing @{argLine} as shown in the Sample.
Right click on a JUnit tests file and click "Run As -> JUnit Test".
It will add automatically the following "VM arguments" to the JUnit "Run Configurations" for the given test.
-ea @{argLine} -javaagent:.......

Sample

                 <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-surefire-plugin</artifactId>
                    <version>${surefire.plugin.version}</version>
                    <configuration>
                        <testFailureIgnore>false</testFailureIgnore>
                        <useSystemClassLoader>true</useSystemClassLoader>
                        <argLine>@{argLine} -javaagent:....</argLine>
                      ...
                    </configuration>
                </plugin>
@martinlippert
Copy link
Member

This is most likely something that belongs to the m2e project (the Maven integration for Eclipse) and should therefore reported here: https://github.com/eclipse-m2e/m2e-core

@martinlippert martinlippert closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2024
@martinlippert martinlippert added status: declined for: eclipse something that is specific for Eclipse and removed status: waiting-for-triage labels Nov 27, 2024
@psybases
Copy link
Author

ok thanks @martinlippert,
indeed it is already addressed in this issue:
eclipse-m2e/m2e-core#1824

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: eclipse something that is specific for Eclipse status: declined type: bug
Projects
None yet
Development

No branches or pull requests

2 participants