Closed vertti closed 10 years ago
Actually I bumped into the exactly same issue with this maven plugin. In my opinion there is no reason to test generated sources, because it is more likely the source generator which you want to test, not what it generates. And assuming we are using a third party library, it's not your job to test it along with your project.
See https://github.com/trautonen/coveralls-maven-plugin/blob/master/pom.xml#L247 as one solution for this problem. It just tells cobertura to ignore the generated source file. I think you could use also the plugin's explicit source directories definition and add also the generated sources dir, but as your project is multi-module project, you'd need to define the submobule source directories too and everything becomes cumbersome.
Do you think this is acceptable solution or should some extra effort be put on finding a better solution for handling generated sources?
Definitely no point in measuring coverages for generated stuff so your suggested solutions is both fine for me and probably the correct way too. I'd add a note of this to your plugins FAQ and close this issue. Thanks for your fast reply!
Added entry in the FAQ, will close now.
When running my
I get error of missing
HelpMojo.java
. My project is a maven plugin and HelpMojo is a generated resource by the maven-plugin-plugin. For some reason coveralls plugin fails to find it.Project I'm working on is https://github.com/NitorCreations/DomainReverseMapper if that helps in debugging.