-
Notifications
You must be signed in to change notification settings - Fork 23
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
RunMojo.java:43-45: Let's avoid code duplication between... #42
Comments
@jrdalpra please proceed, it's yours |
@dmarkov I don't really think that this is a good issue. There's no code duplication here. https://github.com/jcabi/jcabi-dynamodb-maven-plugin/blob/master/src/main/java/com/jcabi/dynamodb/maven/plugin/Instances.java already encapsulates all the work. |
@jrdalpra the difference between |
StartMojo launches dynamodb on a thread; the thread is killed once the jvm ends. RunMojo launches dynamodb on the main thread.
Two ways to build software: |
@pinaf I'm not seeing this difference at souce code. Can you show me line? Thanks. |
@yegor256 looks like this issue is invalid as @simonjenga fixed it in another PR (#43) |
@dmarkov can you close the issue? thanks. |
@yegor256 Closing, thanks all |
@dmarkov thanks :) |
@dmarkov all puzzles are solved |
1 similar comment
@dmarkov all puzzles are solved |
Puzzle
41-e81ff08d
insrc/main/java/com/jcabi/dynamodb/maven/plugin/RunMojo.java:43-45
has to be resolved: Let's avoid code duplication between this class andStartMojo
. One idea is to create a decorator calledThreadedMojo
that receives another mojo in its constructor and, when called, runs it inside a thread.... The puzzle was created by Denis N. Antonioli on 17-Dec-2015.If you have any technical questions, don't ask me, submit new tickets instead
- `42-3038f9e6`/#46 (by )
The text was updated successfully, but these errors were encountered: