[
https://issues.apache.org/jira/browse/TOBAGO-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15714757#comment-15714757
]
Hudson commented on TOBAGO-1636:
--------------------------------
SUCCESS: Integrated in Jenkins build Tobago 3.0.x #660 (See
[https://builds.apache.org/job/Tobago%203.0.x/660/])
TOBAGO-1636 End of theme-dependent resource selection (ResourceManager)
* fix QUnitTests (and "mvn verify -Pqunit-integration-tests")
[developed by hnoeth] (lofwyr:
[http://svn.apache.org/viewvc/?view=rev&rev=1772315])
* (edit)
tobago-3.0.x/tobago-example/tobago-example-demo/src/main/webapp/menu.xhtml
* (edit)
tobago-3.0.x/tobago-example/tobago-example-demo/src/main/webapp/test.xhtml
* (edit)
tobago-3.0.x/tobago-example/tobago-example-demo/src/test/java/org/apache/myfaces/tobago/example/demo/QUnitTests.java
> End of theme-dependent resource selection (ResourceManager)
> -----------------------------------------------------------
>
> Key: TOBAGO-1636
> URL: https://issues.apache.org/jira/browse/TOBAGO-1636
> Project: MyFaces Tobago
> Issue Type: Task
> Components: Core, Themes
> Reporter: Udo Schnurpfeil
> Assignee: Udo Schnurpfeil
> Fix For: 3.0.0-beta-1, 3.0.0
>
>
> In Tobago 2 and lower the resources will be selected from a theme
> automatically. This is a feature on top of JSF.
> In Tobago 3 this is no longer supported, because there is no need (or even
> rare) to have different resources for different themes. This is, because
> these days the features of CSS and JS are much more advantage.
> Moreover the Bootstrap theme generation will generate a complete theme, so
> all resources of the base theme must be excluded.
> Remark: For simplicity, some resources are moved to the core module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
