Hi Simon,

I like your suggestion for the naming standards, +1 for implementing the
same.

I will raise a JIRA to address the same.

If any one has any comments, please let me know. Thanks.

On Mon, Nov 17, 2008 at 8:41 PM, Simon Laws <[EMAIL PROTECTED]>wrote:

>
>
> On Mon, Nov 17, 2008 at 2:49 PM, Dan Becker <[EMAIL PROTECTED]>wrote:
>
>> Hi Ram,
>>
>> Good scouting there. I think having a standard naming convention will
>> increase usability and make it easy for users to become acclimated. I vote
>> to proceed with implementing a standard naming convention.
>>
>>
>> Ramkumar R wrote:
>>
>>> While running a complete build for sca-java-1.x branch, just noticed that
>>> the names of projects in modules and itest are not uniform... for example
>>>
>>> While most of the projects start with a name "Apache Tuscany SCA", few
>>> does
>>> not comply to the standard..... as shown below.
>>>
>>> In sca/java/modules:
>>> - Apache Tuscany Java Interface for JAXWS
>>> - Apache Tuscany Security Policy Model
>>> - Apache Tuscany Reliability Policy Model
>>> - Apache Tuscany Policy Model for JMS binding
>>> - Apache Tuscany Policy Model for Axis2 WS binding
>>> - Apache Tuscany OSGi Runtime Helper Library
>>> - Apache Tuscany AOP-based Logging and Tracing
>>> - Apache Tuscany Logging Policy Model
>>> - Apache Tuscany Data Binding for FastInfoset
>>>
>>> In sca/java/itest:
>>> - Apache Tuscany Test for Callable References over Web Services
>>> - Apache Tuscany Test for Simple Exceptions over Web Services
>>> - Apache Tuscany Interface Integration Tests
>>> - Unnamed - org.apache.tuscany.sca:itest-jms-args:jar:1.4-SNAPSHOT
>>> - Apache Tuscany OSGi Contribution Version 2 classes
>>> - Apache Tuscany OSGi Contribution Version 1 classes
>>> - Apache Tuscany OSGi Contribution tests
>>> - Apache Tuscany OSGi Contribution Tests
>>>
>>> Just wanted to confirm, if we are following a standard in naming the
>>> projects?
>>>
>>>
>> --
>> Thanks, Dan Becker
>>
>
> +1 some of the names are either inconsistent or inaccurate so a tidy up
> here would be good. E.g
>
> Apache Tuscany "ModuleName "
>
> Seems to be the kind of pattern that we have for modules. Would be good to
> extend this so that samples, itests and demos are identifiable.
>
> Apache Tuscany itest "ModuleName "
> Apache Tuscany sample "ModuleName "
> Apache Tuscany demo "ModuleName "
>
> Simon
>



-- 
Thanks & Regards,
Ramkumar Ramalingam

Reply via email to