Hi, Now that I'm able to commit code into Lift (evil grin :-) I would like to adapt a workflow that works for me. I think I'll be more productive if I can hack Lift together alongside my project and not have to switch context all the time.
I've previously added some of the lift modules (e.g mapper) to my eclipse workspace when I needed to try out something and this seem to work for local development. But I need the changes I make to Lift to be picked up by my colleagues, our CI server etc before they make it into Lift master. I see two ways to solve this: 1) I build Lift locally and stuff the jars into a maven repo somewhere. Problem: This maven repo should be globally accessible on the net somewhere. Can you host a maven repo on github? Can Lift be deployed there? 2) I add the Lift modules of interest to our own repo (which is in svn) and include it in our build. This may be a little awkward when changing Lift branches etc. but it looks doable... Any hints or suggestions? /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
