Yes, same trouble to me.
And I believe this unstable build discourage normal user to go further.
Is it possible that set up something like cruisecontrol to monitor the
trunk, if one commit cause the mainline broken, the commitor can get the
mail notification and can fix it asap.
Thoughts?
Freeman
Luciano Resende wrote:
In the past weeks, most, if not all of the times I'm doing a svn
update and
trying to perform a clean build from the trunk I've experiencing build
failures..
Do we have any rules or best practices in place to help increase the
build
stability of our trunk code ?
If nothing is in place, should we recommend something ?
Here is a bat file I use to perform a clean build :
=============
set TUSCANY_HOME=x:\java
set TUSCANY_REPO=C:\Documents and
Settings\lresende\.m2\repository\org\apache\tuscany
x:
cd %TUSCANY_HOME%
call mvn clean > ..\mvnclean.log
call svn update > ..\svnupdate.log
rmdir /q /s %TUSCANY_REPO%
call mvn > ..\mvn.log
cd %TUSCANY_HOME%
================
--
Freeman Fang
Software Engineer
IONA Asia Pacific Software Development Center
No.2 Floor A Unit Information Center
Zhongguancun Software Park Haidian District,
Beijing, P.R.China
Tel.: +86-10-82825151 - ex. 551
Fax: +86-10-8282-5210
[EMAIL PROTECTED]
-------------------------------------------------
Making Software Work Together TM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
