[
https://issues.apache.org/jira/browse/TOBAGO-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623401#comment-16623401
]
Hudson commented on TOBAGO-1913:
--------------------------------
SUCCESS: Integrated in Jenkins build Tobago Trunk #1538 (See
[https://builds.apache.org/job/Tobago%20Trunk/1538/])
TOBAGO-1913: Enhance tobago-config.xsd: there should be an includes tag
(lofwyr: rev 9df8571b0b471df56c3e598d0e67d799a64c4224)
* (edit)
tobago-core/src/main/java/org/apache/myfaces/tobago/internal/config/TobagoConfigParser.java
* (edit)
tobago-core/src/main/java/org/apache/myfaces/tobago/internal/config/TobagoConfigEntityResolver.java
> Enhance tobago-config.xsd: there should be an includes tag in resources tag
> ---------------------------------------------------------------------------
>
> Key: TOBAGO-1913
> URL: https://issues.apache.org/jira/browse/TOBAGO-1913
> Project: MyFaces Tobago
> Issue Type: New Feature
> Components: Core
> Reporter: Udo Schnurpfeil
> Assignee: Udo Schnurpfeil
> Priority: Minor
> Fix For: 5.0.0
>
>
> Currenty, if resources are added to and removed from a theme the syntax in
> the configuration is like this:
> {code}
> ...
> <resources production="true">
> <excludes>
> <script name="/bar.min.js"/>
> <style name="/bar.min.css"/>
> </excludes>
> <script name="/foo.min.js"/>
> <style name="/foo.min.css"/>
> </resources>
> ...
> {code}
> It would be easier to read, if there is an "includes" tag, like the
> "excludes" tag.
> {code}
> ...
> <resources production="true">
> <includes>
> <script name="/foo.min.js"/>
> <style name="/foo.min.css"/>
> </includes>
> <excludes>
> <script name="/bar.min.js"/>
> <style name="/bar.min.css"/>
> </excludes>
> </resources>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
