[jira] [Reopened] (MNG-5976) Replace Plexus Utils OS with Commons Lang SystemUtils
[
https://issues.apache.org/jira/browse/MNG-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MNG-5976:
-
> Replace Plexus Utils OS with Commons Lang SystemUtils
> -
>
> Key: MNG-5976
> URL: https://issues.apache.org/jira/browse/MNG-5976
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Embedding
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
>
> The {{Os}} class have two issues compared to {{SystemUtils}}:
> 1. It modifies the property values by lowercasing it.
> 2. OS detection has a handful of relic operating systems listed which make
> the detection error-prone. E.g., recent versions of Windows are reported as
> OS family {{dos}} is is plain wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MNG-5976) Replace Plexus Utils OS with Commons Lang SystemUtils
[
https://issues.apache.org/jira/browse/MNG-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5976.
---
Resolution: Won't Fix
Fix Version/s: (was: 3.4.0)
Reclosing as won't fix because Plexus Utils does now properly detect. See
[edc1a82b6a4243ff96d510f03eea2b5cc8df6219|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=edc1a82b6a4243ff96d510f03eea2b5cc8df6219]
for details.
> Replace Plexus Utils OS with Commons Lang SystemUtils
> -
>
> Key: MNG-5976
> URL: https://issues.apache.org/jira/browse/MNG-5976
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Embedding
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>
> The {{Os}} class have two issues compared to {{SystemUtils}}:
> 1. It modifies the property values by lowercasing it.
> 2. OS detection has a handful of relic operating systems listed which make
> the detection error-prone. E.g., recent versions of Windows are reported as
> OS family {{dos}} is is plain wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5976) Replace Plexus Utils OS with Commons Lang SystemUtils
[
https://issues.apache.org/jira/browse/MNG-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542991#comment-15542991
]
Hudson commented on MNG-5976:
-
SUCCESS: Integrated in Jenkins build maven-3.x #1384 (See
[https://builds.apache.org/job/maven-3.x/1384/])
Revert "[MNG-5976] Replace Plexus Utils OS with Commons Lang (michaelo: rev
edc1a82b6a4243ff96d510f03eea2b5cc8df6219)
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/CLIReportingUtils.java
> Replace Plexus Utils OS with Commons Lang SystemUtils
> -
>
> Key: MNG-5976
> URL: https://issues.apache.org/jira/browse/MNG-5976
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Embedding
>Affects Versions: 3.3.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>
> The {{Os}} class have two issues compared to {{SystemUtils}}:
> 1. It modifies the property values by lowercasing it.
> 2. OS detection has a handful of relic operating systems listed which make
> the detection error-prone. E.g., recent versions of Windows are reported as
> OS family {{dos}} is is plain wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6098) Unable to run Maven test. Getting org.apache.maven.surefire.util.SurefireReflectionException:
[
https://issues.apache.org/jira/browse/MNG-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543027#comment-15543027
]
Guillaume Boué commented on MNG-6098:
-
There are a couple of issue with your POM. First, you're using an old version
of Surefire (2.12.4), and the version 6.9.13.6 (with 4 digits) isn't correctly
recognized, which explains the failure. Upgrade to version 2.19.1 instead of
2.12.4, that will solve your immediate issue.
Second, it seems you have multiple conflicting versions of TestNG in the
classpath, as shown by:
{noformat}
[WARNING] The POM for org.testng:testng:jar:5.14.3 is invalid, transitive
dependencies (if any) will not be available, enable debug logging for more
details
[WARNING] The POM for org.testng:testng:jar:5.14.4 is invalid, transitive
dependencies (if any) will not be available, enable debug logging for more
details
[WARNING] The POM for org.testng:testng:jar:5.14.5 is invalid, transitive
dependencies (if any) will not be available, enable debug logging for more
details
{noformat}
You should use a single version of TestNG with a {{test}}. With
regard to those warnings, the artifacts downloaded by Maven were most likely
corrupted (partial transfer, proxy settings...), so you'll need to remove them
from your local repository and have Maven redownload them. They should be
located by default in {{~/.m2/repository/org/testng/testng}}.
> Unable to run Maven test. Getting
> org.apache.maven.surefire.util.SurefireReflectionException:
> --
>
> Key: MNG-6098
> URL: https://issues.apache.org/jira/browse/MNG-6098
> Project: Maven
> Issue Type: Question
> Components: Dependencies, POM
>Affects Versions: 3.3.9
> Environment: Windows 10
>Reporter: V Ravi Sankar
>Priority: Blocker
>
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building MavenSelenium3 0.0.1-SNAPSHOT
> [INFO]
>
> [WARNING] The POM for org.testng:testng:jar:5.14.3 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] The POM for org.testng:testng:jar:5.14.4 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] The POM for org.testng:testng:jar:5.14.5 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> MavenSelenium3 ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
> MavenSelenium3 ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> MavenSelenium3 ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
> MavenSelenium3 ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ MavenSelenium3
> ---
> [INFO] Surefire report directory:
> C:\Users\RaviVinnakota\workspace\MavenSelenium3\target\surefire-reports
> ---
> T E S T S
> ---
> Running TestSuite
> org.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> 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:497)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess
[jira] [Commented] (MNG-6091) Failing on upload of some artifacts.
[ https://issues.apache.org/jira/browse/MNG-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543240#comment-15543240 ] Mariana Ciumac commented on MNG-6091: - I installed and run Nexus locally for now, it is on port 8083 because other ports are occupied. Nexus version is OSS 3.0.1-01. I am doing it through WebSphere RAD 8.5.5.3, that uses m2e plugin 1.4.0 and Apache Maven 3.0.4. > Failing on upload of some artifacts. > > > Key: MNG-6091 > URL: https://issues.apache.org/jira/browse/MNG-6091 > Project: Maven > Issue Type: Bug >Reporter: Mariana Ciumac > > When I run "mvn deploy" to upload the artifact to Nexus repository (locally) > sometimes the command is success and sometimes it fails the exception is > below. In caseof failure some of the files are uploaded and some most of > the time jar file it is not, but sometimes jar is uploaded but pom file does > not. > I tried to find the pattern, but there is no partten that I can see, it is > random. > I contacted Nexus and from their log they are saying that there is no error > in their logs. What they see is that for the file that is failed to upload > the request does not come back when challenged with 401 response, while the > requests for other files comes back with credentials. Let me know if you need > more info. > Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on > project service-security: Failed to deploy artifacts: Could not transfer > artifact com.brick:service-security:jar:2.4-20160916.144123-22 from/to > maven-snapshots (http://localhost:8083/repository/maven-snapshots/): Remotely > Closed [id: 0xcb3e29be, /127.0.0.1:57273 :> localhost/127.0.0.1:8083] -> > [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCOMPILER-269) Support modulepath (Java9/Jigsaw)
[ https://issues.apache.org/jira/browse/MCOMPILER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543410#comment-15543410 ] Hudson commented on MCOMPILER-269: -- SUCCESS: Integrated in Jenkins build maven-plugins #7334 (See [https://builds.apache.org/job/maven-plugins/7334/]) [MCOMPILER-269] Support modulepath (Java9/Jigsaw) remove --add-modules, already implicitly added by --add-reads (rfscholte: [http://svn.apache.org/viewvc/?view=rev&rev=1763205]) * (add) maven-compiler-plugin/src/it/MCOMPILER-275_separate-moduleinfo/verify.groovy * (edit) maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java > Support modulepath (Java9/Jigsaw) > - > > Key: MCOMPILER-269 > URL: https://issues.apache.org/jira/browse/MCOMPILER-269 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 3.6 > > > http://openjdk.java.net/jeps/261 describes which arguments to use to make > proper use of modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCOMPILER-279) Passing multiple --add-exports args to the compilerArgs is not supported
[
https://issues.apache.org/jira/browse/MCOMPILER-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543409#comment-15543409
]
Hudson commented on MCOMPILER-279:
--
SUCCESS: Integrated in Jenkins build maven-plugins #7334 (See
[https://builds.apache.org/job/maven-plugins/7334/])
[MCOMPILER-279] Passing multiple --add-exports args to the compilerArgs is not
supported
Use compilerConfiguration.addCompilerCustomArgument() to pass arguments (allows
duplicate keys) (rfscholte:
[http://svn.apache.org/viewvc/?view=rev&rev=1763193])
* (edit)
maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java
> Passing multiple --add-exports args to the compilerArgs is not supported
>
>
> Key: MCOMPILER-279
> URL: https://issues.apache.org/jira/browse/MCOMPILER-279
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.5.1
>Reporter: Michael Musgrove
>Assignee: Robert Scholte
> Fix For: 3.6
>
> Attachments: jdk9-test.tar
>
>
> This plugin collapses multiple compiler args with the same name into a single
> one.
> An example of where this is an issue is when exporting extra packages from a
> Java SE 9 module:
> Suppose we want to export two packages (package1 and package2) from a module
> called FROM-MOD to the OTHER-MOD module. The syntax for this is:
> {code}
> javac ... --add-exports FROM-MOD/package1=OTHER-MOD --add-exports
> FROM-MOD/package2=OTHER-MOD
> {code}
> and the plugin configuration for this is:
> {code:xml}
>
> ...
>
> --add-exports
> FROM-MOD/package1=OTHER-MOD
> --add-exports
> FROM-MOD/package2=OTHER-MOD>
>
>
> {code}
> which produces:
> {code}
> javac ... --add-exports FROM-MOD/package1=OTHER-MOD
> FROM-MOD/package2=OTHER-MOD
> {code}
> Notice the missing --add-exports for the second export so the compiler
> complains with the error:
> bq. Caused by: java.lang.IllegalArgumentException: invalid flag:
> java.corba/com.sun.corba.se.spi.ior=ALL-UNNAMED
> A concrete but basic example maven project is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6091) Failing on upload of some artifacts.
[ https://issues.apache.org/jira/browse/MNG-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543422#comment-15543422 ] Karl Heinz Marbaise commented on MNG-6091: -- You should check if this happens on command line as well? Furthermore M2E 1.4.0 is a little bit out of date...Maven 3.0.4 also... > Failing on upload of some artifacts. > > > Key: MNG-6091 > URL: https://issues.apache.org/jira/browse/MNG-6091 > Project: Maven > Issue Type: Bug >Reporter: Mariana Ciumac > > When I run "mvn deploy" to upload the artifact to Nexus repository (locally) > sometimes the command is success and sometimes it fails the exception is > below. In caseof failure some of the files are uploaded and some most of > the time jar file it is not, but sometimes jar is uploaded but pom file does > not. > I tried to find the pattern, but there is no partten that I can see, it is > random. > I contacted Nexus and from their log they are saying that there is no error > in their logs. What they see is that for the file that is failed to upload > the request does not come back when challenged with 401 response, while the > requests for other files comes back with credentials. Let me know if you need > more info. > Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on > project service-security: Failed to deploy artifacts: Could not transfer > artifact com.brick:service-security:jar:2.4-20160916.144123-22 from/to > maven-snapshots (http://localhost:8083/repository/maven-snapshots/): Remotely > Closed [id: 0xcb3e29be, /127.0.0.1:57273 :> localhost/127.0.0.1:8083] -> > [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-139) maven profile activation in child poms using variable profile.parent.artifactId
Miroslav Zaťko created MPOM-139: --- Summary: maven profile activation in child poms using variable profile.parent.artifactId Key: MPOM-139 URL: https://issues.apache.org/jira/browse/MPOM-139 Project: Maven POMs Issue Type: Bug Components: maven Reporter: Miroslav Zaťko I created a profile activated using property "profile.parent.artifactId" in parent pom so I expected it will be active in child executions. It doesn't work even when its value is as expected project.parent.artifactId my_parent_artifactId . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPOM-139) maven profile activation in child poms using variable profile.parent.artifactId doesn't work
[ https://issues.apache.org/jira/browse/MPOM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miroslav Zaťko updated MPOM-139: Summary: maven profile activation in child poms using variable profile.parent.artifactId doesn't work (was: maven profile activation in child poms using variable profile.parent.artifactId) > maven profile activation in child poms using variable > profile.parent.artifactId doesn't work > > > Key: MPOM-139 > URL: https://issues.apache.org/jira/browse/MPOM-139 > Project: Maven POMs > Issue Type: Bug > Components: maven >Reporter: Miroslav Zaťko > > I created a profile activated using property "profile.parent.artifactId" in > parent pom so I expected it will be active in child executions. It doesn't > work even when its value is as expected > > > >project.parent.artifactId >my_parent_artifactId > > > . > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPOM-139) maven profile activation in child poms using variable profile.parent.artifactId doesn't work
[
https://issues.apache.org/jira/browse/MPOM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Zaťko updated MPOM-139:
Description:
I created a profile activated using property "profile.parent.artifactId" in
parent pom so I expected it will be active in child executions. It doesn't work
even when its value is as expected
{noformat}
project.parent.artifactId
my_parent_artifactId
.
{noformat}
was:
I created a profile activated using property "profile.parent.artifactId" in
parent pom so I expected it will be active in child executions. It doesn't work
even when its value is as expected
project.parent.artifactId
my_parent_artifactId
.
> maven profile activation in child poms using variable
> profile.parent.artifactId doesn't work
>
>
> Key: MPOM-139
> URL: https://issues.apache.org/jira/browse/MPOM-139
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
>Reporter: Miroslav Zaťko
>
> I created a profile activated using property "profile.parent.artifactId" in
> parent pom so I expected it will be active in child executions. It doesn't
> work even when its value is as expected
> {noformat}
>
>
>
>project.parent.artifactId
>my_parent_artifactId
>
>
> .
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MPOM-139) maven profile activation in child poms using variable profile.parent.artifactId doesn't work
[
https://issues.apache.org/jira/browse/MPOM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Zaťko updated MPOM-139:
Description:
I created a profile activated using property "profile.parent.artifactId" in
parent pom so I expected it will be active in child(module) executions. It
doesn't work even when its value is as expected
{noformat}
project.parent.artifactId
my_parent_artifactId
.
{noformat}
Anyway, activation using file+exists, again defined in parent pom, is working
in child(module) executions:
{noformat}
${basedir}/../pom.xml
.
{noformat}
was:
I created a profile activated using property "profile.parent.artifactId" in
parent pom so I expected it will be active in child executions. It doesn't work
even when its value is as expected
{noformat}
project.parent.artifactId
my_parent_artifactId
.
{noformat}
> maven profile activation in child poms using variable
> profile.parent.artifactId doesn't work
>
>
> Key: MPOM-139
> URL: https://issues.apache.org/jira/browse/MPOM-139
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
>Reporter: Miroslav Zaťko
>
> I created a profile activated using property "profile.parent.artifactId" in
> parent pom so I expected it will be active in child(module) executions. It
> doesn't work even when its value is as expected
> {noformat}
>
>
>
>project.parent.artifactId
>my_parent_artifactId
>
>
> .
>
> {noformat}
> Anyway, activation using file+exists, again defined in parent pom, is working
> in child(module) executions:
> {noformat}
>
>
> ${basedir}/../pom.xml
>
> .
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SUREFIRE-1287) Improve logging to understand why test run failed and report the right failed category
[ https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1287: -- Assignee: Tibor Digana > Improve logging to understand why test run failed and report the right failed > category > -- > > Key: SUREFIRE-1287 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1287 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Samarth Jain >Assignee: Tibor Digana > > As part of our automated jenkins builds that run after every checkin, we have > been seeing a lot of these failures: > Failed to execute goal > org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify > (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or > other error in the fork > Sample run: > https://builds.apache.org/job/Phoenix-master/1420/console > Unfortunately that bit of error information doesn't really help. It would be > good to know why exactly the fork timed out or failed. What we do know is > that some of the tests in the Junit category ParallelStatsDisabledTest failed > to complete. However, failsafe incorrectly reports the failed category as the > first category that ran. In this case it happened to be > ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off > next category run even before all the tests in the current category have > finished. I am not sure if that is by design or a bug. > FYI, [~jamestaylor]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1287) Improve logging to understand why test run failed and report the right failed category
[ https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543697#comment-15543697 ] Tibor Digana commented on SUREFIRE-1287: commit https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=e0ce6cb021d42d021704f77a689e3b663aebf084 > Improve logging to understand why test run failed and report the right failed > category > -- > > Key: SUREFIRE-1287 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1287 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Samarth Jain >Assignee: Tibor Digana > > As part of our automated jenkins builds that run after every checkin, we have > been seeing a lot of these failures: > Failed to execute goal > org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify > (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or > other error in the fork > Sample run: > https://builds.apache.org/job/Phoenix-master/1420/console > Unfortunately that bit of error information doesn't really help. It would be > good to know why exactly the fork timed out or failed. What we do know is > that some of the tests in the Junit category ParallelStatsDisabledTest failed > to complete. However, failsafe incorrectly reports the failed category as the > first category that ran. In this case it happened to be > ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off > next category run even before all the tests in the current category have > finished. I am not sure if that is by design or a bug. > FYI, [~jamestaylor]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1287) Improve logging to understand why test run failed and report the right failed category
[ https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543696#comment-15543696 ] Tibor Digana commented on SUREFIRE-1287: commit https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=e0ce6cb021d42d021704f77a689e3b663aebf084 > Improve logging to understand why test run failed and report the right failed > category > -- > > Key: SUREFIRE-1287 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1287 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Samarth Jain >Assignee: Tibor Digana > > As part of our automated jenkins builds that run after every checkin, we have > been seeing a lot of these failures: > Failed to execute goal > org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify > (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or > other error in the fork > Sample run: > https://builds.apache.org/job/Phoenix-master/1420/console > Unfortunately that bit of error information doesn't really help. It would be > good to know why exactly the fork timed out or failed. What we do know is > that some of the tests in the Junit category ParallelStatsDisabledTest failed > to complete. However, failsafe incorrectly reports the failed category as the > first category that ran. In this case it happened to be > ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off > next category run even before all the tests in the current category have > finished. I am not sure if that is by design or a bug. > FYI, [~jamestaylor]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SUREFIRE-1287) Improve logging to understand why test run failed and report the right failed category
[ https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1287: --- Comment: was deleted (was: commit https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=e0ce6cb021d42d021704f77a689e3b663aebf084) > Improve logging to understand why test run failed and report the right failed > category > -- > > Key: SUREFIRE-1287 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1287 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Samarth Jain >Assignee: Tibor Digana > > As part of our automated jenkins builds that run after every checkin, we have > been seeing a lot of these failures: > Failed to execute goal > org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify > (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or > other error in the fork > Sample run: > https://builds.apache.org/job/Phoenix-master/1420/console > Unfortunately that bit of error information doesn't really help. It would be > good to know why exactly the fork timed out or failed. What we do know is > that some of the tests in the Junit category ParallelStatsDisabledTest failed > to complete. However, failsafe incorrectly reports the failed category as the > first category that ran. In this case it happened to be > ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off > next category run even before all the tests in the current category have > finished. I am not sure if that is by design or a bug. > FYI, [~jamestaylor]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1287) Improve logging to understand why test run failed and report the right failed category
[ https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543702#comment-15543702 ] Tibor Digana commented on SUREFIRE-1287: [~jamestaylor] I tested my changes but I don't think it would help us. Try to log OOM as we talked about previously. What would help me is some stack trace from forked JVM. > Improve logging to understand why test run failed and report the right failed > category > -- > > Key: SUREFIRE-1287 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1287 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Samarth Jain >Assignee: Tibor Digana > > As part of our automated jenkins builds that run after every checkin, we have > been seeing a lot of these failures: > Failed to execute goal > org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify > (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or > other error in the fork > Sample run: > https://builds.apache.org/job/Phoenix-master/1420/console > Unfortunately that bit of error information doesn't really help. It would be > good to know why exactly the fork timed out or failed. What we do know is > that some of the tests in the Junit category ParallelStatsDisabledTest failed > to complete. However, failsafe incorrectly reports the failed category as the > first category that ran. In this case it happened to be > ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off > next category run even before all the tests in the current category have > finished. I am not sure if that is by design or a bug. > FYI, [~jamestaylor]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1288) systemProperties should not be deprecated
[
https://issues.apache.org/jira/browse/SUREFIRE-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543710#comment-15543710
]
Tibor Digana commented on SUREFIRE-1288:
[~michaldo]
Surefire deprecated {{systemProperties}} because Maven deprecated using
{{Properties}} in Mojo parameter.
Can you answer my preious question in Jira?
> systemProperties should not be deprecated
> --
>
> Key: SUREFIRE-1288
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1288
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michal Domagala
>
> Current property precedence is: (higher number=more important)
> 1. systemProperties
> 2. systemPropertiesFile
> 3. systemPropertyVariables
> systemPropertyVariables is not replacement for systemProperties because
> meaning is different.
> For me systemProperties are more useful, because I can define default values
> in pom.xml and optionally override them in runtime by configuration file.
> systemPropertyVariables are not useful because can be overriden only by
> command line arguments. Commandline is not friendly if several properties
> must be modified
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SUREFIRE-1286) Failsafe - duplicate class in classpath (in JAR and target/classes)
[
https://issues.apache.org/jira/browse/SUREFIRE-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1286:
--
Assignee: Tibor Digana
> Failsafe - duplicate class in classpath (in JAR and target/classes)
> ---
>
> Key: SUREFIRE-1286
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1286
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.19.1
> Environment: Maven 3.3.9
> Java 8
>Reporter: Christian Danninger
>Assignee: Tibor Digana
> Fix For: 2.18.1
>
>
> I'm not sure if it is releated to SUREFIRE-855. But with version 2.19.1 I got
> a class twice on my classpath (work fine with version 2.18.1). One in the
> maven module JAR and one in target/classes. This is an issue due the fact I'm
> using CDI (WELD).
> This is was my classpath is looking like (taken from
> integration-test/target/surefire/surefire5166061968440405040tmp):
> {code}#surefire
> #Wed Sep 28 15:54:06 CEST 2016
> tc.1=x.productdb.client.v2.ProductDBClientSolrImplTestIT
> tc.0=x.productdb.client.v2.HotelDataSolrImplTestIT
> classPathUrl.0=/Users/xxx/dev/git/lib/xx/integration-test/target/classes
> classPathUrl.1=/Users/xxx/dev/git/lib/xx/integration-test/target/integration-test-2.0.0-SNAPSHOT.jar
> {code}
> Location of TestSolrConfiguration.class:
> ./target/integration-test-2.0.0-SNAPSHOT.jar
> ./target/classes/de/comvel/productdb/test/TestSolrConfiguration.class
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1286) Failsafe - duplicate class in classpath (in JAR and target/classes)
[
https://issues.apache.org/jira/browse/SUREFIRE-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543759#comment-15543759
]
Tibor Digana commented on SUREFIRE-1286:
[~cdanningerCV]
[~christian.dannin...@comvel.de]
Can you please answer my previous question?
> Failsafe - duplicate class in classpath (in JAR and target/classes)
> ---
>
> Key: SUREFIRE-1286
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1286
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.19.1
> Environment: Maven 3.3.9
> Java 8
>Reporter: Christian Danninger
>Assignee: Tibor Digana
> Fix For: 2.18.1
>
>
> I'm not sure if it is releated to SUREFIRE-855. But with version 2.19.1 I got
> a class twice on my classpath (work fine with version 2.18.1). One in the
> maven module JAR and one in target/classes. This is an issue due the fact I'm
> using CDI (WELD).
> This is was my classpath is looking like (taken from
> integration-test/target/surefire/surefire5166061968440405040tmp):
> {code}#surefire
> #Wed Sep 28 15:54:06 CEST 2016
> tc.1=x.productdb.client.v2.ProductDBClientSolrImplTestIT
> tc.0=x.productdb.client.v2.HotelDataSolrImplTestIT
> classPathUrl.0=/Users/xxx/dev/git/lib/xx/integration-test/target/classes
> classPathUrl.1=/Users/xxx/dev/git/lib/xx/integration-test/target/integration-test-2.0.0-SNAPSHOT.jar
> {code}
> Location of TestSolrConfiguration.class:
> ./target/integration-test-2.0.0-SNAPSHOT.jar
> ./target/classes/de/comvel/productdb/test/TestSolrConfiguration.class
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1287) Improve logging to understand why test run failed and report the right failed category
[ https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543983#comment-15543983 ] Hudson commented on SUREFIRE-1287: -- SUCCESS: Integrated in Jenkins build maven-surefire #1633 (See [https://builds.apache.org/job/maven-surefire/1633/]) [SUREFIRE-1287] Improve logging to understand why test run failed and (tibor17: rev e0ce6cb021d42d021704f77a689e3b663aebf084) * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java * (edit) surefire-booter/src/main/java/org/apache/maven/surefire/booter/SurefireBooterForkException.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java * (edit) surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java > Improve logging to understand why test run failed and report the right failed > category > -- > > Key: SUREFIRE-1287 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1287 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Samarth Jain >Assignee: Tibor Digana > > As part of our automated jenkins builds that run after every checkin, we have > been seeing a lot of these failures: > Failed to execute goal > org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify > (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or > other error in the fork > Sample run: > https://builds.apache.org/job/Phoenix-master/1420/console > Unfortunately that bit of error information doesn't really help. It would be > good to know why exactly the fork timed out or failed. What we do know is > that some of the tests in the Junit category ParallelStatsDisabledTest failed > to complete. However, failsafe incorrectly reports the failed category as the > first category that ran. In this case it happened to be > ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off > next category run even before all the tests in the current category have > finished. I am not sure if that is by design or a bug. > FYI, [~jamestaylor]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1281) Fix permanently failing Surefire Windows Build
[ https://issues.apache.org/jira/browse/SUREFIRE-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543982#comment-15543982 ] Hudson commented on SUREFIRE-1281: -- SUCCESS: Integrated in Jenkins build maven-surefire #1633 (See [https://builds.apache.org/job/maven-surefire/1633/]) [SUREFIRE-1281] Fix permanently failing Surefire Windows Build (tibor17: rev 4b43807504d36d624ba9f72649fabd74579eceff) * (edit) surefire-integration-tests/src/test/resources/fail-fast-testng/src/test/java/pkg/CTest.java * (edit) surefire-integration-tests/src/test/resources/fail-fast-testng/src/test/java/pkg/ATest.java * (edit) surefire-integration-tests/src/test/resources/fail-fast-testng/src/test/java/pkg/BTest.java * (edit) surefire-integration-tests/src/test/resources/fail-fast-junit/src/test/java/pkg/BTest.java * (edit) surefire-integration-tests/src/test/resources/fail-fast-testng/src/test/java/pkg/DTest.java * (edit) surefire-integration-tests/src/test/resources/fail-fast-junit/src/test/java/pkg/CTest.java * (edit) surefire-integration-tests/src/test/resources/fail-fast-junit/src/test/java/pkg/ATest.java * (edit) surefire-integration-tests/src/test/resources/fail-fast-junit/src/test/java/pkg/DTest.java > Fix permanently failing Surefire Windows Build > -- > > Key: SUREFIRE-1281 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1281 > Project: Maven Surefire > Issue Type: Task > Environment: Jenkins >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > > 1. > https://builds.apache.org/job/maven-surefire-windows/org.apache.maven.surefire$surefire-integration-tests/1134/ > Error Message > time for successful test is expected to be positive > Stacktrace > java.lang.AssertionError: time for successful test is expected to be positive > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at > org.apache.maven.surefire.its.jiras.Surefire943ReportContentIT.validate(Surefire943ReportContentIT.java:132) > at > org.apache.maven.surefire.its.jiras.Surefire943ReportContentIT.doTest(Surefire943ReportContentIT.java:69) > at > org.apache.maven.surefire.its.jiras.Surefire943ReportContentIT.test_noParallel(Surefire943ReportContentIT.java:39) > 2. > https://builds.apache.org/job/maven-surefire-windows/1142/org.apache.maven.surefire$surefire-integration-tests/testReport/org.apache.maven.surefire.its/ForkModeTestNGIT/testForkModeOncePerThreadTwoThreads/ > Failed > org.apache.maven.surefire.its.ForkModeTestNGIT.testForkModeOncePerThreadTwoThreads > Error Message > number of different pids is not as expected expected:<2> but was:<1> > Stacktrace > java.lang.AssertionError: number of different pids is not as expected > expected:<2> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at > org.apache.maven.surefire.its.ForkModeIT.assertDifferentPids(ForkModeIT.java:171) > at > org.apache.maven.surefire.its.ForkModeIT.testForkModeOncePerThreadTwoThreads(ForkModeIT.java:105) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6098) Unable to run Maven test. Getting org.apache.maven.surefire.util.SurefireReflectionException:
[ https://issues.apache.org/jira/browse/MNG-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544365#comment-15544365 ] V Ravi Sankar commented on MNG-6098: Thank you very much. Upgrading to 2.19.1 worked like magic.. Thanks again. I am trying to do the second one ...need some help here.. I navigated to .m2\repository\org\testng\testng and see tons of testng folders there. Among them 5.14.3, 5.14.4, 5.14.5 are the 3. Should I delete the 3 folders directly? and if so, after that what should I do? > Unable to run Maven test. Getting > org.apache.maven.surefire.util.SurefireReflectionException: > -- > > Key: MNG-6098 > URL: https://issues.apache.org/jira/browse/MNG-6098 > Project: Maven > Issue Type: Question > Components: Dependencies, POM >Affects Versions: 3.3.9 > Environment: Windows 10 >Reporter: V Ravi Sankar >Priority: Blocker > > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building MavenSelenium3 0.0.1-SNAPSHOT > [INFO] > > [WARNING] The POM for org.testng:testng:jar:5.14.3 is invalid, transitive > dependencies (if any) will not be available, enable debug logging for more > details > [WARNING] The POM for org.testng:testng:jar:5.14.4 is invalid, transitive > dependencies (if any) will not be available, enable debug logging for more > details > [WARNING] The POM for org.testng:testng:jar:5.14.5 is invalid, transitive > dependencies (if any) will not be available, enable debug logging for more > details > [INFO] > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ > MavenSelenium3 --- > [WARNING] Using platform encoding (Cp1252 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ > MavenSelenium3 --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ > MavenSelenium3 --- > [WARNING] Using platform encoding (Cp1252 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ > MavenSelenium3 --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ MavenSelenium3 > --- > [INFO] Surefire report directory: > C:\Users\RaviVinnakota\workspace\MavenSelenium3\target\surefire-reports > --- > T E S T S > --- > Running TestSuite > org.apache.maven.surefire.util.SurefireReflectionException: > java.lang.reflect.InvocationTargetException; nested exception is > java.lang.reflect.InvocationTargetException: null > java.lang.reflect.InvocationTargetException > 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:497) > at > org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at > org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at > org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: org.apache.maven.surefire.testset.TestSetFailedException: Unknown > TestNG version 6.9.13.6 > at > org.apache.maven.surefire.testng.TestNGExecutor.getConfigurator(TestNGExecutor.java:207) > at > org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:174) > at > org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at > org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) > ... 9 more > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total
[jira] [Comment Edited] (MNG-6098) Unable to run Maven test. Getting org.apache.maven.surefire.util.SurefireReflectionException:
[ https://issues.apache.org/jira/browse/MNG-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544365#comment-15544365 ] V Ravi Sankar edited comment on MNG-6098 at 10/4/16 5:07 AM: - Thank you very much Guillaume Boué. Upgrading to 2.19.1 worked like magic.. Thanks again. I am trying to do the second one ...need some help here.. I navigated to .m2\repository\org\testng\testng and see tons of testng folders there. Among them 5.14.3, 5.14.4, 5.14.5 are the 3. Should I delete the 3 folders directly? and if so, after that what should I do? was (Author: v ravi sankar): Thank you very much. Upgrading to 2.19.1 worked like magic.. Thanks again. I am trying to do the second one ...need some help here.. I navigated to .m2\repository\org\testng\testng and see tons of testng folders there. Among them 5.14.3, 5.14.4, 5.14.5 are the 3. Should I delete the 3 folders directly? and if so, after that what should I do? > Unable to run Maven test. Getting > org.apache.maven.surefire.util.SurefireReflectionException: > -- > > Key: MNG-6098 > URL: https://issues.apache.org/jira/browse/MNG-6098 > Project: Maven > Issue Type: Question > Components: Dependencies, POM >Affects Versions: 3.3.9 > Environment: Windows 10 >Reporter: V Ravi Sankar >Priority: Blocker > > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building MavenSelenium3 0.0.1-SNAPSHOT > [INFO] > > [WARNING] The POM for org.testng:testng:jar:5.14.3 is invalid, transitive > dependencies (if any) will not be available, enable debug logging for more > details > [WARNING] The POM for org.testng:testng:jar:5.14.4 is invalid, transitive > dependencies (if any) will not be available, enable debug logging for more > details > [WARNING] The POM for org.testng:testng:jar:5.14.5 is invalid, transitive > dependencies (if any) will not be available, enable debug logging for more > details > [INFO] > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ > MavenSelenium3 --- > [WARNING] Using platform encoding (Cp1252 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ > MavenSelenium3 --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ > MavenSelenium3 --- > [WARNING] Using platform encoding (Cp1252 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ > MavenSelenium3 --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ MavenSelenium3 > --- > [INFO] Surefire report directory: > C:\Users\RaviVinnakota\workspace\MavenSelenium3\target\surefire-reports > --- > T E S T S > --- > Running TestSuite > org.apache.maven.surefire.util.SurefireReflectionException: > java.lang.reflect.InvocationTargetException; nested exception is > java.lang.reflect.InvocationTargetException: null > java.lang.reflect.InvocationTargetException > 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:497) > at > org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at > org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at > org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: org.apache.maven.surefire.testset.TestSetFailedException: Unknown > TestNG version 6.9.13.6 > at > org.apache.maven.surefire.testng.TestNGExecutor.getConfigurator(TestNGExecutor.java:207) > at > org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:174) > at > org.apache.maven.surefire.te
