Yup, you've about got it right.
As I understand it, Hudson uses Maven to fetch the latest code from Github,
compile, test, and deploy it. (By 'deploy' I mean: put jars, scaladocs, and
archetypes on scala-tools.org)
When commits are made to Github, it takes about an hour for changes to
appear on scala-tools.org
mvn -U forces an update. mvn (without -U) will also periodically check for
updates anyway. mvn -o forces offline (no updates) mode.
--j
On Tue, Dec 16, 2008 at 9:24 PM, Matt Harrington mbh.li...@gmail.comwrote:
A few times over the past week, I've had something of a ghost in the
machine with Maven. I haven't spent the time to track things down and
have just blown away my repository and things resolve themselves.
However, the next time Maven acts up I want to really figure things
out. It'd help if I knew more about what happens behind the scenes
with 0.10-SNAPSHOT. Here's a guess:
1.) Committers upload to github.org
2.) A machine (named hudson maybe?) builds 0.10-SNAPSHOT from the
github source (how often?)
3.) The compiled artifacts such as lift-mapper are transfered to
scala-tools.org
4.) Scaladocs are built from step 3 by scala-tools.org
5.) The lift archetypes get updated
Let's say that breaking changes are made in step 1. That will only
affect me if I run mvn -U, right?
---Matt
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
