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

Unable To Export Results #97

Open
Donwangugi opened this issue Jun 27, 2014 · 4 comments
Open

Unable To Export Results #97

Donwangugi opened this issue Jun 27, 2014 · 4 comments

Comments

@Donwangugi
Copy link

Unless I know otherwise. It is not easy for me to export the results to someone else. I am a security researcher on a team with developers. I wanted to run this tool, prune the false positives and then export the results to the developers so that they could handle them.

@VioletGiraffe
Copy link
Owner

What format would you like to export in? Would something like CSV do?

@Dmitry-Me
Copy link
Collaborator

Why wouldn't the developers run the thing? They should know the code better and so have a better idea of whether a specific warning is a false positive.

@VioletGiraffe
Copy link
Owner

Yes, I agree, that is a very reasonable argument.

@Donwangugi
Copy link
Author

In our scenario the developers who own the code I have discovered issues in do not use FindBugs. So I could tell them to install and run the tool but it would be easier and makes more sense if I could send them a report out.

I think XML or CSV makes sense.

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

No branches or pull requests

3 participants