roq

Author: jasondlee

content/docs.html

@@ -2,62 +2,63 @@
 layout: default
 title: Documentation
 selflink: docs
-permalink: /docs/
+link: /docs/
 ---
 <h3>RESTEasy Documentation (Latest)</h3>
 
 
 <div class="release-container" id="documentation">
-    {% for release in site.data.releases %}
-    {% if release.supported %}
-    {% assign detail = release.detail[0] %}
+    {#for release in cdi:releases.list}
+    {#if release.supported}
+    {#let detail = release.detail[0]}
     <div class="release">
         <div class="release-body">
-            <h4 class="release-title">RESTEasy {{ detail.version }} <small>({{ detail.date }})</small></h4>
-            {% if detail.jakarta_rest_spec %}
+            <h4 class="release-title">RESTEasy {detail.version} <small>({detail.date})</small></h4>
+            {#if detail.spec}
             <div class="spec">
-                <strong>Implements</strong> <a href="{{ detail.jakarta_rest_spec.link }}" target="_blank">Jakarta REST {{ detail.jakarta_rest_spec.version }}</a>
-                <span><a href="{{ detail.jakarta_rest_spec.java_doc }}" target="_blank">(JavaDoc)</a> </span>
+                <strong>Implements</strong> <a href="{detail.spec.link}" target="_blank">Jakarta REST {detail.spec.version}</a>
+                <span><a href="{detail.spec.javadoc}" target="_blank">(JavaDoc)</a> </span>
             </div>
-            {% endif %}
+            {/if}
             <ul>
-                {% if detail.documentation.link %}
-                <li><a href="{{ detail.documentation.link }}" target="_blank">Documentation</a></li>
-                {% endif %}
-                {% if detail.documentation.java_doc %}
-                <li><a href="{{ detail.documentation.java_doc }}" target="_blank">JavaDoc</a></li>
-                {% endif %}
-                {% if detail.download_link %}
-                <li><a href="{{ detail.download_link }}" target="_blank">Download</a></li>
-                {% endif %}
-                {% if detail.release_notes %}
-                <li><a href="{{ detail.release_notes }}" target="_blank">Release Notes</a></li>
-                {% endif %}
+                {#if detail.documentation.link}
+                <li><a href="{detail.documentation.link}" target="_blank">Documentation</a></li>
+                {/if}
+                {#if detail.documentation.javadoc}
+                <li><a href="{detail.documentation.javadoc}" target="_blank">JavaDoc</a></li>
+                {/if}
+                {#if detail.downloadLink}
+                <li><a href="{detail.downloadLink}" target="_blank">Download</a></li>
+                {/if}
+                {#if detail.releaseNotes}
+                <li><a href="{detail.releaseNotes}" target="_blank">Release Notes</a></li>
+                {/if}
             </ul>
         </div>
         <div>
-            <a href="{{ site.baseurl }}{% link docs/all-docs.md %}#{{ detail.version  | replace:'.','' }}">Older Releases</a>
+            <a href="{site.url('docs/all')}#{detail.version.replace('.','')}">Older Releases</a>
         </div>
     </div>
-    {% endif %}
-    {% endfor %}
-    {% for release in site.data.grpc.releases %}
-    {% if release.supported %}
-    {% assign detail = release.detail[0] %}
+    {/if}
+    {/for}
+
+    {#for release in cdi:grpcreleases.list}
+    {#if release.supported}
+    {#let detail = release.detail[0]}
     <div class="release">
         <div class="release-body">
-            <h4 class="release-title">RESTEasy gRPC {{ detail.version }} <small>({{ detail.date }})</small></h4>
+            <h4 class="release-title">RESTEasy gRPC {detail.version} <small>({detail.date})</small></h4>
             <ul>
-                <li><a href="{{ site.baseurl }}{{ detail.documentation.link }}">Documentation</a></li>
-                {% if detail.download_link %}
-                <li><a href="{{ detail.download_link }}">Download</a></li>
-                {% endif %}
-                {% if detail.release_notes %}
-                <li><a href="{{ detail.release_notes }}">Release Notes</a></li>
-                {% endif %}
+                <li><a href="{site.url(detail.documentation.link)}">Documentation</a></li>
+                {#if detail.downloadLink}
+                <li><a href="{detail.downloadLink}">Download</a></li>
+                {/if}
+                {#if detail.releaseNotes}
+                <li><a href="{detail.releaseNotes}">Release Notes</a></li>
+                {/if}
             </ul>
         </div>
     </div>
-    {% endif %}
-    {% endfor %}
+    {/if}
+    {/for}
 </div>

content/docs/all-docs.md

@@ -1,5 +1,5 @@
 ---
 layout: doc-listing
 title: Documentation
-permalink: /docs/all/
+link: /docs/all/
 ---

content/feed.xml

@@ -2,7 +2,7 @@
 layout:     post
 title:       "On the road to RESTEasy 3.1.0 release..."
 subtitle:   ""
-date:            2019-09-13 12:06:00
+date:       2016-09-13 12:06:00
 author:     Alessio Soldano
 ---
 

content/posts/2016-09-13-on-the-road-to-resteasy-310-release.md

@@ -2,7 +2,7 @@
 layout:     post
 title:       "RESTEasy 3.1.0.Final is out"
 subtitle:   ""
-date:            2016-12-14 10:17:00
+date:       2016-12-14 10:17:00
 author:     Alessio Soldano
 ---
 

content/posts/2016-12-14-resteasy-310final-is-out.md

@@ -2,7 +2,7 @@
 layout:     post
 title:       "A brief introduction to the RESTEasy Tracing Feature"
 subtitle:   ""
-date:            2018-06-11 23:53:00
+date:       2018-06-11 23:53:00
 author:     Weinan Li
 ---
 Tracing feature is a way for the users of the RESTEasy to understand what's going on internally in the container when a request is processed. It's different from the pure logging system or profiling feature, which provide more general information about the request/response info, etc.

content/posts/2018-06-11-a-brief-introduction-to-the-resteasy-tracing-feature.md

@@ -2,7 +2,7 @@
 layout:     post
 title:       "New: Asynchronous container filters"
 subtitle:   ""
-date:            2018-06-18 00:03:55
+date:       2018-06-18 00:03:55
 author:     Stephane Epardaud
 ---
 

content/posts/2018-06-18-new-asynchronous-container-filters.md

@@ -2,7 +2,7 @@
 layout:     post
 title:       "RESTEasy Spring Boot starter 2.0.0.Final"
 subtitle:   ""
-date:            2018-07-31 10:18:00
+date:       2018-07-31 10:18:00
 author:     Alessio Soldano
 ---
 A couple of months ago, we [announced](https://developer.jboss.org/community/resteasy/blog/2018/05/23/resteasy-spring-boot-starter-has-moved) the move of the **RESTEasy Spring Boot starter** to [RESTEasy organization on GitHub](https://github.com/resteasy/resteasy-spring-boot). We also mentioned that soon a new version of the starter would have been available... and here we are today, presenting [release 2.0.0.Final](https://github.com/resteasy/resteasy-spring-boot/tree/2.0.0.Final), which

content/posts/2018-07-31-resteasy-spring-boot-starter-200final.md

@@ -12,7 +12,7 @@ RESTEasy has added WADL grammar support by this PR:
 
 The major change is that `ResteasyWadlGrammar` is added into `ResteasyWadlWriter`：
 
-![Class+Diagram22](/img/blog/Class+Diagram22.png)
+![Class+Diagram22](/img/blog/Class-Diagram22.png)
 
 In addition, the `ResteasyWadlWriter` is rewritten now, and all the static methods are now instance methods. It means users need to create an instance of `ResteasyWadlWriter` and put it into per-deployment scope.
 

content/posts/2018-10-31-resteasy-wadl-grammar-support.md

@@ -2,7 +2,7 @@
 layout:     post
 title:       "The UndertowJaxrsSpringServer"
 subtitle:   ""
-date:            2019-03-13 12:48:00
+date:       2019-03-13 12:48:00
 author:     Weinan Li
 ---