Joined September 2012·
648,241 Total ProTip Views
Have at least one original repo where some form of shell script is the dominant language
Sent at least one pull request during the first 24 days of December 2013
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Would you expect anything less? Have at least one original repo where Python is the dominant language
Komodo Dragon 3
Have at least three original repos where Java is the dominant language
Have a project valued enough to be forked by someone else
Have at least one original Node.js-specific repo
Github Gameoff Participant
Participated in the Github Gameoff 2012 building a game based on git concepts of forking, branching, etc
Sent at least one pull request during the first 24 days of December 2012
Fork and commit to someone's open source project in need
Have at least one original jQuery or Prototype open source repo
Have at least one original repo where Java is the dominant language
@gembinz I haven't seen that error before. May have to google the error to see what's going wrong. If you are able to curl the endpoint, does that mean the registry container is up and running?
It should appear as a .vbox file in the folder where you saved your VM. If I have a VM named sandbox, the .vmdk, .vbox and log files are saved under C:\Users\me\VirtualBox VMs\sandbox. The file location might be different for you though.
Hope this helps.
@javicka Glad it helps. Can I get an upvote on the protip please?
@dpkkaruna can i get an upvote then? :-)
you know it, bro :-)
@jpannikk Can you write your tests outside of eclipse, say using maven?
@jpannikk Also, which patch did you use? I used the bug3271933.4.2hack.zip (dated 2012-08-15) patch.
@jpannikk c:\ccviews\jpannikkview15\ccrs_new doesn't look like a long path to me. Does your classpath includes long paths? Can you try a quick experiment by copying your test codes to a shorter path to see if that works?
Assuming you copied all the classes in the patch to the right location under the Eclipse home folder, it should work after a restart.
Let me know how it goes.
My preference is to use descriptive names over comments. No comments is better than wrong, outdated comments. I like to let the my codes speak for themselves.
Whenever I come across codes with single return statements, I am obligated to read them to the end even after I locate the relevant condition/guard clause. I think those annoying long-lived local variables are actually more time-consuming to debug..