[ 
https://issues.apache.org/jira/browse/CXF-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Liguori updated CXF-3841:
--------------------------------

    Description: 
CXF Projects: Samples vs Examples vs Demos

Case Study:
Apache ServiceMix and Apache Camel place their example projects under an 
"examples" folder.  Apache ActiveMQ uses an "example" folder (without the s).

Recommendation:
Rename CXF's "samples" folder to "examples". Specifically, change 
"\apache-cxf-2.4.2\samples" to "\apache-cxf-2.4.2\examples".

Justification:
The terms "Samples" and "Examples" are pretty much interchangeable, with the 
difference of "samples" being generally thought of as something *collected*, 
and "examples" being generally thought of as something *created*.  I believe 
that CXF example projects fall into the latter sub-classification.

* Also, since CXF is in the same family as the other SOA-related tools that use 
"examples", this is another reason to align directory names.

Thanks for the consideration.

Some other use cases: Eclipse, XMLSpy and Tcl/TK use 'examples'. However, 
NetBeans and XMLBeans do use 'samples'.

* I also recommend that Apache ActiveMQ changes their folder from "example" to 
"examples", for the same alignment purposes.

  was:
CXF Projects: Samples vs Examples vs Demos

Case Study:
Apache ServiceMix and Apache Camel place their example projects under an 
"examples" folder.  Apache ActiveMQ uses an "example" folder (without the s).

Recommendation:
Rename CXF's "samples" folder to "examples". Specifically, change 
"\apache-cxf-2.4.2\samples" to "\apache-cxf-2.4.2\examples".

Justification:
The terms "Samples" and "Examples" are pretty much interchangeable, with the 
difference of "samples" being generally thought of as something *collected*, 
and "examples" being generally thought of as something *created*.  I believe 
that CXF example projects fall into the latter sub-classification.

* Also, since CXF is in the same family as the other SOA-related tools that use 
"examples", this is another reason to align directory names.

Thanks for the consideration.

Some other use cases: Eclipse, XMLSpy and Tcl/TK use 'examples'. However, 
NetBeans and XMLBeans do use 'samples'.

* I also recommend that Apache ActiveMQ changes their folder from "example" to 
"examples".

    
> Change "samples" folder to "examples"
> -------------------------------------
>
>                 Key: CXF-3841
>                 URL: https://issues.apache.org/jira/browse/CXF-3841
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.4.2
>            Reporter: Robert Liguori
>            Priority: Trivial
>
> CXF Projects: Samples vs Examples vs Demos
> Case Study:
> Apache ServiceMix and Apache Camel place their example projects under an 
> "examples" folder.  Apache ActiveMQ uses an "example" folder (without the s).
> Recommendation:
> Rename CXF's "samples" folder to "examples". Specifically, change 
> "\apache-cxf-2.4.2\samples" to "\apache-cxf-2.4.2\examples".
> Justification:
> The terms "Samples" and "Examples" are pretty much interchangeable, with the 
> difference of "samples" being generally thought of as something *collected*, 
> and "examples" being generally thought of as something *created*.  I believe 
> that CXF example projects fall into the latter sub-classification.
> * Also, since CXF is in the same family as the other SOA-related tools that 
> use "examples", this is another reason to align directory names.
> Thanks for the consideration.
> Some other use cases: Eclipse, XMLSpy and Tcl/TK use 'examples'. However, 
> NetBeans and XMLBeans do use 'samples'.
> * I also recommend that Apache ActiveMQ changes their folder from "example" 
> to "examples", for the same alignment purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to