[
https://issues.apache.org/jira/browse/SLING-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572399#action_12572399
]
Felix Meschberger commented on SLING-272:
-----------------------------------------
Fixed in Rev. 631155 for the JavaScriptEngineFactory dropping support for the
.js extension and adding support for the .ecma extension.
> Change default server-side JavaScript extension
> -----------------------------------------------
>
> Key: SLING-272
> URL: https://issues.apache.org/jira/browse/SLING-272
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> As discussed on the dev list [1], the server-side file extension for
> JavaScript sources should be changed. Currently it is ".js", which is also
> used to identify client-side JavaScript to be run in browsers. To prevent
> collisions in both server-side script execution support and human
> recognization, the server-side file extension should be changed.
> Two options are at discussion: .ecma or .es. As .es reminds me of the
> two-letter country code of Spain (yes, this a human brain thing, not
> technical ...), I would actually prefer .ecma. This also leans to wards the
> official name of the language ECMAScript.
> In addition, it alligns well with the jsp extension: "jsp" is short for "java
> server pages", where java is also used as a file extension for source code.
> For JavaScript it is "esp" for "ECMAScript server pages" and "ecma" for the
> plain language source code.
> [1] http://www.mail-archive.com/sling-dev@incubator.apache.org/msg02830.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
