Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lcov 1.11 + CocoaPod + Cobertura #29

Merged
merged 26 commits into from
Mar 21, 2015
Merged

Lcov 1.11 + CocoaPod + Cobertura #29

merged 26 commits into from
Mar 21, 2015

Conversation

designatednerd
Copy link
Contributor

This pull request is to add lcov 1.11 (addressing #24) as well as adding support for adding the tool via CocoaPods. I've updated the README to show the appropriate instructions - the TL;DR is it's less flexible, but WAY easier to get started.

If you do want to add CocoaPods support, please tag your repo once this is merged in with 1.0.0 and then push up to the CocoaPods trunk.

Please let me know if you have any questions whatsoever.

@designatednerd designatednerd changed the title Lcov 1.11 + CocoaPod Lcov 1.11 + CocoaPod + Cobertura Dec 5, 2014
@designatednerd
Copy link
Contributor Author

Most recent changes will use the lcov-to-cobertura-xml python script to also output Cobertura XML should you work with a front-end that can ingest it.

@emartynov
Copy link

What are news for this pull request?

@designatednerd
Copy link
Contributor Author

@jonreid Just updated so this can be auto-merged. Is there anything else I can do to facilitate getting this merged down?

jonreid added a commit that referenced this pull request Mar 21, 2015
Lcov 1.11 + CocoaPod + Cobertura
@jonreid jonreid merged commit 99e8c2a into jonreid:master Mar 21, 2015
@jonreid
Copy link
Owner

jonreid commented Mar 21, 2015

Wow, I didn't know there was activity on XcodeCoverage. This looks awesome, thanks for pinging.

@designatednerd
Copy link
Contributor Author

You bet - let me know if there's anything I can do to help get a pod up onto trunk - The changes I'd made since originally opening the PR would mean the current version should get tagged as 1.0.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants