On Thu, Sep 16, 2010 at 9:26 PM, Simon Laws <[email protected]> wrote: > On Thu, Sep 16, 2010 at 9:10 PM, ant elder <[email protected]> wrote: >> On Thu, Sep 16, 2010 at 5:46 PM, kelvin goodson >> <[email protected]> wrote: >>> I have a problem with the samples builds which I believe is due to >>> having messed up the backwards pointers to parent poms. I have >>> commented out "samples" from all the top level pom's profiles. I had >>> forgotten that the artifactid etc in the parent pom stanza needs to >>> reflect the content of ../pom.xml file as specified in the relative >>> path. I need to go all through my reorganisation to check this is >>> correct. I'll do this in the morning. >>> >>> Kelvin. >>> >> >> Are you thinking of having each sample refer to the parent in the >> directory immediately above the sample or to have all the samples just >> point to the one parent at trunk\samples\pom.xml? Having everything >> use the one trunk\samples\pom.xml makes things a little bit simpler i >> think. >> >> ...ant >> > > Also, what value is the relative path adding? Docs say... > > "Notice the relativePath element. It is not required, but may be used > as a signifier to Maven to first search the path given for this > project's parent, before searching the local and then remote > repositories." >
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
