I was able to build from the tagged source using the released parent pom, integration tests passed on Windows 7 (love it). I also was able to generate the site using the released skin.
+1 On Thu, Jan 3, 2013 at 1:27 AM, Brent Atkinson <brent.atkin...@gmail.com>wrote: > Ok, I'll run through myself as well. I appreciate the help and the > background. Thanks. > > > On Thu, Jan 3, 2013 at 12:58 AM, Brett Porter <br...@apache.org> wrote: > >> >> On 03/01/2013, at 4:34 PM, Brent Atkinson <brent.atkin...@gmail.com> >> wrote: >> >> > Hi, >> > >> > I have checked the following. >> > >> > * Sums and signatures for sources and binaries >> > * Start and configure standalone continuum >> > * Start and configure standalone continuum-buildagent >> > * Configured buildagent in continuum, built a project through the agent >> > * Inspected generated site docs >> > >> > Everything looks good so far. What is usually done to validate the >> parent >> > pom and site skin? I didn't see any mention of it here: >> > >> > >> http://continuum.apache.org/development/release.html#Verifying_a_Release >> >> Good question. Per >> http://www.apache.org/dev/release.html#what-must-every-release-contain, >> a downloader needs everything necessary to be able to build the source >> package. What I did was removed ~/.m2/repository/org/apache/continuum, then >> built the parent, skin, and continuum to confirm it was a complete set. >> >> - Brett >> >> -- >> Brett Porter >> br...@apache.org >> http://brettporter.wordpress.com/ >> http://au.linkedin.com/in/brettporter >> http://twitter.com/brettporter >> >> >> >> >> >> >
