I should also mention that I had a few issues to deal with which
required manual intervention (outside of Maven config)
Problem 1
---------
BUILD FAILED
...something about "Provider
org.apache.xalan.processor.TransformerFactoryImpl not found"
Since I'm building with jdk1.5, I kept getting this error during the
current/tiles build. The error is not very intuitive, but if you
google it, you'll find...
http://mail-archives.apache.org/mod_mbox/incubator-jackrabbit-dev/
200502.mbox/[EMAIL PROTECTED]
...which says...
"Place xalan.jar in $MAVEN_HOME/lib/endorsed ..."
...which fixes the error.
Problem 2
---------
...
...
BUILD FAILED
File...... /home/jmitchell/svn/struts/build/maven.xml
Element... maven:reactor
Line...... 61
Column.... 32
Java heap space
Total time: 10 minutes 11 seconds
Finished at: Wed Sep 21 01:57:43 GMT+00:00 2005
Seems even the zone couldn't handle such a large build.
Solution:
Before rerunning 'maven nightly', I do this...
$export MAVEN_OPTS=-Xmx1024m
(of course, it may not need that much, but whatever the standard
max is, wasn't enough)
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 21, 2005, at 12:10 AM, James Mitchell wrote:
I have finally gotten around to finishing the setup of my account
on our zone (http://www.apache.org/dev/solaris-zones.html) and
thanks to Martin and Google, I'm now able to fully build the
nightly (by hand) of the entire Struts project.
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up' portion
of the script. This basically caused Maven do say "oh cool,
nothings changed, let's not build any artifacts", and the rest of
the shell script just happily uploads the same jars from the last
build. This explains the mismatch in date/name of some of the
nightly artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/). I also updated the
readme on the regular nightly download page to point to this
interim spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right now, both Craig and my own personal machines are configured
to pull from cvs/svn, run the build, and upload something to that
location. This can only happen as a cron job if we copy the
appropriate ssh keys to the target server (no login prompted).
The question really comes down to "Where will the nightlies live?".
If we want to use some generic account on the zone to build the
nightly, the script would need to either:
a) use someone's account (mine?) to build/scp the nightlies over to
cvs.apache.org
b) build via a generic account and scp via a valid account
(committer account on the zone)
Although, we can actually avoid all of this by just hosting the
nightlies from the zone. The url might look like this:
http://struts.zones.apache.org/~nightly/
Somewhat related - Craig, if you are interested, I'd be happy to
help you move your nightly Ant builds to the new zone.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
---------------------------------------------------------------------
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]
