On Sun, Feb 20, 2011 at 8:35 AM, ant elder <antel...@apache.org> wrote: > On Tue, Feb 15, 2011 at 7:08 PM, ant elder <antel...@apache.org> wrote: >> On Thu, Feb 10, 2011 at 9:10 AM, ant elder <antel...@apache.org> wrote: >> >>> >>> I have now done these. There's a beta2 branch for the release, and all >>> the trunk samples are now in contrib/samples and the helloworld sample >>> is in unreleased/samples where we can continuing with making it like >>> we want. >>> >> >> So how do we progress this? What do we need to change in the >> helloworld sample at >> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/unreleased/samples/helloworld-contribution/ >> to make in complete and move it back to trunk/samples? >> >> ...ant >> > > Ok no comments so if we're all happy with that then in a few days i'll > move it back to trunk/samples and use it as a model for the next ones. > > ...ant >
I wonder whether we need the ability to run from maven at all. We need a way for people to compile samples of course. I've be happy with the following. 1 - use the shell as the primary out of the box mechanism for loading/running sample contributions where possible 2 - present all the other options for running/embedding Tuscany under "running tuscany" which is after all why we created that directory in the first place, i.e. to separate sample contributions from the large number of ways we have of running them 3 - make using the sample contributions in eclipse really easy (re-instate the eclipse plugin? provide instructions for generating projects files? Or even ship project files?) I'd also like us to use this one sample to decide how we are going to do the docs so the get it right for the rest of them. I'm +1 for moving back to trunk as is for further development. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
