Support analysis of pack200 jars in Jacoco analyzer

[marchof]

This request is originally inspired by this issue: jacoco/eclemma#49 . Allowing pack200'd bundles in Jacoco analyzer would allow to generate reports when jars are pack200.
This would force people to use the pack200'd jar as input rather than the classfile, but I think it's an acceptable and clean improvement.

[marchof]

@mickaelistria Can you please provide a example pack200 JAR?

[mickaelistria]

You can create one from this repo:
https://github.com/mickaelistria/bug-jacoco-pack200
just run "mvn clean verify -Ppack200" from the "api" folder, and you'll
see a pack200'd jar in repository/target/repository/plugins.

HTH

Mickael Istria
Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
My blog http://mickaelistria.wordpress.com - My Tweets
http://twitter.com/mickaelistria

[marchof]

@mickaelistria I implemented Pack200 support and attached it as a pull request to this issue. Feel free to review the implementation if you find some time.

Can you please test your scenario, here is a build of this branch: http://download.eclipselab.org/transfer/mho/jacoco-0.6.3.201303221140.zip

[buildhive]

Java Code Coverage Tools » jacoco #43 SUCCESS
This pull request looks good
(what's this?)

[Godin]

@marchof FYI results of builds of pull-requests are available from BuildHive, i.e. no need to do custom deployment somewhere. For example for this one: https://buildhive.cloudbees.com/job/jacoco/job/jacoco/43/org.jacoco$jacoco/artifact/org.jacoco/jacoco/0.6.3-SNAPSHOT/jacoco-0.6.3-SNAPSHOT.zip

[marchof]

@Godin I didn't knew results are also available for branches, thanks!