-
Notifications
You must be signed in to change notification settings - Fork 111
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
DefaultMavenEnvironmentTest.java:136-143: Ideally integration test is required... #699
Comments
@dskalenko please pick this up, and keep in mind these instructions. Any technical questions - ask right here. 30 mins is the budget of the task. This is exactly how much will be paid when the problem is solved (no matter how much time you will actually spend). See this for more information |
…ation test is required
@davvd need more time for code review |
@dskalenko will take a look, thanks |
@dskalenko of course, thanks for letting me know, take your time |
…ation test is required revert changes of PUZZLES file
…ation test is required(add new line to the end of the files)
@davvd this is not urgent |
@krzyk I am closing it, thanks all |
@dskalenko I added 30 mins to your account, many thanks for working with the project (79409485)! The completion time here was 552 hours and 14 mins.; +30 added to your rating, current score is: +105 |
@davvd this is not urgent |
Puzzle
676-be080182
inqulice-maven-plugin/src/test/java/com/qulice/maven/DefaultMavenEnvironmentTest.java:136-143
has to be resolved: Ideally integration test is required to reproduce NPE in issue #676. To reproduce problem firstly revert changes marked with #676, then add to pom.xml of IT project at least one exclude rule in configuration.excludes block and dependency (in my case worked org.hibernate:hibernate-annotations:3.5.6-Final). Suggestion is that dependency must be compile-time scope as far as JUnit didn't work as test-scope dependency.... The puzzle was created by Viktor Kuchyn on 9-Feb-2016.If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code.
The text was updated successfully, but these errors were encountered: