On Wed, Feb 2, 2011 at 1:41 PM, Richard Yao <[email protected]> wrote: > For "(5) When the sample reorganization happened often relativePath was > not > updated correctly so now the parent can't be found" > > Just curious that do we have some kind of "continuous build" to make > sure new change won't break old code? > > I am doing a POC for SCA and having worked on both Fabric3 and Tuscany > for the past few days. So far, I feel Fabric3 is easier for newbie > because their samples can pass the build and be used just as is. Both > projects do not have a lot of detailed documents and samples are the > documentation itself. So having working samples is very very important > because even I want to spend more time to dig but my boss won't allow > me. > > Just as I said, I am a newbie and sure some my statements could be very > wrong. >
I think you're right Richard. We need to be running the samples from the build as we expect the user to run them. We have a place to do this (itest/distribution) but not all samples are included in that yet. If we drive them from there then they will get run Hudson. At the moments the samples only get built as part of the main top down build which is not precisely how the user sees them. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
