You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by co...@apache.org on 2017/08/29 11:26:29 UTC
svn commit: r1017425 - in /websites/production/santuario/content:
cache/main.pageCache contributing.html download.html history.html
index.html javaindex.html javareleasenotes.html mailing.html team.html
Author: coheigea
Date: Tue Aug 29 11:26:28 2017
New Revision: 1017425
Log:
Updating webpage
Modified:
websites/production/santuario/content/cache/main.pageCache
websites/production/santuario/content/contributing.html
websites/production/santuario/content/download.html
websites/production/santuario/content/history.html
websites/production/santuario/content/index.html
websites/production/santuario/content/javaindex.html
websites/production/santuario/content/javareleasenotes.html
websites/production/santuario/content/mailing.html
websites/production/santuario/content/team.html
Modified: websites/production/santuario/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/santuario/content/contributing.html
==============================================================================
--- websites/production/santuario/content/contributing.html (original)
+++ websites/production/santuario/content/contributing.html Tue Aug 29 11:26:28 2017
@@ -99,61 +99,7 @@ Apache Santuario -- contributing
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent">
-<h1 id="contributing-ContributingtoApacheSantuario">Contributing to Apache Santuario</h1>
-
-<h3 id="contributing-Introduction">Introduction</h3>
-
-<p>The Apache Santuario Project is an Open Source volunteer project released under a very open license. This means there are many ways to contribute to the project - either with direct participation (coding, documenting, answering questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by resource donations (money, time, publicity, hardware, software, conference presentations, speeches, etc...).</p>
-
-<p>To begin with, we suggest you to subscribe to the Apache Santuario <a shape="rect" href="mailing.html">mailing list</a> (follow the link for information on how to subscribe and to access the mail list archives). Listen-in for a while, to hear how others make contributions.</p>
-
-<p>You can get your local working copy of the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/santuario/">latest and greatest code</a>. Review the todo list, choose a task (or perhaps you have noticed something that needs patching). Make the changes, do the testing, generate a patch, and post to the dev mailing list. (Do not worry - the process is easy and explained below.)</p>
-
-<h3 id="contributing-HelpWantedHere">Help Wanted Here</h3>
-
-<p>The rest of this document is mainly about contributing new or improved code and/or documentation, but we would also be glad to have extra help in any of the following areas:</p>
-
-<ul><li>Answering questions on the mailing list - there is often a problem of having too many questioners and not enough experts to respond to all the questions.</li><li>Testing the package (especially its less-frequently-used features) on various configurations and reporting back.</li><li>Debugging - producing reproducable test cases and/or finding causes of bugs. Some known bugs are informally listed on To Do, and some are recorded in Jira (see explanation below).</li><li>Specifying/analysing/designing new features - and beyond. (If you wish to get involved with this, please join the mailing list, install and try out xml-security and read some of the <a shape="rect" href="mailing.html">mail archives</a>. You should have a strong "fluency" in XML technologies especially XMLDSig and XML Encryption, Java or C++ and a basic understanding of the architecture of this package.</li></ul>
-
-
-<h3 id="contributing-Subversion(SVN)UsageOverview">Subversion (SVN) Usage Overview</h3>
-
-<p>An overview of how to use Subversion to participate in the Apache Santuario development. Do not be afraid - you cannot accidently destroy the actual code repository, because you are working with a local copy as an anonymous user. Therefore, you do not have the system permissions to change anything. You can only update your local repository and compare your revisions with the real repository.</p>
-
-<p>(Further general Subversion usage information is at <a shape="rect" class="external-link" href="http://subversion.tigris.org/" rel="nofollow">subversion.tigris.org</a> and your local user documentation.)</p>
-
-<p>Have a look at the Java or C++ installation pages to see how to get a local copy of the source.</p>
-
-<h3 id="contributing-SubversionCommitterwithHTTPSaccess">Subversion Committer with HTTPS access</h3>
-
-<p>After a developer has consistently provided contributions (code, documentation and discussion), then the rest of the dev community may vote to grant this developer commit access to SVN.</p>
-
-<p>You will need secure access to the repository to be able to commit patches. Here are some resources that help to get your machine configured to use the repository via HTTPS.</p>
-
-<ul><li><a shape="rect" class="external-link" href="http://apache.org/dev/version-control.html#https-svn">Apache Committer Subversion Access</a></li><li><a shape="rect" class="external-link" href="http://svnbook.red-bean.com/" rel="nofollow">Subversion book</a></li></ul>
-
-
-<h3 id="contributing-ProcedureforRaisingDevelopmentIssues">Procedure for Raising Development Issues</h3>
-
-<p>There are two methods for discussing development and submitting patches. So that everyone can be productive, it is important to know which method is appropriate for a certain situation and how to go about it without confusion. This section explains when to use the developer <a shape="rect" href="mailing.html">mailing list</a> or the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">bug database</a>.</p>
-
-<p>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Prepare your post clearly and concisely.</p>
-
-<p>Most issues will be discovered, resolved, and then patched quickly via the developer mailing list. Larger issues, and ones that are not yet fully understood or are hard to solve, are destined for Jira. Santuario uses Jira for issue tracking. To report a issue, or to submit a patch, go <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">here</a>.</p>
-
-<p>Experienced developers use Jira directly, as they are very sure when they have found a bug and when not. However, less experienced users should first discuss it on the user or developer mailing list (as appropriate). Impatient people always enter everything into Jira without caring if it is a bug of our package or their own installation/configuration mistake - please do not do this.</p>
-
-<p>As a rule-of-thumb, discuss an issue on the developers mailing list first to work out any details. After it is confirmed to be worthwhile, and you are clear about it, then submit the bug description or patch via Bug Tracking.</p>
-
-<p>Perhaps you do not get any answer on your first reply, so just post it again until you get one. (But please not every hour - allow a few days for the list to deal with it.) Do not be impatient - remember that the whole world is busy, not just you. Bear in mind that other countries will have holidays at different times to your country and that they are in different time zones. You might also consider rewriting your initial posting - perhaps it was not clear enough and the readers eyes glazed over.</p>
-
-<h3 id="contributing-ContributionNotesandTips">Contribution Notes and Tips</h3>
-
-<p>This is a collection of tips for contributing to the project in a manner that is productive for all parties.</p>
-
-<ul><li>Every contribution is worthwhile. Even if the ensuing discussion proves it to be off-beam, then it may jog ideas for other people.</li><li>Use sensible and concise email subject headings. Search engines, and humans trying to browse a voluminous list, will respond favourably to a descriptive title.</li><li>Start new threads with a new Subject for new topics, rather than reusing the previous Subject line.</li><li>Keep each topic focused. If some new topic arises then start a new discussion. This leaves the original topic to continue uncluttered.</li><li>Whenever you decide to start a new topic, then start with a fresh new email message window. Do not use the "Reply to" button, because threaded mail-readers get confused (they utilise the In-reply-to header). If so, then your new topic will get lost in the previous thread and go unanswered.</li><li>Prepend your email subject line with a marker when that is appropriate, e.g. <a shape="rect" class="unresolved" href="#">Patch</a>,
<a shape="rect" class="unresolved" href="#">Proposal</a>, <a shape="rect" class="unresolved" href="#">RT</a> (Random Thought which quickly blossom into research topics <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">, <a shape="rect" class="unresolved" href="#">STATUS</a> (development status of a certain facility).</li><li>When making changes to XML documentation, or any XML document for that matter, use a <a shape="rect" class="external-link" href="http://www.oasis-open.org/cover/" rel="nofollow">validating parser</a> (one that is tried and true is <a shape="rect" class="external-link" href="http://openjade.sourceforge.net/" rel="nofollow">OpenSP/onsgmls</a>). This procedure will detect errors without having to go through the whole build docs process to find them. Do not expect Forrest or the build system to detect the va
lidation errors for you - they can do it, but that is not their purpose. (Anyway, nsgmls validation error messages are more informative.)</li><li>Remember that most people are participating in development on a volunteer basis and in their "spare time". These enthusiasts will attempt to respond to issues. It may take a little while to get your answers.</li><li>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Do not just perceive a problem and then rush out with a question - instead, delve.</li><li>Try to at least offer a partial solution and not just a problem statement.</li><li>Take the time to clearly explain your issue and write a concise email message. Less confusion facilitates fast and complete resolution.</li><li>Do not bother to send an email reply that simply says "thanks". When the issue is resolved, that is the finish - end of thread. Reduce clutter.
</li><li>You would usually do any development work against the HEAD branch of CVS.</li><li>When sending a patch, you usually do not need to worry about which CVS branch it should be applied to. The maintainers of the repository will decide.</li><li>If an issue starts to get bogged down in list discussion, then it may be appropriate to go into private off-list discussion with a few interested other people. Spare the list from the gory details. Report a summary back to the list to finalise the thread.</li><li>Become familiar with the mailing lists. As you browse and search, you will see the way other people do things. Follow the leading examples.</li></ul>
-</div>
+<div id="ConfluenceContent"><h1 id="contributing-ContributingtoApacheSantuario™">Contributing to Apache Santuario™</h1><h3 id="contributing-Introduction">Introduction</h3><p>The Apache Santuario™ Project is an Open Source volunteer project released under a very open license. This means there are many ways to contribute to the project - either with direct participation (coding, documenting, answering questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by resource donations (money, time, publicity, hardware, software, conference presentations, speeches, etc...).</p><p>To begin with, we suggest you to subscribe to the Apache Santuario <a shape="rect" href="mailing.html">mailing list</a> (follow the link for information on how to subscribe and to access the mail list archives). Listen-in for a while, to hear how others make contributions.</p><p>You can get your local working copy of the <a shape="rect" class="external-link" href="http://svn.apac
he.org/repos/asf/santuario/">latest and greatest code</a>. Review the todo list, choose a task (or perhaps you have noticed something that needs patching). Make the changes, do the testing, generate a patch, and post to the dev mailing list. (Do not worry - the process is easy and explained below.)</p><h3 id="contributing-HelpWantedHere">Help Wanted Here</h3><p>The rest of this document is mainly about contributing new or improved code and/or documentation, but we would also be glad to have extra help in any of the following areas:</p><ul><li>Answering questions on the mailing list - there is often a problem of having too many questioners and not enough experts to respond to all the questions.</li><li>Testing the package (especially its less-frequently-used features) on various configurations and reporting back.</li><li>Debugging - producing reproducable test cases and/or finding causes of bugs. Some known bugs are informally listed on To Do, and some are recorded in Jira (see expla
nation below).</li><li>Specifying/analysing/designing new features - and beyond. (If you wish to get involved with this, please join the mailing list, install and try out xml-security and read some of the <a shape="rect" href="mailing.html">mail archives</a>. You should have a strong "fluency" in XML technologies especially XMLDSig and XML Encryption, Java or C++ and a basic understanding of the architecture of this package.</li></ul><h3 id="contributing-Subversion(SVN)UsageOverview">Subversion (SVN) Usage Overview</h3><p>An overview of how to use Subversion to participate in the Apache Santuario development. Do not be afraid - you cannot accidently destroy the actual code repository, because you are working with a local copy as an anonymous user. Therefore, you do not have the system permissions to change anything. You can only update your local repository and compare your revisions with the real repository.</p><p>(Further general Subversion usage information is at <a shape="rect"
class="external-link" href="http://subversion.tigris.org/" rel="nofollow">subversion.tigris.org</a> and your local user documentation.)</p><p>Have a look at the Java or C++ installation pages to see how to get a local copy of the source.</p><h3 id="contributing-SubversionCommitterwithHTTPSaccess">Subversion Committer with HTTPS access</h3><p>After a developer has consistently provided contributions (code, documentation and discussion), then the rest of the dev community may vote to grant this developer commit access to SVN.</p><p>You will need secure access to the repository to be able to commit patches. Here are some resources that help to get your machine configured to use the repository via HTTPS.</p><ul><li><a shape="rect" class="external-link" href="http://apache.org/dev/version-control.html#https-svn">Apache Committer Subversion Access</a></li><li><a shape="rect" class="external-link" href="http://svnbook.red-bean.com/" rel="nofollow">Subversion book</a></li></ul><h3 id="contr
ibuting-ProcedureforRaisingDevelopmentIssues">Procedure for Raising Development Issues</h3><p>There are two methods for discussing development and submitting patches. So that everyone can be productive, it is important to know which method is appropriate for a certain situation and how to go about it without confusion. This section explains when to use the developer <a shape="rect" href="mailing.html">mailing list</a> or the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">bug database</a>.</p><p>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Prepare your post clearly and concisely.</p><p>Most issues will be discovered, resolved, and then patched quickly via the developer mailing list. Larger issues, and ones that are not yet fully understood or are hard to solve, are destined for Jira. Santuario uses Jira for issue
tracking. To report a issue, or to submit a patch, go <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">here</a>.</p><p>Experienced developers use Jira directly, as they are very sure when they have found a bug and when not. However, less experienced users should first discuss it on the user or developer mailing list (as appropriate). Impatient people always enter everything into Jira without caring if it is a bug of our package or their own installation/configuration mistake - please do not do this.</p><p>As a rule-of-thumb, discuss an issue on the developers mailing list first to work out any details. After it is confirmed to be worthwhile, and you are clear about it, then submit the bug description or patch via Bug Tracking.</p><p>Perhaps you do not get any answer on your first reply, so just post it again until you get one. (But please not every hour - allow a few days for the list to deal with it.) Do not be impatient - remember that t
he whole world is busy, not just you. Bear in mind that other countries will have holidays at different times to your country and that they are in different time zones. You might also consider rewriting your initial posting - perhaps it was not clear enough and the readers eyes glazed over.</p><h3 id="contributing-ContributionNotesandTips">Contribution Notes and Tips</h3><p>This is a collection of tips for contributing to the project in a manner that is productive for all parties.</p><ul><li>Every contribution is worthwhile. Even if the ensuing discussion proves it to be off-beam, then it may jog ideas for other people.</li><li>Use sensible and concise email subject headings. Search engines, and humans trying to browse a voluminous list, will respond favourably to a descriptive title.</li><li>Start new threads with a new Subject for new topics, rather than reusing the previous Subject line.</li><li>Keep each topic focused. If some new topic arises then start a new discussion. This l
eaves the original topic to continue uncluttered.</li><li>Whenever you decide to start a new topic, then start with a fresh new email message window. Do not use the "Reply to" button, because threaded mail-readers get confused (they utilise the In-reply-to header). If so, then your new topic will get lost in the previous thread and go unanswered.</li><li>Prepend your email subject line with a marker when that is appropriate, e.g. <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=Patch&linkCreation=true&fromPageId=24193313">Patch</a>, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=Proposal&linkCreation=true&fromPageId=24193313">Proposal</a>, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=RT&linkCreation=true&fromPageId
=24193313">RT</a> (Random Thought which quickly blossom into research topics <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=STATUS&linkCreation=true&fromPageId=24193313">STATUS</a> (development status of a certain facility).</li><li>When making changes to XML documentation, or any XML document for that matter, use a <a shape="rect" class="external-link" href="http://www.oasis-open.org/cover/" rel="nofollow">validating parser</a> (one that is tried and true is <a shape="rect" class="external-link" href="http://openjade.sourceforge.net/" rel="nofollow">OpenSP/onsgmls</a>). This procedure will detect errors without having to go through the whole build docs process to find them. Do not ex
pect Forrest or the build system to detect the validation errors for you - they can do it, but that is not their purpose. (Anyway, nsgmls validation error messages are more informative.)</li><li>Remember that most people are participating in development on a volunteer basis and in their "spare time". These enthusiasts will attempt to respond to issues. It may take a little while to get your answers.</li><li>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Do not just perceive a problem and then rush out with a question - instead, delve.</li><li>Try to at least offer a partial solution and not just a problem statement.</li><li>Take the time to clearly explain your issue and write a concise email message. Less confusion facilitates fast and complete resolution.</li><li>Do not bother to send an email reply that simply says "thanks". When the issue is resolved, th
at is the finish - end of thread. Reduce clutter.</li><li>You would usually do any development work against the HEAD branch of CVS.</li><li>When sending a patch, you usually do not need to worry about which CVS branch it should be applied to. The maintainers of the repository will decide.</li><li>If an issue starts to get bogged down in list discussion, then it may be appropriate to go into private off-list discussion with a few interested other people. Spare the list from the gory details. Report a summary back to the list to finalise the thread.</li><li>Become familiar with the mailing lists. As you browse and search, you will see the way other people do things. Follow the leading examples.</li></ul></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/download.html
==============================================================================
--- websites/production/santuario/content/download.html (original)
+++ websites/production/santuario/content/download.html Tue Aug 29 11:26:28 2017
@@ -108,7 +108,7 @@ Apache Santuario -- download
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="download-ObtaintheApacheSantuariodistribution">Obtain the Apache Santuario distribution</h1><p>The <strong>Apache Santuario</strong> project is aimed at providing implementation of the primary security standards for XML. Two libraries are currently available.</p><ul><li>Apache XML Security for Java - This library includes a mature Digital Signature and Encryption implementation. It also includes the standard JSR 105 (Java XML Digital Signature) API. Applications can use the standard JSR 105 API or the Apache Santuario API to create and validate XML Signatures.</li><li>Apache XML Security for C++ - This library includes a mature Digital Signature and Encryption implementation using a proprietary C++ API on top of the Xerces-C XML Parser's DOM API. It includes a pluggable cryptographic layer, but support for alternatives to OpenSSL are less complete and less mature.</li></ul><h3 id="download-Howtodownload">How to download</h3><p>Use the links below
to download a distribution of Apache Santuario from one of our mirrors. It is good practice to verify the integrity of the distribution files. Apache Santuario releases are available under the <a shape="rect" class="external-link" href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> - see the LICENSE.txt and NOTICE.txt files contained in each release artifact.</p><h3 id="download-Currentofficialrelease(closestmirrorsiteselectedautomatically)">Current official release (closest mirror site selected automatically)</h3><ul><li>The current stable Java release is Apache XML Security for Java 2.0.8: <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/java-library/2_0_8/xmlsec-2.0.8-source-release.zip">xmlsec-2.0.8-source-release.zip</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/2_0_8/xmlsec-2.0.8-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" hr
ef="https://www.apache.org/dist/santuario/java-library/2_0_8/xmlsec-2.0.8-source-release.zip.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/2_0_8/xmlsec-2.0.8-source-release.zip.sha1">SHA1</a>)</li><li>The older stable Java release is Apache XML Security for Java 1.5.8: <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/java-library/1_5_8/xml-security-bin-1_5_8.zip">xml-security-bin-1_5_8.zip</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/1_5_8/xml-security-bin-1_5_8.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/1_5_8/xml-security-bin-1_5_8.zip.md5">MD5</a>)</li><li>The current C++ release is Apache XML Security for C++ 1.7.3:<br clear="none"><ul><li><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-
c-1.7.3.tar.gz">xml-security-c-1.7.3.tar.gz</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.sha1">SHA1</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.sha256">SHA256</a>)</li><li><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-1.7.3.tar.bz2">xml-security-c-1.7.3.tar.bz2</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.bz2.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/
xml-security-c-1.7.3.tar.bz2.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.bz2.sha1">SHA1</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.bz2.sha256">SHA256</a>)</li><li><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-1.7.3.zip">xml-security-c-1.7.3.zip</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.zip.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.zip.sha1">SHA1</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.
3.zip.sha256">SHA256</a>)</li></ul></li></ul><h3 id="download-Archiveofoldreleases">Archive of old releases</h3><p>Older releases are available in the <a shape="rect" class="external-link" href="http://archive.apache.org/dist/santuario/">archive</a>.</p><h3 id="download-Verifyreleases">Verify releases</h3><p>It is essential that you verify the integrity of the downloaded files using the MD5/SHA and PGP signatures. Digest verification ensures the file was not corrupted or tampered with. PGP verification ensures that the file is authentic. In practice, PGP verification is <strong>much</strong> more important and makes checksum verification redundant.</p><h3 id="download-PGPSignature">PGP Signature</h3><p>The PGP signatures can be verified using <a shape="rect" class="external-link" href="http://www.pgpi.org/" rel="nofollow">PGP</a> or <a shape="rect" class="external-link" href="http://www.gnupg.org/" rel="nofollow">GPG</a>. First download the Apache Santuario <a shape="rect" class="ex
ternal-link" href="https://www.apache.org/dist/santuario/KEYS">KEYS</a> as well as the *.asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div id="ConfluenceContent"><h1 id="download-ObtaintheApacheSantuario™distribution">Obtain the Apache Santuario™ distribution</h1><p>The <strong>Apache Santuario™</strong> project is aimed at providing implementation of the primary security standards for XML. Two libraries are currently available.</p><ul><li>Apache XML Security for Java - This library includes a mature Digital Signature and Encryption implementation. It also includes the standard JSR 105 (Java XML Digital Signature) API. Applications can use the standard JSR 105 API or the Apache Santuario API to create and validate XML Signatures.</li><li>Apache XML Security for C++ - This library includes a mature Digital Signature and Encryption implementation using a proprietary C++ API on top of the Xerces-C XML Parser's DOM API. It includes a pluggable cryptographic layer, but support for alternatives to OpenSSL are less complete and less mature.</li></ul><h3 id="download-Howtodownload">How to download</h3><p
>Use the links below to download a distribution of Apache Santuario from one of our mirrors. It is good practice to verify the integrity of the distribution files. Apache Santuario releases are available under the <a shape="rect" class="external-link" href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> - see the LICENSE.txt and NOTICE.txt files contained in each release artifact.</p><h3 id="download-Currentofficialrelease(closestmirrorsiteselectedautomatically)">Current official release (closest mirror site selected automatically)</h3><ul><li>The current stable Java release is Apache XML Security for Java 2.1.0: <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/java-library/2_1_0/xmlsec-2.1.0-source-release.zip">xmlsec-2.1.0-source-release.zip</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/2_1_0/xmlsec-2.1.0-source-release.zip.asc">PGP</a>) (<a shape="rect" cla
ss="external-link" href="https://www.apache.org/dist/santuario/java-library/2_1_0/xmlsec-2.1.0-source-release.zip.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/2_1_0/xmlsec-2.1.0-source-release.zip.sha1">SHA1</a>)</li><li>The older stable Java release is Apache XML Security for Java 2.0.9:  <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/java-library/2_0_9/xmlsec-2.0.9-source-release.zip">xmlsec-2.0.9-source-release.zip</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/2_0_9/xmlsec-2.0.9-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/2_0_9/xmlsec-2.0.9-source-release.zip.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/java-library/2_0_9/xmlsec-2.0.9-source-release.zip.sha1">SHA1</a>)</li><li>The
current C++ release is Apache XML Security for C++ 1.7.3:<br clear="none"><ul><li><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-1.7.3.tar.gz">xml-security-c-1.7.3.tar.gz</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.sha1">SHA1</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.gz.sha256">SHA256</a>)</li><li><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-1.7.3.tar.bz2">xml-security-c-1.7.3.tar.bz2</a> (<a shape="rect" class="external
-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.bz2.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.bz2.md5">MD5</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.bz2.sha1">SHA1</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.tar.bz2.sha256">SHA256</a>)</li><li><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-1.7.3.zip">xml-security-c-1.7.3.zip</a> (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.zip.md5">MD5</a>) (<a shape="rect" class="external-link" href="http
s://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.zip.sha1">SHA1</a>) (<a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/c-library/xml-security-c-1.7.3.zip.sha256">SHA256</a>)</li></ul></li></ul><h3 id="download-Archiveofoldreleases">Archive of old releases</h3><p>Older releases are available in the <a shape="rect" class="external-link" href="http://archive.apache.org/dist/santuario/">archive</a>.</p><h3 id="download-Verifyreleases">Verify releases</h3><p>It is essential that you verify the integrity of the downloaded files using the MD5/SHA and PGP signatures. Digest verification ensures the file was not corrupted or tampered with. PGP verification ensures that the file is authentic. In practice, PGP verification is <strong>much</strong> more important and makes checksum verification redundant.</p><h3 id="download-PGPSignature">PGP Signature</h3><p>The PGP signatures can be verified using <a shape="rect" class="external-link" href="htt
p://www.pgpi.org/" rel="nofollow">PGP</a> or <a shape="rect" class="external-link" href="http://www.gnupg.org/" rel="nofollow">GPG</a>. First download the Apache Santuario <a shape="rect" class="external-link" href="https://www.apache.org/dist/santuario/KEYS">KEYS</a> as well as the *.asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">% pgpk -a KEYS
% pgpv xml-security-bin-1_4_4.zip.asc
or
Modified: websites/production/santuario/content/history.html
==============================================================================
--- websites/production/santuario/content/history.html (original)
+++ websites/production/santuario/content/history.html Tue Aug 29 11:26:28 2017
@@ -99,27 +99,7 @@ Apache Santuario -- history
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="history-ApacheSantuarioHistory">Apache Santuario History</h1>
-
-<h3 id="history-TheApacheSantuarioproject">The Apache Santuario project</h3>
-
-<p>In mid-1999, the <a shape="rect" class="external-link" href="http://www.nue.et-inf.uni-siegen.de/" rel="nofollow">Institute for Data Communications Systems</a> at the <a shape="rect" class="external-link" href="http://www.uni-siegen.de/" rel="nofollow">University of Siegen</a> in Germany looked for partners to participate in a European project for implementing the upcoming <a shape="rect" class="external-link" href="http://www.w3c.org/Signature" rel="nofollow">XML Signature standard</a>. We found our partners in the companies <a shape="rect" class="external-link" href="http://www.expnet.gr/" rel="nofollow">Expertnet S.A.</a> and <a shape="rect" class="external-link" href="http://www.proodos.gr/" rel="nofollow">PROODOS S.A.</a>, both from Athens, who were willing to use our XML Signature library in a first commercial project.</p>
-
-<p>The project started in January 2000 and ended up in September 2001. 50% of the costs have been funded by the European Commission in the <a shape="rect" class="external-link" href="http://www.ispo.cec.be/isis/99websig.htm" rel="nofollow">ISIS programme</a>. Goal was to develop a Java library for creating and validating XML Signatures and to make the binaries of this software freely available.</p>
-
-<p>In September 2001, Christian Geuer-Pollmann and the Institute for Data Communications Systems decided to make the sources freely available, too, to promote the use of digital signatures and to give XML Signature a spin. The decision was made to give the complete library (including an implementation of "Canonical XML" and "XML Signature") under the hood of the Apache Software Foundation to ensure availability of the source and to enable other people to use it under the Apache License.</p>
-
-<h3 id="history-XMLEncryptioninJava">XML Encryption in Java</h3>
-
-<p>A beta implementation of XML Encryption was first included in version 1.1 of the XML Security for Java library.</p>
-
-<h3 id="history-TheXMLSecurityforC++Library">The XML Security for C++ Library</h3>
-
-<p>The XML Security C++ library was a much more recent addition to the XML-Security project. It started out on Sourceforge and was migrated into XML Security in early 2003.</p>
-
-<h3 id="history-TheApacheSantuarioTLP">The Apache Santuario TLP</h3>
-
-<p>In 2006, the XML-Security project was voted as an Apache TLP and was rebranded as Apache Santuario. The Apache Santuario project at present includes the Apache XML Security for Java and the Apache XML Security for C++ library projects.</p></div>
+<div id="ConfluenceContent"><h1 id="history-ApacheSantuario™History">Apache Santuario™ History</h1><h3 id="history-TheApacheSantuario™project">The Apache Santuario™ project</h3><p>In mid-1999, the <a shape="rect" class="external-link" href="http://www.nue.et-inf.uni-siegen.de/" rel="nofollow">Institute for Data Communications Systems</a> at the <a shape="rect" class="external-link" href="http://www.uni-siegen.de/" rel="nofollow">University of Siegen</a> in Germany looked for partners to participate in a European project for implementing the upcoming <a shape="rect" class="external-link" href="http://www.w3c.org/Signature" rel="nofollow">XML Signature standard</a>. We found our partners in the companies <a shape="rect" class="external-link" href="http://www.expnet.gr/" rel="nofollow">Expertnet S.A.</a> and <a shape="rect" class="external-link" href="http://www.proodos.gr/" rel="nofollow">PROODOS S.A.</a>, both from Athens, who were willing to use our XML Signa
ture library in a first commercial project.</p><p>The project started in January 2000 and ended up in September 2001. 50% of the costs have been funded by the European Commission in the <a shape="rect" class="external-link" href="http://www.ispo.cec.be/isis/99websig.htm" rel="nofollow">ISIS programme</a>. Goal was to develop a Java library for creating and validating XML Signatures and to make the binaries of this software freely available.</p><p>In September 2001, Christian Geuer-Pollmann and the Institute for Data Communications Systems decided to make the sources freely available, too, to promote the use of digital signatures and to give XML Signature a spin. The decision was made to give the complete library (including an implementation of "Canonical XML" and "XML Signature") under the hood of the Apache Software Foundation to ensure availability of the source and to enable other people to use it under the Apache License.</p><h3 id="history-XMLEncryptioninJava">XML Encryption in
Java</h3><p>A beta implementation of XML Encryption was first included in version 1.1 of the XML Security for Java library.</p><h3 id="history-TheXMLSecurityforC++Library">The XML Security for C++ Library</h3><p>The XML Security C++ library was a much more recent addition to the XML-Security project. It started out on Sourceforge and was migrated into XML Security in early 2003.</p><h3 id="history-TheApacheSantuarioTLP">The Apache Santuario TLP</h3><p>In 2006, the XML-Security project was voted as an Apache TLP and was rebranded as Apache Santuario. The Apache Santuario project at present includes the Apache XML Security for Java and the Apache XML Security for C++ library projects.</p></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/index.html
==============================================================================
--- websites/production/santuario/content/index.html (original)
+++ websites/production/santuario/content/index.html Tue Aug 29 11:26:28 2017
@@ -99,7 +99,7 @@ Apache Santuario -- Index
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="Index-WelcometoApacheSantuario">Welcome to Apache Santuario</h1><h3 id="Index-TheProject">The Project</h3><p>The <strong>Apache Santuario</strong> project is aimed at providing implementation of the primary security standards for XML:</p><ul><li>XML-Signature Syntax and Processing</li><li>XML Encryption Syntax and Processing.</li></ul><p>Two libraries are currently available.</p><ul><li>Apache XML Security for Java: This library includes the standard JSR-105 (Java XML Digital Signature) API,  a mature DOM-based implementation of both XML Signature and XML Encryption, as well as a more recent StAX-based (streaming) XML Signature and XML Encryption implementation.</li><li>Apache XML Security for C++: This library includes a mature Digital Signature and Encryption implementation using a proprietary C++ API on top of the Xerces-C XML Parser's DOM API. It includes a pluggable cryptographic layer, but support for alternatives to OpenSSL are less co
mplete and less mature.</li></ul><p>Apache Santuario, Apache, and the Apache feather logo are trademarks of The Apache Software Foundation.</p><h3 id="Index-News">News</h3><h5 id="Index-December2016">December 2016</h5><p>Version 2.0.8 of the Apache XML Security for Java library has been released.</p><p>Please see the <span class="confluence-link"><a shape="rect" href="javareleasenotes.html">release notes</a></span> for more information.</p><h5 id="Index-March2015">March 2015</h5><p>Version 1.7.3 of the Apache XML Security for C++ library has been released, fixing a number of bugs, including a major issue involving ECDSA signature generation.</p><h3 id="Index-OlderNews">Older News</h3><p>See <a shape="rect" href="oldnews.html">here</a> for old news.</p><p> </p></div>
+<div id="ConfluenceContent"><h1 id="Index-WelcometoApacheSantuario™">Welcome to Apache Santuario™</h1><h3 id="Index-TheProject">The Project</h3><p>The <strong>Apache Santuario™</strong> project is aimed at providing implementation of the primary security standards for XML:</p><ul><li>XML-Signature Syntax and Processing</li><li>XML Encryption Syntax and Processing.</li></ul><p>Two libraries are currently available.</p><ul><li>Apache XML Security for Java: This library includes the standard JSR-105 (Java XML Digital Signature) API,  a mature DOM-based implementation of both XML Signature and XML Encryption, as well as a more recent StAX-based (streaming) XML Signature and XML Encryption implementation.</li><li>Apache XML Security for C++: This library includes a mature Digital Signature and Encryption implementation using a proprietary C++ API on top of the Xerces-C XML Parser's DOM API. It includes a pluggable cryptographic layer, but support for alternatives t
o OpenSSL are less complete and less mature.</li></ul><h3 id="Index-News">News</h3><h5 id="Index-August2017">August 2017</h5><p>Versions 2.1.0 and 2.0.9 of the Apache XML Security for Java library have been released.</p><p>Please see the <span class="confluence-link"><a shape="rect" href="javareleasenotes.html">release notes</a></span> for more information.</p><h5 id="Index-March2015">March 2015</h5><p>Version 1.7.3 of the Apache XML Security for C++ library has been released, fixing a number of bugs, including a major issue involving ECDSA signature generation.</p><h3 id="Index-OlderNews">Older News</h3><p>See <a shape="rect" href="oldnews.html">here</a> for old news.</p><p> </p></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/javaindex.html
==============================================================================
--- websites/production/santuario/content/javaindex.html (original)
+++ websites/production/santuario/content/javaindex.html Tue Aug 29 11:26:28 2017
@@ -99,7 +99,7 @@ Apache Santuario -- java_index
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="java_index-ApacheXMLSecurityforJava">Apache XML Security for Java</h1><h3 id="java_index-Overview">Overview</h3><p>The Apache XML Security for Java library supports <a shape="rect" class="external-link" href="http://www.w3c.org/TR/2002/REC-xmldsig-core-20020212/" rel="nofollow">XML-Signature Syntax and Processing, W3C Recommendation 12 February 2002</a> and <a shape="rect" class="external-link" href="http://www.w3c.org/TR/2002/REC-xmlenc-core-20021210/" rel="nofollow">XML Encryption Syntax and Processing, W3C Recommendation 10 December 2002</a>.</p><p>There are a number of different options open to the developer using the library. For XML Signature, three different approaches are available:</p><ul><li>The JSR-105 API: The standard Java XML Digital Signature API. This uses a DOM (in-memory) implementation under-the-hood.</li><li>The Apache Santuario Java DOM API: The older DOM API which pre-dates JSR-105.</li><li>The Apache Santuario Java StAX API:
The newer StAX-based (streaming) API which uses far less memory for large XML trees than the DOM approach.</li></ul><p>For XML Encryption, two different approaches are available:</p><ul><li>The Apache Santuario Java DOM API: A DOM API for XML Encryption.</li><li>The Apache Santuario Java StAX API: The newer StAX-based (streaming) API which uses far less memory for large XML trees than the DOM approach.</li></ul><p>The StAX-based (streaming) functionality is only available as of the 2.0.0 release. Please see the <a shape="rect" href="streaming-xml-security.html">Streaming XML Security</a> page for more information about how to use this approach.</p><h3 id="java_index-News">News</h3><h5 id="java_index-December2016">December 2016</h5><p>Version 2.0.8 of the Apache XML Security for Java library has been released.</p><p>Please see the <span class="confluence-link"><a shape="rect" href="https://cwiki.apache.org/confluence/display/SANTUARIO/java_release_notes">release notes</a></span> for
more information.</p><h3 id="java_index-OldNews">Old News</h3><p>See <a shape="rect" href="oldnews.html">here</a> for older news.</p></div>
+<div id="ConfluenceContent"><h1 id="java_index-ApacheXMLSecurityforJava">Apache XML Security for Java</h1><h3 id="java_index-Overview">Overview</h3><p>The Apache XML Security for Java library supports <a shape="rect" class="external-link" href="http://www.w3c.org/TR/2002/REC-xmldsig-core-20020212/" rel="nofollow">XML-Signature Syntax and Processing, W3C Recommendation 12 February 2002</a> and <a shape="rect" class="external-link" href="http://www.w3c.org/TR/2002/REC-xmlenc-core-20021210/" rel="nofollow">XML Encryption Syntax and Processing, W3C Recommendation 10 December 2002</a>.</p><p>There are a number of different options open to the developer using the library. For XML Signature, three different approaches are available:</p><ul><li>The JSR-105 API: The standard Java XML Digital Signature API. This uses a DOM (in-memory) implementation under-the-hood.</li><li>The Apache Santuario Java DOM API: The older DOM API which pre-dates JSR-105.</li><li>The Apache Santuario Java StAX API:
The newer StAX-based (streaming) API which uses far less memory for large XML trees than the DOM approach.</li></ul><p>For XML Encryption, two different approaches are available:</p><ul><li>The Apache Santuario Java DOM API: A DOM API for XML Encryption.</li><li>The Apache Santuario Java StAX API: The newer StAX-based (streaming) API which uses far less memory for large XML trees than the DOM approach.</li></ul><p>The StAX-based (streaming) functionality is only available as of the 2.0.0 release. Please see the <a shape="rect" href="streaming-xml-security.html">Streaming XML Security</a> page for more information about how to use this approach.</p><h3 id="java_index-News">News</h3><h5 id="java_index-August2017">August 2017</h5><p>Versions 2.1.0 and 2.0.9 of the Apache XML Security for Java library have been released.</p><p>Please see the <span class="confluence-link"><a shape="rect" href="https://cwiki.apache.org/confluence/display/SANTUARIO/java_release_notes">release notes</a></s
pan> for more information.</p><h3 id="java_index-OldNews">Old News</h3><p>See <a shape="rect" href="oldnews.html">here</a> for older news.</p></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/javareleasenotes.html
==============================================================================
--- websites/production/santuario/content/javareleasenotes.html (original)
+++ websites/production/santuario/content/javareleasenotes.html Tue Aug 29 11:26:28 2017
@@ -99,7 +99,7 @@ Apache Santuario -- java_release_notes
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="java_release_notes-ApacheXMLSecurityforJavaReleaseNotes">Apache XML Security for Java Release Notes</h1><h3 class="confluence-link" id="java_release_notes-CurrentReleases">Current Releases</h3><ul><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12336742">Apache XML Security for Java 2.0.8</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12327162">Apache XML Security for Java 1.5.8</a></li></ul><h3 id="java_release_notes-Olderreleases">Older releases</h3><ul><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12334297">Apache XML Security for Java 2.0.7</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12333015">Apache XML Security for Java 2.0.6</a></li><li><a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12332067">Apache XML Security for Java 2.0.5</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12329273">Apache XML Security for Java 2.0.4</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12328679">Apache XML Security for Java 2.0.3</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12325592">Apache XML Security for Java 1.5.7</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12326812">Apache XML Security for Java 2.0.1</a><span class="confluence-link"> </span></li><li><span class="confluence-link"><a shape="rect" href="java200releasenotes.html">Apache XML Security for Java 2.0.0</a></span></li><li><a shape="rect" href="java156releasenotes.htm
l">Apache XML Security for Java 1.5.6</a></li><li><a shape="rect" href="java148releasenotes.html">Apache XML Security for Java 1.4.8</a></li><li><a shape="rect" href="java155releasenotes.html">Apache XML Security for Java 1.5.5</a></li><li><a shape="rect" href="java154releasenotes.html">Apache XML Security for Java 1.5.4</a></li><li><a shape="rect" href="java147releasenotes.html">Apache XML Security for Java 1.4.7</a></li><li><a shape="rect" href="java153releasenotes.html">Apache XML Security for Java 1.5.3</a></li><li><a shape="rect" href="java152releasenotes.html">Apache XML Security for Java 1.5.2</a></li><li><a shape="rect" href="java151releasenotes.html">Apache XML Security for Java 1.5.1</a></li><li><a shape="rect" href="java146releasenotes.html">Apache XML Security for Java 1.4.6</a></li><li><a shape="rect" href="java150releasenotes.html">Apache XML Security for Java 1.5.0</a></li><li><a shape="rect" href="java145releasenotes.html">Apache XML Security for Java 1.4.5</a></li><
li><a shape="rect" href="java144releasenotes.html">Apache XML Security for Java 1.4.4</a></li><li><a shape="rect" href="java143releasenotes.html">Apache XML Security for Java 1.4.3</a></li><li><a shape="rect" href="java142releasenotes.html">Apache XML Security for Java 1.4.2</a></li><li><a shape="rect" href="java141releasenotes.html">Apache XML Security for Java 1.4.1</a></li><li><a shape="rect" href="java140releasenotes.html">Apache XML Security for Java 1.4.0</a></li><li><a shape="rect" href="java130releasenotes.html">Apache XML Security for Java 1.3.0</a></li><li><a shape="rect" href="java121releasenotes.html">Apache XML Security for Java 1.2.1</a></li><li><a shape="rect" href="java120releasenotes.html">Apache XML Security for Java 1.2.0</a></li></ul></div>
+<div id="ConfluenceContent"><h1 id="java_release_notes-ApacheXMLSecurityforJavaReleaseNotes">Apache XML Security for Java Release Notes</h1><h3 class="confluence-link" id="java_release_notes-CurrentReleases">Current Releases</h3><ul><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/projects/SANTUARIO/versions/12338413">Apache XML Security for Java 2.1.0</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/projects/SANTUARIO/versions/12338799">Apache XML Security for Java 2.0.9</a></li></ul><h3 id="java_release_notes-Olderreleases">Older releases</h3><ul><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12336742">Apache XML Security for Java 2.0.8</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12327162">Apache XML Security for Java 1.5.8</a></li><li><a shape="rect" class="external-link" href="
https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12334297">Apache XML Security for Java 2.0.7</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12333015">Apache XML Security for Java 2.0.6</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12332067">Apache XML Security for Java 2.0.5</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12329273">Apache XML Security for Java 2.0.4</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12328679">Apache XML Security for Java 2.0.3</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO/fixforversion/12325592">Apache XML Security for Java 1.5.7</a></li><li><a shape="rect" class="external-link" href="https://issues.apac
he.org/jira/browse/SANTUARIO/fixforversion/12326812">Apache XML Security for Java 2.0.1</a><span class="confluence-link"> </span></li><li><span class="confluence-link"><a shape="rect" href="java200releasenotes.html">Apache XML Security for Java 2.0.0</a></span></li><li><a shape="rect" href="java156releasenotes.html">Apache XML Security for Java 1.5.6</a></li><li><a shape="rect" href="java148releasenotes.html">Apache XML Security for Java 1.4.8</a></li><li><a shape="rect" href="java155releasenotes.html">Apache XML Security for Java 1.5.5</a></li><li><a shape="rect" href="java154releasenotes.html">Apache XML Security for Java 1.5.4</a></li><li><a shape="rect" href="java147releasenotes.html">Apache XML Security for Java 1.4.7</a></li><li><a shape="rect" href="java153releasenotes.html">Apache XML Security for Java 1.5.3</a></li><li><a shape="rect" href="java152releasenotes.html">Apache XML Security for Java 1.5.2</a></li><li><a shape="rect" href="java151releasenotes.html">Apache XM
L Security for Java 1.5.1</a></li><li><a shape="rect" href="java146releasenotes.html">Apache XML Security for Java 1.4.6</a></li><li><a shape="rect" href="java150releasenotes.html">Apache XML Security for Java 1.5.0</a></li><li><a shape="rect" href="java145releasenotes.html">Apache XML Security for Java 1.4.5</a></li><li><a shape="rect" href="java144releasenotes.html">Apache XML Security for Java 1.4.4</a></li><li><a shape="rect" href="java143releasenotes.html">Apache XML Security for Java 1.4.3</a></li><li><a shape="rect" href="java142releasenotes.html">Apache XML Security for Java 1.4.2</a></li><li><a shape="rect" href="java141releasenotes.html">Apache XML Security for Java 1.4.1</a></li><li><a shape="rect" href="java140releasenotes.html">Apache XML Security for Java 1.4.0</a></li><li><a shape="rect" href="java130releasenotes.html">Apache XML Security for Java 1.3.0</a></li><li><a shape="rect" href="java121releasenotes.html">Apache XML Security for Java 1.2.1</a></li><li><a shape=
"rect" href="java120releasenotes.html">Apache XML Security for Java 1.2.0</a></li></ul></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/mailing.html
==============================================================================
--- websites/production/santuario/content/mailing.html (original)
+++ websites/production/santuario/content/mailing.html Tue Aug 29 11:26:28 2017
@@ -99,7 +99,7 @@ Apache Santuario -- mailing
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="mailing-ApacheSantuariomailinglist">Apache Santuario mailing list</h1><h3 id="mailing-MailingList">Mailing List</h3><p>There exists a mailing list which you can subscribe to ask questions:</p><p>The <a shape="rect" class="external-link" href="http://santuario.apache.org/mail">ezmlm mailing list controller</a> accepts commands by sending emails to it, generally like the following:</p><ul><li><a shape="rect" class="external-link" href="mailto:dev-subscribe.at.santuario.apache.org" rel="nofollow">dev-subscribe</a> to subscribe your current email address to the list.</li><li><a shape="rect" class="external-link" href="mailto:dev-unsubscribe.at.santuario.apache.org" rel="nofollow">dev-unsubscribe</a> to unsubscribe your <strong>current</strong> email address from the list.</li><li><a shape="rect" class="external-link" href="mailto:dev-help.at.santuario.apache.org" rel="nofollow">dev-help</a> to get Help on mailing list commands.</li></ul><h3 id="mailin
g-MailingListArchives">Mailing List Archives</h3><p>An archive of this list is kept <a shape="rect" class="external-link" href="http://apache-xml-project.6118.n7.nabble.com/Apache-XML-Security-Dev-f33675.html" rel="nofollow">here</a>.</p></div>
+<div id="ConfluenceContent"><h1 id="mailing-ApacheSantuario™mailinglist">Apache Santuario™ mailing list</h1><h3 id="mailing-MailingList">Mailing List</h3><p>There exists a mailing list which you can subscribe to ask questions:</p><p>The <a shape="rect" class="external-link" href="http://santuario.apache.org/mail">ezmlm mailing list controller</a> accepts commands by sending emails to it, generally like the following:</p><ul><li><a shape="rect" class="external-link" href="mailto:dev-subscribe.at.santuario.apache.org" rel="nofollow">dev-subscribe</a> to subscribe your current email address to the list.</li><li><a shape="rect" class="external-link" href="mailto:dev-unsubscribe.at.santuario.apache.org" rel="nofollow">dev-unsubscribe</a> to unsubscribe your <strong>current</strong> email address from the list.</li><li><a shape="rect" class="external-link" href="mailto:dev-help.at.santuario.apache.org" rel="nofollow">dev-help</a> to get Help on mailing list commands.</li></ul>
<h3 id="mailing-MailingListArchives">Mailing List Archives</h3><p>An archive of this list is kept <a shape="rect" class="external-link" href="http://apache-xml-project.6118.n7.nabble.com/Apache-XML-Security-Dev-f33675.html" rel="nofollow">here</a>.</p></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/team.html
==============================================================================
--- websites/production/santuario/content/team.html (original)
+++ websites/production/santuario/content/team.html Tue Aug 29 11:26:28 2017
@@ -99,32 +99,7 @@ Apache Santuario -- team
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="team-TheApacheSantuarioCommunity">The Apache Santuario Community</h1>
-
-<p>The Apache Santuario Project operates on a meritocracy: the more you do, the more responsibility you will obtain. This page lists all of the people who have gone the extra mile and are Committers. If you would like to get involved, the first step is to join the mailing lists.</p>
-
-<p>We ask that you please do not send us emails privately asking for support. We are non-paid volunteers who help out with the project and we do not necessarily have the time or energy to help people on an individual basis. Instead, we have set up mailing lists which often contain hundreds of individuals who will help answer detailed requests for help. The benefit of using mailing lists over private communication is that it is a shared resource where others can also learn from common mistakes and as a community we all grow together.</p>
-
-<h3 id="team-PMC">PMC</h3>
-
-<p>The following people are members of the Project Management Committee (PMC) for this project:</p>
-
-<ul><li>Berin Lautenbach</li><li>Colm O hEigeartaigh (chair)</li><li>Sean Mullan</li><li>Raul Benito Garcia</li><li>Scott Cantor</li><li>Marc Giger</li></ul>
-
-
-<h3 id="team-EmeritusPMC">Emeritus PMC</h3>
-
-<p>The following people are emeritus members of the Project Management Committee (PMC) for this project:</p>
-
-<ul><li>Axl Mattheus</li><li>Werner Dittman</li><li>Davanum Srinivas</li></ul>
-
-
-<h3 id="team-Committers">Committers</h3>
-
-<p>In addition to the PMC members, the following people have commit rights to the Apache Santuario project:</p>
-
-<ul><li>Christian Geuer-Pollmann</li><li>Chad La Joie</li><li>Milan Tomic</li><li>Ted Leung</li><li>Erwin van der Koogh</li><li>Vishal Mahajan</li><li>Dirk-Willem van Gulik</li></ul>
-</div>
+<div id="ConfluenceContent"><h1 id="team-TheApacheSantuario™Community">The Apache Santuario™ Community</h1><p>The Apache Santuario™ Project operates on a meritocracy: the more you do, the more responsibility you will obtain. This page lists all of the people who have gone the extra mile and are Committers. If you would like to get involved, the first step is to join the mailing lists.</p><p>We ask that you please do not send us emails privately asking for support. We are non-paid volunteers who help out with the project and we do not necessarily have the time or energy to help people on an individual basis. Instead, we have set up mailing lists which often contain hundreds of individuals who will help answer detailed requests for help. The benefit of using mailing lists over private communication is that it is a shared resource where others can also learn from common mistakes and as a community we all grow together.</p><h3 id="team-PMC">PMC</h3><p>The following peo
ple are members of the Project Management Committee (PMC) for this project:</p><ul><li>Berin Lautenbach</li><li>Colm O hEigeartaigh (chair)</li><li>Sean Mullan</li><li>Raul Benito Garcia</li><li>Scott Cantor</li><li>Marc Giger</li></ul><h3 id="team-EmeritusPMC">Emeritus PMC</h3><p>The following people are emeritus members of the Project Management Committee (PMC) for this project:</p><ul><li>Axl Mattheus</li><li>Werner Dittman</li><li>Davanum Srinivas</li></ul><h3 id="team-Committers">Committers</h3><p>In addition to the PMC members, the following people have commit rights to the Apache Santuario project:</p><ul><li>Christian Geuer-Pollmann</li><li>Chad La Joie</li><li>Milan Tomic</li><li>Ted Leung</li><li>Erwin van der Koogh</li><li>Vishal Mahajan</li><li>Dirk-Willem van Gulik</li></ul></div>
</div>
<!-- Content -->
</td>