<?xml version='1.0' encoding='utf-8' ?>
<rss version='2.0'>
<channel>
	<title>neilpahl.com Logs Feed: Lift</title>
	<link></link>
	<description></description>
	<pubDate>Thu, 22 Jul 21 07:39:47 -0400</pubDate>
	<ttl>60</ttl>
	<item>
		<title>Lift:: Entry 5: Github Fork For My Personalised Skeleton Liftweb App</title>
		<description><![CDATA[I forked heiflo's github project so that I can customize it a bit and use it as my skeleton liftweb projects in the future while not having to worry about it being updated and breaking my comfortable configurations. Mainly, I just wanted to change the jetty port... repo found here:https://github.com/neildaemond/lift-basic-2.4-sbt-0.11.2.gitFeel free to clone/fork as you please]]></description>
		<pubDate>Fri, 29 Jun 12 00:17:32 -0400</pubDate>
		<link>http://archived.neilpahl.com/logs/jvm/scala/lift/5-github-fork-for-my-personalised-skeleton-liftweb-app/</link>
	</item>
	<item>
		<title>Lift:: Entry 4: Move to sbt 0.11.3 Broke Lifty</title>
		<description><![CDATA[I gave sbt 0.11.3 a go and lifty broke. I guess moving to the newest versions of sbt isn't the greatest idea, since it carries the potential for breaking its plugins. However, did I really need lifty anyways? Now I'm thinking not really.Thanks to heiflo on github who has a nice project going that has a skeleton project using lift 2.4, and sbt 0.11.2. This project contains all the configurations and such sorted out for the new versions of sbt. I just need to clone the project from https://github.com/heiflo/lift-basic-2.4-sbt-0.11.2, cd into the directory and run ./sbtThe first load takes a while to download the dependancies, but then you are set. Now onto the coding...]]></description>
		<pubDate>Thu, 28 Jun 12 00:23:54 -0400</pubDate>
		<link>http://archived.neilpahl.com/logs/jvm/scala/lift/4-move-to-sbt-0.11.3-broke-lifty/</link>
	</item>
	<item>
		<title>Lift:: Entry 3: First Steps Developing with Lift</title>
		<description><![CDATA[Ok, so I'm going to let lifty build my project and directory structure... but, I'll make it start with the project-blank recipe.So far, I installed sbt 0.10 and put the suggested build.sbt and project/plugins.sbt into the project's root folder. But it turns out that lifty can take care of all that now anyways (they were out of sync before the 1.7.5-SNAPSHOT).But, it turns out that lifty was more convinient than I thought. I origionally used the 1.7.4 version, but it had issues with it and sbt .10, so the 1.7.5-SNAPSHOT version ended up working. Installing lifty is easy, as all you need to do is create the following global sbt settings:~/.sbt/plugins/build.sbtresolvers += Resolver.url("sbt-plugin-snapshots", new URL("http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-snapshots/"))(Resolver.ivyStylePatterns)addSbtPlugin("org.lifty" % "lifty" % "1.7.5-SNAPSHOT")(leave a one line space between both statements)~/.sbt/build.sbtseq( Lifty.liftySettings : _*) And that's it to installing Lifty!]]></description>
		<pubDate>Sat, 16 Jun 12 01:22:31 -0400</pubDate>
		<link>http://archived.neilpahl.com/logs/jvm/scala/lift/3-first-steps-developing-with-lift/</link>
	</item>
	<item>
		<title>Lift:: Entry 2: Configuring SBT for Lift</title>
		<description><![CDATA[First, your going to need to install sbt. you can use your package manager like "apt-get install sbt", but last time it gave me the older version. I followed the unix instructions:Download sbt-launch.jar and place it in ~/bin.Create a script to run the jar, by placing this in a file called sbt in your ~/bin directory:java -Xms512M -Xmx1536M -Xss1M -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=384M -jar `dirname $0`/sbt-launch.jar "$@"
Make the script executable:$ chmod u+x ~/bin/sbt
Then, going through the process of figuring out sbt for the second time, I realized its actually quite easy if you follow the instructions they have on assembla. The first time was confusing because they give instructions for the outdated version (which has a higher version number [0.7 &gt; 0.10] when .10 is actually newer)Lift documentation seems to be trying to catch up to the switch from sbt 0.7 to 0.10 (i still dont get why .1 is new than .7 since .7 is clearly greater than .1,]]></description>
		<pubDate>Thu, 14 Jun 12 10:02:58 -0400</pubDate>
		<link>http://archived.neilpahl.com/logs/jvm/scala/lift/2-configuring-sbt-for-lift/</link>
	</item>
	<item>
		<title>Lift:: Entry 1: SBT or Maven?</title>
		<description><![CDATA[I've been meaning to post this for a bit, but a very strange bug caused by a third party service provided by my web host had my page rendered uneditable for a brief while. I wouldn't mind hosting this site on my own servers, but I've already paid for this place... Anyways, back to the post:At first, when I first started studying scala and lift, I was under the impression that Maven was the way to go to manage ones Lift (liftweb) projects. I began with (and still am) reading Programming in Scala (http://www.artima.com/shop/programming_in_scala) to learn the fascinating scala language.After reading enough to get an idea, I am ready to dive in and get some hands on experience with it.Really wanting to get my lift skills going, I figured I'd start with a mainly theoretical knowledge of scala,]]></description>
		<pubDate>Wed, 13 Jun 12 09:27:57 -0400</pubDate>
		<link>http://archived.neilpahl.com/logs/jvm/scala/lift/1-sbt-or-maven/</link>
	</item>
</channel>
</rss>