On Wed, Feb 2, 2011 at 11:11 AM, Simon Laws <[email protected]> wrote: >> >> Hello, >> >>> >>> I think this should work for the bin and src distros if you build from >>> the top level samples directory first as opposed to building >>> individual samples. That doesn't seem that intuitive so we need to >>> think if we can make that better. On the Beta2 thread there is a >>> discussion of samples usability so I'll add this point. >> >> >> I tried building from the samples top-level directory >> (tuscany-sca-2.0-Beta1\samples) for the Windows bin distribution and got >> the error mentioned above. >> >> And I still think that it's because there's no pom for 2.0-Beta1 in >> http://repo2.maven.org/maven2/org/apache/tuscany/sca/tuscany-samples/ >> >> And there is no alternative maven repository defined in the samples pom >> that comes with the bin distribution. >> >> >> >>> >>> Simon > > Strange. You're right that the top level samples pom is not published > to the maven repos (we should do that). However it's parent is so in > theory building at the samples level should push it into you local > repo and hence you should be able to build it's children. I've > probably missed something. Let me go try it. > > Simon >
Some points to help understand whats going on (not saying these are good/bad, its just how things are): (1) None of the sample artifacts contain the ASF legal files, i think that was to avoid clutter (2) None of the sample artifacts are published to the central repo, they can't be because of (1) and to allow simplified naming (3) To get (2) to happen simply and to simplify building releases the config to prevent deploying the sample artifacts is done in the top-level sample folder pom.xml (note i'm not sure if that is really needed now as the release profile doesn't include the samples tree) (4) Because of (3) and (2) the top-level sample pom.xml is not in the central repo so samples using it as a parent need to use <relativePath> in their parent definition. When using relativePath the parent doesn't need to be published in a local or remote repo as its access directly at the relative location. (5) When the sample reorganization happened often relativePath was not updated correctly so now the parent can't be found I think its (5) that is causing the problem here. ...ant
