[
https://issues.apache.org/jira/browse/TAP5-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940368#comment-17940368
]
Hudson commented on TAP5-2803:
------------------------------
SUCCESS: Integrated in Jenkins build Tapestry » TAP5-2803 #4 (See
[https://ci-builds.apache.org/job/Tapestry/job/TAP5-2803/4/])
TAP5-2803: fixing broken commit_with_no_javascript test (thiago: rev
d4cccd20af6537dc289fca98331fd2c28b2fc9ea)
* (edit)
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/JavaScriptSupportImpl.java
> Add support for JavaScript/ECMAScript 6 modules
> -----------------------------------------------
>
> Key: TAP5-2803
> URL: https://issues.apache.org/jira/browse/TAP5-2803
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Thiago Henrique De Paula Figueiredo
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Major
>
> Right now, while Tapestry has built-in support for including JavaScript files
> and Require.js modules in components, pages and mixins, it has none for
> JavaScript/ECMAScript 6
> [modules|[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules].]
> This makes using them in Tapestry webapps hard to do.
> To avoid confusion with Require.js modules, which are referred as "modules"
> in the Tapestry support for them (@Import's module attribute,
> JavaScriptSupport require() methods), JavaScript modules will be referred in
> the new code as "esModule" (as in ECMAScript module, ECMAScript 6 being the
> JavaScript standard which defines how modules work).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
