naaman

#!/usr/bin/env bash
mkdir vim
curl https://s3.amazonaws.com/heroku-vim/vim-7.3.tar.gz --location --silent | tar xz -C vim
export PATH=$PATH:/app/vim/bin

naaman

pane() {
  local currentDir=$(pwd)
  osascript <<EOD 
tell application "iTerm"
  tell application "System Events" to keystroke "d" using command down
  tell current session of current terminal
    write text "cd $currentDir"
    write text "$@"
  end tell
end tell

naaman

package models;

import org.codehaus.jackson.annotate.JsonIgnoreProperties;

import javax.xml.bind.annotation.XmlRootElement;
import java.io.Serializable;

/**
 * TODO: Javadoc
 *

naaman

logs
project/project
project/target
target
tmp

naaman

for app in $(heroku apps); do heroku apps:destroy --app $app --confirm $app; done

naaman

Hot Swapping With Maven, Jetty and IntelliJ

Based on Configuring Jetty, Maven, and Eclipse together with Hot Swap

I've always been a bit jealous when it comes to the Play! framework and the great dev mode they have for hot swapping classes at runtime. Jetty has a configuration setting, scanIntervalSeconds, that mimics this when working with a more traditional WAR, but does so by looking for changes to a file and restarting the server.

Fortunately, Jetty also provides the ability to rapidly test code with hot swapping. No more server restarts. The trick to getting hot swapping to work is to attach a remote debugger to your Jetty process. The following instructions outline how to do this in IntelliJ (tested with IDEA 10.5 CE).

Modify your jetty-maven-plugin to ignore the scan interval

1. Open your pom and locate the plugins section