On Fri, Sep 17, 2010 at 11:26 AM, kelvin goodson <[email protected]> wrote: > Hi, > > I've only just got back to this and I'm not sure how to come to > closure . Is it reasonable to adopt the "publish a top level sample > pom as the parent of all samples" approach at this point, or do we > need to be more circumspect? I could take a look at more projects, > but I don't have a good idea who might have a good story to tell. I > could ask on the maven users' list, or I could just go ahead and > change all the sample poms to reference this one parent. thoughts? > > Kelvin. >
Hi Kelvin I wasn't trying to make this more complex than needs be. Was just looking to reduce the amount of cross referencing that goes on if it's not necessary. I looked a OpenEJB and they don't seem to refer to samples. I am attracted by the idea that samples projects are stand alone and hence are easy to copy and compile outside the context of the Tuscany distribution. It would be interesting to find out precisely what dependencies and configuration are required to get a sample working when it doesn't ultimately reference the Tuscany parent pom. This is what our users are going to have to find out I suspect. It maybe best to separate this discussion for the discussion about getting the structure right and for now just stick with the relative reference to each sample parent. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
