jpi new NAME failing
drnic opened this issue · 7 comments
drnic commented
$ jpi new ey-deploy
"new" was called incorrectly. Call as "jpi new NAME".
$ jpi new eydeploy
"new" was called incorrectly. Call as "jpi new NAME".
$ jpi new NAME
"new" was called incorrectly. Call as "jpi new NAME".
It seems confused.
cowboyd commented
What a regression. We need some cukes for the jpi tool. The only thing that's currently under test is the runtime gem. Let me try and track this down. Meantime, use 0.3.4. I should probably yank 0.3.5
jorgenpt commented
This only reproduces on 1.9.3 (maybe 1.9.x?) for me - it does not reproduce on 1.8.7 or JRuby 1.6.5.1.
cowboyd commented
I see it also on jruby 1.6.7
cowboyd commented
nvm, 0.3.5 works for me on jruby 1.6.7
mattriley commented
I was just about to write my first plugin and had the same issue on version 0.3.7
yyuu commented
This did not reproduced with jpi 0.3.8 on 1.9.3-p429, jruby-1.6.8 and jruby-1.7.4.
I want to close this issue if the problem has been fixed.
yyuu commented
Close this issue since this is not reproduced. Please reopen this if there is progress.