[
https://issues.apache.org/jira/browse/TAP5-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18011603#comment-18011603
]
Hudson commented on TAP5-2810:
------------------------------
FAILURE: Integrated in Jenkins build Tapestry ยป TAP5-2810 #11 (See
[https://ci-builds.apache.org/job/Tapestry/job/TAP5-2810/11/])
TAP5-2810: adjusting pageinit so it works with AMD and ES (thiago: rev
89b8fe4a1ce9ad368adcad3df99cc6276c6d8577)
* (edit) tapestry-core/src/main/resources/org/apache/tapestry5/core.properties
* (edit) tapestry-core/src/main/typescript/src/t5/core/pageinit.ts
* (edit)
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/javascript/EsModuleManagerImpl.java
> Support for running Tapestry without Require.js
> -----------------------------------------------
>
> Key: TAP5-2810
> URL: https://issues.apache.org/jira/browse/TAP5-2810
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Thiago Henrique De Paula Figueiredo
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Major
>
> Starting with 5.10.1, Tapestry has support for ES (ES6/JavaScript) modules,
> which have their own module resolution and dependency mechanisms provided by
> the browser itself. Require.js is an old tool for module resolution and
> dependencies, with its own problems, so Tapestry should, out of the box,
> support ability to run without Require.js if the user wants that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
