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

Add maven goal for PIT report generation and maven site integration #10

Closed
hcoles opened this issue Jan 7, 2014 · 12 comments
Closed

Add maven goal for PIT report generation and maven site integration #10

hcoles opened this issue Jan 7, 2014 · 12 comments
Labels

Comments

@hcoles
Copy link
Owner

hcoles commented Jan 7, 2014

From [email protected] on September 18, 2011 13:45:09

PIT is currently hard coded to produce only a html report (see Issue 9 ). After revising the reporting stuff an enhanced maven plugin would be nice that generates a report integrated into the maven site.

Original issue: http://code.google.com/p/pitestrunner/issues/detail?id=10

@dustinbarnes
Copy link

Is there any plan to get this in there? I'm currently trying to hack around it, but this would be the thing that really cleanly integrates into the code quality lifecycle.

@hcoles
Copy link
Owner Author

hcoles commented Feb 26, 2015

@dustinbarnes Although I agree this would be good to have, I'm afraid it is unlikely to happen unless some-one jumps in and contributes a fix.

@dustinbarnes
Copy link

That sounds fair enough. It's not so much a fix as a new feature request, really.

If I have some time, I might take a whack at it. I've created some maven mojo plugins, but never a reporting plugin. People can always go modify a site.xml and dump the PIT stuff into the ${basedir}/target/site directory, but it's kind of a pain.

@hcoles
Copy link
Owner Author

hcoles commented Feb 28, 2015

Pull requests gratefully received.

@jasonmfehr
Copy link
Contributor

I'm working on writing a reporting mojo. I'm not very far along, and given my current schedule, it will be a few weeks. If you need it quicker and are going to work on it, please let me know so I can stop working on mine.

jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Mar 11, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Mar 11, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Mar 11, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Mar 14, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Mar 14, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Mar 14, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 7, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 7, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 7, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 9, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 9, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 9, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 14, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 15, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 19, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 20, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 20, 2015
hcoles added a commit that referenced this issue Apr 28, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 29, 2015
jasonmfehr pushed a commit to jasonmfehr/pitest that referenced this issue Apr 29, 2015
@lkwg82
Copy link
Contributor

lkwg82 commented May 17, 2015

I'm curious about the status.

@jasonmfehr
Copy link
Contributor

The initial development is done (other than fixing the long running integration tests). In its current state, the reporting mojo simply copies the contents of the target/pit-reports directory.

I really want to add the ability to use the xml or csv files along with the doxia sink to generate a report that is fully integrated into the maven site, but that is not something I will have time to work on for a couple months. If anyone else wants to work on it, I would be more than willing to help out where I can.

@lkwg82
Copy link
Contributor

lkwg82 commented May 19, 2015

Maybe this issue can be split into done and to do? An issue with commits and status unfinished for long time looks like some blocker.

This makes the status and progress much more clearer.

@jasonmfehr
Copy link
Contributor

Yeah, definitely. Want me to take care of closing down this issue an opening a new one?

@lkwg82
Copy link
Contributor

lkwg82 commented May 20, 2015

Would be the best. You are on the topic and you know what have done and what is open. This also supports the maintainer to make releases and release notes. Thx.

jasonmfehr added a commit to jasonmfehr/pitest that referenced this issue May 25, 2015
jasonmfehr added a commit to jasonmfehr/pitest that referenced this issue May 25, 2015
jasonmfehr added a commit to jasonmfehr/pitest that referenced this issue May 27, 2015
@jasonmfehr
Copy link
Contributor

A basic report mojo has been implemented and will be available with pitest-maven 1.1.6. Issue #209 was created to further the work on the report mojo. Please close this issue as done.

@lkwg82
Copy link
Contributor

lkwg82 commented Jul 27, 2015

this can be closed

@hcoles hcoles closed this as completed Jul 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants