Hi guys,
Hope you are doing well!
I'm having a weird issue with Maven and would like to know if any of you is facing something similar with your KillBill plugins.
I've succesfully developed a new Java Plugin based on the killbill-plugin-framework.
The issue is that after adding a couple of Unit tests (using JUnit and Mockito) now Maven can't succesfully Build my project.
Before adding the Unit tests and all its dependencies I was able to run "mvn clean install" without any issue.
Now when I run it, during the "maven-surefire-plugin" goal I have the following error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on project XXX-XXX-plugin: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test failed: There was an error in the forked process
[ERROR] java.lang.RuntimeException: Unable to load category: fast
I've been researching and found out that this "fast" category is an specified "group" of tests of the KillBill Core.
Question is: why is Maven trying to run that group of Tests of the Core if I don't have them in my Plugin code?
Should I use TestNG instead of JUnit and always use the annotation @BeforeClass(groups = "fast") in my tests? (I've seen that in other Java plugins)
Another thing: telling Maven to use the profile "jdk18" solves the issue and the Build runs without problems.
That is:
mvn clean install -P jdk18
Should I always run Maven with the profile jdk18?
That could be an issue for me, because it fails when I try to build it from Travis for example.
Hope you can help me!
Thanks in advance.
Regards,
Javier.