Update outgoing links for JBoss and JSR-88 container features

codehaus-cargo · Aug 27, 2023 · 102a962 · 102a962
1 parent 57b70ee
commit 102a962
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 19 deletions.
diff --git a/cargo/JBoss+Remote+Deployer.html b/cargo/JBoss+Remote+Deployer.html
@@ -487,7 +487,7 @@ <h3 id="JBossRemoteDeployer-JBoss5.0.x,5.1.x,6.0.xand6.1.x">JBoss 5.0.x, 5.1.x,
 </pre>
              </div>
             </div>
-            <p>That is a known bug, documented in <a href="http://community.jboss.org/wiki/WhydoIgetasocketconnectionerrorwhenusingremoteJBossAS">http://community.jboss.org/wiki/WhydoIgetasocketconnectionerrorwhenusingremoteJBossAS</a> and the solution presented on that document is to use a cron job as the root user to fix the file when it gets broken.</p>
+            <p>That is a known bug, documented in <span class="nolink"><a href="https://developer.jboss.org/docs/DOC-16380">https://developer.jboss.org/docs/DOC-16380</a>,</span> and the solution presented on that document is to use a cron job as the root user to fix the file when it gets broken.</p>
             <p>First, create the correct version of <code>/etc/hosts</code> and save it somewhere, such as <code>/etc/hosts.fixed</code>, and populate it with the following contents (replace <code>myhost</code> with the hostname of your computer, as reported by the <code>hostname</code> command, and the correct IP assignment, as reported by <code>ipconfig</code>):</p>
             <div class="code panel pdl conf-macro output-block" style="border-width: 1px;">
              <div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;">

diff --git a/cargo/JSR88.html b/cargo/JSR88.html
@@ -301,26 +301,16 @@ <h3 id="JSR88-Explanation">Explanation</h3>
            <script type="text/javascript" src="https://pagead2.googlesyndication.com/pagead/show_ads.js">
   </script>
           </center>
-          <h3 id="JSR88-GlassFish3.xto5.xandPayara">GlassFish 3.x to 5.x and Payara</h3>
-          <div class="confluence-information-macro confluence-information-macro-information conf-macro output-block">
-           <p class="title">GlassFish 6.x and remote deployment</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span>
-           <div class="confluence-information-macro-body">
-            <p>The <a href="GlassFish+6.x.html">GlassFish 6.x</a> container doesn't have any remote deployers yet, as GlassFish 6.0 lacks JSR-88 support and it is unclear whether this will be included in a future release.</p>
-            <p>Until then, please follow the <a href="Remote+deployments+to+GlassFish+6.x+onwards+and+to+recent+Payara+versions.html">remote deployment instructions for GlassFish 6.x</a>.</p>
-           </div>
-          </div>
-          <div class="confluence-information-macro confluence-information-macro-information conf-macro output-block">
-           <p class="title">Remote deployment to recent Payara versions</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span>
-           <div class="confluence-information-macro-body">
-            <p>Recent versions of Payara might have <a href="https://codehaus-cargo.atlassian.net/browse/CARGO-1588">issues getting deployables uploaded via JSR-88</a>, resulting in errors such as:</p>
-            <div class="code panel pdl conf-macro output-block" style="border-width: 1px;">
-             <div class="codeContent panelContent pdl">
-              <pre class="syntaxhighlighter-pre">Distributing failed: Action failed Deploying application to target server failed; File not found</pre>
-             </div>
-            </div>
-            <p>If you encounter such errors, please follow the <a href="Remote+deployments+to+GlassFish+6.x+onwards+and+to+recent+Payara+versions.html">remote deployment instructions for recent Payara versions</a>.</p>
+          <h3 id="JSR88-GlassFish6.xonwards,aswellasnewerversionsofPayara">GlassFish 6.x onwards, as well as newer versions of Payara</h3>
+          <p>The <a href="GlassFish+6.x.html">GlassFish 6.x</a> container doesn't have any remote deployers yet, as GlassFish 6.0 lacks JSR-88 support and it is unclear whether this will be included in a future release. Until then, please follow the <a href="Remote+deployments+to+GlassFish+6.x+onwards+and+to+recent+Payara+versions.html">remote deployment instructions for GlassFish 6.x</a>.</p>
+          <p>Recent versions of Payara might have <a href="https://codehaus-cargo.atlassian.net/browse/CARGO-1588">issues getting deployables uploaded via JSR-88</a>, resulting in errors such as:</p>
+          <div class="code panel pdl conf-macro output-block" style="border-width: 1px;">
+           <div class="codeContent panelContent pdl">
+            <pre class="syntaxhighlighter-pre">Distributing failed: Action failed Deploying application to target server failed; File not found</pre>
            </div>
           </div>
+          <p>If you encounter such errors, please follow the <a href="Remote+deployments+to+GlassFish+6.x+onwards+and+to+recent+Payara+versions.html">remote deployment instructions for recent Payara versions</a>.</p>
+          <h3 id="JSR88-GlassFish3.xto5.xandPayara">GlassFish 3.x to 5.x and Payara</h3>
           <p>The <a href="GlassFish+3.x.html">GlassFish 3.x</a>, <a href="GlassFish+4.x.html">GlassFish 4.x</a>,&nbsp;<a href="GlassFish+5.x.html">GlassFish 5.x</a> and&nbsp;<a href="Payara.html">Payara</a> remote containers use the JSR-88 API. For the connection to succeed, the following JARs need to be in the container classpath or in the current Java Thread's context classloader:</p>
           <ul>
            <li>deployment-client.jar and its dependencies - for <a href="GlassFish+3.x.html">GlassFish 3.x</a>, these seem to be: