Jeremy Boynes wrote:
On Feb 21, 2007, at 1:25 PM, Raymond Feng wrote:
So are you going to publish SNAPSHOT versions of the different
modules to maven repo all the time? I assume the published artifacts
are the dependencies used by modules. Otherwise, those who want to
play with the source code won't have a good clue to build modules by
the right order.
All the time no, but certainly frequently (i.e. whenever something
significant changes).
The goal is to support people who want to "play with the source code"
without requiring them to build everything as we have seen that that
is fragile and does not work. Most such people will start with an
extension module (like a fractal container or a REST binding) and so
we need to ensure the dependencies they need (primarily the kernel)
are published and available.
For example, once we review and release the spec jar, *it should never
change* until the next release of the spec. The same with the kernel
apis/spis - the things extensions should depend on - although the
implementation of them (tuscany-core) may rev faster.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I share Raymond's concerns. I find top-down builds with profiles listing
the modules that work together very useful. This allows people to simply
do svn co sca, mvn, and get a good build with jars in sync with the
source. One more command, mvn -Peclipse eclipse:eclipse to get the whole
source loaded in an Eclipse workspace (or the Idea equivalent command),
and you're ready to do some work.
Having to go into each module directory to build them individually, in a
specific order, or with dependencies on external JARs with no simple way
to generate a consistent IDE workspace with the correct level of source
attached to the JARs is very error prone and confusing. This approach
just does not work for me.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
