This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/mina-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new ba953409e Updated site from master
(03c9bf93c3280d413c93bdc9dcec8081e4346f6e)
ba953409e is described below
commit ba953409eb5f69a7a1d245a2b4b83b782254d49b
Author: jenkins <[email protected]>
AuthorDate: Tue Oct 15 13:57:02 2024 +0000
Updated site from master (03c9bf93c3280d413c93bdc9dcec8081e4346f6e)
---
content/index.xml | 2 +-
content/mina-project/developer-guide.html | 11 +++++++----
content/mina-project/index.xml | 2 +-
content/sitemap.xml | 4 ++--
4 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/content/index.xml b/content/index.xml
index 0c6982c68..bec435baa 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -1250,7 +1250,7 @@ Why use a ProtocolCodecFilter? TCP guarantees delivery
of all packets in the co
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://mina.apache.org/mina-project/developer-guide.html</guid>
- <description>Building MINA Please read the Developer Infrastructure
Information if you haven't yet before you proceed. Preparing the release
for the vote Step 0: Building MINA Step 1: Tagging and Deploying step 2 :
Processing with a dry run Step 3 : Processing with the real release Step 4 :
perform the release Step 5 : closing the staging release on nexus Step 6 :
Build the Site Step 7 : Sign the packages Step 8 : Publish Source and Binary
Distribution Packages Step 9 : Test [...]
+ <description>Building MINA Please read the Developer Infrastructure
Information if you haven't yet before you proceed. Preparing the release
for the vote Step 0: Building MINA Step 1: Tagging and Deploying step 2 :
Processing with a dry run Step 3 : Processing with the real release Step 4 :
perform the release Step 5 : closing the staging release on nexus Step 6 :
Build the Site Step 7 : Sign the packages Step 8 : Publish Source and Binary
Distribution Packages Step 9 : Test [...]
</item>
<item>
diff --git a/content/mina-project/developer-guide.html
b/content/mina-project/developer-guide.html
index 123de1175..00efc6be5 100644
--- a/content/mina-project/developer-guide.html
+++ b/content/mina-project/developer-guide.html
@@ -155,7 +155,10 @@
</ul>
</nav>
<h1 id="checking-out-the-code">Checking out the code</h1>
-<p>You need Git to check out the source code from our source code repository,
and [Maven(https://maven.apache.org/) 3.8.5 (pick the latest Maven version) to
build the source code (Building with Maven 3.0 will also work). The following
example shows how to build the current stable branch (2.0.9).</p>
+<div class="note" markdown="1">
+ The current <em>MINA</em>em> code requires to be built with Java 11 or
higher.
+</div>
+<p>You need <strong>Git</strong> to check out the source code from our source
code repository, and <a href="https://maven.apache.org/">Maven</a> 3.8.5 (pick
the latest Maven version) to build the source code (Building with Maven 3.0
will also work). The following example shows how to build the current stable
branch (2.0.9).</p>
<div class="highlight"><pre
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code
class="language-bash" data-lang="bash">$ git clone
https://gitbox.apache.org/repos/asf/mina.git mina
$ <span style="color:#a2f">cd</span> mina
$ mvn -Pserial clean install <span
style="color:#080;font-style:italic"># Build packages (JARs) for the core API
and other</span>
@@ -164,8 +167,8 @@ $ mvn -Pserial site <span
style="color:#080;font-style:ital
$ mvn -Pserial package assembly:assembly <span
style="color:#080;font-style:italic"># Generate a tarball (package goal needed
to fix an assembly plugin bug)</span>
$ mvn -Pserial eclipse:eclipse <span
style="color:#080;font-style:italic"># Generate Eclipse project files if you
want</span>
</code></pre></div><p>Eclipse users:
-Don’t forget to declare a classpath variable named M2_REPO, pointing to
<code>~/.m2/repository</code>, otherwise many links to existing jars will be
broken.
-You can declare new variables in Eclipse in Windows -> Preferences…
and selecting Java -> Build Path -> Classpath Variables</p>
+Don’t forget to declare a classpath variable named
<strong>M2_REPO</strong>, pointing to <code>~/.m2/repository</code>, otherwise
many links to existing jars will be broken.
+You can declare new variables in Eclipse in <em>Windows ->
Preferences…</em> and selecting <em>Java -> Build Path ->
Classpath Variables</em>.</p>
<p>There are also other branches that might interest you:</p>
<ul>
<li>trunk: Where big changes take place everyday</li>
@@ -278,7 +281,7 @@ $ mvn clean install -Pserial
</div>
<div class="info" markdown="1">
<strong>In case of a problem...</strong><br>
-<pre><code>It's frequent that the dry-run fails, typically when you have some
Javadoc issues (with Java 8, the compiler is really picky about wrong HTML tags
or missing parameters).
+<pre><code>It's frequent that the dry-run fails, typically when you have some
Javadoc issues (starting with Java 8, the compiler is really picky about wrong
HTML tags or missing parameters).
You can rollback the release with the command:
diff --git a/content/mina-project/index.xml b/content/mina-project/index.xml
index b9fcce822..4be000e9b 100644
--- a/content/mina-project/index.xml
+++ b/content/mina-project/index.xml
@@ -613,7 +613,7 @@ Why use a ProtocolCodecFilter? TCP guarantees delivery of
all packets in the co
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://mina.apache.org/mina-project/developer-guide.html</guid>
- <description>Building MINA Please read the Developer Infrastructure
Information if you haven't yet before you proceed. Preparing the release
for the vote Step 0: Building MINA Step 1: Tagging and Deploying step 2 :
Processing with a dry run Step 3 : Processing with the real release Step 4 :
perform the release Step 5 : closing the staging release on nexus Step 6 :
Build the Site Step 7 : Sign the packages Step 8 : Publish Source and Binary
Distribution Packages Step 9 : Test [...]
+ <description>Building MINA Please read the Developer Infrastructure
Information if you haven't yet before you proceed. Preparing the release
for the vote Step 0: Building MINA Step 1: Tagging and Deploying step 2 :
Processing with a dry run Step 3 : Processing with the real release Step 4 :
perform the release Step 5 : closing the staging release on nexus Step 6 :
Build the Site Step 7 : Sign the packages Step 8 : Publish Source and Binary
Distribution Packages Step 9 : Test [...]
</item>
<item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 597932bad..c6c18cfcb 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -619,7 +619,7 @@
<url>
<loc>https://mina.apache.org/mina-project/developer-guide.html</loc>
- <lastmod>2023-06-04T07:12:06+02:00</lastmod>
+ <lastmod>2024-10-15T15:51:07+02:00</lastmod>
</url>
<url>
@@ -919,7 +919,7 @@
<url>
<loc>https://mina.apache.org/mina-project.html</loc>
- <lastmod>2024-10-15T12:01:00+02:00</lastmod>
+ <lastmod>2024-10-15T15:51:07+02:00</lastmod>
</url>
<url>