All geek questions in one place

Hudson and Maven tests run twice

Parsing POMs Discovered a new module be.howest:someproject someproject

It seems that I first found a new module when I do the hudson work. Well, there is nothing to worry about, but it seems that all this is done twice, and I do not know why. Another thing: it gives this odd error (at least for me):

 [WARNING] Removing: cobertura from forked lifecycle, to prevent recursive invocation. [WARNING] Removing: findbugs from forked lifecycle, to prevent recursive invocation.

It seems to me that he tried to execute twice, but why does this elude me. In addition, he has a module under the assembly, which I am not very familiar with, but I would not worry too much (and considered it normal) if he did not perform my tests twice.

right now it starts two phases: clean and test . I changed it to clean package because I included javadoc in the package life cycle, but nothing changed.

+4
source share
2 answers

Maven will run the tests first without any tools, then it will execute the cobertura plugin, which will process the classes and re-run all the tests. Thus, the tests will be executed twice.

+5
source

This is cobertura , which makes tests a second time.

+3
source

Source: https://habr.com/ru/post/1333228/

More articles:


All Articles