sbt 0.11.2 and lifty 1.7.4: Wasn't able to parse json file...

33 views
Skip to first unread message

Alex

unread,
Jan 8, 2012, 9:54:07 AM1/8/12
to Lifty
Hi,

I have tried to upgrade lifty to 1.7.4. After changed my ~/.sbt/
plugins/build.sbt so it has

addSbtPlugin("org.lifty" % "lifty" % "1.7.4")

and run

lifty delete lift
lifty learn lift https://raw.github.com/Lifty/lifty/master/lifty-recipe/lifty.json

I get an error message: Wasn't able to parse json file: /home/
alex/.lifty/lift/lift.json

Cheers,
Alex

Mads Hartmann

unread,
Jan 8, 2012, 10:14:29 AM1/8/12
to li...@googlegroups.com
Hi, 

Please delete the entire ~/.lifty folder

rm -rf ~/.lifty

Now try again :) 

Alex

unread,
Jan 9, 2012, 4:17:45 PM1/9/12
to Lifty
Hi Mads,

I tried it, but it didn't help. Further ideas?

Cheers,
Alex
Message has been deleted

Mads Hartmann

unread,
Jan 9, 2012, 4:37:12 PM1/9/12
to li...@googlegroups.com
Please try to remove your ~/.sbt/plugins/project/target and your ~/.sbt/plugins/target folders .. I might be that it hasn't recompiled with the new version.

I have 1.7.4 installed here and it works fine.

I hope this helps,
Mads

Alex

unread,
Jan 9, 2012, 4:49:15 PM1/9/12
to Lifty
Hi,

it didn't help too.
But I have started sbt in a fresh directory and tried it again. It
seems to work now. Thanks!

Cheers,
Alex

Mads Hartmann Jensen

unread,
Jan 9, 2012, 4:52:15 PM1/9/12
to li...@googlegroups.com
Hmm, that is weird - but I'm glad that you got it working! :)

Alex

unread,
Jan 11, 2012, 5:04:53 PM1/11/12
to Lifty
Hi,

I've invested some time into this problem and it seems to be the
character "-" in the directory name: My-Project.

If I start sbt in a directory with a "-" in it's name and run
something like lifty update lift, I got an error message (Wasn't able
to parse...). But if I start sbt in a directory without "-" in it's
name, lifty update lift works fine.

Bug or feature?

Cheers,
Alex

Mads Hartmann

unread,
Jan 11, 2012, 5:56:20 PM1/11/12
to li...@googlegroups.com
Thanks for taking a deeper look into this! :) It's definitely a bug - I'll take a look at it.
Reply all
Reply to author
Forward
0 new messages