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

FindBugsValidator.java:66-71: Create integration tests to check... #352

Closed
davvd opened this issue Jan 1, 2015 · 13 comments
Closed

FindBugsValidator.java:66-71: Create integration tests to check... #352

davvd opened this issue Jan 1, 2015 · 13 comments

Comments

@davvd
Copy link

davvd commented Jan 1, 2015

Puzzle 149-fa59b6ee in qulice-findbugs/src/main/java/com/qulice/findbugs/FindBugsValidator.java:66-71 has to be resolved: Create integration tests to check that FindBugsValidator can exclude classes from check. see http://findbugs.sourceforge.net/manual/filter.html for details of findbug filter patterns. Don't forget to update example-exclude.apt.vm with example for findbugs exclusion.

If you have any technical questions, don't ask me, submit new tickets instead


- `352-f6cf61e2`/#421 (by Michal Kordas)
@davvd
Copy link
Author

davvd commented Jan 1, 2015

@alevohin this task is yours, please help (see our key principles of work). If you have any technical questions, don't hesitate to ask right here

The cost of this task is 30 mins (this is exactly how much will be paid, not less not more), when the task is done

@davvd davvd added IMP labels Jan 1, 2015
alevohin pushed a commit to alevohin/qulice that referenced this issue Jan 2, 2015
@davvd
Copy link
Author

davvd commented Jan 14, 2015

@alevohin you're working with this issue for 13 days already. as a reminder, don't forget to remove the @todo puzzle from the source code. -30 to your rating, your total score is +135

@alevohin
Copy link

@davvd your comment looks strange because PR #357 for this issue created 12 days ago. And you were looking for reviewer for 12 days.

@yegor256
Copy link
Owner

@davvd we need more time here, obviously

@davvd
Copy link
Author

davvd commented Jan 16, 2015

@davvd we need more time here, obviously

@yegor256 of course, thanks for letting me know, take your time

@alevohin
Copy link

@davvd PR #357 was merged. Please check and close issue.

1 similar comment
@alevohin
Copy link

@davvd PR #357 was merged. Please check and close issue.

@davvd
Copy link
Author

davvd commented Jan 19, 2015

once 352-f6cf61e2 puzzle is resolved, this ticket will be complete

@alevohin
Copy link

@davvd could you explain what does it mean?

once 352-f6cf61e2 puzzle is resolved, this ticket will be complete

@yegor256
Copy link
Owner

@alevohin this means that the problem will be fully (!) fixed when this puzzle is resolved. Your job is done here already. This information is for us to track the big scope of the project.

@davvd
Copy link
Author

davvd commented Jan 20, 2015

Closing this issue now...

@davvd davvd closed this as completed Jan 20, 2015
@davvd
Copy link
Author

davvd commented Jan 20, 2015

@alevohin Thanks a lot, I just topped your account for 30 mins, transaction ID 50519039; +30 to your rating, your total score is +195

@davvd
Copy link
Author

davvd commented Feb 29, 2016

@krzyk the last puzzle 352-f6cf61e2/#421 originated from here solved

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

No branches or pull requests

3 participants