If we follow the pattern we have been using for SDO, DAS, once we build the project, the samples are built together to make sure changes on the core didn't break functionality used by the samples. In the case of SCA, don't we want to do the same, and when building sca, we would build the samples as well ? (e.g java/sca, java/samples/sca and java/distribution/sca)... While we still don't have the ideal unit/integration tests that would exercise all our scenarios, the sample applications have always a good source to help as improve quality in the project.
Maybe one solution would be to have those items moved to inside the sca project. -- Luciano Resende http://people.apache.org/~lresende On 2/21/07, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Feb 21, 2007, at 11:31 AM, Luciano Resende wrote: > Hi Jeremy > > Wouldn't we still have scenarios where we would like to build > multiple > projects from the Tuscany project root ? (e.g sca and samples/sca or > sca/sca-api-r1.0 and kernel). If so, the profiles inside java/pom.xml > should be way to go, no ? I don't think so, no. If we're doing that all the time then it implies that the modules are coupled together and that's a problem that should be solved by explicitly bundling those modules together into one or by managing the relationship between the modules better (i.e. keeping the interfaces compatible). -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
