The intention was to be identical except for the simpler dependencies.
Is there any reason the two can't stay the same as each other?

   ...ant

On Tue, Sep 21, 2010 at 10:09 AM, kelvin goodson
<[email protected]> wrote:
> In looking at the sample osgi launcher project, there is a parallel
> sample-osgi-base project for which the only difference is dependence
> on the base jar rather than a set of features.  I am currently
> splitting the multi-way launcher of the non-base variant project into
> a set of simpler launchers, as has been done in the embedded jse
> sample project.  I'm assuming it would be in the spirit of the
> original purpose of  the base variant project to modify it to just
> retain a single launcher, dependent on the base jar. Please correct me
> if I am wrong.
>
> Kelvin.
>
> On Thu, Sep 9, 2010 at 10:48 AM, Simon Laws <[email protected]> wrote:
>> On Thu, Sep 9, 2010 at 10:37 AM, kelvin goodson
>> <[email protected]> wrote:
>>> I'm taking another look at the samples again, with a view to having a
>>> better story for the 2.0 beta release.  Does anyone have any
>>> particular thoughts about what we need to do with them?
>>>
>>> Kelvin.
>>>
>>
>> Firstly, let look to classify the samples so we can understand what they're 
>> for.
>>
>> Helloworld samples (first stop for the new user?)
>>   e.g. helloworld
>> SCA feature samples (showing specific SCA extensions)
>>   e.g. binding-ws, binding-rmi etc + whichever launcher you choose
>> Tuscany samples (showing wider Tuscany specific features
>>   e.g. distributed OSGi support, or the launcher options used to run
>> the SCA feature samples
>> Applications samples (working SCA applications
>>   e.g. store, store-webapp
>>
>> These are all fine things but it's not obvious where the user should start.
>>
>> So my first suggestion would be design the structure of the samples +
>> associated README files to make them more accessible.
>>
>> I started by (re) organizing the pom.xml file a little bit a while ago
>> but we should think wider than this.
>>
>> Simon
>>
>> --
>> Apache Tuscany committer: tuscany.apache.org
>> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>>
>

Reply via email to