This is to avoid a naming conflict with a preexisting Step Framework at http://sourceforge.net/projects/stepframework.
…-pom. This will let us keep the sbt build synchronized with the Maven build, while preserving the extra ceremonial data that Maven central requires. TODO: can the make-pom task be configured to overwrite the POMs instead of generating them to the target directory?
Conflicts: example/src/main/scala/com/thinkminimo/step/TemplateExample.scala project/build.properties project/build/src/StepProject.scala
What used to be params(":foo") before Step 2.0 is now params("foo"). Step is heavily influenced by Ruby's Sinatra, and the leading colon was a bit of Ruby syntax that was accidentally propagated into Step. Removing the colon makes Step more like the whole Sinatra family of frameworks.