cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r905506 - in /websites/production/cxf/content: cache/main.pageCache roadmap.html support.html
Date Tue, 08 Apr 2014 22:48:06 GMT
Author: buildbot
Date: Tue Apr  8 22:48:06 2014
New Revision: 905506

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/roadmap.html
    websites/production/cxf/content/support.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/roadmap.html
==============================================================================
--- websites/production/cxf/content/roadmap.html (original)
+++ websites/production/cxf/content/roadmap.html Tue Apr  8 22:48:06 2014
@@ -99,45 +99,7 @@ Apache CXF -- Roadmap
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="Roadmap-Roadmap">Roadmap</h1>
-
-<p>Current Roadmap for future versions of CXF.  (this is an ongoing "work in progress",
subject to change.) Note that a primary goal of the Apache CXF team is to make frequent CXF
releases. This includes major, stabilized, and thoroughly tested releases, as well as minor
patch releases.</p>
-
-<h2 id="Roadmap-Futureversion">Future version </h2>
-<p>These may find their way into one of the releases below if people step up to finish
them.</p>
-<ul><li>SOAP/TCP support (GSoC project)</li><li>Better management
capabilities</li><li>Better Acegi integration</li><li>Update to WS-RM
1.1</li><li>Enhancements to WS-Trust support</li></ul>
-
-
-<h2 id="Roadmap-CXFversion2.7.x">CXF version 2.7.x</h2>
-
-<p>The CXF 2.7.x releases include bug fix releases for issues users encounter with
2.7.x versions.   These releases will be done on a branch by selectively merging fixes from
the trunk on an as-needed basis.  For the most part, there would be fixes for:</p>
-<ul><li>Interopability issues</li><li>Critical show stoppers</li></ul>
-
-
-<p>Some new features may be back ported from trunk to provide some new functionality
to users quicker if it doesn't affect the existing stuff or can enhance some of the new features
in 2.7.  </p>
-
-<p>See the <a shape="rect" href="http://cxf.apache.org/docs/27-migration-guide.html">2.7
Migration Guide</a> for more details about new features and changes.</p>
-
-
-<h2 id="Roadmap-CXFversions2.6.x/2.5.x">CXF versions 2.6.x/2.5.x</h2>
-<p>The CXF 2.6.x and 2.5.x releases include bug fix releases for issues users encounter
with those versions.   These releases will be done on a branch by selectively merging fixes
from the trunk on an as-needed basis.  For the most part, there would be fixes for:</p>
-<ul><li>Interopability issues</li><li>Critical show stoppers</li></ul>
-
-
-<p>A few new features may be back ported from trunk to provide some new functionality
to users quicker if it doesn't affect the existing stuff.  </p>
-
-<p>See the <a shape="rect" href="http://cxf.apache.org/docs/26-migration-guide.html">2.6
Migration Guide</a> for more details about new features and changes.</p>
-
-<p>See the <a shape="rect" href="http://cxf.apache.org/docs/26-migration-guide.html">2.5
Migration Guide</a> for more details about new features and changes.</p>
-
-<h2 id="Roadmap-LegacyCXFversions2.4.x,2.3.,2.2.x,2.1.x,and2.0.x-EOL">Legacy CXF versions
2.4.x, 2.3., 2.2.x, 2.1.x, and 2.0.x - EOL</h2>
-
-<p>Versions of CXF prior to 2.5.x are no longer supported at Apache.  They are now
considered end-of-life and are therefore unsupported. Users are highly encouraged to <a
shape="rect" href="http://cxf.apache.org/docs/migration-guides.html">migrate</a>
to newer versions of CXF.</p>
-
-
-
-
-</div>
+<div id="ConfluenceContent"><h1 id="Roadmap-Roadmap">Roadmap</h1><p>Current
Roadmap for future versions of CXF. (This is an ongoing "work in progress", subject to change.)
Note that a primary goal of the Apache CXF team is to make frequent CXF releases. This includes
major, stabilized, and thoroughly tested releases, as well as minor patch releases.</p><h2
id="Roadmap-Futureversion">Future version</h2><p>These may find their way into
one of the releases below if people step up to finish them.</p><ul><li>SOAP/TCP
support (GSoC project)</li><li>Better management capabilities</li><li>Better
Acegi integration</li><li>Update to WS-RM 1.1</li><li>Enhancements
to WS-Trust support</li></ul><h2 id="Roadmap-CXFversion2.7.x">CXF version
2.7.x</h2><p>The CXF 2.7.x releases include bug fix releases for issues users
encounter with 2.7.x versions. These releases will be done on a branch by selectively merging
fixes from the trunk on an as-needed basis. For the most part, there would be fixes for:<
 /p><ul><li>Interopability issues</li><li>Critical show stoppers</li></ul><p>Some
new features may be back ported from trunk to provide some new functionality to users quicker
if it doesn't affect the existing stuff or can enhance some of the new features in 2.7.</p><p>See
the <a shape="rect" href="http://cxf.apache.org/docs/27-migration-guide.html">2.7 Migration
Guide</a> for more details about new features and changes.</p><h2 id="Roadmap-CXFversions2.6.x/2.5.x">CXF
versions 2.6.x/2.5.x</h2><p>The CXF 2.6.x and 2.5.x releases include bug fix releases
for issues users encounter with those versions. These releases will be done on a branch by
selectively merging fixes from the trunk on an as-needed basis. For the most part, there would
be fixes for:</p><ul><li>Interopability issues</li><li>Critical
show stoppers</li></ul><p>A few new features may be back ported from trunk
to provide some new functionality to users quicker if it doesn't affect the existing stuff.</p><p>See
the <a shape=
 "rect" href="http://cxf.apache.org/docs/26-migration-guide.html">2.6 Migration Guide</a>
for more details about new features and changes.</p><p>See the <a shape="rect"
href="http://cxf.apache.org/docs/26-migration-guide.html">2.5 Migration Guide</a>
for more details about new features and changes.</p><h2 id="Roadmap-LegacyCXFversions2.4.x,2.3.,2.2.x,2.1.x,and2.0.x-EOL">Legacy
CXF versions 2.4.x, 2.3., 2.2.x, 2.1.x, and 2.0.x - EOL</h2><p>Versions of CXF
prior to 2.5.x are no longer supported at Apache. They are now considered end-of-life and
are therefore unsupported. Users are highly encouraged to <a shape="rect" href="http://cxf.apache.org/docs/migration-guides.html">migrate</a>
to newer versions of CXF.</p></div>
            </div>
            <!-- Content -->
          </td>

Modified: websites/production/cxf/content/support.html
==============================================================================
--- websites/production/cxf/content/support.html (original)
+++ websites/production/cxf/content/support.html Tue Apr  8 22:48:06 2014
@@ -99,41 +99,7 @@ Apache CXF -- Support
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="Support-Support">Support </h1>
-
-<p>There are two types of help available for Apache CXF: </p>
-
-<ul><li><a shape="rect" href="#Support-cxfsupport">Support from the Apache
CXF open source project</a></li><li><a shape="rect" href="#Support-commercialsupport">Commercial
Support</a></li></ul>
-
-
-<p><span class="confluence-anchor-link" id="Support-cxfsupport"></span></p>
-<h2 id="Support-SupportFromtheApacheCXFOpenSourceProject">Support From the Apache CXF
Open Source Project </h2>
-
-<p>If you are experiencing problems using CXF please report your problem via the <a
shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CXF">Issue
Tracker</a>. You may also find it useful to discuss your issues with the community on
the <a shape="rect" href="mailing-lists.html">Mailing Lists</a>. Below are some
resources to check before asking for help: </p>
-
-<ul><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CXF">Issue
Tracker</a></li><li><a shape="rect" href="mailing-lists.html">Mailing
Lists</a></li><li><a shape="rect" href="faq.html">FAQ</a></li></ul>
-
-
-<p>Before asking for help with your issue, it's a very good idea to search for your
issue in the mailing list archives and the FAQ. The majority of issues can be solved in this
manner without having to send an email to the mailing list. If you don't find an answer, use
the guidelines below when writing the e-mail.</p>
-
-<h3 id="Support-Howtogethelp">How to get help</h3>
-
-<p>Whenever you are reporting a problem, please be sure to include as much information
as possible; the more we know, the better the chance of a quicker resolution.</p>
-
-<ul><li>which version of the software</li><li>what platform and JDK</li><li>any
particular container being used - if so what version</li><li>stack traces generally
really help! If in doubt include the whole thing; often exceptions get wrapped in other exceptions
and the exception right near the bottom explains the actual error, not the first few lines
at the top. Its very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>log
output can be useful too; sometimes <a shape="rect" href="http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-UsingLog4jInsteadofjava.util.logging">enabling
DEBUG logging</a> can help</li><li>your code &amp; configuration files
are often useful</li></ul>
-
-
-<h3 id="Support-Howtogethelpfaster">How to get help faster</h3>
-
-<p>We can help you much quicker if you try the following</p>
-
-<ul><li>provide us with a JUnit test case that demonstrates your issue. e.g.
if you think you've found a bug, can you create a test case to demonstrate the bug?</li><li><a
shape="rect" href="getting-involved.html">submit a patch</a> fixing the bug! (We
also buy you beer when we meet you if you submit bug fixes <img class="emoticon emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png"
data-emoticon-name="smile" alt="(smile)"></li><li>for memory leaks or performance
related issues, if you can run a profiler on your test case and attach the output as a file
(or zipped file if its huge) to the JIRA we can normally fix things much faster. e.g. run
JProfiler or YourKit on your code and send us the output. To find memory leaks its quicker
to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure
out whats wrong from that.</li></ul>
-
-
-<p><span class="confluence-anchor-link" id="Support-commercialsupport"></span></p>
-<h2 id="Support-CommercialSupport">Commercial Support </h2>
-
-<p>There are several companies that support CXF directly or provide products and services
based on CXF.   See the <a shape="rect" href="commercial-cxf-offerings.html">Commercial
CXF Offerings</a> page for more information about those offerings.</p></div>
+<div id="ConfluenceContent"><h1 id="Support-Support">Support</h1><p>There
are two types of help available for Apache CXF:</p><ul><li><a shape="rect"
href="#Support-cxfsupport">Support from the Apache CXF open source project</a></li><li><a
shape="rect" href="#Support-commercialsupport">Commercial Support</a></li></ul><p><span
class="confluence-anchor-link" id="Support-cxfsupport"></span></p><h2 id="Support-SupportFromtheApacheCXFOpenSourceProject">Support
From the Apache CXF Open Source Project</h2><p>If you are experiencing problems
using CXF please report your problem via the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CXF">Issue
Tracker</a>. You may also find it useful to discuss your issues with the community on
the <a shape="rect" href="mailing-lists.html">Mailing Lists</a>. Below are some
resources to check before asking for help:</p><ul><li><a shape="rect"
class="external-link" href="http://issues.apache.org/jira/browse/CXF">Issue Tracker</
 a></li><li><a shape="rect" href="mailing-lists.html">Mailing Lists</a></li><li><a
shape="rect" href="faq.html">FAQ</a></li></ul><p>Before asking
for help with your issue, it's a very good idea to search for your issue in the mailing list
archives and the FAQ. The majority of issues can be solved in this manner without having to
send an email to the mailing list. If you don't find an answer, use the guidelines below when
writing the email.</p><h3 id="Support-Howtogethelp">How to get help</h3><p>Whenever
you are reporting a problem, please be sure to include as much information as possible; the
more we know, the better the chance of a quicker resolution.</p><ul><li>which
version of the software</li><li>what platform and JDK</li><li>any
particular container being used - if so what version</li><li>stack traces generally
really help! If in doubt include the whole thing; often exceptions get wrapped in other exceptions
and the exception right near the bottom explains the actual error, not
  the first few lines at the top. It's very easy for us to skim-read past unnecessary parts
of a stack trace.</li><li>log output can be useful too; sometimes <a shape="rect"
href="http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-UsingLog4jInsteadofjava.util.logging">enabling
DEBUG logging</a> can help</li><li>your code &amp; configuration files
are often useful</li></ul><h3 id="Support-Howtogethelpfaster">How to get
help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>provide
us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug,
can you create a test case to demonstrate the bug?</li><li><a shape="rect"
href="getting-involved.html">submit a patch</a> fixing the bug! (We also buy you
beer when we meet you if you submit bug fixes <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoti
 cons/smile.png" data-emoticon-name="smile" alt="(smile)">)</li><li>for memory
leaks or performance related issues, if you can run a profiler on your test case and attach
the output as a file (or zipped file if it's huge) to the JIRA we can normally fix things
much faster. e.g. run JProfiler or YourKit on your code and send us the output. To find memory
leaks, it's quicker to resolve if you can tell us what classes are taking up all of the RAM;
we can normally figure out what's wrong from that.</li></ul><p><span
class="confluence-anchor-link" id="Support-commercialsupport"></span></p><h2
id="Support-CommercialSupport">Commercial Support</h2><p>There are several
companies that support CXF directly or provide products and services based on CXF. See the
<a shape="rect" href="commercial-cxf-offerings.html">Commercial CXF Offerings</a>
page for more information about those offerings.</p></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message