On Fri, Sep 17, 2010 at 9:25 AM, Simon Laws <[email protected]> wrote: >>> >> >> Its about whether or not we publish all the artifacts to the live >> maven repo. If the samples refer to their direct parent, eg helloworld >> having its parent be samples\getting-started\contributions\pom.xml >> then without the <relativePath> we must publish >> samples\getting-started\contributions\pom.xml. We don't publish any of >> the sample artifacts presently so without the <relativePath> none of >> them would work as they wouldn't find the parent pom. >> >> ...ant >> > > OK, interesting, it hadn't occurred to me that of course we don't > publish the samples independently. Let me clarify my question though. > Does each sample need to refer to it's direct parent pom? >
No. They only need to refer to a parent that has the default maven config which they need, what that is i guess depends on how we want the samples to work. One view might be that individual samples should be entirely self contained so a user can copy it and hack about making their own app and not have to worry about that dragging in any unnecessary other tuscany stuff in which case they may not even need a parent pom. But that then means each sample pom.xml gets cluttered up with all the maven config for standard stuff like the java compiler and surefire etc, plus any tuscany specific stuff they might need like the tuscany svn maven repo, so we might want each sample to use a parent that has all that standard stuff. Presently we have all the samples get the standard stuff that the top level trunk pom.xml defines. But also to make the release process simpler there now is config in the pom.xml in the top level sample folder that sets the deploy and remote resources plugins to be skipped, so if thats an approach we want to continue with then each sample should have trunk\samples\pom.xml as its parent or at least somewhere in the parent hierarchy. If we publish trunk\samples\pom.xml then perhaps its simplest if each sample has that as its parent and no relativepath. Maybe we should have a quick look at some other project samples to see what they do. ...ant
