Review Board 1.5.4

Issue 543 -- added an SBT maven archetype

Updated 1 year, 8 months ago

David Pollak Reviewers
dpp, timperrett, marius, charles, joni, atsuhiko, jorge, naftoli, kris, indrajit, alexb, dlouwers, mstarzyk, rmellgren, jhoffman, probinett, jmadsen, mhartmann, jstrachan, jgoday
None LiftWeb-archive
https://liftweb.assembla.com/spaces/liftweb/tickets/543-sbt-archetype

dpp_issue_543

Added an archetype for creating an sbt project
Manual testing
Posted 1 year, 8 months ago (June 3rd, 2010, 10:28 a.m.)
Instead of creating altogether a separate archetype with SBT support, would it be possible to consider SBT-izing the existing basic archetype(s)?
I haven't been able to keep track of things for last few weeks, so apologies if something has already been agreed upon on this.
  1. This one is the lift-archetype-basic except with the sbt stuff added.
    
    I chose to do a separate archetype simply to call it out as sbt.
    
    There has been no discussion of this on the list, but I really wanted to get an sbt archetype in before 2.0
  2. By "separate archetype simply to call it out as sbt" do you mean an archetype explicitly marked to be used with SBT or an archetype that allows you to do "sbt clean jetty-run" similar to "mvn clean jetty:run"?
    
    I was thinking if we could do the latter. That is, have lift-archetype-basic and lift-archetype-blank SBT-ized so that people could use mvn and sbt interchangeably OOTB :)
    
  3. What I mean is an archetype with sbt in the name so that people know that it's the sbt archetype.  So, the basic archetype doesn't have sbt in the name, so it's a maven archetype.  The sbt archetype has sbt in the name so people know it's an sbt archetype... even though the sbt archetype can also be used with Maven.
    
    The decision to separate them was deliberate.  I understand the maintenance issues of having 2 nearly identical piles of bytes and the trade-off is one that I think is correct.
  4. I was not thinking from maintenance PoV. lift-archetype-basic-sbt would become a complete mirror of lift-archetype-basic with additional feature of SBT support. So there would be no distinct value in lift-archetype-basic anymore. We might as well consider deprecating lift-archetype-basic in that case.