[
https://issues.apache.org/jira/browse/TAP5-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183232#comment-15183232
]
Barry Books commented on TAP5-2534:
-----------------------------------
I did see that JIRA but it's closed without an explanation. All I'm proposing
is adding
public static void contributeClasspathAssetAliasManager(MappedConfiguration
configuration) {
configuration.add("webjars", "META-INF/resources/webjars");
}
to the JavascriptModule so multiple 3rd party modules could use webjars without
a configuration conflict. I'm not proposing any existing code be converted to
webjars.
> Add support for webjars
> -----------------------
>
> Key: TAP5-2534
> URL: https://issues.apache.org/jira/browse/TAP5-2534
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Barry Books
> Priority: Minor
> Labels: feature, improvement, patch
>
> The webjars project (webjars.org) packages javascript/css projects into jar
> files and publishes them to Maven Central so the can be managed like any
> other Java dependency. Supporting this in Tapestry is easy and they even have
> an example.
> Patch to follow
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
