On Feb 28, 2007, at 10:25 AM, Luciano Resende wrote:
To run the samples, as we have not cut a release yet, you will need
to manually create a distribution. This should be pretty
straightforward:
1. In /kernel do 'mvn'
2. In /runtime/standalone run 'mvn'
3. In /core-samples/common run 'mvn install'
4. In /core-samples/ run 'mvn install'
5. Run the calculator:
Just a suggestion, isn't much simpler to have a profile defined
where it
would run necessary modules for specific scenarios (e.g running
standalone
samples) ? The we can redirect the users to something like mvn -P
<standalone samples> or a more appropriated profile name.
I would hope users should never have to checkout code - they would
just download the distribution, build the sample they are interested
in and java -jar <launcher jar> <app jar>. If they need runtime
source they would just download the source distro.
Tuscany samples developers should use the distribution as well in
order to verify the sample works with the distribution image.
There will be cases where someone needs to build multiple independent
modules, e.g. Simon's. In that case, profiles are not really Maven's
way to do it. I also don't think this use scales or addresses the
problem of build stability. For example, the combinations of
independent modules are numerous and having profiles for everyone
will quickly become unwieldy. Also, profiles will become unstable
when a module breaks and will involve constant shuffling of the build
script.
The way I think this is best addressed is by grouping related modules
together. This is how Maven was intended to work. In the specific
case here, perhaps we should move core under runtime?
I've found the modular build has greatly increased my productivity
and made checkins more accurate as I am not hampered by orthogonal
issues in unrelated modules.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
