Jeppe, How about:
-- Fork http://github.com/dpp/liftweb to http://github.com/jeppenejsum/liftweb and maintaining on your own with frequent "git pull dpp master"
-- Deploy your artifacts to an internal server (all that you need is an http server where you can 'deploy' the artifact via webdav/ssh etc.)
-- Use mirror settings for scala-tools.org (http://maven.apache.org/guides/mini/guide-mirror-settings.html) pointing to the intenal server set up above OR keep a modified resources/lift-parent/pom.xml in your forked repo (http://github.com/jeppenejsum/liftweb) with customized server location.
Cheers, Indrajit On 25/01/10 4:27 PM, Jeppe Nejsum Madsen wrote:
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 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.
