Closed amalagaura closed 9 years ago
yes, it needs some better "command". honestly I am a bit unsure: jbundle install --force
to recreate the .jbundle/classpath.rb would be possibility
Sorry, i am ignorant of the underlying issues.
What is the problem with running jbundle
or jbundle install
to simply update it.
That is expected behavior if things are out of date.
Sorry if I am being simplistic about it.
yes, regenerating the .jbundler/classpath.rb is OK.
the underlying issue was/is this #48
Thank you for work on this gem. I ran into this today.
I updated from jbundler 0.6.2 and got this warning/error (which one, not sure):
"the .jbundler/classpath.rb is stale, i.e. Gemfile or Jarfile is newer.
jbundle update
will update it"But this message is not clear. I ran
jbundle
which used to update everything. But if I runjbundle update
it ranbundle update
and updates all my gems (Rails version, etc).If I want to simply get rid of the "stale" error message, I should not have to run
bundle update
.Now I just ran
rm -rf .jbundler && jbundle
, but that is just odd.