Yes. There is a wiki page for this as well.
It's a work in progress, and I'm about to head out, but I'd like to
ask Wendy a few questions wrt pom, parent-pom, snapshot vs. released,
etc, etc.
Back in a bit.

6/14/06, James Mitchell <jmitchell (AT) apache (DOT) orgwrote:

Yes. There is a wiki page for this as well.

It's a work in progress, and I'm about to head out, but I'd like to
ask Wendy a few questions wrt pom, parent-pom, snapshot vs. released,
etc, etc.

Back in a bit.

That was a few days ago. :)

Craig, are you ready to get Shale set up on Continuum? I assume you'd
like to get out of the nightly builds business, and have them run from
the zone.

In another thread, I think Sean mentioned it's ready to start adding things.

I started to update the Shale site yesterday, but I need to know where
the nightly builds/snapshots are going to be so I can link to them.

Thanks,

Wonderful timing, I was just about to start a new thread wrt getting
the nightlies back online. And so I'll move my thoughts here.

So, with the mini hackathon out of the way, and our new buddy
MrStruts taking care of the continuous integration for us (ok, he
isn't doing much right now, but he is there and ready to roll), I'd
like to turn at least some of my attention to getting the nightlies
back online. Sorry if this was already discussed/decided on a
different thread, I'm behind on every list I am currently subscribed
to, except dev (AT) struts (DOT)

I plan to have MrStruts do full nightly builds using a similar
nightly script to the one I was using for many months with the Maven
1 built nightlies. I'm in the process (as I type this) of creating
the necessary build scripts to produce nightly artifacts of Struts
Action 1 (1.2.x and 1.3.x), Struts Action 2, and Shale.

Currently, we publish the nightlies here:

and I see Craig has begun publishing Shale nightlies to this spot:

So, on that note, I'll begin publishing Action 1 and 2 nightlies in a
(almost) similar fashion.

Craig, I've already zapped the 'maven' directory, can we:
1. remove the extra directory 'maven2' and just have p.a.o/builds/
struts/shale (requires you to change your scp script)?
2. rm -fr 'nightly' from the same dir?

So, (high level) we would have:

(eventually)

and each directory (Maven 2 built) would have a directory for the
particular module, which would have the current jar, war, or zip, and
6 days prior.

How does this sound?

Wendy wrote:
That was a few days ago. :)

Yes, I know, I never got back to this. Sorry, it's been a heck of a
month this week ;) My questions would have been about the PM
changes that Sean eluded to during our mini hackathon. I could be
wrong, but I thought he said there would be an issue with something
we needed and it not being published yet and that may or may not have
stemmed from a private conversation you may or may not have had over
IM. Sorry, the details are still a little cloudy. Forget about it
for now, I'm sure if it's a problem we'll know as soon as we begin
adding more projects to Continuum.

6/19/06, James Mitchell <jmitchell (AT) apache (DOT) orgwrote:

Craig, I've already zapped the 'maven' directory, can we:
1. remove the extra directory 'maven2' and just have p.a.o/builds/
struts/shale (requires you to change your scp script)?

Related: I'm using
temporarily,
staging the site locally wasn't working very well. Let me know if
that's a problem, I can change the URLs and deploy it somewhere else.

Done. Password set to cryptic default and will be mailed to your
privately. What address would you to receive it on?
craigmcc (AT) apache (DOT) org ?

6/19/06, Wendy Smoak <wsmoak (AT) gmail (DOT) comwrote:

6/14/06, James Mitchell <jmitchell (AT) apache (DOT) orgwrote:

Yes. There is a wiki page for this as well.

It's a work in progress, and I'm about to head out, but I'd like to
ask Wendy a few questions wrt pom, parent-pom, snapshot vs. released,
etc, etc.

Back in a bit.

That was a few days ago. :)

Craig, are you ready to get Shale set up on Continuum?

I am. Shale's trunk is now the Maven2 build, as you are well aware :-), so
it should be ready to go.

I assume you'd
like to get out of the nightly builds business, and have them run from
the zone.

That would be great. I've also cut-n-pasted below the shell script I'm
currently experimenting with it updates the snapshot repository as well
as posting all the nightly build artifacts (the output is piped to a
date-stamped HTML page):

#!/bin/sh
#

# buildShaleNightlyMaven -- Shale Nightly Builds (with Maven)
#

#

# Setup
#

export BUILD_HME=/home/craigmcc/Build
export CLASSPATH=.
export TSTAMP=`date +%Y%m%d`

echo \<html\>
echo \<head\>
echo \<title\>Shale Nightly Build \(with Maven\) For $TSTAMP\</title\>
echo \</head\>
echo \<body\>
echo \<h1\>Shale Nightly Build \(with Maven\) For $TSTAMP\</h1\>

#

# Update From Subversion Repository
#

echo \<h2\>Update From Subversion Repository\</h2\>
cd $BUILD_HME/struts/current/shale
echo \<pre\>
svn update
echo \</pre\>

#

# Build and Deploy Framework Artifaces
#

echo \<h2\>Build and Deploy Framework Artifacts\</h2\>
cd $BUILD_HME/struts/current/shale
echo \<pre\>
mvn clean site install deploy

cd shale-apps
mvn deploy -N
cd

cd shale-dist
mvn assembly:assembly
scp *.tar.gz \
craigmcc (AT) people (DOT) apache.org
$TSTAMP.tar.gz
scp *.zip \
craigmcc (AT) people (DOT) apache.org
$TSTAMP.zip
cd

echo \</pre\>

#

# Build and Deploy Sample Application Artifacts
#

echo \<h2\>Build and Deploy Sample Application Artifacts\</h2\>
cd $

export APPS="shale-blank shale-clay-usecases shale-mailreader"
export APPS="$APPS shale-sql-browser shale-usecases"

for APP in $APPS; do

cd $APP
echo \<h3\>Processing sample application $APP\</h3\>
echo \<pre\>

mvn clean install deploy assembly:assembly
scp target/$APPtar.gz \
craigmcc (AT) people (DOT) apache.org
$APP-$TSTAMP.tar.gz
scp target/$APPzip \
craigmcc (AT) people (DOT) apache.org
$APP-$TSTAMP.zip

echo \</pre\>
cd

done

#

# Finish Up
#

echo \<h2\>Job Completed\</h2\>
echo \</body\>
echo \</html\>

In another thread, I think Sean mentioned it's ready to start adding things.

Cool if you guys want to set me up as a user no the zone machine as well
(preferably with user id "craigmcc") I can help out directly as well.

I started to update the Shale site yesterday, but I need to know where
the nightly builds/snapshots are going to be so I can link to them.

As you can see from the script above, I started putting them in
"/", figuring we could do
parallel updates for "action" into
"/" and so on.

Thanks,

That brings up another interesting problem. Generated docs. I know
we try to keep the latest and greatest docs online (main site) but
for branched versions (Action 1.2.x), we would need to provide the
docs as well. So it might look like

<-- 1.2
docs here

and if we did the same for others

Maybe 1.2.x is a special case or maybe we should just do it anyway so
we can see the latest and greatest documentation (build hourly is
even possible).

6/19/06, James Mitchell <jmitchell (AT) apache (DOT) orgwrote:

Wonderful timing, I was just about to start a new thread wrt getting
the nightlies back online. And so I'll move my thoughts here.

So, with the mini hackathon out of the way, and our new buddy
MrStruts taking care of the continuous integration for us (ok, he
isn't doing much right now, but he is there and ready to roll), I'd
like to turn at least some of my attention to getting the nightlies
back online. Sorry if this was already discussed/decided on a
different thread, I'm behind on every list I am currently subscribed
to, except dev (AT) struts (DOT)

I plan to have MrStruts do full nightly builds using a similar
nightly script to the one I was using for many months with the Maven
1 built nightlies. I'm in the process (as I type this) of creating
the necessary build scripts to produce nightly artifacts of Struts
Action 1 (1.2.x and 1.3.x), Struts Action 2, and Shale.

Currently, we publish the nightlies here:

and I see Craig has begun publishing Shale nightlies to this spot:

So, on that note, I'll begin publishing Action 1 and 2 nightlies in a
(almost) similar fashion.

Craig, I've already zapped the 'maven' directory, can we:
1. remove the extra directory 'maven2' and just have p.a.o/builds/
struts/shale (requires you to change your scp script)?
2. rm -fr 'nightly' from the same dir?

Not a problem I'll switch for tonight's build. Indeed, I hadn't
announced the destination until we had a chance to coordinate across the
various builds. I published my shell script from before this change in an
earlier response to Wendy's questions it's four simple substitutions.

So, (high level) we would have:

(eventually)

and each directory (Maven 2 built) would have a directory for the
particular module, which would have the current jar, war, or zip, and
6 days prior.
--
How does this sound?

Sounds good, but I've got some additional thoughts that I would like to see
us implement consistently.

* In addition to publishing artifacts in this directory, I'm also updating
the snapshots for all the poms and jars. That way, people who like
to live dangerously :-) and have dependencies on the HEAD code
effectively get daily updates, without having to manually check out
the sources and rebuild them.

* I succumbed to my historical habits :-) and produced both .zip and
.tar.gz versions of the artifacts. I'd be open to publishing only in zip
format since it's pretty universal, and we don't particularly care about
file permissions in what we publish (i.e. no executables to worry
about).

* I'm really happy with the way that the assemblies constructed by the
Shale build scripts (both for the framework itself, and for each
individual
sample app) are themselves buildable if you have Maven2 installed.
This kind of thing will encourage others to get on the bandwagon (listen
to me, the latecomer :-), even if they don't want to try to download and
build the framework itself from Subversion. I'd like to see this approach
implemented consistently across our artifacts.

* I'm not so happy with the lukewarm support Maven2 currently offers for
integration testing. Wendy got inspired by some comments on the user
mailling list for Maven, though, and created a nice workaround in the
poms for the Shale sample apps. If you do something like:

mvn install -Pitest

then you can run the system integration tests built into the same project,
rather than having to set up a parallel project for those tests. Shale's
integration tests happen to be built with HtmlUnit, but it should be
equally
feasible to use Canoo or whatever else you like. We're also leveraging
the Cargo plugin to even start and stop your favorite container for you.

Craig

Wendy wrote:
That was a few days ago. :)

Yes, I know, I never got back to this. Sorry, it's been a heck of a
month this week ;) My questions would have been about the PM
changes that Sean eluded to during our mini hackathon. I could be
wrong, but I thought he said there would be an issue with something
we needed and it not being published yet and that may or may not have
stemmed from a private conversation you may or may not have had over
IM. Sorry, the details are still a little cloudy. Forget about it
for now, I'm sure if it's a problem we'll know as soon as we begin
adding more projects to Continuum.
--

6/19/06, James Mitchell <jmitchell (AT) apache (DOT) orgwrote:
Done. Password set to cryptic default and will be mailed to your
privately. What address would you to receive it on?
craigmcc (AT) apache (DOT) org ?
Yep. Thanks.

, with my latest change, we now have the 1.2.x nightlies back online.
The only hickup was the log file, but that's already resolved and I'm
firing off another build in 2 minutes.

6/19/06, James Mitchell <jmitchell (AT) apache (DOT) orgwrote:

My questions would have been about the PM
changes that Sean eluded to during our mini hackathon. I could be
wrong, but I thought he said there would be an issue with something
we needed and it not being published yet and that may or may not have
stemmed from a private conversation you may or may not have had over
IM. Sorry, the details are still a little cloudy. Forget about it
for now, I'm sure if it's a problem we'll know as soon as we begin
adding more projects to Continuum.

I'm sure it was about changing the struts-parent pom to version
3-SNAPSHT. I hadn't incremented it after the v2 release, so when
Sean made a change to it, there was the potential of someone
publishing a different v2 than the one on ibiblio. I commented on the
commit message on the list, then caught Sean on IM to make sure he saw
it.

There is a snapshot available:
<>

The sub-project parent poms can be changed to depend on this version,
and we'll need to tag and vote on struts-parent v3 after we add the
new committers and make any other necessary changes.

If Frank's checkstyle changes are acceptable, we'll also need to
release another struts-build.jar.

(Depending on the SAF 1.3.5 schedule, it might need to stay on the
current released versions.)

, I've added Action 1, Action 2, and Shale to Continuum. We need
to decide on a schedule for regular builds.
@Sean or anyone who knows,
Can we do nightlies with Continuum? I didn't think that was
possible, but I seem to remember some discussion about it somewhere.