[Lift] Re: Directory structure

2009-12-20 Thread Timothy Perrett
Agreed. Its annoying, but right now I think we are probably stuck with
it.

Cheers, Tim

On Dec 20, 9:06 pm, Indrajit Raychaudhuri indraj...@gmail.com wrote:
 On 21/12/09 2:18 AM, Alex Boisvert wrote:

  I don't think it's worth a lot of effort.   If it's been tried and
  doesn't work nicely, I'm fine with sticking with the current structure.

  At some point, though, you have to decide who's boss, you or the build
  system ;)

  (I love taking jabs at Maven, sorry)

 So do I, no worries. Ironically, Maven is still getting away with all these!

 - IRC





  alex

  On Sun, Dec 20, 2009 at 12:42 PM, Indrajit Raychaudhuri
  indraj...@gmail.com mailto:indraj...@gmail.com wrote:

      Alex,

      Yes, it's possible to have artifactId ≠ directoryName for Maven
      projects. But last time I did this Maven chose to be very cruel with me
      (site generation, relative path resolutions etc. broke).

      Also see the point and convergence to decision here:
     http://groups.google.com/group/liftweb/msg/73a5652a55076384

      In this case, I would usually type out cd liftcore blindly and the
      right thing would happen automatically thanks to shopt -s cdspell in
      my .bashrc config. But I digress.

      However, I won't mind re-opening this discussion on 'lift-' prefix if
      you want me to.

      Cheers, Indrajit

      On 21/12/09 1:29 AM, Alex Boisvert wrote:
        While we're discussing lift-core in a separate thread, I wanted
      to bring
        up a minor annoyance

        All module directories in the repository start with lift-,

        boisv...@smudge:~/git/liftweb$ tree -L 2 | grep lift
        |-- lift-archetypes
        |   |-- lift-archetype-basic
        |   |-- lift-archetype-blank
        |   |-- lift-archetype-jpa-basic
        |   |-- lift-archetype-jpa-blank
        |   |-- lift-archetype-jpa-blank-single
        |-- lift-base
        |   |-- lift-actor
        |   |-- lift-common
        |   |-- lift-json
        |   |-- lift-util
        |   |-- lift-webkit
        |-- lift-core
        |-- lift-examples
        |   |-- hellolift
        |-- lift-misc
        |   |-- lift-installer
        |-- lift-modules
        |   |-- lift-amqp
        |   |-- lift-facebook
        |   |-- lift-jta
        |   |-- lift-machine
        |   |-- lift-oauth
        |   |-- lift-openid
        |   |-- lift-osgi
        |   |-- lift-paypal
        |   |-- lift-testkit
        |   |-- lift-textile
        |   |-- lift-widgets
        |   |-- lift-wizard
        |   |-- lift-xmpp
        |-- lift-persistence
        |   |-- lift-jpa
        |   |-- lift-mapper
        |   |-- lift-record

        This naming isn't very practical when navigating the directory
      structure
        since it meddles with completion.

        e.g.  cd TAB (beep!) lift- TAB (beep!) c TAB (finally completes
        core)

        Does Maven support simpler names?  Could we have something like this?

        |-- base
        |   |-- actor
        |   |-- common
        |   |-- json
        |   |-- util
        |   |-- webkit
        |-- modules
        |   |-- amqp
        |   |-- ...
        |   |-- ...

        (I'm not suggesting change the names of the modules;  just the
      names of
        the directories)

        alex

        --

        You received this message because you are subscribed to the Google
        Groups Lift group.
        To post to this group, send email to liftweb@googlegroups.com
      mailto:liftweb@googlegroups.com.
        To unsubscribe from this group, send email to
        liftweb+unsubscr...@googlegroups.com
      mailto:liftweb%2bunsubscr...@googlegroups.com.
        For more options, visit this group at
       http://groups.google.com/group/liftweb?hl=en.

      --

      You received this message because you are subscribed to the Google
      Groups Lift group.
      To post to this group, send email to liftweb@googlegroups.com
      mailto:liftweb@googlegroups.com.
      To unsubscribe from this group, send email to
      liftweb+unsubscr...@googlegroups.com
      mailto:liftweb%2bunsubscr...@googlegroups.com.
      For more options, visit this group at
     http://groups.google.com/group/liftweb?hl=en.

  --

  You received this message because you are subscribed to the Google
  Groups Lift group.
  To post to this group, send email to lift...@googlegroups.com.
  To unsubscribe from this group, send email to
  liftweb+unsubscr...@googlegroups.com.
  For more options, visit this group at
 http://groups.google.com/group/liftweb?hl=en.

--

You received this message because you are subscribed to the Google Groups 
Lift group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.




[Lift] Re: directory structure

2009-06-17 Thread Derek Chen-Becker
The default behavior is to look at for a snippets sub-package to any
packages you've configured for snippets, so yes, that's required if you're
using snippets. If you're not using a particular feature (i.e. snippets,
views, or comet) then the directory can be missing, I think. I can't
remember if there's anything special about the model subdirectory or if
that's just convention.

Derek

On Tue, Jun 16, 2009 at 7:35 PM, Oliver Lambert olambo...@gmail.com wrote:

 In Boot.scala can I call LiftRules.addToPackages multiple times to add
 multiple directories with snippets in them?

 Do I have to have a directory structure ending with snippet, for snippets?
 Do I need the directories comet, model and view, when they are just empty?

 cheers
 Oliver

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---