Displaying #maven/2017-01-07.log:

Sat Jan 7 00:35:39 2017  jimklo:Joined the channel
Sat Jan 7 01:04:50 2017  jimklo_:Joined the channel
Sat Jan 7 01:36:54 2017  conan:Joined the channel
Sat Jan 7 02:05:49 2017  Sasazuka:Joined the channel
Sat Jan 7 02:06:30 2017  tsunamie:Joined the channel
Sat Jan 7 07:18:57 2017  ManosGEM:Joined the channel
Sat Jan 7 07:55:55 2017  jknetl:Joined the channel
Sat Jan 7 08:53:32 2017  lefou:Joined the channel
Sat Jan 7 10:52:42 2017  thc202:Joined the channel
Sat Jan 7 15:01:55 2017  jsightler:Joined the channel
Sat Jan 7 16:49:39 2017  ManosGEM:Joined the channel
Sat Jan 7 17:48:35 2017  toogley:Joined the channel
Sat Jan 7 18:43:08 2017  __JavaMonkey:Joined the channel
Sat Jan 7 18:47:30 2017  __JavaMonkey:I have a maven project with multiple test files annotated with testng "Test" annotation. The pom file does not use the surefire plugin, but of course tests do run when mvn test is invoked. The interesting thing is SOME tests definitely DO NOT run, but I cannot see how they are excluded. I discovered this group of non-running tests after introducing the surefire plugin and testng suite files. This configuration causes all the tests to
Sat Jan 7 19:32:24 2017  denisMone:Joined the channel
Sat Jan 7 19:36:31 2017  toogley1:Joined the channel
Sat Jan 7 19:37:34 2017  denisMone:Joined the channel
Sat Jan 7 19:39:47 2017  toogley:Joined the channel
Sat Jan 7 22:02:23 2017  conan:Joined the channel
Sat Jan 7 22:31:39 2017  toogley:Joined the channel

Comments