Here's a quick outline of what I'm planning on doing for this:
* publish snapshots of latest pom and buildtools modules
* restructure "runtime" directory to have one sub-module per
"runtime" (i.e. standalone, webapp, osgi)
* add sub-module for "junit"
* add sub-module for maven/itest-plugin
* add assembly goals to produce the packaged runtime distros
* regroup "services" by "things to be released together"
* add "axis2" sub-module with binding, databinding, etc.
* add "sdo" sub-module
* add other sub-modules as needed, including module-specific samples
* move testing/sca to sca/testing
* move samples/sca to sca/samples (without module-specific samples,
this will be similar to "applications" from M2)
--
Jeremy
On Dec 18, 2006, at 2:18 PM, Jeremy Boynes wrote:
This keeps coming back to haunt us :(
We've discussed breaking the build up before and in light of this I
think it's time we started making those changes. I have some free
time this week and will get stuck in.
--
Jeremy
On Dec 18, 2006, at 1:37 PM, 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%
================
--
Luciano Resende
http://people.apache.org/~lresende
---------------------------------------------------------------------
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]
