I'd be happy to help. Although last I remember, you guys didn't want
anything to do with Maven. Has that changed?
--
James Mitchell
678.910.8017
On Nov 5, 2005, at 9:10 PM, Sean Schofield wrote:
James,
I will have to get some more info on the zones from you. I am VERY
behind on my site-dev reading and apparently I have missed a lot.
Maybe at some point you could help us set this up for MyFaces as well?
There is already an effort to migrate the build to Maven so maybe we
could use most of your work on this ...
sean
On 11/4/05, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 11/4/05, James Mitchell <[EMAIL PROTECTED]> wrote:
There is still a small chance that infra could yank the zone from us
or do something to cause it be (or need to be) wiped clean.
And so, knowing this I've kept everything in svn, so that
recovery is
a matter of:
a) finding a different box
b) svn co the project
c) cp maven-nightly.sh.current nightly.sh
d) chmod u+x nightly.sh
e) copy my public key to .ssh/authorized_keys on the target box
f) setup a crontab
And except for that weird issue with automount, it has been running
like a champ, totally hands off.
Cool.
I'm still tweaking what you gave me, so what I'll do is (once my
tweaks actually work ;), begin building/scp-ing the nightlies to a
different (not over yours) location. This will be a staging area of
sorts, until you decide that you are comfortable with the nightly
process on the zone.
That sounds great. Having it on the zone would mean more people
than just me
could maintain and fix it, so that would be goodness.
I know you are/were building some of the commons nightlies too, we
can certainly pick that up for you if you like. (??)
That's be great (for the same reasons) ... the only question is
whether we
should do this in the Struts zone or not :-). I'll send you that
script
separately ... it's actually simpler because the process for each
individual
commons package is identical.
Craig
--
James Mitchell
678.910.8017
On Nov 3, 2005, at 10:11 PM, Craig McClanahan wrote:
On 11/3/05, James Mitchell <[EMAIL PROTECTED]> wrote:
So, does that mean you do not want me to add the ant process to
the
zone builds?
I fixed it on my desktop for tonight. Are we confident enough in
the zone
builds to run nightlies from there instead? If so, I'll just
comment it out
of my crontab. Also, have you had a chance to mess with the nightly
builds
for the commons packages also, or is that a separate kettle of
fish?
--
James Mitchell
678.910.8017
Craig
On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote:
On 11/3/05, James Mitchell <[EMAIL PROTECTED]> wrote:
Um, sorry, the build failed (which I half expected anyway, not
having
run it on the particular machine yet) so I'll rework a few
things and
kick it off again. I'll ping the list when they are available.
Thanks.
Thanks James. I was also able to access my home desktop and
figured
out what
was going wrong (I botched a PATH setup when I reorganized my
system a bit),
so tonight's nightlies should be produced on schedule.
--
James Mitchell
678.910.8017
Craig
On Nov 3, 2005, at 12:49 PM, James Mitchell wrote:
I have Craig's nightly script and I am running it as I type
this.
Look for some nightlies in a few minutes.
--
James Mitchell
678.910.8017
On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote:
I was hoping to get the latest build of shale, to get the
latest
clay
changes, and I noticed that the latest nightly build is from
10/28. Is there
a reason why there is no 11/3 build?
Thanks,
Ryan
---------------------------------------------------------------
---
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------
---
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
