You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by sh...@apache.org on 2014/05/16 18:11:35 UTC
svn commit: r1595253 [1/18] - in /xalan/java/branches/WebSite: ./ xalan-j/
xalan-j/design/ xalan-j/design/resources/ xalan-j/resources/ xalan-j/xsltc/
xalan-j/xsltc/resources/
Author: shathaway
Date: Fri May 16 16:11:33 2014
New Revision: 1595253
URL: http://svn.apache.org/r1595253
Log:
New Branch - WebSite - for prototypes
Added:
xalan/java/branches/WebSite/xalan-j/
xalan/java/branches/WebSite/xalan-j/bugreporting.html (with props)
xalan/java/branches/WebSite/xalan-j/builds.html (with props)
xalan/java/branches/WebSite/xalan-j/charter.html (with props)
xalan/java/branches/WebSite/xalan-j/commandline.html (with props)
xalan/java/branches/WebSite/xalan-j/commandline_xsltc.html (with props)
xalan/java/branches/WebSite/xalan-j/contact_us.html (with props)
xalan/java/branches/WebSite/xalan-j/design/
xalan/java/branches/WebSite/xalan-j/design/compilation.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/conceptual.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/data.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/design2_0_0.html (with props)
xalan/java/branches/WebSite/xalan-j/design/org_apache.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/process.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/resources/
xalan/java/branches/WebSite/xalan-j/design/resources/Xalan-Logo-tm.png (with props)
xalan/java/branches/WebSite/xalan-j/design/resources/Xalan-Logo.txt (with props)
xalan/java/branches/WebSite/xalan-j/design/resources/Xalan-Trademark.txt (with props)
xalan/java/branches/WebSite/xalan-j/design/resources/XalanJ-Logo-tm.png (with props)
xalan/java/branches/WebSite/xalan-j/design/resources/apache-xalan.css
xalan/java/branches/WebSite/xalan-j/design/resources/asf_logo.png (with props)
xalan/java/branches/WebSite/xalan-j/design/resources/note.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/trax.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/xalan.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/xalan1_1x1.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/xmllogo.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/xpath.gif (with props)
xalan/java/branches/WebSite/xalan-j/design/xslt_abstract.gif (with props)
xalan/java/branches/WebSite/xalan-j/downloads.html (with props)
xalan/java/branches/WebSite/xalan-j/dtm.html (with props)
xalan/java/branches/WebSite/xalan-j/extensions.html (with props)
xalan/java/branches/WebSite/xalan-j/extensions_xsltc.html (with props)
xalan/java/branches/WebSite/xalan-j/extensionslib.html (with props)
xalan/java/branches/WebSite/xalan-j/faq.html (with props)
xalan/java/branches/WebSite/xalan-j/features.html (with props)
xalan/java/branches/WebSite/xalan-j/getstarted.html (with props)
xalan/java/branches/WebSite/xalan-j/history.html (with props)
xalan/java/branches/WebSite/xalan-j/index.html (with props)
xalan/java/branches/WebSite/xalan-j/overview.html (with props)
xalan/java/branches/WebSite/xalan-j/public_apis.html (with props)
xalan/java/branches/WebSite/xalan-j/readme.html (with props)
xalan/java/branches/WebSite/xalan-j/resources/
xalan/java/branches/WebSite/xalan-j/resources.html (with props)
xalan/java/branches/WebSite/xalan-j/resources/Xalan-Logo-tm.png (with props)
xalan/java/branches/WebSite/xalan-j/resources/Xalan-Logo.txt (with props)
xalan/java/branches/WebSite/xalan-j/resources/Xalan-Trademark.txt (with props)
xalan/java/branches/WebSite/xalan-j/resources/XalanJ-Logo-tm.png (with props)
xalan/java/branches/WebSite/xalan-j/resources/apache-xalan.css
xalan/java/branches/WebSite/xalan-j/resources/asf_logo.png (with props)
xalan/java/branches/WebSite/xalan-j/resources/note.gif (with props)
xalan/java/branches/WebSite/xalan-j/samples.html (with props)
xalan/java/branches/WebSite/xalan-j/trax.html (with props)
xalan/java/branches/WebSite/xalan-j/usagepatterns.html (with props)
xalan/java/branches/WebSite/xalan-j/whatsnew.html (with props)
xalan/java/branches/WebSite/xalan-j/xmlfilters.gif (with props)
xalan/java/branches/WebSite/xalan-j/xpath_apis.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/
xalan/java/branches/WebSite/xalan-j/xsltc/DOMInterface.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/DOMLocking.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/all_namespaces.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/ast_stage1.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/ast_stage2.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/ast_stage3.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/cast_expression.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/class_loader.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/compiler_AST.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/compiler_DOM.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/compiler_architecture.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/compiler_design.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/dom_namespace1.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/dom_namespace2.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/dom_namespace3.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/index.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/iterator_stack.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/key_relations.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/match_namespace1.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/match_namespace2.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/namespace_stack.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/output_namespaces1.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/output_namespaces2.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/output_settings.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/overall_design.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/pattern_objects.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/resources/
xalan/java/branches/WebSite/xalan-j/xsltc/resources/Xalan-Logo-tm.png (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/resources/Xalan-Logo.txt (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/resources/Xalan-Trademark.txt (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/resources/XalanJ-Logo-tm.png (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/resources/apache-xalan.css
xalan/java/branches/WebSite/xalan-j/xsltc/resources/asf_logo.png (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/resources/note.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/runtime_architecture.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/runtime_design.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/runtime_type_mapping.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/sort_objects.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/translet_wrapping.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/trax_output_settings.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/trax_translet_wrapping.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/type_mapping.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/type_mappings.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/typecast.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/uri_resolver.gif (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_choose_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_comment_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_if_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_include_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_key_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_lang_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_sort_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_unparsed_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_variable_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsl_whitespace_design.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_compiler.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_dom.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_iterators.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_namespace.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_native_api.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_overview.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_performance.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_predicates.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_runtime.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_trax.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc/xsltc_trax_api.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc_history.html (with props)
xalan/java/branches/WebSite/xalan-j/xsltc_usage.html (with props)
Removed:
xalan/java/branches/WebSite/README.txt
Added: xalan/java/branches/WebSite/xalan-j/bugreporting.html
URL: http://svn.apache.org/viewvc/xalan/java/branches/WebSite/xalan-j/bugreporting.html?rev=1595253&view=auto
==============================================================================
--- xalan/java/branches/WebSite/xalan-j/bugreporting.html (added)
+++ xalan/java/branches/WebSite/xalan-j/bugreporting.html Fri May 16 16:11:33 2014
@@ -0,0 +1,233 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Reporting Bugs</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanJ-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan XSL Transformer User's Guide</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Reporting Bugs</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="http://xalan.apache.org/index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-J 2.7.2</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="readme.html">Release Notes</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="downloads.html">Download/Build</a>
+</li>
+<li>
+<a href="getstarted.html">Getting Started</a>
+</li>
+<li>
+<a href="xsltc_usage.html">Using XSLTC</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li></ul><hr /><ul>
+<li>
+<a href="features.html">Features</a>
+</li>
+<li>
+<a href="trax.html">Transform API</a>
+</li>
+<li>
+<a href="xpath_apis.html">XPath API</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="apidocs/index.html">Xalan-J API</a>
+</li>
+<li>
+<a href="public_apis.html">Public APIs</a>
+</li>
+<li>
+<a href="dtm.html">DTM</a>
+</li></ul><hr /><ul>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="extensions_xsltc.html">XSLTC Exts</a>
+</li></ul><hr /><ul>
+<li>
+<a href="design/design2_0_0.html">Xalan 2 Design</a>
+</li>
+<li>
+<a href="xsltc/index.html">XSLTC Design</a>
+</li></ul><hr /><ul>
+<li>
+<a href="builds.html">Building a release</a>
+</li>
+<li>
+<a href="http://xml.apache.org/xalan-j/test/overview.html">Testing</a>
+</li>
+<li>Bug Reporting<br />
+</li></ul><hr /><ul>
+<li>
+<a href="contact_us.html">Contact us</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Reporting Bugs</h2>
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Before you report a bug</h3>
+ <p>Before you report a bug, please, <b>read</b> the following instructions:</p>
+ <ul>
+ <li>If doubt exists whether the behaviour in question is a bug or a feature,
+ please post a message to the
+ <a href="mailto:j-users@xalan.apache.org">j-users@xalan.apache.org</a>
+ list for clarification.</li>
+ <li>To help eliminate duplicate or invalid bug reports, please take a quick look at
+ bugs in JIRA to see whether the bug has been already reported and/or fixed.
+ You can also download the
+ <a href="downloads.html">latest code</a>
+ and check if you can reproduce the bug.</li>
+ <li>Report bugs against the newest release.</li>
+ </ul>
+ <p>We strongly encourage you to write patches for problems you find and attach
+ them to your JIRA issue. Being specific in the description of your bug report, and
+ providing enough information to reproduce the bug will improve the likelihood that
+ bugs, adding enhancements, and addressing outstanding design issues, we need your
+ active participation in the ongoing development of Xalan Java.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Bugzilla is not used</h3>
+ <p>
+ The old bug tracking system,
+ <a href="http://issues.apache.org/bugzilla/">bugzilla</a>,
+ is still available but please only use it to look up old bugs.
+ Bugzilla has been replaced by <a href="http://issues.apache.org/jira/browse/XALANJ">JIRA</a>
+ and old bugzilla <b>bugs</b> have been migrated to JIRA as <b>issues</b>.
+ </p>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Report a bug</h3>
+ <p>After reading the instructions above, click
+ <a href="http://issues.apache.org/jira/browse/XALANJ">here</a> to submit a bug report using JIRA.
+ </p>
+ <p>
+ Note that the functionality shown by the JIRA user interface changes depending on whether
+ you <b>Log In</b> or not. In particular, to have the <b>CREATE NEW ISSUE</b> link
+ you will need to click the <b>Log In</b> in small font, in the top right corner
+ of the page and log in.
+ </p>
+ <p>
+ <table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">
+ If you had a bugzilla account previously, and had used it with Xalan bugzilla bugs,
+ your account should be migrated to JIRA. In this case, do not create a new account,
+ but use the same e-mail account name and click on "Forgot Password" on the JIRA home page.
+ </td>
+</tr>
+</table>
+ </p>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+</div>
+<div id="footer">Copyright © 1999-2014 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2014-05-15</div>
+</div>
+</body>
+</html>
Propchange: xalan/java/branches/WebSite/xalan-j/bugreporting.html
------------------------------------------------------------------------------
svn:eol-style = native
Added: xalan/java/branches/WebSite/xalan-j/builds.html
URL: http://svn.apache.org/viewvc/xalan/java/branches/WebSite/xalan-j/builds.html?rev=1595253&view=auto
==============================================================================
--- xalan/java/branches/WebSite/xalan-j/builds.html (added)
+++ xalan/java/branches/WebSite/xalan-j/builds.html Fri May 16 16:11:33 2014
@@ -0,0 +1,691 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Xalan-Java Release builds</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanJ-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan XSL Transformer User's Guide</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Xalan-Java Release builds</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="http://xalan.apache.org/index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-J 2.7.2</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="readme.html">Release Notes</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="downloads.html">Download/Build</a>
+</li>
+<li>
+<a href="getstarted.html">Getting Started</a>
+</li>
+<li>
+<a href="xsltc_usage.html">Using XSLTC</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li></ul><hr /><ul>
+<li>
+<a href="features.html">Features</a>
+</li>
+<li>
+<a href="trax.html">Transform API</a>
+</li>
+<li>
+<a href="xpath_apis.html">XPath API</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="apidocs/index.html">Xalan-J API</a>
+</li>
+<li>
+<a href="public_apis.html">Public APIs</a>
+</li>
+<li>
+<a href="dtm.html">DTM</a>
+</li></ul><hr /><ul>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="extensions_xsltc.html">XSLTC Exts</a>
+</li></ul><hr /><ul>
+<li>
+<a href="design/design2_0_0.html">Xalan 2 Design</a>
+</li>
+<li>
+<a href="xsltc/index.html">XSLTC Design</a>
+</li></ul><hr /><ul>
+<li>Building a release<br />
+</li>
+<li>
+<a href="http://xml.apache.org/xalan-j/test/overview.html">Testing</a>
+</li>
+<li>
+<a href="bugreporting.html">Bug Reporting</a>
+</li></ul><hr /><ul>
+<li>
+<a href="contact_us.html">Contact us</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Xalan-Java Release builds</h2>
+<ul>
+<li>
+<a href="#intro">Introduction</a>
+</li>
+<li>
+<a href="#developers">Developer Guidelines</a>
+</li>
+<li>
+<a href="#builds">Running Product Builds - Overview</a>
+</li>
+<li>
+<a href="#builds2">Running Product Builds - Details</a>
+</li>
+</ul>
+
+
+<a name="intro">â</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Introduction</h3>
+ <p>
+ This page is <b>not</b> for users
+ who want to download pre-built jars of Xalan-Java or download
+ the source code for Xalan-Java and build from that.
+ Users who want to do that
+ should see the <a href="downloads.html">Download/Build</a> page.
+ </p>
+ <p>
+ This page is intended for Xalan committers and developers and is about the
+ process to create a new release. It
+ provides a selection of brief checklists for committers and developers
+ about build procedures for the Xalan-Java community. Community input
+ is appreciated; if you have questions, please ask on
+ <a href="contact_us.html">xalan-dev</a>.
+ </p>
+ <p>
+ <table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">The product build related sections of this document are still
+ quite thin - they're mainly bullet points almost in checklist style.
+ If you don't fully understand the procedures in this document, then
+ you probably should ask for help first!
+ </td>
+</tr>
+</table>
+ </p>
+
+
+
+
+<a name="developers">â</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Developer Guidelines</h3>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">This section is meant to become a set of guidelines for all Xalan-Java
+committers and developers who wish to submit patches. It's still in progress;
+suggestions to xalan-dev@xml.apache.org appreciated.</td>
+</tr>
+</table>
+ <p>The project's technical mailing list for all committers and developers
+ interested in the API and inner workings is
+ <a href="mailto:xalan-dev@xml.apache.org">xalan-dev@xml.apache.org</a>;
+ it's a good idea to
+ <a href="contact_us.html#dev-mailing-list">subscribe</a>
+ if you plan to work on Xalan-Java. Logs of all Subversion
+ commits are automatically sent to <a href="mailto:xalan-cvs@xml.apache.org">xalan-cvs@xml.apache.org</a>, although
+ discussions should happen on xalan-dev. You can read more <a href="http://xml.apache.org/mail.html">about mailing lists.</a>
+</p>
+ <p>Xalan-Java is a fairly mature project; one where most committers and many
+ users expect that the daily build will be mostly functional. Very risky changes
+ or major architecture updates should be discussed ahead of time or committed onto
+ branches.</p>
+ <p>Developers should always run the Smoketest before checking in files or
+ submitting patches to the list. If the Smoketest does not pass, you should
+ either fix whatever you broke or get consensus from xalan-dev that
+ it's OK to break the Smoketest temporarily. The Smoketest is a selection of
+ API functionality tests and a pass through a wide variety of XSLT conformance
+ tests that ensure basic functionality. You can also read a full set of
+ <a href="http://xml.apache.org/xalan-j/test/overview.html">documentation about the tests</a>.</p>
+ <p>
+ (Smoketest doc is TBD!)
+<blockquote class="source">
+<pre>cvs co xml-xalan/java xml-xalan/test
+cd xml-xalan/java
+build smoketest
+# Ant build will fail if smoketest fails.
+</pre>
+</blockquote>
+</p>
+
+
+<a name="builds">â</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Running Product Builds - Overview</h3>
+<p>Official builds of Xalan-Java require a few more steps than simply doing
+'build fulldist'. This is a quick checklist of the steps; if you are
+not comfortable following this list, then please seek help on xalan-dev.</p>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Release Types</h4>
+<p>Official builds come in several flavors:</p>
+<ul>
+<li>Major version releases: when significant new or changed functionality comes out,
+we bump up the major build number; i.e. from 2.3 to 3.0. This is fairly rare;
+anyone reading xalan-dev will know when this is happening.<br />
+<br />
+</li>
+<li>Minor version releases happen when we fix bugs or make moderate improvements to
+the product. These are moving from 2.3 to 2.4; they should be planned out.<br />
+<br />
+</li>
+<li>Maintenance point releases are when we find bugs in an existing version and fix them without
+adding new functionality; these go from 2.3 to 2.3.1. They should be done on a
+branch if the mainline development has already moved forward; the point is to
+make critical bugfixes for existing customers who want to stay on the stable release.<br />
+<br />
+</li>
+<li>Developer releases are very ad hoc; they represent a chunk of progress along the
+HEAD of our Subversion tree towards a new major or minor release. The developer release
+versions would be going from 2.3 to a new 2.4.D1 - the developer release is somewhat
+like a 'beta' towards a new 2.4 minor version release. Quality standards for developer
+releases are much less stringent than other releases.<br />
+<br />
+</li>
+</ul>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Condensed Build Checklist</h4>
+<p>A very brief list of stages in running a build.</p>
+<ol>
+<li>Email xalan-dev with build plan.<br />
+<br />
+</li>
+<li>Verify all code changes are checked in.<br />
+<br />
+</li>
+<li>Verify any doc updates for code changes are in.<br />
+<br />
+</li>
+<li>Update build numbers in doc, code, and build scripts.<br />
+<br />
+</li>
+<li>Do a clean checkout and tag the sources.<br />
+<br />
+</li>
+<li>build fulldist -logfile ..\fulldist.log<br />
+<br />
+</li>
+<li>build fulldist-separatejars -logfile ..\fulldist-separatejars.log<br />
+<br />
+</li>
+<li>Run the smoketest for Xalan Interpretive and XSLTC.<br />
+<br />
+</li>
+<li>Verify smoketest passed; check docs built with new build numbers.<br />
+<br />
+</li>
+<li>PGP/GPG sign all .zip/.tar.gz distribution files (distros).<br />
+<br />
+</li>
+<li>Copy distros up to the website.<br />
+<br />
+</li>
+<li>Update website documentation set.<br />
+<br />
+</li>
+<li>Email xalan-dev with build notice!<br />
+<br />
+</li>
+</ol>
+
+
+
+
+<a name="builds2">â</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Running Product Builds - Details</h3>
+<p>This section is still in progress, but should have all the basics.
+You should already have read the <a href="#builds">build overview</a> above and you should already be
+familiar with our build.xml script and development processes.</p>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Pre-Build Steps</h4>
+<p>Preparation before you run a build.</p>
+<ul>
+<li>Email xalan-dev with build plan.</li>
+</ul>
+<p>Apache projects are communities: you should always let the community know what
+the plans for builds are. The xalan-dev mailing list is the primary communication
+mechanisim for committers and developers working on Xalan-Java; you may also wish
+to cc: the xalan-j-users list to let other users and folks know what's coming.
+For major releases you may also want to cc: the general@xml.apache.org list so that
+other xml.apache.org projects know our plans, although this is not required.</p>
+<ul>
+<li>Verify all code changes are checked in.</li>
+</ul>
+<p>Ensure that any code changes you're planning to have in this release are actually
+checked in; make sure any open work by other committers is in a stable state.
+You should also review any other projects we're dependent on and make sure
+that (when possible) we've updated to the latest version of their .jar files:
+like <code>xercesImpl.jar</code>, <code>ant.jar</code>, etc. Note that occasionally we will have a specific
+development need to stay with a different version of these projects.</p>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Updating Doc And Version Numbers</h4>
+<p>Getting documentation and version numbers in sync.</p>
+<ul>
+<li>Verify any doc updates for code changes are in.</li>
+</ul>
+<p>Check that the documentation is up to date. Make sure that any new
+features or major functionality changes are properly documented.</p>
+<p>Update the commits list and the 'what was done' list in xdocs/sources/xalan/readme.xml
+and whatsnew.xml. Note that currently some of the status information for the
+XSLTC portion of Xalan-Java is stored separately in xsltc_history.xml and XSLTCDONE
+</p>
+<p>Check in all your work!</p>
+
+<ul>
+<li>Update build numbers in doc, code, and build scripts.</li>
+</ul>
+<p>Once you know what the version number should be, you'll need to update
+it in a number of places - both for the product itself, for the build
+system, and for the documentation. If you don't understand how to update
+any of these files, then please get help - don't just try to wing it.</p>
+<ul>
+<li>build.xml
+Update the following lines for each version field:<br />
+<property name="version.VERSION" value="2"/><br />
+<property name="version.RELEASE" value="7"/><br />
+<property name="version.DEVELOPER" value=""/><br />
+<property name="version.MINOR" value="0"/><br />
+<property name="parser.version.VERSION" value="2"/><br />
+<property name="parser.version.RELEASE" value="7"/><br />
+<property name="parser.version.MINOR" value="1"/><br />
+<br />
+</li>
+<li>xml-xalan/java/xdocs/sources/xalan-jsite (document id="index" label="Xalan-Java x.x")<br />
+<br />
+</li>
+<li>If you updated <code>xercesImpl.jar</code> or <code>xml-apis.jar</code>, add a new entry in
+xml-xalan/java/src/org/apache/xalan/xslt/EnvironmentCheck.java</li>
+</ul>
+<p>I did remind you to check in all your work, didn't I?</p>
+
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Run A Candidate Distribution Build</h4>
+<p>Get clean sources and build a distribution and (at least) the smoketest.</p>
+<ul>
+<li>Do a clean checkout and tag the sources.</li>
+</ul>
+<p>Of course, you checked in all your earlier work to the Subversion repository, right?</p>
+<p>The safest way to perform a build for distribution is to check out a fresh
+new copy of the repository from Subversion. This avoids any potential problems with
+uncommitted changes or extra files on your local machine.</p>
+<p>Check out a new copy of both xml-xalan/java and xml-xalan/test repositories
+to a blank directory on your local machine. You then need to tag the files in
+the repository with a marker noting that these versions are the actual ones
+being used in the build (you could actually do this after running the build below).
+Use the Subversion tag command to add the tag to both repositories (/java and /test).
+The tag name should be something like 'xalan-j_2_4'; look at the log of any file
+to see the exact format of previous builds.</p>
+
+
+<ul>
+<li>build fulldist site -logfile ..\fulldist.log</li>
+</ul>
+<p>The above command will build the binary and source distribution .zip/.tar.gz
+files, in which the Xalan Interpretive and Xalan Compiled (XSLTC) processors
+are combined into the <code>xalan.jar</code> file. All the samples and the documentation
+are built as well. The log of the build is saved in ..\fulldist.log. Note
+that this will take up a moderate amount of space, especially when building
+the .tar.gz files, so ensure you have plenty of disk space first.</p>
+<p>Review the fulldist.log file quickly to ensure there were no build errors.
+Note that you can ignore any 'warnings' from the javadoc target; however any
+'error's in the documentation must be fixed.</p>
+
+<ul>
+<li>build fulldist-separatejars site -logfile ..\fulldist-separatejars.log</li>
+</ul>
+<p>Before running this command, rename the generated ./build directory from
+the 'fulldist' command above to another name, for example, build-combinedjar. The
+'fulldist-separatejars' command will build the binary and source distribution
+.zip/.tar.gz files, in which the Xalan Interpretive and Xalan Compiled (XSLTC) processors
+are built into separate jars; <code>xalan.jar</code> and <code>xsltc.jar</code> respectively. All the samples and
+the documentation are built as well. The log of the build is saved in ..\fulldist-separatejars.log.
+Note that this will take up a moderate amount of space, especially when building the .tar.gz
+files, so ensure you have plenty of disk space first.</p>
+<p>Review the fulldist-separatejars.log file quickly to ensure there were no build errors.
+Note that you can ignore any 'warnings' from the javadoc target; however any
+'error's in the documentation must be fixed.</p>
+<p>The results of the build will be
+placed in the ./build directory. Rename the xalan-j_2_x_x-bin.zip and xalan-j_2_x_x-bin.tar.gz
+files to xalan-j_2_x_x-bin-2jars.zip and xalan-j_2_x_x-bin-2jars.tar.gz respectively so that
+this binary distribution can be distinguished from the binary distributions created by the
+'fulldist' target. The source distributions, xalan-j_2_x_x-src.zip and xalan-j_2_x_x-src.tar.gz
+are duplicates of those created by the 'fulldist' target.</p>
+
+<ul>
+<li>Run the smoketest for Xalan Interpretive and XSLTC.</li>
+</ul>
+<p>Change to the xml-xalan\test directory and build the test harness by entering
+"build jar -logfile jar.log". Run the smoketest for the Xalan Interpretive processor by
+entering "build smoketest -logfile smoketest.log". Run the smoketest for the XSLTC by
+entering "build smoketest.xsltc -logfile smoketest.xsltc.log".
+</p>
+
+<ul>
+<li>Verify smoketest passed; check docs built with new build numbers.</li>
+</ul>
+<p>Review the smoketest.log and smoketest.xsltc.log files. If they do not say
+that the Smoketest passed, then you must fix the test results before
+posting the build. Even for developer's builds, we must ensure that at least
+the Smoketest passes. For major or minor releases, we should also perform more
+testing to ensure stability. More detailed log files for the Smoketest can
+be found in the xml-xalan/test/smoketest/ directory.</p>
+<p>You should also test that the documentation built properly, and that it
+has the proper build or release number that you edited above.</p>
+<p>IMPORTANT: if you changed any files at all, be sure to check in your work
+and re-start this process!</p>
+
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Code Signing and Posting</h4>
+<p>Sign the distribution units so end-users can trust them, then copy to the website.</p>
+<ul>
+<li>PGP/GPG sign all .zip/.tar.gz distribution files (distros).</li>
+</ul>
+<p>As a security measure, all xml.apache.org projects must sign or otherwise
+ensure the integrity of their public distributions. This is most commonly done
+by signing the actual .zip/.tar.gz files with your personal PGP or GPG key.
+Note that you must sign the files before copying them up to the website.</p>
+<p>The Xalan Java distributions consist of: the source distribution files
+(xalan-j_x_x_x-src.zip and xalan-j_x_x_x-src.tar.gz) and the two binary distributions
+files (xalan-j_x_x_x-bin.zip and xalan-j_x_x_x-bin.tar.gz, and xalan-j_x_x_x-bin-2jars.zip
+and xalan-j_x_x_x-bin-2jars.tar.gz).</p>
+<p>Two prerequisites to signing the distribution are: 1) you must have a
+personal PGP or GPG key, and 2) the public half of your key must be in the
+appropriate KEYS file before you begin a build. If you hadn't previously checked
+in your public key to the KEYS file before beginning this whole process, you'll
+have to go back and start again.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">We need some good links on getting <a href="http://web.mit.edu/network/pgp.html">PGP</a>
+and <a href="http://www.gnupg.org/">GPG</a>, and on actually
+code signing and verifying signatures. Jakarta has some, but they're
+scattered. This would be a good volunteer project for someone.</td>
+</tr>
+</table>
+<p>Sign every .zip and .tar.gz file with your personal key, and make a detached
+text file with the signature - this will usually create a
+foo.zip.asc or foo.zip.sig file for each foo.zip file you sign.</p>
+<ul>
+<li>Copy distros up to the website.</li>
+</ul>
+<p>You'll need to copy all of the distros plus all of your
+detached signature files to the website so people can download them. Note
+that apache.org machines generally do not allow inbound ftp, so you'll need to
+either scp them or login to the apache machines and use scp or pftp from there
+outbound to some server that you've copied them to.</p>
+<p>(Subject to change as www.apache.org/dist gets ready for mirroring)
+You'll need to log on to xml.apache.org (which is a separate machine
+from svn.apache.org) and upload the files to /www/xml.apache.org/xalan-j/dist</p>
+<p>You should also update the distribution directory's html files
+to note the new build numbers. Carefully edit the .htaccess file
+to update the 'Latest Stable Build' and 'Latest Developers Build' lines
+as needed. If you don't understand the format of this file, ask for help.</p>
+
+
+
+
+
+ <a name="doc">â</a>
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Rebuilding the Xalan-Java documentation</h4>
+ <p>Xalan-Java includes a number of XML source files, XSL stylesheets, document type definition (DTD)
+ files, entity relationship (ENT) files, graphics, and a JavaScript file that provide the input for the Xalan-Java
+ HTML User's Guide, and the overview and package-level documents used during the generation of Javadoc.
+ </p>
+ <p>
+ Before rebuilding the documentation there are probably a number of pages
+ that need to be updated, at a minimum consider these:
+
+ <table border="1">
+ <tr>
+<td class="content" rowspan="1" colspan="1">
+<b>XML source file</b>
+</td>
+<td class="content" rowspan="1" colspan="1">
+<b>Description of contents</b>
+</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">downloads.xml</td>
+<td class="content" rowspan="1" colspan="1">how to download releases</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">readme.xml</td>
+<td class="content" rowspan="1" colspan="1">has the release notes for each release (most recent to the oldest release)</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">whatsnew.xml</td>
+<td class="content" rowspan="1" colspan="1">describes what is new in the latest release</td>
+</tr>
+ </table>
+ <p>
+ For a new release it is quite likely that some information in the
+ <b>whatesnew.xml</b> page needs to be moved into the appropriate
+ section of the <b>readme.xml</b> or release notes page before
+ updating both of these pages with the information for the new release.
+ </p>
+ </p>
+ <p>To rebuild the documentation, you must use the StyleBook tool and the JDK 1.2.2 java and javadoc
+ tools. StyleBook (which uses Xalan and Xerces) is in <code>stylebook-1.0-b2.jar</code>. Some of the document definition files,
+ stylesheets, and resources are stored in xml-site-style.tar.gz, and are unzipped when you run Ant as described
+ below.
+ </p>
+ <p>You can use Ant with the docs target to regenerate the User's Guide and with the javadocs target to regenerate the
+ Javadoc API documentation.
+ </p>
+ <p>
+ When building the Javadoc API documentation, or the HTML pages for
+ the website the following Ant Targets are of interest:
+ </p>
+ <table border="1">
+ <tr>
+<td class="content" rowspan="1" colspan="1">
+<b>Ant Target</b>
+</td>
+<td class="content" rowspan="1" colspan="1">
+<b>What Ant does</b>
+</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">javadocs</td>
+<td class="content" rowspan="1" colspan="1">creates the API documentation</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">serializer.javadocs</td>
+<td class="content" rowspan="1" colspan="1">creates the API documetation for the serializer</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">site</td>
+<td class="content" rowspan="1" colspan="1">creates the HTML pages for the site http://xml.apache.org/xalan-j</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">xalan.apache.org.site</td>
+<td class="content" rowspan="1" colspan="1">creates the HTML pages for the site http://xalan.apache.org</td>
+</tr>
+ </table>
+
+
+
+
+
+
+
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Post-Build Docs and Email</h4>
+<p>Update the live website doc and let the community know you're done!</p>
+<ul>
+<li>Update website documentation set.</li>
+</ul>
+<p>Now that the distribution is available for downloading, you should also
+update the static copy of the documentation that's posted to xml.apache.org.
+</p>
+
+<ul>
+<li>Email xalan-dev with build notice!</li>
+</ul>
+<p>After everything is posted, you need to let the community know that
+a new build is available. Write up a short email announcing this with just
+a couple of the highlights of the new build, and a link to the
+distribution area.</p>
+
+<p>Make the subject something like: [ANN] Xalan-J 2.x Point/Developers/Whatever Release posted to xml.apache.org
+and send your email to: general@xml.apache.org, xalan-dev@xml.apache.org, xalan-j-users@xml.apache.org. Note
+that for developers releases, you can omit the general@xml.apache.org address if you
+don't think it will be of interest to the larger audience.
+</p>
+
+
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+</div>
+<div id="footer">Copyright © 1999-2014 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2014-05-15</div>
+</div>
+</body>
+</html>
Propchange: xalan/java/branches/WebSite/xalan-j/builds.html
------------------------------------------------------------------------------
svn:eol-style = native
Added: xalan/java/branches/WebSite/xalan-j/charter.html
URL: http://svn.apache.org/viewvc/xalan/java/branches/WebSite/xalan-j/charter.html?rev=1595253&view=auto
==============================================================================
--- xalan/java/branches/WebSite/xalan-j/charter.html (added)
+++ xalan/java/branches/WebSite/xalan-j/charter.html Fri May 16 16:11:33 2014
@@ -0,0 +1,509 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Xalan Project Charter</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanJ-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan XSL Transformer User's Guide</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Xalan Project Charter</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="http://xalan.apache.org/index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-J 2.7.2</a>
+</li>
+<li>Charter<br />
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="readme.html">Release Notes</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="downloads.html">Download/Build</a>
+</li>
+<li>
+<a href="getstarted.html">Getting Started</a>
+</li>
+<li>
+<a href="xsltc_usage.html">Using XSLTC</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li></ul><hr /><ul>
+<li>
+<a href="features.html">Features</a>
+</li>
+<li>
+<a href="trax.html">Transform API</a>
+</li>
+<li>
+<a href="xpath_apis.html">XPath API</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="apidocs/index.html">Xalan-J API</a>
+</li>
+<li>
+<a href="public_apis.html">Public APIs</a>
+</li>
+<li>
+<a href="dtm.html">DTM</a>
+</li></ul><hr /><ul>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="extensions_xsltc.html">XSLTC Exts</a>
+</li></ul><hr /><ul>
+<li>
+<a href="design/design2_0_0.html">Xalan 2 Design</a>
+</li>
+<li>
+<a href="xsltc/index.html">XSLTC Design</a>
+</li></ul><hr /><ul>
+<li>
+<a href="builds.html">Building a release</a>
+</li>
+<li>
+<a href="http://xml.apache.org/xalan-j/test/overview.html">Testing</a>
+</li>
+<li>
+<a href="bugreporting.html">Bug Reporting</a>
+</li></ul><hr /><ul>
+<li>
+<a href="contact_us.html">Contact us</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Xalan Project Charter</h2>
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Xalan Project Charter</h3>
+ <p>The following charter applies to all Xalan projects.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>1 INTRODUCTION</h3>
+ <p>1.1 Apache Xalan is a collaborative software development project
+ dedicated to providing robust, full-featured, commercial-quality, and
+ freely available XSLT support on a wide variety of platforms. This
+ project is managed in cooperation with various individuals worldwide
+ (both independent and company-affiliated experts), who use the
+ Internet to communicate, plan, and develop XSLT software and related
+ documentation.</p>
+ <p>1.2 This charter briefly describes the mission, history, organization
+ and processes of the project.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>2 MISSION</h3>
+ <p>2.1 Apache Xalan exists to promote the use of XSLT. We view XSLT
+ (Extensible Stylesheet Language Transformations) as a compelling
+ paradigm that transforms XML documents, thereby facilitating the
+ exchange, transformation, and presentation of knowledge. The ability
+ to transform XML documents into usable information has great potential
+ to improve the functionality and use of information systems. We intend
+ to build freely available XSLT processing components in order to
+ engender such improvements.</p>
+ <p>2.2 Apache Xalan consists of a set of components that transform XML
+ documents. Where appropriate, these components plug into other XML
+ components using standard APIs (formal, de facto, or proposed). The
+ components must be high performance, reliable, and easy to use. Where
+ inter-related, the components must be part of an underlying architectural
+ orchestration that will allow them to work together without major
+ negotiations or breakage.</p>
+ <p>2.3 We believe that the best way to define this XML transformation
+ architecture is by having both individuals and corporations
+ collaborate on the best possible infrastructure, APIs, code, testing,
+ and release cycles. Components must be vendor neutral and usable as
+ core components for all.</p>
+ <p>2.4 In order to achieve a coherent architecture between Apache Xalan
+ components and other components and applications, standards (formal or
+ de facto) will be used as much as possible for both protocols and
+ APIs. Where appropriate, experiences and lessons learned will be fed
+ back to standards bodies in an effort to assist in the development of
+ those standards. We will also encourage the innovation of new
+ protocols, APIs, and components in order to seed new concepts not
+ yet defined by standards.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>3 HISTORY</h3>
+ <p>3.1 This project was established under the direction of the Apache
+ Software Foundation in October 2004 to facilitate joint open-source
+ development. Prior to October 2004 this project was a subproject
+ of the Apache XML project.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>4 TERMS</h3>
+ <p>4.1 The ASF Board. The management board of the Apache Software
+ Foundation.</p>
+ <p>4.2 The Project. The Apache Xalan project; intended to refer to the
+ source code, website, subprojects, and community that are Apache Xalan.</p>
+ <p>4.3 Subproject. The Apache Xalan project may have subprojects; a
+ subproject is responsible for a component or application whose scope
+ is well defined.</p>
+ <p>4.4 Product. Some deliverable (usually a binary or source package)
+ that a subproject makes available to the public. Subprojects may have
+ multiple products.</p>
+ <p>4.5 Release. A specific version of a product. Subprojects may have
+ multiple releases of a given product.</p>
+ <p>4.6 Contributor. Anyone who makes a contribution to the development
+ of the Apache Xalan project.</p>
+ <p>4.7 Committer. The Apache Xalan project has a set of committers.
+ Committers are contributors who have read/write access to the source
+ code repository.</p>
+ <p>4.8 PMC. The PMC (Project Management Committee) is the group of people
+ that form the entity that makes decisions and controls the project.
+ Individual people or committers do not control the project.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>5 THE PROJECT MANAGEMENT COMMITTEE</h3>
+ <p>5.1 The Apache Xalan project is managed by a core group of committers
+ known as the Project Management Committee [PMC]. Subprojects, if any,
+ much each have at least one representative committer on the PMC.</p>
+ <p>5.2 The activities of the PMC are coordinated by the Chairperson,
+ who is an officer of the corporation and reports to the Apache
+ Board. The Chairperson will, on the request of the Apache Board,
+ provide reports to the Board on issues related to the running of
+ the Apache Xalan project.</p>
+ <p>5.3 The PMC has the following responsibilities:</p>
+ <p>a) Accepting new subproject proposals, formally submitting these
+ proposals for Apache Xalan committer vote, and creating the subproject
+ (see SUBPROJECTS below). This is done in collaboration with the
+ Incubator (see <a href="http://incubator.apache.org">http://incubator.apache.org</a>).</p>
+ <p>b) Facilitating code or other donations by individuals or companies,
+ in collaboration with the Incubator.</p>
+ <p>c) Resolving license issues and other legal issues in conjunction with
+ the ASF board.</p>
+ <p>d) Ensuring that administrative and infrastructure work is completed.</p>
+ <p>e) Facilitating relationships among projects and subprojects.</p>
+ <p>f) Facilitating relationships between the Apache Xalan project and the
+ external world.</p>
+ <p>g) Overseeing Apache Xalan to ensure that the mission defined in this
+ document is being fulfilled.</p>
+ <p>h) Resolving conflicts within the project.</p>
+ <p>i) Reporting to the ASF board (through the Chair) on the progress
+ of the project.</p>
+ <p>j) Propose new releases of projects or subprojects. Such proposals pass
+ if 75% of the PMC members vote in agreement.</p>
+
+ <p>5.4 A contributor can, at any time, nominate a committer to be on the PMC,
+ by calling for a vote. If two thirds, or more, of the active committers
+ vote in agreement then the nomination is given to the PMC. The person
+ becomes a new PMC member if 75% or more of the PMC members vote in
+ agreement, with no dissenting votes among the PMC members. This individual
+ should be elected based on merit for the evolution of the project and
+ demonstration of commitment.</p>
+ <p>5.5 In cases where the subproject is unable to directly provide a
+ representative on the PMC, another member of the PMC will be required to
+ represent that subproject on the PMC. This will be strongly discouraged.
+ It is preferable that all subprojects have direct representation on the
+ PMC.</p>
+ <p>5.6 At least every twelve months, or more often if directed by the ASF
+ board, the PMC members will elect a Chairperson from among themselves;
+ the person with the most votes from the other PMC members is recommended
+ to the ASF board for the position of Chairperson, and with the ASF board's
+ approval, becomes the Chairperson for the new term.</p>
+ <p>5.7 Upon agreement by the Apache Board, the recommended Chairperson will,
+ if they are not already, be appointed an officer of the corporation. See
+ <a href="http://www.apache.org/foundation/bylaws.html">
+ http://www.apache.org/foundation/bylaws.html</a> for more information.</p>
+ <p>5.8 The PMC is responsible for maintaining and updating this charter.
+ Development must follow the process outlined below, so any change to the
+ development process necessitates a change to the charter. Proposed changes
+ to this charter by the PMC are passed if 75% or more of the PMC members
+ approve the proposal, with no dissenting votes. However, an active Apache
+ Xalan committer may challenge the change.</p>
+ <p>5.9 An active Apache Xalan committer may challenge a change to this charter
+ proposed by the PMC within two weeks of its proposal. When challenged the
+ proposed change is passed if within two weeks of the challenge the active
+ committers approve the change with a two-thirds majority vote.</p>
+ <p>5.10 The PMC ultimately makes the decisions for the project, not the individual
+ people. At any time the PMC can reject patches or other contributions to the
+ project if 75% or more of the PMC members vote to reject the contribution.</p>
+ <p>5.11 A PMC member may resign their membership at any time. However, in the
+ unlikely event that a member of the PMC becomes disruptive to the process,
+ such as ceasing to take part in PMC votes, the PMC member may be removed from
+ the PMC by a vote among the other PMC members. The PMC member is removed if
+ 75% or more of the other PMC members approve the removal, with no dissenting
+ votes among the other PMC members.</p>
+ <p>5.12 A person remains a PMC member until he or she resigns, is removed by a
+ vote from among the other PMC members, dies or is incapacitated.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>6 SUBPROJECTS</h3>
+ <p>6.1 A subproject of the Apache Xalan project is responsible for a component
+ or application whose scope is well defined. Each subproject has its own set
+ of developers, and is responsible for approving its own committers. Apache
+ Xalan is composed of subprojects which fit into one of two categories:</p>
+ <p>(a) An XSLT processor implementation in some particular programming
+ language. There may be multiple processors for a given language if
+ the API's the processors support are sufficiently dissimilar. At the
+ time of writing, there is one processor for C++ and two for Java.</p>
+ <p>(b) A set of components which are used in related applications and are
+ tightly bound, usually through internal API's, to one (or more) of the
+ processor subprojects.</p>
+ <p>6.2 A new subproject proposal is submitted to the PMC, and then accepted
+ by a majority Apache Xalan project active committer vote within two weeks
+ after the proposal.</p>
+ <p>6.3 Each subproject must have a set of requirements as well as an
+ up-to-date release plan and design document on its dedicated web page.</p>
+ <p>6.4 It is recommended that each subproject have a smoke-test system
+ that works at least as a basic integration test.</p>
+ <p>6.5 A subproject may be removed if 75% or more of the PMC members approve
+ the proposal, there are no dissenting votes among the PMC members,
+ and no challenges by active Apache Xalan project committers
+ within two weeks after the proposal.
+ A contributor may challenge the proposed removal
+ of a subproject within two weeks of the proposal.
+ In this case the proposed removal is passed if within two weeks of the
+ challenge the active committers approve the removal with a two-thirds
+ majority vote. Any subproject removal is subject to the approval of the
+ ASF board.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>7 CONTRIBUTORS</h3>
+ <p>7.1 Like all Apache projects, the Apache Xalan project is a
+ meritocracy -- the more work you do, the more you are allowed to do.</p>
+ <p>7.2 People who make regular and substantial contributions may become
+ committers as described below. Contributions include: participating in
+ mailing lists, reporting issues or bugs in issue-records in the Issue Database,
+ providing patches, and proposing changes to a product.</p>
+ <p>7.3 In order to ensure that all code contained in the Apache Xalan
+ project's code repository is free of licensing, intellectual property and patent
+ issues, any person wishing to contribute a new feature to Apache Xalan must either
+ sign:</p>
+ <p>a) If contributing as an individual, sign the "Individual
+ Contributor License Agreement (CLA)"
+ (<a href="http://www.apache.org/licenses/icla.txt">http://www.apache.org/licenses/icla.txt</a>)
+ and file a copy with the Secretary of the Corporation; or </p>
+ <p>b) If making the contribution as part of their employment
+ responsibilities, sign the "Corporate CLA (CCLA)",
+ (<a href="http://www.apache.org/licenses/cla-corporate.txt">http://www.apache.org/licenses/cla-corporate.txt</a>)
+ and file a copy with the Secretary of the Corporation.</p>
+ <p>7.4 If the contribution in question is a small bugfix, the contributor need
+ not sign a CLA, but need only provide the following information, attaching
+ it to the communication containing the patch:</p>
+ <p>a) Name and employer</p>
+ <p>b) Are you the author of the code being contributed?</p>
+ <p>c) Do you have the right to grant the copyright and patent
+ licenses for the contribution that are set forth in the ASF v.2.0
+ license (<a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)?</p>
+ <p>d) Does your employer have any rights to code that you have
+ written, for example, through your contract for employment? If
+ so, has your employer given you permission to contribute the code
+ on its behalf or waived its rights in the code?</p>
+ <p>e) Are you aware of any third-party licenses or other
+ restrictions (such as related patents or trademarks) that could
+ apply to your contribution? If so, what are they?</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>8 COMMITTERS</h3>
+ <p>8.1 The Apache Xalan project has a set of committers. If there
+ are subprojects, each subproject will also have a set of committers.
+ Committers are contributors who have read/write access to the source code
+ repository. New committers are added when a contributor is nominated by a
+ committer and approved by at least 50 percent of the active committers for
+ that subproject with no opposing votes. In most cases, new committers will
+ already be participating in the development process by submitting suggestions
+ and/or fixes via issue-records in the Issue Database or mailing lists.</p>
+ <p>8.2 For the purposes of voting, committers will be classed as "active" or
+ "inactive". Only active committers will be included in the totals used to
+ determine the success or failure of a particular vote.</p>
+ <p>8.3 Committers remain active as long as they are contributing code or
+ posting to the project or subproject mailing lists. If a committers has
+ neither contributed code nor posted to the mailing lists in 3
+ months, a member of the PMC will e-mail the committer,
+ the project or subproject development list, and the PMC mailing list
+ notifying the committer that they are now in inactive status.</p>
+ <p>8.4 An inactive status will not prevent a committer committing new code
+ changes or posting to the mailing lists. Either of these activities will
+ automatically re-activate the committer for the purposes of voting.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>9 INFRASTRUCTURE</h3>
+ <p>9.1 The Apache Xalan project relies on the Apache XML project
+ and the Apache Infrastructure project for the following:</p>
+ <p>a) Issue Database -- This is a system with issue-records,
+ for tracking bugs, issues, features and requests.</p>
+ <p>b) Repository -- The xalan.apache.org project has its set
+ of parts that make up the software, and these parts are
+ managed in a repository. Committers make changes to the source code,
+ documentation and other associated parts that are stored in
+ the repository. Any subproject will have its set of committers
+ for its repository.</p>
+ <p>c) Website -- The website <a href="http://xalan.apache.org">xalan.apache.org</a>
+ will contain information about the Apache Xalan project and its subprojects,
+ including documentation, downloads of releases, and this charter.</p>
+ <p>d) Mailing Lists -- appropriate mailing lists will be created
+ at the discretion of the PMC. Such mailing lists could
+ for example include: a PMC mailing list, a general mailing list,
+ project or subproject public developer mailing lists,
+ project or subproject public user mailing lists.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>10 LICENSING</h3>
+ <p>10.1 All contributions to the Apache Xalan project adhere to the "Apache
+ Software Foundation License, Version 2.0"
+ (<a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>).
+ All further contributions, including patches, must be made under the same terms.</p>
+ <p>10.2 When a committer is considering integrating a contribution
+ from a contributor who has no CLA on file with the Corporation,
+ it is the responsibility of the committer, in consultation with
+ the PMC, to conduct due diligence on the pedigree of the
+ contribution under consideration; see sections 7.3 and 7.4. </p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>11 THE DEVELOPMENT PROCESS</h3>
+ <p>11.1 For a committer to commit a change to the MAIN branch of the
+ repository an issue-record must be opened in the "Issue Database"
+ to track the change. The status of the issue must be kept up to date.</p>
+ <p>11.2 No voting is required to commit changes, but one other active
+ committer must review the changes. Before the changes are committed, the reviewer
+ must add a comment in the corresponding issue-record indicating that
+ they have reviewed and approve the changes.</p>
+ <p>11.3 Issue-records and reviews are not required for committing changes to
+ other experimental branches (not the MAIN branch) in a repository.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>12 VOTING</h3>
+ <p>12.1 Unless otherwise stated in this mission, votes cast on Apache Xalan
+ proposals must be made within two weeks of the proposal. A challenge to
+ a proposal must also be made within two weeks of the proposal. Likewise,
+ votes cast on challenges must be cast within two weeks of the challenge.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>13 RELATIONSHIP TO OTHER APACHE PROJECTS</h3>
+ <p>13.1 The Apache Xalan project should work closely with other Apache
+ projects, such as Xerces and XML, to avoid redundancy
+ and achieve a coherent architecture among Apache Xalan and these
+ projects.</p>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+</div>
+<div id="footer">Copyright © 1999-2014 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2014-05-15</div>
+</div>
+</body>
+</html>
Propchange: xalan/java/branches/WebSite/xalan-j/charter.html
------------------------------------------------------------------------------
svn:eol-style = native
Added: xalan/java/branches/WebSite/xalan-j/commandline.html
URL: http://svn.apache.org/viewvc/xalan/java/branches/WebSite/xalan-j/commandline.html?rev=1595253&view=auto
==============================================================================
--- xalan/java/branches/WebSite/xalan-j/commandline.html (added)
+++ xalan/java/branches/WebSite/xalan-j/commandline.html Fri May 16 16:11:33 2014
@@ -0,0 +1,289 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Command-Line Utility</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanJ-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan XSL Transformer User's Guide</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Command-Line Utility</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="http://xalan.apache.org/index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-J 2.7.2</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="readme.html">Release Notes</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="downloads.html">Download/Build</a>
+</li>
+<li>
+<a href="getstarted.html">Getting Started</a>
+</li>
+<li>
+<a href="xsltc_usage.html">Using XSLTC</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>Command Line<br />
+</li></ul><hr /><ul>
+<li>
+<a href="features.html">Features</a>
+</li>
+<li>
+<a href="trax.html">Transform API</a>
+</li>
+<li>
+<a href="xpath_apis.html">XPath API</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="apidocs/index.html">Xalan-J API</a>
+</li>
+<li>
+<a href="public_apis.html">Public APIs</a>
+</li>
+<li>
+<a href="dtm.html">DTM</a>
+</li></ul><hr /><ul>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="extensions_xsltc.html">XSLTC Exts</a>
+</li></ul><hr /><ul>
+<li>
+<a href="design/design2_0_0.html">Xalan 2 Design</a>
+</li>
+<li>
+<a href="xsltc/index.html">XSLTC Design</a>
+</li></ul><hr /><ul>
+<li>
+<a href="builds.html">Building a release</a>
+</li>
+<li>
+<a href="http://xml.apache.org/xalan-j/test/overview.html">Testing</a>
+</li>
+<li>
+<a href="bugreporting.html">Bug Reporting</a>
+</li></ul><hr /><ul>
+<li>
+<a href="contact_us.html">Contact us</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Command-Line Utility</h2>
+<ul>
+<li>
+<a href="commandline_xsltc.html">Command line options for XSLTC</a>
+</li>
+</ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Using the Command-Line Utility</h3>
+ <p>To perform a transformation, you can call Xalan-Java from the command line (or script),
+ an applet, an application, or a servlet (see <a href="usagepatterns.html">Usage Patterns</a>).</p>
+ <p>The org.apache.xalan.xslt.Process main() method provides a command-line interface
+ for performing XSL transformation. To perform a transformation from the command line or a script,
+ do the following:</p>
+ <ol>
+ <li>Download Xalan-Java.<br />
+<br />
+</li>
+ <li>
+<a href="getstarted.html#classpath">Set the Java classpath</a> to include <code>xalan.jar</code>, <code>serializer.jar</code>, <code>xml-apis.jar</code>, and
+ <code>xercesImpl.jar</code> -- or another conformant XML Parser -- (see <a href="usagepatterns.html#plug">Plugging in
+ the Transformer and XML parser</a>).<br />
+<br />
+</li>
+ <li>Call java and the Process class with the appropriate flags and
+ arguments (described below). The following command line, for example, includes the -IN, -XSL,
+ and -OUT flags with their accompanying arguments -- the XML source document, the XSL
+ stylesheet, and the output file:<br />
+<br />
+ <code>java org.apache.xalan.xslt.Process -IN foo.xml -XSL foo.xsl -OUT foo.out</code>
+ </li>
+</ol>
+ <p>The command line utility can take the following flags and arguments (the flags are case insensitive):</p>
+ <blockquote class="source">
+<pre>
+ Common Options
+
+-XSLTC (use XSLTC for transformation)
+-IN inputXMLURL
+-XSL XSLTransformationURL
+-OUT outputFileName
+-V (Version info)
+-EDUMP [optional filename] (Do stackdump on error.)
+-XML (Use XML formatter and add XML header.)
+-TEXT (Use simple Text formatter.)
+-HTML (Use HTML formatter.)
+-PARAM name expression (Set a stylesheet parameter)
+-MEDIA mediaType (use media attribute to find stylesheet associated with a document)
+-FLAVOR flavorName (Explicitly use s2s=SAX or d2d=DOM to do transform)
+-DIAG (Print overall milliseconds transform took)
+-URIRESOLVER full class name (URIResolver to be used to resolve URIs)
+-ENTITYRESOLVER full class name (EntityResolver to be used to resolve entities)
+-CONTENTHANDLER full class name (ContentHandler to be used to serialize output)
+-SECURE (set the secure processing feature to true)
+
+ Options for Xalan-Java Interpretive
+
+-QC (Quiet Pattern Conflicts Warnings)
+-TT (Trace the templates as they are being called)
+-TG (Trace each generation event)
+-TS (Trace each selection event)
+-TTC (Trace the template children as they are being processed)
+-TCLASS (TraceListener class for trace extensions)
+-L (use line numbers for source document)
+-INCREMENTAL (request incremental DTM construction by setting
+ http://xml.apache.org/xalan/features/incremental to true)
+-NOOPTIMIMIZE (request no stylesheet optimization proccessing by setting
+ http://xml.apache.org/xalan/features/optimize to false)
+-RL recursionlimit (assert numeric limit on stylesheet recursion depth)
+
+ Options for Xalan-Java Compiled (XSLTC)
+
+-XO [optional transletName] (assign the name to the generated translet)
+-XD destinationDirectory (specify a destination directory for translet)
+-XJ jarfile (package translet classes into a jar file of name <jarfile>)
+-XP package (specify a package name prefix for all generated translet classes)
+-XN (enable XSL template inlining into one big method)
+-XX (turn on additional debugging message output)
+-XT (use translet to transform if possible)
+</pre>
+</blockquote>
+ <p>Use <code>-XSLTC</code> if you want to transform with XSLTC. Please refer to
+ <a href="commandline_xsltc.html">this document</a> for a detailed description on
+ XSLTC related options.</p>
+ <p>Use <code>-IN</code> to specify the XML source document.</p>
+ <p>Use <code>-XSL</code> to specify the XSL stylesheet file.</p>
+ <p>Use <code>-TEXT</code> if you want the output to include only element values (not element tags with element names and
+ attributes).</p>
+ <p>Use <code>-HTML</code> to write 4.0 transitional HTML (some elements, such as <br>, are
+ not well formed XML).</p>
+ <p>To set stylesheet parameters from the command line, use <br />
+ <code>java org.apache.xalan.xslt.Process -PARAM <b>
+<i>name value</i>
+</b>
+</code>
+</p>
+ <p>The value is passed to the transformer as a String.</p>
+ <p>For information about incremental and optimized stylesheet processing, see <a href="dtm.html#settings">DTM settings</a>.</p>
+ <p>Use <code>-L</code> to obtain access to a SourceLocator that a stylesheet extension can use to get information about the location
+ of nodes in the source document. For more information, see <a href="extensionslib.html#nodeinfo">NodeInfo extension functions</a>
+ and <a href="features.html#source_location">source_location</a>.</p>
+ <p>Use <code>-URIRESOLVER</code> with a fully qualified class name to utilize a custom implementation of the
+ <a href="apidocs/javax/xml/transform/URIResolver.html">URIResolver</a> JAXP interface to resolve URIs for
+ xsl:include, xsl:import, and the document() function.</p>
+ <p>Use <code>-ENTITYRESOLVER</code> with a fully qualified class name to utilize a custom implementation of the
+ <a href="apidocs/org/xml/sax/EntityResolver.html">EntityResolver</a> SAX interface to handle external entity references.</p>
+ <p>Use <code>-CONTENTHANDLER</code> with a fully qualified class name to utilize a custom implementation of the
+ <a href="apidocs/org/xml/sax/ContentHandler.html">ContentHandler</a> SAX interface to serialize output.
+ If this same class implements the <a href="apidocs/org/xml/sax/ext/LexicalHandler.html">org.xml.sax.ext.LexicalHandler</a>
+ interface and the output method is "xml", it will also receive lexical information about the XML document during serialization.</p>
+ <table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">If you want to validate an XML document (verify that it adheres to its DOCTYPE declaration), you can use the
+ <a href="samples.html#validateutility">Validate utility</a> shipped with Xalan-Java Version 2.7.2.</td>
+</tr>
+</table>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+</div>
+<div id="footer">Copyright © 1999-2014 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2014-05-15</div>
+</div>
+</body>
+</html>
Propchange: xalan/java/branches/WebSite/xalan-j/commandline.html
------------------------------------------------------------------------------
svn:eol-style = native
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xalan.apache.org
For additional commands, e-mail: commits-help@xalan.apache.org