On Mar 12, 2007, at 2:15 PM, Luciano Resende wrote:
Jim said:
The trunk has been quite stable for some time.
What's your scope of trunk ? Following the instructions in
https://svn.apache.org/repos/asf/incubator/tuscany/java/
BUILDING.txt nothing
get's built. Trying to build the sca profile or going directly to
java/sca
give me an error, as there is no pom.xml available after Jeremy
changed the
sca pom.xml to pom/sca.
That is exactly the correct and documented behavior because we don't
build everything at once. Ironically, Jeremy proposed removing the
pom as inappropriate but several people objected, so it was left in
place. Please see to the following discussion for details:
http://www.mail-archive.com/[email protected]/msg14396.html
Also, couple modules does not built as of today, due
to changes in kernel, and there is no documentation of what's
working or
not.
The persistence modules and wsdl haven't yet been updated from the
release. I forgot to do that as I had a few left-over things in my
mvn repo and will go ahead and update them. This is hardly unstable,
just a few pom updates I forgot to make over the weekend. Mia culpa.
And if you have to try to figure this out, you have to try each
module/project inside sca and try to figure out what's failing and
what's
not. Is this considered stable ?
Each extension should have their own section of the wiki with this
type of info. I started to do that for the ones I care about.
Based on some e-mails I've read on this list, looks like if we
really want
to expand out Tuscany SCA community, we really need some
improvement over
what we have today around build and probably other areas as well.
Also,
being able to build multiple modules at once, should not break the
modularity policy.
We can build multiple modules today, e.g. kernel. Building from root
won't work because of different versions required by extensions
modules. Jeremy suggested a way to build assemblies. Why not adopt
that approach?
Or maybe I'm really missing something, and maybe someone
could share with me an easy way to verify and build multiple
modules for the
SCA project in trunk as currently I'm using a pretty old technique, a
build.bat that builds the modules i know are working.
It's called "continuous integration": http://www.martinfowler.com/
articles/continuousIntegration.html
Note the article is linked from our developer instructions:
http://cwiki.apache.org/TUSCANY/sca-java-development.html
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
