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/activemq-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 617e875de Automatic Site Publish by Buildbot
617e875de is described below
commit 617e875def62875afe9f5cc8d948286068f69dbd
Author: buildbot <[email protected]>
AuthorDate: Fri Nov 15 16:57:20 2024 +0000
Automatic Site Publish by Buildbot
---
.../classic/documentation/activemq-artemis-roadmap.html | 4 ++--
.../how-does-classic-compare-to-artemis.html | 2 +-
output/index.html | 16 +---------------
3 files changed, 4 insertions(+), 18 deletions(-)
diff --git
a/output/components/classic/documentation/activemq-artemis-roadmap.html
b/output/components/classic/documentation/activemq-artemis-roadmap.html
index c2caabaa7..7c5d59729 100644
--- a/output/components/classic/documentation/activemq-artemis-roadmap.html
+++ b/output/components/classic/documentation/activemq-artemis-roadmap.html
@@ -93,13 +93,13 @@
<div class="container" >
<div class="row" style="margin-top: 30px">
<div class="col-12 main">
- <p>The goal of this page is to identify the outstanding issues that
must be addressed by Artemis in order to achieve feature parity with Classic.
The overall objective for working toward feature parity between Classic and
Artemis is for Artemis to eventually become the next major version of ActiveMQ.
This page exists so that we can work together as a group to achieve this goal.
This page does <strong>not</strong> list the features which Artemis has
<em>beyond</em> what currently [...]
+ <p>The goal of this page is to identify the outstanding issues that
must be addressed by Artemis in order to achieve feature parity with ActiveMQ
Classic. This page does <strong>not</strong> list the features which Artemis
has <em>beyond</em> what currently exists in Classic.</p>
<h2 id="featuresscenarios">Features/Scenarios</h2>
<p>This section should be used to compare what features from ActiveMQ Classic
have been implemented in Artemis. Feature items can be listed, with links to
JIRA tickets for longer conversation and hashing out specific feature details.
This will help us to more clearly track everything that Artemis needs. This
list of features was taken from the Classic <a href="features">features
page</a>.</p>
-<p>Keep in mind that not every feature must have a β
. Artemis may still be
ready to become ActiveMQ <em>Next</em> even if features on this page still have
an β if those features are deemed low priority. Artemis is not meant to be a
100% complete reimplementation of ActiveMQ Classic. Features should only be
reimplemented where it makes good sense.</p>
+<p>Keep in mind that not every feature must have a β
. Artemis is not meant to
be a 100% complete reimplementation of ActiveMQ Classic. Features should only
be reimplemented where it makes good sense.</p>
<h3 id="protocol-support">Protocol Support</h3>
diff --git
a/output/components/classic/documentation/how-does-classic-compare-to-artemis.html
b/output/components/classic/documentation/how-does-classic-compare-to-artemis.html
index f047fee31..ddd6e68d1 100644
---
a/output/components/classic/documentation/how-does-classic-compare-to-artemis.html
+++
b/output/components/classic/documentation/how-does-classic-compare-to-artemis.html
@@ -97,7 +97,7 @@
<p><a href="../../../components/artemis">Artemis</a> is the codename used for
the HornetQ code that was donated to the Apache Foundation.</p>
-<p>Artemis may eventually become the successor to Classic 6.x/5.x. Classic 6.x
is a modernization of Classic 5.x with support for Jakarta EE.</p>
+<p>Itβs a complete broker, similar to ActiveMQ Classic.</p>
</div>
</div>
diff --git a/output/index.html b/output/index.html
index 12fe5ea1e..5d24514fa 100644
--- a/output/index.html
+++ b/output/index.html
@@ -167,20 +167,6 @@
</div>
- <!-- General info -->
-<div class="row d-none d-lg-block">
- <div class="col-sm-12 narative">
- <div class="card">
- <div class="card-body narative">
- <span>
- <p>There are currently two "flavors" of ActiveMQ available - the
well-known "classic" broker and the "next generation" broker code-named
<i>Artemis</i>. Once Artemis reaches a sufficient level of feature parity with
the "Classic" code-base it will become the next major version of ActiveMQ.
Initial <a href="/components/artemis/migration">migration documentation</a> is
available as well as a development <a
href="/activemq-artemis-roadmap">roadmap</a> for Artemis.</p>
- </span>
- </div>
- </div>
- </div>
-</div>
-
-
<!-- Components -->
<div class="row align-middle">
<div class="col-lg-6 col-md-auto">
@@ -189,7 +175,7 @@
<h4 class="card-title text-pink">ActiveMQ Classic</h4>
<p>Long established, endlessly pluggable architecture serving many
generations of applications.</p>
<ul>
- <li>Jakarta 3.1, JMS 2.0, and JMS 1.1 with full client
implementation including JNDI</li>
+ <li>Jakarta Messaging 3.1, JMS 2.0, and JMS 1.1 with full client
implementation including JNDI</li>
<li>High availability using shared storage</li>
<li>Familiar JMS-based addressing model</li>
<li>Network of brokers for distributing load</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
