[jira] [Created] (SUREFIRE-2202) NullPointerException if super class is an Interface
Javier A. Ortiz created SUREFIRE-2202:
-
Summary: NullPointerException if super class is an Interface
Key: SUREFIRE-2202
URL: https://issues.apache.org/jira/browse/SUREFIRE-2202
Project: Maven Surefire
Issue Type: Bug
Components: TestNG support
Affects Versions: 3.1.2
Reporter: Javier A. Ortiz
Code is throwing a NPE when clazz.getSuperClass() returns null on the previous
iteration.
As per the JavaDocs:
{code:java}
If this {@code Class} represents either the {@code Object} class, an interface,
a primitive type, or void, then null is returned.{code}
Current code doesn't handle this case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2180) Surefire not invoking tests with TestNG DataProvider
[
https://issues.apache.org/jira/browse/SUREFIRE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741764#comment-17741764
]
Javier A. Ortiz commented on SUREFIRE-2180:
---
The issue was a bit convoluted but neither TestNG nor Sunfire were at fault. It
was a mix of a custom TestNG listener skipping the test but not logging when it
did. The test was being skipped due to another test injecting a parameter in
the environment that was causing the listener to skip the test.
Once the test cleaned properly the environment when done the issue went away.
> Surefire not invoking tests with TestNG DataProvider
>
>
> Key: SUREFIRE-2180
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2180
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 3.1.2
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I'm having a weird issue I can't figure out. It's driving me insane.
> I have a Maven project for which I'm running the same command both locally
> and on Jenkins. The environment is the same as far as I can tell:
> - Maven 3.9.2 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - JDK 11 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - TestNG 7.8.0
> Command:
> {code:java}
> mvn -Ddependency.surefire.verbose=10 -Pcoverage verify -B -U -Dgroup=PLATFORM
> {code}
> Relevant POM section:
> {code:java}
>
>
>
>
> org.jacoco
> jacoco-maven-plugin
> 0.8.10
>
> ...
>
>
> ...
>
> ...
>
>
> coverage
>
>
>
> org.jacoco
> jacoco-maven-plugin
>
>
> com/XXX/framework/dataproviders/**/*
> com/XXX/v2/basetest/**/*
> **/*Exception*
>
>
>
>
>
> prepare-agent
>
>
>
>
> report
> test
>
> report
>
>
>
>
> jacoco-check
>
> check
>
>
>
>
> BUNDLE
>
>
> INSTRUCTION
> COVEREDRATIO
> 60%
>
>
> CLASS
> MISSEDCOUNT
> 0
>
>
>
>
> PACKAGE
>
>
> LINE
> COVEREDRATIO
> 60%
>
>
>
>
> ${skipTests}
>
>
>
>
>
>
>
> {code}
> One of the tests that have the issue (only tests with DataProviders) show
> this pattern in the logs. Enabled verbose to level 10 in hopes that something
> would show up.
> Locally:
> {code:java}
> [2023-06-06 16:55:46.795] [INFO] [TestClass] Creating TestClass for
> [ClassImpl class=com.XXX.framework.utils.TimeUtilsTest]
> [2023-06-06 16:55:46.796] [INFO] Method public java.lang.Object[][]
> com.XXX.framework.utils.TimeUtilsTest.getTimeData() has a @Test annotation
> but also a return value: ignoring it. Use
> to fix this
> [2023-06-06 16:55:46.797] [INFO] [TestClass] Adding method
> TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
> instance:null] on TestClass class com.XXX.framework.utils.TimeUtilsTest
> {code}
> ...
> {code:java}
> [2023-06-06 16:55:47.316] [INFO] = Test class
> com.XXX.framework.utils.TimeUtilsTest
> [2023-06-06 16:55:47.316] [INFO] @Test
> TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
> instance:com.XXX.framework.utils.TimeUtilsTest@283eb984]
> [2023-06-06 16:55:47.316] [INFO] ==
> {code}
> ...
> {code:java}
> [TestNG] INVOKING: "Surefire test" -
> com.XXX.framework.utils.TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)(value(s):
> NANOSECONDS, 60, "60ns", TestNameParameter(customName=60 NANOSECONDS))
> {code}
> ...
> Test executes
[jira] [Commented] (SUREFIRE-2180) Surefire not invoking tests with TestNG DataProvider
[
https://issues.apache.org/jira/browse/SUREFIRE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735865#comment-17735865
]
Javier A. Ortiz commented on SUREFIRE-2180:
---
Any hints on where I can find in the code where the invocations happen? I
assumed that it would be somewhere in the SureFire TestNG Runner module.
> Surefire not invoking tests with TestNG DataProvider
>
>
> Key: SUREFIRE-2180
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2180
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 3.1.2
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I'm having a weird issue I can't figure out. It's driving me insane.
> I have a Maven project for which I'm running the same command both locally
> and on Jenkins. The environment is the same as far as I can tell:
> - Maven 3.9.2 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - JDK 11 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - TestNG 7.8.0
> Command:
> {code:java}
> mvn -Ddependency.surefire.verbose=10 -Pcoverage verify -B -U -Dgroup=PLATFORM
> {code}
> Relevant POM section:
> {code:java}
>
>
>
>
> org.jacoco
> jacoco-maven-plugin
> 0.8.10
>
> ...
>
>
> ...
>
> ...
>
>
> coverage
>
>
>
> org.jacoco
> jacoco-maven-plugin
>
>
> com/XXX/framework/dataproviders/**/*
> com/XXX/v2/basetest/**/*
> **/*Exception*
>
>
>
>
>
> prepare-agent
>
>
>
>
> report
> test
>
> report
>
>
>
>
> jacoco-check
>
> check
>
>
>
>
> BUNDLE
>
>
> INSTRUCTION
> COVEREDRATIO
> 60%
>
>
> CLASS
> MISSEDCOUNT
> 0
>
>
>
>
> PACKAGE
>
>
> LINE
> COVEREDRATIO
> 60%
>
>
>
>
> ${skipTests}
>
>
>
>
>
>
>
> {code}
> One of the tests that have the issue (only tests with DataProviders) show
> this pattern in the logs. Enabled verbose to level 10 in hopes that something
> would show up.
> Locally:
> {code:java}
> [2023-06-06 16:55:46.795] [INFO] [TestClass] Creating TestClass for
> [ClassImpl class=com.XXX.framework.utils.TimeUtilsTest]
> [2023-06-06 16:55:46.796] [INFO] Method public java.lang.Object[][]
> com.XXX.framework.utils.TimeUtilsTest.getTimeData() has a @Test annotation
> but also a return value: ignoring it. Use
> to fix this
> [2023-06-06 16:55:46.797] [INFO] [TestClass] Adding method
> TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
> instance:null] on TestClass class com.XXX.framework.utils.TimeUtilsTest
> {code}
> ...
> {code:java}
> [2023-06-06 16:55:47.316] [INFO] = Test class
> com.XXX.framework.utils.TimeUtilsTest
> [2023-06-06 16:55:47.316] [INFO] @Test
> TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
> instance:com.XXX.framework.utils.TimeUtilsTest@283eb984]
> [2023-06-06 16:55:47.316] [INFO] ==
> {code}
> ...
> {code:java}
> [TestNG] INVOKING: "Surefire test" -
> com.XXX.framework.utils.TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)(value(s):
> NANOSECONDS, 60, "60ns", TestNameParameter(customName=60 NANOSECONDS))
> {code}
> ...
> Test executes and results, etc.
> On Jenkins:
> {code:java}
> [2023-06-06 21:02:29.270] [INFO] [TestClass] Creating TestClass for
> [ClassImpl class=com.XXX.framework.utils.TimeUtilsTest]
> [2023-06-06 21:02:29.271] [INFO] Method public
[jira] [Commented] (SUREFIRE-2180) Surefire not invoking tests with TestNG DataProvider
[
https://issues.apache.org/jira/browse/SUREFIRE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735316#comment-17735316
]
Javier A. Ortiz commented on SUREFIRE-2180:
---
I haven't been able to make a simple project to reproduce the issue and I can't
share my code as it is proprietary stuff from work. I was hoping for some kind
of logging I could add besides the verbose setting so I can further diagnose.
* The version of surefire is listed in the issue fields.
* Failsafe version is also 3.1.2.
This is the test:
{code:java}
import static java.util.concurrent.TimeUnit.DAYS;
import static java.util.concurrent.TimeUnit.HOURS;
import static java.util.concurrent.TimeUnit.MICROSECONDS;
import static java.util.concurrent.TimeUnit.MILLISECONDS;
import static java.util.concurrent.TimeUnit.MINUTES;
import static java.util.concurrent.TimeUnit.NANOSECONDS;
import static java.util.concurrent.TimeUnit.SECONDS;
import static org.testng.Assert.assertEquals;import com.pingidentity.Groups;
import java.util.Arrays;
import java.util.List;
import java.util.concurrent.TimeUnit;
import lombok.NonNull;
import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;
@Test(groups = Groups.PLATFORM)
public class TimeUtilsTest {
@DataProvider(parallel = true)
public Object[][] getTimeData() {
List values = Arrays.asList(TimeUnit.values());
Object[][] result = new Object[values.size()][3];
int i = 0;
for (TimeUnit tu : values) {
result[i][0] = tu;
result[i][1] = 60;
switch (tu) {
case NANOSECONDS:
result[i][2] = result[i][1] + "ns";
break;
case MICROSECONDS:
result[i][2] = result[i][1] + "us";
break;
case MILLISECONDS:
result[i][2] = result[i][1] + "ms";
break;
case SECONDS:
result[i][2] = ((int) result[i][1]) / 60 + "m";
break;
case MINUTES:
result[i][2] = ((int) result[i][1]) / 60 + "h";
break;
case HOURS:
result[i][2] = ((int) result[i][1]) / 24 + "d " + ((int)
result[i][1]) % 24 + "h";
break;
case DAYS:
result[i][2] = result[i][1] + "d";
break;
default:
throw new AssertionError(tu.name());
}
i++;
}
return result;
} @Test(dataProvider = "getTimeData")
public void testToFormattedString(
@NonNull TimeUnit timeUnit,
int value,
@NonNull String expectedValue) {
assertEquals(TimeUtils.toFormattedString(value, timeUnit), expectedValue);
}
} {code}
> Surefire not invoking tests with TestNG DataProvider
>
>
> Key: SUREFIRE-2180
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2180
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 3.1.2
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I'm having a weird issue I can't figure out. It's driving me insane.
> I have a Maven project for which I'm running the same command both locally
> and on Jenkins. The environment is the same as far as I can tell:
> - Maven 3.9.2 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - JDK 11 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - TestNG 7.8.0
> Command:
> {code:java}
> mvn -Ddependency.surefire.verbose=10 -Pcoverage verify -B -U -Dgroup=PLATFORM
> {code}
> Relevant POM section:
> {code:java}
>
>
>
>
> org.jacoco
> jacoco-maven-plugin
> 0.8.10
>
> ...
>
>
> ...
>
> ...
>
>
> coverage
>
>
>
> org.jacoco
> jacoco-maven-plugin
>
>
> com/XXX/framework/dataproviders/**/*
> com/XXX/v2/basetest/**/*
> **/*Exception*
>
>
>
>
>
> prepare-agent
>
>
>
>
> report
> test
>
> report
>
>
>
>
> jacoco-check
>
> check
>
>
>
>
> BUNDLE
>
>
> INSTRUCTION
> COVEREDRATIO
> 60%
>
>
> CLASS
> MISSEDCOUNT
> 0
>
>
>
[jira] [Updated] (SUREFIRE-2180) Surefire not invoking tests with TestNG DataProvider
[
https://issues.apache.org/jira/browse/SUREFIRE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Javier A. Ortiz updated SUREFIRE-2180:
--
Description:
I'm having a weird issue I can't figure out. It's driving me insane.
I have a Maven project for which I'm running the same command both locally and
on Jenkins. The environment is the same as far as I can tell:
- Maven 3.9.2 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
- JDK 11 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
- TestNG 7.8.0
Command:
{code:java}
mvn -Ddependency.surefire.verbose=10 -Pcoverage verify -B -U -Dgroup=PLATFORM
{code}
Relevant POM section:
{code:java}
org.jacoco
jacoco-maven-plugin
0.8.10
...
...
...
coverage
org.jacoco
jacoco-maven-plugin
com/XXX/framework/dataproviders/**/*
com/XXX/v2/basetest/**/*
**/*Exception*
prepare-agent
report
test
report
jacoco-check
check
BUNDLE
INSTRUCTION
COVEREDRATIO
60%
CLASS
MISSEDCOUNT
0
PACKAGE
LINE
COVEREDRATIO
60%
${skipTests}
{code}
One of the tests that have the issue (only tests with DataProviders) show this
pattern in the logs. Enabled verbose to level 10 in hopes that something would
show up.
Locally:
{code:java}
[2023-06-06 16:55:46.795] [INFO] [TestClass] Creating TestClass for [ClassImpl
class=com.XXX.framework.utils.TimeUtilsTest]
[2023-06-06 16:55:46.796] [INFO] Method public java.lang.Object[][]
com.XXX.framework.utils.TimeUtilsTest.getTimeData() has a @Test annotation but
also a return value: ignoring it. Use to fix
this
[2023-06-06 16:55:46.797] [INFO] [TestClass] Adding method
TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
instance:null] on TestClass class com.XXX.framework.utils.TimeUtilsTest
{code}
...
{code:java}
[2023-06-06 16:55:47.316] [INFO] = Test class
com.XXX.framework.utils.TimeUtilsTest
[2023-06-06 16:55:47.316] [INFO] @Test
TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
instance:com.XXX.framework.utils.TimeUtilsTest@283eb984]
[2023-06-06 16:55:47.316] [INFO] ==
{code}
...
{code:java}
[TestNG] INVOKING: "Surefire test" -
com.XXX.framework.utils.TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)(value(s):
NANOSECONDS, 60, "60ns", TestNameParameter(customName=60 NANOSECONDS))
{code}
...
Test executes and results, etc.
On Jenkins:
{code:java}
[2023-06-06 21:02:29.270] [INFO] [TestClass] Creating TestClass for [ClassImpl
class=com.XXX.framework.utils.TimeUtilsTest]
[2023-06-06 21:02:29.271] [INFO] Method public java.lang.Object[][]
com.XXX.framework.utils.TimeUtilsTest.getTimeData() has a @Test annotation but
also a return value: ignoring it. Use to fix
this
[2023-06-06 21:02:29.271] [INFO] [TestClass] Adding method
TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
instance:null] on TestClass class com.XXX.framework.utils.TimeUtilsTest
{code}
...
{code:java}
[2023-06-06 21:02:29.529] [INFO] = Test class
com.XXX.framework.utils.TimeUtilsTest
[2023-06-06 21:02:29.529] [INFO] @Test
TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
instance:com.XXX.framework.utils.TimeUtilsTest@52f9a620]
[2023-06-06 21:02:29.529] [INFO] ==
{code}
I see no other references about the test
[jira] [Created] (SUREFIRE-2180) Surefire not invoking tests with TestNG DataProvider
Javier A. Ortiz created SUREFIRE-2180:
-
Summary: Surefire not invoking tests with TestNG DataProvider
Key: SUREFIRE-2180
URL: https://issues.apache.org/jira/browse/SUREFIRE-2180
Project: Maven Surefire
Issue Type: Bug
Components: TestNG support
Affects Versions: 3.1.2
Reporter: Javier A. Ortiz
I'm having a weird issue I can't figure out. It's driving me insane.
I have a Maven project for which I'm running the same command both locally and
on Jenkins. The environment is the same as far as I can tell:
- Maven 3.9.2 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
- JDK 11 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
- TestNG 7.8.0
Command:
{code}
mvn -Ddependency.surefire.verbose=10 -Pcoverage verify -B -U -Dgroup=PLATFORM
{code}
Relevant POM section:
{code}
org.jacoco
jacoco-maven-plugin
0.8.10
...
...
...
coverage
org.jacoco
jacoco-maven-plugin
com/XXX/framework/dataproviders/**/*
com/XXX/v2/basetest/**/*
**/*Exception*
prepare-agent
report
test
report
jacoco-check
check
BUNDLE
INSTRUCTION
COVEREDRATIO
60%
CLASS
MISSEDCOUNT
0
PACKAGE
LINE
COVEREDRATIO
60%
${skipTests}
{code}
One of the tests that have the issue (only tests with DataProviders) show this
pattern in the logs. Enabled verbose to level 10 in hopes that something would
show up.
Locally:
{code}
[2023-06-06 16:55:46.795] [INFO] [TestClass] Creating TestClass for [ClassImpl
class=com.XXX.framework.utils.TimeUtilsTest]
[2023-06-06 16:55:46.796] [INFO] Method public java.lang.Object[][]
com.XXX.framework.utils.TimeUtilsTest.getTimeData() has a @Test annotation but
also a return value: ignoring it. Use to fix
this
[2023-06-06 16:55:46.797] [INFO] [TestClass] Adding method
TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
instance:null] on TestClass class com.XXX.framework.utils.TimeUtilsTest
{code}
...
{code}
[2023-06-06 16:55:47.316] [INFO] = Test class
com.XXX.framework.utils.TimeUtilsTest
[2023-06-06 16:55:47.316] [INFO] @Test
TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
instance:com.XXX.framework.utils.TimeUtilsTest@283eb984]
[2023-06-06 16:55:47.316] [INFO] ==
{code}
...
{code}
[TestNG] INVOKING: "Surefire test" -
com.XXX.framework.utils.TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)(value(s):
NANOSECONDS, 60, "60ns", TestNameParameter(customName=60 NANOSECONDS))
{code}
...
Test executes and results, etc.
On Jenkins:
{code}
[2023-06-06 21:02:29.270] [INFO] [TestClass] Creating TestClass for [ClassImpl
class=com.XXX.framework.utils.TimeUtilsTest]
[2023-06-06 21:02:29.271] [INFO] Method public java.lang.Object[][]
com.XXX.framework.utils.TimeUtilsTest.getTimeData() has a @Test annotation but
also a return value: ignoring it. Use to fix
this
[2023-06-06 21:02:29.271] [INFO] [TestClass] Adding method
TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
instance:null] on TestClass class com.XXX.framework.utils.TimeUtilsTest
{code}
...
{code}
[2023-06-06 21:02:29.529] [INFO] = Test class
com.XXX.framework.utils.TimeUtilsTest
[2023-06-06 21:02:29.529] [INFO] @Test
[jira] [Commented] (MENFORCER-482) enforcer:enforce is unable to find rules but works when installing
[
https://issues.apache.org/jira/browse/MENFORCER-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723151#comment-17723151
]
Javier A. Ortiz commented on MENFORCER-482:
---
This seems specific for the versions which would work on this example. Seems
that wouldn't trigger the dependency convergence either right?
> enforcer:enforce is unable to find rules but works when installing
> --
>
> Key: MENFORCER-482
> URL: https://issues.apache.org/jira/browse/MENFORCER-482
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.3.0
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I have a normal project configured as follows:
> {code:java}
>
> org.apache.maven.plugins
> maven-enforcer-plugin
>3.3.0
>
>
> enforce-versions
>
> enforce
>
>
>
>
>
> [3.9.0,)
>
>
> 11
>
>
>
>
>
> {code}
> Running _mvn install_ runs the plugin as expected but doing mvn
> enforcer:enforce leads to:
> {code}
> Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.3.0:enforce (default-cli) on
> project p14c-api-tests: No rules are configured. Use the skip flag if you
> want to disable execution. -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MENFORCER-482) enforcer:enforce is unable to find rules but works when installing
Javier A. Ortiz created MENFORCER-482:
-
Summary: enforcer:enforce is unable to find rules but works when
installing
Key: MENFORCER-482
URL: https://issues.apache.org/jira/browse/MENFORCER-482
Project: Maven Enforcer Plugin
Issue Type: Bug
Components: Plugin
Affects Versions: 3.3.0
Reporter: Javier A. Ortiz
I have a normal project configured as follows:
{code:java}
org.apache.maven.plugins
maven-enforcer-plugin
3.3.0
enforce-versions
enforce
[3.9.0,)
11
{code}
Running _mvn install_ runs the plugin as expected but doing mvn
enforcer:enforce leads to:
{code}
Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.3.0:enforce (default-cli) on
project p14c-api-tests: No rules are configured. Use the skip flag if you want
to disable execution. -> [Help 1]
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-1677) NullPointerException at org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
[
https://issues.apache.org/jira/browse/SUREFIRE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919886#comment-16919886
]
Javier A. Ortiz commented on SUREFIRE-1677:
---
Didn't see an option to close it.
> NullPointerException at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
> ---
>
> Key: SUREFIRE-1677
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1677
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1, 2.22.2, 3.0.0-M3
> Environment: Mac 10.14.5
> JDK Open JDK 11.0.3
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I have a TestNG project that worked fine on JDK 8 with 2.22.1 but moving to
> JDK 11 (both Oracle and OpenJDK) causes this error:
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun(MethodSelector.java:68)
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.includeMethod(MethodSelector.java:53)
> at org.testng.internal.RunInfo.includeMethod(RunInfo.java:50)
> at
> org.testng.internal.MethodGroupsHelper.includeMethod(MethodGroupsHelper.java:86)
> at
> org.testng.internal.MethodGroupsHelper.collectMethodsByGroup(MethodGroupsHelper.java:52)
> at
> org.testng.internal.MethodHelper.collectAndOrderMethods(MethodHelper.java:57)
> at org.testng.TestRunner.initMethods(TestRunner.java:438)
> at org.testng.TestRunner.init(TestRunner.java:271)
> at org.testng.TestRunner.init(TestRunner.java:241)
> at org.testng.TestRunner.(TestRunner.java:167)
> at
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:663)
> at org.testng.SuiteRunner.init(SuiteRunner.java:260)
> at org.testng.SuiteRunner.(SuiteRunner.java:198)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1295)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1273)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1128)
> at org.testng.TestNG.runSuites(TestNG.java:1049)
> at org.testng.TestNG.run(TestNG.java:1017)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {code}
> Had to downgrade to 2.12.4 to make it work.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (SUREFIRE-1677) NullPointerException at org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
[
https://issues.apache.org/jira/browse/SUREFIRE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919883#comment-16919883
]
Javier A. Ortiz commented on SUREFIRE-1677:
---
Tried to reproduce it to provide what you requested but I'm unable to do so.
> NullPointerException at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
> ---
>
> Key: SUREFIRE-1677
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1677
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1, 2.22.2, 3.0.0-M3
> Environment: Mac 10.14.5
> JDK Open JDK 11.0.3
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I have a TestNG project that worked fine on JDK 8 with 2.22.1 but moving to
> JDK 11 (both Oracle and OpenJDK) causes this error:
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun(MethodSelector.java:68)
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.includeMethod(MethodSelector.java:53)
> at org.testng.internal.RunInfo.includeMethod(RunInfo.java:50)
> at
> org.testng.internal.MethodGroupsHelper.includeMethod(MethodGroupsHelper.java:86)
> at
> org.testng.internal.MethodGroupsHelper.collectMethodsByGroup(MethodGroupsHelper.java:52)
> at
> org.testng.internal.MethodHelper.collectAndOrderMethods(MethodHelper.java:57)
> at org.testng.TestRunner.initMethods(TestRunner.java:438)
> at org.testng.TestRunner.init(TestRunner.java:271)
> at org.testng.TestRunner.init(TestRunner.java:241)
> at org.testng.TestRunner.(TestRunner.java:167)
> at
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:663)
> at org.testng.SuiteRunner.init(SuiteRunner.java:260)
> at org.testng.SuiteRunner.(SuiteRunner.java:198)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1295)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1273)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1128)
> at org.testng.TestNG.runSuites(TestNG.java:1049)
> at org.testng.TestNG.run(TestNG.java:1017)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {code}
> Had to downgrade to 2.12.4 to make it work.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (SUREFIRE-1677) NullPointerException at org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
[
https://issues.apache.org/jira/browse/SUREFIRE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1679#comment-1679
]
Javier A. Ortiz commented on SUREFIRE-1677:
---
Sadly it is not open source and has proprietary information.
> NullPointerException at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
> ---
>
> Key: SUREFIRE-1677
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1677
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1, 2.22.2, 3.0.0-M3
> Environment: Mac 10.14.5
> JDK Open JDK 11.0.3
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I have a TestNG project that worked fine on JDK 8 with 2.22.1 but moving to
> JDK 11 (both Oracle and OpenJDK) causes this error:
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun(MethodSelector.java:68)
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.includeMethod(MethodSelector.java:53)
> at org.testng.internal.RunInfo.includeMethod(RunInfo.java:50)
> at
> org.testng.internal.MethodGroupsHelper.includeMethod(MethodGroupsHelper.java:86)
> at
> org.testng.internal.MethodGroupsHelper.collectMethodsByGroup(MethodGroupsHelper.java:52)
> at
> org.testng.internal.MethodHelper.collectAndOrderMethods(MethodHelper.java:57)
> at org.testng.TestRunner.initMethods(TestRunner.java:438)
> at org.testng.TestRunner.init(TestRunner.java:271)
> at org.testng.TestRunner.init(TestRunner.java:241)
> at org.testng.TestRunner.(TestRunner.java:167)
> at
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:663)
> at org.testng.SuiteRunner.init(SuiteRunner.java:260)
> at org.testng.SuiteRunner.(SuiteRunner.java:198)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1295)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1273)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1128)
> at org.testng.TestNG.runSuites(TestNG.java:1049)
> at org.testng.TestNG.run(TestNG.java:1017)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {code}
> Had to downgrade to 2.12.4 to make it work.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (SUREFIRE-1677) NullPointerException at org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
[
https://issues.apache.org/jira/browse/SUREFIRE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884188#comment-16884188
]
Javier A. Ortiz commented on SUREFIRE-1677:
---
I was unable to reproduce in a smaller project. Here is a curated output with
-X flag:
{code}
cd /Users/xxx/Documents/xxx/xxx-selenium-tests;
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.0.3.jdk/Contents/Home
M2_HOME=/usr/local/apache-maven-3.5.2 /usr/local/apache-maven-3.5.2/bin/mvn
-Dtest=com.xxx.p2.auth.FacebookSocialRegisterUserTest#test
-DSELENIUM_BROWSER=chrome -DtestEnvironment=local -Dretries=1 surefire:test -X
Running NetBeans Compile On Save execution. Phase execution is skipped and
output directories of dependency projects (with Compile on Save turned on) will
be used instead of their jar artifacts.
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T02:58:13-05:00)
Maven home: /usr/local/apache-maven-3.5.2
Java version: 11.0.3, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk-11.0.3.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.5", arch: "x86_64", family: "mac"
Included /Applications/NetBeans/NetBeans
11.app/Contents/Resources/NetBeans/java/maven-nblib/netbeans-eventspy.jar
Included /Applications/NetBeans/NetBeans
11.app/Contents/Resources/NetBeans/java/maven-nblib/netbeans-cos.jar
Populating class realm maven.ext
Included /Applications/NetBeans/NetBeans
11.app/Contents/Resources/NetBeans/java/maven-nblib/netbeans-eventspy.jar
Included /Applications/NetBeans/NetBeans
11.app/Contents/Resources/NetBeans/java/maven-nblib/netbeans-cos.jar
Created new class realm maven.api
Importing foreign packages into class realm maven.api
Imported: javax.annotation.* < maven.ext
Imported: javax.enterprise.inject.* < maven.ext
Imported: javax.enterprise.util.* < maven.ext
Imported: javax.inject.* < maven.ext
Imported: org.apache.maven.* < maven.ext
Imported: org.apache.maven.artifact < maven.ext
Imported: org.apache.maven.classrealm < maven.ext
Imported: org.apache.maven.cli < maven.ext
Imported: org.apache.maven.configuration < maven.ext
Imported: org.apache.maven.exception < maven.ext
Imported: org.apache.maven.execution < maven.ext
Imported: org.apache.maven.execution.scope < maven.ext
Imported: org.apache.maven.lifecycle < maven.ext
Imported: org.apache.maven.model < maven.ext
Imported: org.apache.maven.monitor < maven.ext
Imported: org.apache.maven.plugin < maven.ext
Imported: org.apache.maven.profiles < maven.ext
Imported: org.apache.maven.project < maven.ext
Imported: org.apache.maven.reporting < maven.ext
Imported: org.apache.maven.repository < maven.ext
Imported: org.apache.maven.rtinfo < maven.ext
Imported: org.apache.maven.settings < maven.ext
Imported: org.apache.maven.toolchain < maven.ext
Imported: org.apache.maven.usability < maven.ext
Imported: org.apache.maven.wagon.* < maven.ext
Imported: org.apache.maven.wagon.authentication < maven.ext
Imported: org.apache.maven.wagon.authorization < maven.ext
Imported: org.apache.maven.wagon.events < maven.ext
Imported: org.apache.maven.wagon.observers < maven.ext
Imported: org.apache.maven.wagon.proxy < maven.ext
Imported: org.apache.maven.wagon.repository < maven.ext
Imported: org.apache.maven.wagon.resource < maven.ext
Imported: org.codehaus.classworlds < maven.ext
Imported: org.codehaus.plexus.* < maven.ext
Imported: org.codehaus.plexus.classworlds < maven.ext
Imported: org.codehaus.plexus.component < maven.ext
Imported: org.codehaus.plexus.configuration < maven.ext
Imported: org.codehaus.plexus.container < maven.ext
Imported: org.codehaus.plexus.context < maven.ext
Imported: org.codehaus.plexus.lifecycle < maven.ext
Imported: org.codehaus.plexus.logging < maven.ext
Imported: org.codehaus.plexus.personality < maven.ext
Imported: org.codehaus.plexus.util.xml.Xpp3Dom < maven.ext
Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < maven.ext
Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < maven.ext
Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < maven.ext
Imported: org.eclipse.aether.* < maven.ext
Imported: org.eclipse.aether.artifact < maven.ext
Imported: org.eclipse.aether.collection < maven.ext
Imported: org.eclipse.aether.deployment < maven.ext
Imported: org.eclipse.aether.graph < maven.ext
Imported: org.eclipse.aether.impl < maven.ext
Imported: org.eclipse.aether.installation < maven.ext
Imported: org.eclipse.aether.internal.impl < maven.ext
Imported: org.eclipse.aether.metadata < maven.ext
Imported: org.eclipse.aether.repository < maven.ext
Imported: org.eclipse.aether.resolution < maven.ext
Imported: org.eclipse.aether.spi < maven.ext
Imported: org.eclipse.aether.transfer < maven.ext
Imported:
[jira] [Commented] (SUREFIRE-1677) NullPointerException at org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
[
https://issues.apache.org/jira/browse/SUREFIRE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884174#comment-16884174
]
Javier A. Ortiz commented on SUREFIRE-1677:
---
Trying to get a sample project I can share reproducing the issue.
> NullPointerException at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
> ---
>
> Key: SUREFIRE-1677
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1677
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1, 2.22.2, 3.0.0-M3
> Environment: Mac 10.14.5
> JDK Open JDK 11.0.3
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I have a TestNG project that worked fine on JDK 8 with 2.22.1 but moving to
> JDK 11 (both Oracle and OpenJDK) causes this error:
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun(MethodSelector.java:68)
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.includeMethod(MethodSelector.java:53)
> at org.testng.internal.RunInfo.includeMethod(RunInfo.java:50)
> at
> org.testng.internal.MethodGroupsHelper.includeMethod(MethodGroupsHelper.java:86)
> at
> org.testng.internal.MethodGroupsHelper.collectMethodsByGroup(MethodGroupsHelper.java:52)
> at
> org.testng.internal.MethodHelper.collectAndOrderMethods(MethodHelper.java:57)
> at org.testng.TestRunner.initMethods(TestRunner.java:438)
> at org.testng.TestRunner.init(TestRunner.java:271)
> at org.testng.TestRunner.init(TestRunner.java:241)
> at org.testng.TestRunner.(TestRunner.java:167)
> at
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:663)
> at org.testng.SuiteRunner.init(SuiteRunner.java:260)
> at org.testng.SuiteRunner.(SuiteRunner.java:198)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1295)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1273)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1128)
> at org.testng.TestNG.runSuites(TestNG.java:1049)
> at org.testng.TestNG.run(TestNG.java:1017)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {code}
> Had to downgrade to 2.12.4 to make it work.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (SUREFIRE-1677) NullPointerException at org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
[
https://issues.apache.org/jira/browse/SUREFIRE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Javier A. Ortiz updated SUREFIRE-1677:
--
Environment:
Mac 10.14.5
JDK Open JDK 11.0.3
> NullPointerException at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
> ---
>
> Key: SUREFIRE-1677
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1677
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1, 2.22.2, 3.0.0-M3
> Environment: Mac 10.14.5
> JDK Open JDK 11.0.3
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I have a TestNG project that worked fine on JDK 8 with 2.22.1 but moving to
> JDK 11 (both Oracle and OpenJDK) causes this error:
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun(MethodSelector.java:68)
> at
> org.apache.maven.surefire.testng.utils.MethodSelector.includeMethod(MethodSelector.java:53)
> at org.testng.internal.RunInfo.includeMethod(RunInfo.java:50)
> at
> org.testng.internal.MethodGroupsHelper.includeMethod(MethodGroupsHelper.java:86)
> at
> org.testng.internal.MethodGroupsHelper.collectMethodsByGroup(MethodGroupsHelper.java:52)
> at
> org.testng.internal.MethodHelper.collectAndOrderMethods(MethodHelper.java:57)
> at org.testng.TestRunner.initMethods(TestRunner.java:438)
> at org.testng.TestRunner.init(TestRunner.java:271)
> at org.testng.TestRunner.init(TestRunner.java:241)
> at org.testng.TestRunner.(TestRunner.java:167)
> at
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:663)
> at org.testng.SuiteRunner.init(SuiteRunner.java:260)
> at org.testng.SuiteRunner.(SuiteRunner.java:198)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1295)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1273)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1128)
> at org.testng.TestNG.runSuites(TestNG.java:1049)
> at org.testng.TestNG.run(TestNG.java:1017)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {code}
> Had to downgrade to 2.12.4 to make it work.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (SUREFIRE-1677) NullPointerException at org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
Javier A. Ortiz created SUREFIRE-1677:
-
Summary: NullPointerException at
org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun
Key: SUREFIRE-1677
URL: https://issues.apache.org/jira/browse/SUREFIRE-1677
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 3.0.0-M3, 2.22.2, 2.22.1
Reporter: Javier A. Ortiz
I have a TestNG project that worked fine on JDK 8 with 2.22.1 but moving to JDK
11 (both Oracle and OpenJDK) causes this error:
{code}
java.lang.NullPointerException
at
org.apache.maven.surefire.testng.utils.MethodSelector.shouldRun(MethodSelector.java:68)
at
org.apache.maven.surefire.testng.utils.MethodSelector.includeMethod(MethodSelector.java:53)
at org.testng.internal.RunInfo.includeMethod(RunInfo.java:50)
at
org.testng.internal.MethodGroupsHelper.includeMethod(MethodGroupsHelper.java:86)
at
org.testng.internal.MethodGroupsHelper.collectMethodsByGroup(MethodGroupsHelper.java:52)
at
org.testng.internal.MethodHelper.collectAndOrderMethods(MethodHelper.java:57)
at org.testng.TestRunner.initMethods(TestRunner.java:438)
at org.testng.TestRunner.init(TestRunner.java:271)
at org.testng.TestRunner.init(TestRunner.java:241)
at org.testng.TestRunner.(TestRunner.java:167)
at
org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:663)
at org.testng.SuiteRunner.init(SuiteRunner.java:260)
at org.testng.SuiteRunner.(SuiteRunner.java:198)
at org.testng.TestNG.createSuiteRunner(TestNG.java:1295)
at org.testng.TestNG.createSuiteRunners(TestNG.java:1273)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1128)
at org.testng.TestNG.runSuites(TestNG.java:1049)
at org.testng.TestNG.run(TestNG.java:1017)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
{code}
Had to downgrade to 2.12.4 to make it work.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (MTOOLCHAINS-18) toolchain.xml file should support environment variables
[
https://issues.apache.org/jira/browse/MTOOLCHAINS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357508#comment-16357508
]
Javier A. Ortiz commented on MTOOLCHAINS-18:
I completely agree. I tried this and was surprised to see it doesn't work like
any other maven configuration file.
Kind of beats the purpose if it needs to be updated as well as the environment
variables.
> toolchain.xml file should support environment variables
> ---
>
> Key: MTOOLCHAINS-18
> URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-18
> Project: Maven Toolchains Plugin
> Issue Type: Improvement
>Affects Versions: 1.1
> Environment: Windows 7 64bit
>Reporter: Nicolas Radde
>Priority: Minor
>
> When the toolchain.xml file is configured as follow :
> {code:xml}
>
> jdk
>
> 1.8
> sun
>
>
> ${env.JDK_HOME_8}
>
>
> {code}
> The execution of a maven compile fail with the following error :
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-toolchains-plugin:
> 1.1:toolchain (default) on project monitoring-mq-web: Misconfigured
> toolchains.
> Non-existing JDK home configuration at
> L:\test-monitoring-mq\${env.JDK_HOME_8} -> [Help 1]
> {noformat}
> While the environment variable *JDK_HOME_8* exist.
> Using environment variable is a very convenient way to have the same
> toolchain.xml file for all developers or jenkins slaves and would be a nice
> addition to the plugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
