On Tue, Mar 17, 2009 at 7:20 PM, Dan Becker (JIRA)
<[email protected]> wrote:
> - Show quoted text -
>     [ 
> https://issues.apache.org/jira/browse/TUSCANY-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
>
> Dan Becker resolved TUSCANY-2822.
> ---------------------------------
>
>    Resolution: Duplicate
>
> Since this is superceded by TUSCANY-2917, I will let the later, more 
> comprehensive Jira take care of the fix.
>
>> Focus samples names on the Tuscany feature being tested.
>> --------------------------------------------------------
>>
>>                 Key: TUSCANY-2822
>>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2822
>>             Project: Tuscany
>>          Issue Type: Improvement
>>          Components: Java SCA Samples
>>    Affects Versions: Java-SCA-2.0
>>         Environment: All
>>            Reporter: Simon Laws
>>            Priority: Minor
>>
>> In 1.x our samples were names
>> calculator-???
>> helloworld-???
>> Which puts the focus on the application scenario rather that the Tuscany 
>> feature being demonstrated by the sample. Change sample names and directory 
>> names to the form
>> binding-rmi-reference-calculator
>> binding-rmi-service-calculator
>> binding-ws-calculator
>> host-webapp-calculator
>> implementation-java-calculator
>> launcher-osgi-calculator
>> launcher-jse-calculator
>> maven-osgi-junit-calculator
>> To focus on the main thing being shown by the sample. This has the effect of 
>> focusing the samples on specific extensions (of course each sample will use 
>> more features but these features are not the focus of the sample). It also 
>> has the effect of grouping samples in the sample directory according to what 
>> feature they are testing so it is easier to find a sample of interest.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Hi Dan

Why is this a duplicate? I think one is to do with the module name and
the the other is to do with how that module name is used in the
description within the pom. Maybe I'm miss-reading 2917.

Simon

Reply via email to