Removal of support of Maven 2.2.1 ?

[Evgeny Mandrikov]

Hi JaCoCo Maven Plugin Users,

Maven 2.x reached its end-of-life in February 2014, and had its last release 2.2.1 in November 2009 ( https://maven.apache.org/maven-2.x-eol.html ).

Instead of maintaining compatibility with it, we'd like to focus on more interesting features, such as better support of multi-module projects.

So for upcoming JaCoCo releases we are considering removal of support of Maven 2.2.1 ( https://github.com/jacoco/jacoco/issues/194 ).

But before doing this, we'd like to hear your opinion on subject, so don't hesitate to post your thoughts here.

[Peter Ansell]

If the last release date was November 2009 then that is what its effective EOL date was/is IMO, even if the declaration was only made for February 2014.

If it is simpler to support multi-module projects with one of the recent 3.x series then I would be all for upgrading to that. Are there particular new features that you are looking at with the 3.x API that make multi-module projects simpler? Personally I have only developed one plugin, and it uses the 3.x API, so I have not used any parts of the API relating to multi-module builds and I am not familiar with the advantages of it compared to 2.x.

Thanks,

Peter

[Evgeny Mandrikov]

Hi Peter,

First of all - thank you for the answer.

And just to clarify - for now this is primarily not about some APIs/features available in 3.x, but about reduction of costs on various levels from development, testing and maintenance till answers on questions, given the limited amount of time developers behind JaCoCo can allocate to it in addition to their primary job and other open source projects.

Best regards

[labare...@gmail.com]

Hello
I have a question about Jacoco, I'm not expert.
I'm using jacoco for code coverage, for the html report generated for source code i'm confused with source code annotations with yellow. some time it marks a simple intruction as "x of y branches missed" even if no branches are declared. I don't understand why. Thank you in advance for helping me

[Evgeny Mandrikov]

Hi,

Please don't post questions into unrelated existing threads.

But answering your question: such artifacts could be observed for some constructions, because Java compiler generates bytecode, which contains branches, while source code not - one of examples is a Java 7 switch on String or try with resource. You can start a new thread with an example (screenshot) of your report in order to receive a more precise explanation for your particular example.

Thanks for your understanding.