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/struts-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1336acf Updates production by Jenkins
1336acf is described below
commit 1336acf0cd1be91eb1c35a8a2dbf5653df17bd8c
Author: jenkins <bui...@apache.org>
AuthorDate: Tue Feb 20 18:30:58 2018 +0000
Updates production by Jenkins
---
content/announce-2006.html | 4 +-
content/builds.html | 4 +-
content/doap_Struts.rdf | 2 +-
content/kickstart.html | 230 ++++++++++++++--------------------------
content/release-guidelines.html | 2 +-
5 files changed, 85 insertions(+), 157 deletions(-)
diff --git a/content/announce-2006.html b/content/announce-2006.html
index 00908ec..c3693af 100644
--- a/content/announce-2006.html
+++ b/content/announce-2006.html
@@ -630,8 +630,8 @@
</p>
<ul>
<li>
- <a href="http://struts.apache.org/downloads.html";>
- http://struts.apache.org/downloads.html</a>
+ <a href="http://struts.apache.org/releases.html";>
+ http://struts.apache.org/releases.html</a>
</li>
</ul>
<p>
diff --git a/content/builds.html b/content/builds.html
index 9742e2e..0c2178f 100644
--- a/content/builds.html
+++ b/content/builds.html
@@ -200,7 +200,7 @@ your own applications!)</p>
<p><em>Again: Use at your own risk!</em></p>
<p>If you do <strong>not</strong> plan to contribute to the development of the
framework, then you probably want to download a
-<a href="downloads.html">release</a></p>
+<a href="releases.html">release</a></p>
<p>NOTE: The Struts 2 nightly build is not fully operational. We suggest that
contributors checkout
the <a href="#SourceCode">source code</a> instead.</p>
@@ -215,7 +215,7 @@ Library distributions include any external dependencies
needed to use a product
When a build is judged “ready for prime time”, it is promoted to “General
Availability” status and may be
made the “Best Available” release. If the group feels that a build requires
more testing, then it may be marked
as “Beta” release. When a test build is upgraded to “Beta” or “GA” by a vote
of the project members,
-we make the distribution available as a formal <a
href="downloads.html">release.</a></p>
+we make the distribution available as a formal <a
href="releases.html">release.</a></p>
<h2 id="maven-snapshots">Maven Snapshots</h2>
diff --git a/content/doap_Struts.rdf b/content/doap_Struts.rdf
index 6337de6..1cc7cbe 100644
--- a/content/doap_Struts.rdf
+++ b/content/doap_Struts.rdf
@@ -31,7 +31,7 @@
<description>The Apache Struts Project offers the Apache Struts 2 web
framework which is a comprehensive and modular tooling stack for creating
web-based Java applications. Struts 2, emerged from the WebWork 2 framework, is
an excellent choice for teams who value elegant solutions to difficult
problems. </description>
<bug-database rdf:resource="https://issues.apache.org/jira/browse/WW/"; />
<mailing-list rdf:resource="http://struts.apache.org/mail.html"; />
- <download-page rdf:resource="http://struts.apache.org/downloads.html"; />
+ <download-page rdf:resource="http://struts.apache.org/releases.html"; />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/web-framework";
/>
</Project>
diff --git a/content/kickstart.html b/content/kickstart.html
index 5e55667..6a956de 100644
--- a/content/kickstart.html
+++ b/content/kickstart.html
@@ -132,7 +132,7 @@
<ul id="markdown-toc">
<li><a href="#general" id="markdown-toc-general">General</a> <ul>
<li><a href="#im-new-to-apache-struts-how-do-i-get-started"
id="markdown-toc-im-new-to-apache-struts-how-do-i-get-started">I’m new to
Apache Struts. How do I get started?</a></li>
- <li><a
href="#looking-at-the-releases-page-some-versions-seem-to-be-missing-what-happened-to-them"
id="markdown-toc-looking-at-the-releases-page-some-versions-seem-to-be-missing-what-happened-to-them">Looking
at the releases page, some versions seem to be missing. What happened to
them?</a></li>
+ <li><a href="#releases" id="markdown-toc-releases">Looking at the
releases page, some versions seem to be missing. What happened to them?</a></li>
<li><a href="#why-is-the-project-called-struts"
id="markdown-toc-why-is-the-project-called-struts">Why is the project called
“Struts”?</a></li>
<li><a href="#how-is-apache-struts-licensed"
id="markdown-toc-how-is-apache-struts-licensed">How is Apache Struts
licensed?</a></li>
<li><a href="#can-apache-struts-be-used-in-a-commercial-product"
id="markdown-toc-can-apache-struts-be-used-in-a-commercial-product">Can Apache
Struts be used in a commercial product?</a></li>
@@ -161,232 +161,160 @@
<h2 id="general">General</h2>
-<ul>
- <li>
- <h3 id="im-new-to-apache-struts-how-do-i-get-started">I’m new to Apache
Struts. How do I get started?</h3>
- </li>
-</ul>
+<h3 id="im-new-to-apache-struts-how-do-i-get-started">I’m new to Apache
Struts. How do I get started?</h3>
-<p>The best place to start is with the “best available” <a
href="downloads.html">release</a>.
- If you are new to Java or web development, as well as Apache Struts, be sure
to review the
- <a href="primer.html">Key Technologies Primer</a>.</p>
+<p>The best place to start is with the “best available” <a
href="releases.html">release</a>.
+If you are new to Java or web development, as well as Apache Struts, be sure
to review the
+<a href="primer.html">Key Technologies Primer</a>.</p>
<p>The main Struts web site includes documentation for the latest “General
Availability” release
- in each major release series. The development section of the site inclues
draft documentation
- for upcoming releases. If you are just getting started, focus on the latest
General
- Availability release, Documentation for past <a
href="downloads.html">releases</a> is also available.</p>
+in each major release series. The development section of the site inclues
draft documentation
+for upcoming releases. If you are just getting started, focus on the latest
General
+Availability release, Documentation for past <a
href="releases.html">releases</a> is also available.</p>
<p>If you have questions, you can search the <a href="mail.html#archives">User
Mailing List archives</a>,
- or <a href="mail.html">post your own question to the list</a>. (Plain old
Google usually works too!)</p>
+or <a href="mail.html">post your own question to the list</a>. (Plain old
Google usually works too!)</p>
-<ul>
- <li>
- <h3
id="looking-at-the-releases-page-some-versions-seem-to-be-missing-what-happened-to-them">Looking
at the releases page, some versions seem to be missing. What happened to
them?</h3>
- </li>
-</ul>
+<h3 id="releases">Looking at the releases page, some versions seem to be
missing. What happened to them?</h3>
<p>Apache Struts uses a “milestone build” system to create releases. First, we
create a build
- with a milestone version number, like Struts 2.0.42, and post the
distribution in the development area.
- The development group tests the distribution, and then we decide whether or
not to release it.
- The distribution includes everything that would be released, including the
documentation and the release notes
- for this version.</p>
+with a milestone version number, like Struts 2.0.42, and post the distribution
in the development area.
+The development group tests the distribution, and then we decide whether or
not to release it.
+The distribution includes everything that would be released, including the
documentation and the release notes
+for this version.</p>
<p>If we find a significant problem with the distribution, we may decide not
to release it, and just leave
- the distribution as a “test build”. The testing may take several days, and
in the meantime, we want to keep
- the project moving, and so we just go onto the next version number.
- Using our example, the next distribution would be labeled 2.0.43, even if
version 2.0.42 was never officially
- released.</p>
+the distribution as a “test build”. The testing may take several days, and in
the meantime, we want to keep
+the project moving, and so we just go onto the next version number.
+Using our example, the next distribution would be labeled 2.0.43, even if
version 2.0.42 was never officially
+released.</p>
<p>Often we will first grade a release as a “beta”, and invite other users to
test it too. If this second
- round of beta testing goes well, then we may mark the release “General
Availability”.
- Usually, that designation would also make it the new “Best Available”
release. In this case, we don’t create
- another distribution, but simply adjust the status of the same set of bits
that people have been testing all along.</p>
+round of beta testing goes well, then we may mark the release “General
Availability”.
+Usually, that designation would also make it the new “Best Available” release.
In this case, we don’t create
+another distribution, but simply adjust the status of the same set of bits
that people have been testing all along.</p>
<p>In practice, the milestone build system is fast and efficient and creates
the fewest number of “candidate builds”
- between releases.</p>
+between releases.</p>
-<ul>
- <li>
- <h3 id="why-is-the-project-called-struts">Why is the project called
“Struts”?</h3>
- </li>
-</ul>
+<h3 id="why-is-the-project-called-struts">Why is the project called
“Struts”?</h3>
<p>It’s a reference to “struts” in the architectural sense, a reminder of the
nearly invisible pieces that hold up
- buildings, houses, and bridges.</p>
+buildings, houses, and bridges.</p>
-<ul>
- <li>
- <h3 id="how-is-apache-struts-licensed">How is Apache Struts licensed?</h3>
- </li>
-</ul>
+<h3 id="how-is-apache-struts-licensed">How is Apache Struts licensed?</h3>
<p>All Apache Struts products are copyrighted software available under the <a
href="http://www.apache.org/licenses";>Apache License</a>,
- a "free-to-use, business-friendly license".</p>
+a "free-to-use, business-friendly license".</p>
-<ul>
- <li>
- <h3 id="can-apache-struts-be-used-in-a-commercial-product">Can Apache
Struts be used in a commercial product?</h3>
- </li>
-</ul>
+<h3 id="can-apache-struts-be-used-in-a-commercial-product">Can Apache Struts
be used in a commercial product?</h3>
<p>Yes. The only requirements you must meet are those listed in the <a
href="http://www.apache.org/licenses";>Apache License</a>.</p>
-<ul>
- <li>
- <h3 id="do-i-have-to-credit-apache-struts-on-my-own-web-site">Do I have to
credit Apache Struts on my own web site?</h3>
- </li>
-</ul>
+<h3 id="do-i-have-to-credit-apache-struts-on-my-own-web-site">Do I have to
credit Apache Struts on my own web site?</h3>
<p>You need to credit Apache Struts if you <strong>redistribute your own
framework</strong> based on our products
- for other people to use. (See the <a
href="http://www.apache.org/LICENSE";>Apache License</a> for details.)
- But you do <strong>not</strong> need to credit Apache Struts just because
your web application utilizes one of our products.
- It’s the same situation as using the Apache HTTPD server or Tomcat. Not
required if its just running your web site.
- Required if you’ve used the source code to create your own server that you
are redistributing to other people.</p>
-
-<ul>
- <li>
- <h3 id="are-there-isps-that-will-host-my-java-web-application">Are there
ISPs that will host my Java web application?</h3>
- </li>
-</ul>
+for other people to use. (See the <a
href="http://www.apache.org/LICENSE";>Apache License</a> for details.)
+But you do <strong>not</strong> need to credit Apache Struts just because your
web application utilizes one of our products.
+It’s the same situation as using the Apache HTTPD server or Tomcat. Not
required if its just running your web site.
+Required if you’ve used the source code to create your own server that you are
redistributing to other people.</p>
+
+<h3 id="are-there-isps-that-will-host-my-java-web-application">Are there ISPs
that will host my Java web application?</h3>
<p>For a listing of some Java and Struts ISPs, visit the <a
href="http://struts.sf.net/community/index.html";>Struts Community Resources</a>
- area on SourceForge.</p>
+area on SourceForge.</p>
-<ul>
- <li>
- <h3 id="is-there-a-particularly-good-ide-to-use">Is there a particularly
good IDE to use?</h3>
- </li>
-</ul>
+<h3 id="is-there-a-particularly-good-ide-to-use">Is there a particularly good
IDE to use?</h3>
<p>The frameworks should work well with any development environment that you
would like to use, as well as with any
- programmers editor. The members of the Apache Struts development group each
use their own tools such as
- <a href="http://www.gnu.org/software/emacs/emacs.html";>Emacs</a>, <a
href="http://www.jetbrains.com/idea/";>IntelliJ IDEA</a>,
- <a href="http://www.eclipse.org/";>Eclipse</a>, and <a
href="http://www.netbeans.org/";>NetBeans</a>.</p>
+programmers editor. The members of the Apache Struts development group each
use their own tools such as
+<a href="http://www.gnu.org/software/emacs/emacs.html";>Emacs</a>, <a
href="http://www.jetbrains.com/idea/";>IntelliJ IDEA</a>,
+<a href="http://www.eclipse.org/";>Eclipse</a>, and <a
href="http://www.netbeans.org/";>NetBeans</a>.</p>
<p>For more, see the <a
href="http://wiki.apache.org/struts/StrutsMyFavoriteIDE";>IDE discussion
page</a> in the Struts wiki.</p>
<h2 id="product-support">Product Support</h2>
-<ul>
- <li>
- <h3 id="where-can-i-get-help-with-apache-struts">Where can I get help with
Apache Struts?</h3>
- </li>
-</ul>
+<h3 id="where-can-i-get-help-with-apache-struts">Where can I get help with
Apache Struts?</h3>
<p>Each release of Struts comes with a User Guide or set of Tutorials to
introduce people to the framework
- and its underlying technologies. Various components also have their own
in-depth Developers Guide, to cover
- more advanced topics. Comprehensive Javadocs are provided for each release,
along with the <strong>full source code</strong>.</p>
+and its underlying technologies. Various components also have their own
in-depth Developers Guide, to cover
+more advanced topics. Comprehensive Javadocs are provided for each release,
along with the <strong>full source code</strong>.</p>
<p>The <a href="mail.html">Struts user mailing list</a> is also very active,
and welcomes posts from new users. Before
- posting a new question, be sure to consult the <strong><a
href="mail.html#Archives">MAILING LIST ARCHIVE</a></strong>
- and the very excellent <a
href="http://www.catb.org/~esr/faqs/smart-questions.html";>How To Ask Questions
The Smart Way</a>
- by Eric Raymond. Please do be sure to <a
href="http://expita.com/nomime.html";>turn off HTML</a> in your
- email client before posting.</p>
-
-<ul>
- <li>
- <h3 id="is-commercial-support-available">Is commercial support
available?</h3>
- </li>
-</ul>
+posting a new question, be sure to consult the <strong><a
href="mail.html#Archives">MAILING LIST ARCHIVE</a></strong>
+and the very excellent <a
href="http://www.catb.org/~esr/faqs/smart-questions.html";>How To Ask Questions
The Smart Way</a>
+by Eric Raymond. Please do be sure to <a
href="http://expita.com/nomime.html";>turn off HTML</a> in your
+email client before posting.</p>
+
+<h3 id="is-commercial-support-available">Is commercial support available?</h3>
<p>The Apache Software Foundation does not provide commercial support for any
of our software products,
- including Apache Struts. However, third parties may offer different degrees
of support.</p>
+including Apache Struts. However, third parties may offer different degrees of
support.</p>
-<ul>
- <li>
- <h3
id="if-a-product-doesnt-do-what-i-want-can-i-request-that-a-feature-be-added">If
a product doesn’t do what I want, can I request that a feature be added?</h3>
- </li>
-</ul>
+<h3
id="if-a-product-doesnt-do-what-i-want-can-i-request-that-a-feature-be-added">If
a product doesn’t do what I want, can I request that a feature be added?</h3>
<p>First, it’s important to remember that Apache Struts is an all-volunteer
project. We don’t charge anyone
- anything to use Apache Struts products. Committers and other developers work
on Apache Struts products because
- they need to use it with their own applications. If others can use it too,
that’s “icing on the cake”.
- If you <a href="helping.html">submit a patch</a> for a feature that a
Committer finds useful, then that
- Committer may choose to volunteer his or her time to apply the patch.
- If you just submit an idea without a patch, it is much less likely to be
added (since first someone else has to
- volunteer their time to write the patch).</p>
+anything to use Apache Struts products. Committers and other developers work
on Apache Struts products because
+they need to use it with their own applications. If others can use it too,
that’s “icing on the cake”.
+If you <a href="helping.html">submit a patch</a> for a feature that a
Committer finds useful, then that
+Committer may choose to volunteer his or her time to apply the patch.
+If you just submit an idea without a patch, it is much less likely to be added
(since first someone else has to
+volunteer their time to write the patch).</p>
<p>We are grateful for any patches, and we welcome new ideas, but the best way
to see that something gets added
- to the framework is to do as much of the work as you can, rather than rely
on the “kindness of strangers”.
- Worst case, you can apply the patch to your copy of the framework and still
use the feature in your own application.
- (Which is what open source is <em>really</em> all about.)</p>
+to the framework is to do as much of the work as you can, rather than rely on
the “kindness of strangers”.
+Worst case, you can apply the patch to your copy of the framework and still
use the feature in your own application.
+(Which is what open source is <em>really</em> all about.)</p>
-<ul>
- <li>
- <h3 id="is-there-a-press-kit-for-apache-struts">Is there a press kit for
Apache Struts?</h3>
- </li>
-</ul>
+<h3 id="is-there-a-press-kit-for-apache-struts">Is there a press kit for
Apache Struts?</h3>
<p>Except for our <a href="announce.html">announcements page</a>, there is not
a formal press or media kit for Apache Struts.
- Queries from the press (and ONLY queries from the press, NOT support
questions or anything else!)
- should go to our media relations address: <a
href="mailto:press@apache.org">press@apache.org</a>.</p>
+Queries from the press (and ONLY queries from the press, NOT support questions
or anything else!)
+should go to our media relations address: <a
href="mailto:press@apache.org">press@apache.org</a>.</p>
-<ul>
- <li>
- <h3 id="where-can-i-report-a-potential-security-vulnerability">Where can I
report a potential security vulnerability?</h3>
- </li>
-</ul>
+<h3 id="where-can-i-report-a-potential-security-vulnerability">Where can I
report a potential security vulnerability?</h3>
<p>If you believe you’ve found a security vulnerability in Apache Struts,
please contact our security address - any
- emails not relating to security vulnerabilities will be ignored without a
reply (all security related information
- will be kept confidential unless otherwise indicated): <a
href="mailto:security@struts.apache.org">security@struts.apache.org</a>.</p>
+emails not relating to security vulnerabilities will be ignored without a
reply (all security related information
+will be kept confidential unless otherwise indicated): <a
href="mailto:security@struts.apache.org">security@struts.apache.org</a>.</p>
<h2 id="mailing-lists">Mailing Lists</h2>
-<ul>
- <li>
- <h3 id="is-there-a-digest-for-the-user-list">Is there a digest for the
User list?</h3>
- </li>
-</ul>
+<h3 id="is-there-a-digest-for-the-user-list">Is there a digest for the User
list?</h3>
<p>Yes. Send a blank message to <a
href="mailto:user-digest-subscribe@struts.apache.org">user-digest-subscribe@struts.	
[...]
<p>If you are subscribed to the digest, you can also post to the list. Just be
sure to send your post to
- the <a
href="mailto:user@struts.apache.org">user
list</a> rather than trying to reply to the digest.</p>
+the <a
href="mailto:user@struts.apache.org">user
list</a> rather than trying to reply to the digest.</p>
-<ul>
- <li>
- <h3 id="is-there-an-apache-struts-newsgroup">Is there an Apache Struts
newsgroup?</h3>
- </li>
-</ul>
+<h3 id="is-there-an-apache-struts-newsgroup">Is there an Apache Struts
newsgroup?</h3>
<p>Not a usenet group, but the Apache Struts User list can be accessed with
your favorite newsgroup reader from
- the <a href="http://news.gmane.org/";>GMane News Site</a>. Subscribe to
groups <code class="highlighter-rouge">gmane.comp.jakarta.struts.user</code>
- for the user list.</p>
+the <a href="http://news.gmane.org/";>GMane News Site</a>. Subscribe to groups
<code class="highlighter-rouge">gmane.comp.jakarta.struts.user</code>
+for the user list.</p>
-<ul>
- <li>
- <h3 id="why-didnt-my-posting-show-up-on-the-user-list">Why didn’t my
posting show up on the user list?</h3>
- </li>
-</ul>
+<h3 id="why-didnt-my-posting-show-up-on-the-user-list">Why didn’t my posting
show up on the user list?</h3>
<p>You must be subscribed to the <a
href="mailto:user-subscribe@struts.apache.org">user
list</a> or
- <a
href="mailto:user-digest-subscribe@struts.apache.org">user
digest</a> before posting (or use the
- <a href="http://news.gmane.org";>GMane Newsgroups</a> instead).</p>
+<a
href="mailto:user-digest-subscribe@struts.apache.org">user
digest</a> before posting (or use the
+<a href="http://news.gmane.org";>GMane Newsgroups</a> instead).</p>
-<ul>
- <li>
- <h3 id="are-there-separate-user-lists-for-struts-1-and-struts-2">Are there
separate user lists for Struts 1 and Struts 2?</h3>
- </li>
-</ul>
+<h3 id="are-there-separate-user-lists-for-struts-1-and-struts-2">Are there
separate user lists for Struts 1 and Struts 2?</h3>
<p>No. Each major version has it’s own JIRA project, but we share the mailing
lists.</p>
<p>To get the best response to an inquiry, please specify which version of
Struts is being used,
- including the milestone (“Struts 1.2.9”, for example). You can also include
the label <strong>[s1]</strong>
- or <strong>[s2]</strong> in the subject line of your post.</p>
+including the milestone (“Struts 1.2.9”, for example). You can also include
the label <strong>[s1]</strong>
+or <strong>[s2]</strong> in the subject line of your post.</p>
-<ul>
- <li>
- <h3 id="how-do-i-unsubscribe-from-the-mailing-list">How do I unsubscribe
from the mailing list?</h3>
- </li>
-</ul>
+<h3 id="how-do-i-unsubscribe-from-the-mailing-list">How do I unsubscribe from
the mailing list?</h3>
<p><strong>From the email account used to subscribe to the list</strong>, send
a blank message to
- <a
href="mailto:user-unsubscribe@struts.apache.org">user-unsubscribe@struts.apache.org</a>.</p>
+<a
href="mailto:user-unsubscribe@struts.apache.org">user-unsubscribe@struts.apache.org</a>.</p>
<p>If you are receiving the digest, you must send a blank email to
- <a
href="mailto:user-digest-unsubscribe@struts.apache.org">user-unsubscr...@struts.apache.org</a>
instead.</p>
+<a
href="mailto:user-digest-unsubscribe@struts.apache.org">user-unsubscr...@struts.apache.org</a>
instead.</p>
</section>
</article>
diff --git a/content/release-guidelines.html b/content/release-guidelines.html
index 5befcb2..a4e8480 100644
--- a/content/release-guidelines.html
+++ b/content/release-guidelines.html
@@ -137,7 +137,7 @@
<p>This document describes the Apache Struts release process and our <a
href="#Coding">coding conventions</a>,
which are applicable to all subprojects. Both stable and development releases
are
-<a href="downloads.html">available for download.</a></p>
+<a href="releases.html">available for download.</a></p>
<h2 id="release-process">Release Process</h2>
--
To stop receiving notification emails like this one, please contact
git-site-r...@apache.org.
