Reinhard Nägele unguiculus

A better way to set up Java web apps

If you're building a Java web app that you yourself or your organization will be deploying then you can save yourself a lot of trouble by avoiding the whole build-to-war + deploy-to-server approach. Instead, you should build your web app as a normal Java application with an embedded web app server. Don't build a WAR, just compile the code and serve the files out of their source location. This has the following advantages:

You can code and test iteratively because you don't have to copy files and create war packages every time you make a change. This is similar to what the mvn jetty:run command is being used for by many developers today.
You run the same exact code in production as you do in development. Hopefully I don't have to elaborate on the advantages of that. Most developers today use mvn jetty:run or similar to achieve a quick, iterative dev cycle. But come time for deployment, they build a WAR and throw it over the wall to be deployed in some app server

	import org.apache.maven.shared.dependency.analyzer.ClassAnalyzer
	import org.apache.maven.shared.dependency.analyzer.DefaultClassAnalyzer
	import org.apache.maven.shared.dependency.analyzer.DependencyAnalyzer
	import org.apache.maven.shared.dependency.analyzer.ProjectDependencyAnalysis
	import org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer
	import org.gradle.api.Project
	import org.gradle.api.artifacts.ConfigurationContainer
	import org.gradle.api.artifacts.ResolvedArtifact
	import org.gradle.api.artifacts.ResolvedDependency

	package com.squareup.example;

	public abstract BaseActivity extends SherlockActivity {
	private final ScopedBus scopedBus = new ScopedBus();

	protected ScopedBus getBus() {
	return scopedBus;
	}

	@Override public void onPause() {

	#!/usr/bin/env ruby

	require 'tempfile'
	require 'optparse'

	def parse_version(text)
	if (text.match(/^\s<version>\s(.?)\s<\/version>\s*$/))
	$1
	else
	nil