hstdefault/sitemap/javascript-yui.xml

<?xml version="1.0" encoding="UTF-8"?>
<sv:node sv:name="javascript" xmlns:sv="http://www.jcp.org/jcr/sv/1.0">
  <sv:property sv:name="jcr:primaryType" sv:type="Name">
    <sv:value>hst:sitemapitem</sv:value>
  </sv:property>
  <sv:node sv:name="yui">
    <sv:property sv:name="jcr:primaryType" sv:type="Name">
      <sv:value>hst:sitemapitem</sv:value>
    </sv:property>
    <sv:property sv:name="hst:containerresource" sv:type="Boolean">
      <sv:value>true</sv:value>
    </sv:property>
    <sv:node sv:name="_any_">
      <sv:property sv:name="jcr:primaryType" sv:type="Name">
        <sv:value>hst:sitemapitem</sv:value>
      </sv:property>
    </sv:node>
  </sv:node>
</sv:node>
Revision:	47790
Committed:	Wed Dec 24 11:18:19 2014 UTC (6 years ago) by aschrijvers
Content type:	text/xml
File size:	688 byte(s)
Log Message:	GOGREEN-1303 again remove filter.prefix.exclusions and filter.suffix.exclusions since HST issue has been fixed. Since /javascript/yui should result in container resources, and I prefer not to override filter.prefix.exclusions (and having to change the hst-config.properties in deployed environments as well) I have added /javascript/yui as a container resource sitemap item
#	User	Rev	Content
1	aschrijvers	47790	<?xml version="1.0" encoding="UTF-8"?>
2			<sv:node sv:name="javascript" xmlns:sv="http://www.jcp.org/jcr/sv/1.0">
3			<sv:property sv:name="jcr:primaryType" sv:type="Name">
4			<sv:value>hst:sitemapitem</sv:value>
5			</sv:property>
6			<sv:node sv:name="yui">
7			<sv:property sv:name="jcr:primaryType" sv:type="Name">
8			<sv:value>hst:sitemapitem</sv:value>
9			</sv:property>
10			<sv:property sv:name="hst:containerresource" sv:type="Boolean">
11			<sv:value>true</sv:value>
12			</sv:property>
13			<sv:node sv:name="_any_">
14			<sv:property sv:name="jcr:primaryType" sv:type="Name">
15			<sv:value>hst:sitemapitem</sv:value>
16			</sv:property>
17			</sv:node>
18			</sv:node>
19			</sv:node>