Author: ggregory
Date: Sat Jan 26 00:21:31 2019
New Revision: 1852193
URL: http://svn.apache.org/viewvc?rev=1852193&view=rev
Log:
Prepare for 2.3.
Modified:
commons/proper/vfs/trunk/CONTRIBUTING.md
commons/proper/vfs/trunk/NOTICE.txt
commons/proper/vfs/trunk/README.md
commons/proper/vfs/trunk/pom.xml
commons/proper/vfs/trunk/src/site/xdoc/download_vfs2.xml
commons/proper/vfs/trunk/src/site/xdoc/issue-tracking.xml
commons/proper/vfs/trunk/src/site/xdoc/mail-lists.xml
Modified: commons/proper/vfs/trunk/CONTRIBUTING.md
URL:
http://svn.apache.org/viewvc/commons/proper/vfs/trunk/CONTRIBUTING.md?rev=1852193&r1=1852192&r2=1852193&view=diff
==============================================================================
--- commons/proper/vfs/trunk/CONTRIBUTING.md (original)
+++ commons/proper/vfs/trunk/CONTRIBUTING.md Sat Jan 26 00:21:31 2019
@@ -1,97 +1,115 @@
-<!---
- 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.
--->
-<!---
- +======================================================================+
- |**** ****|
- |**** THIS FILE IS GENERATED BY THE COMMONS BUILD PLUGIN ****|
- |**** DO NOT EDIT DIRECTLY ****|
- |**** ****|
- +======================================================================+
- | TEMPLATE FILE: contributing-md-template.md |
- | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
- +======================================================================+
- | |
- | 1) Re-generate using: mvn commons:contributing-md |
- | |
- | 2) Set the following properties in the component's pom: |
- | - commons.jira.id (required, alphabetic, upper case) |
- | |
- | 3) Example Properties |
- | |
- | <properties> |
- | <commons.jira.id>MATH</commons.jira.id> |
- | </properties> |
- | |
- +======================================================================+
---->
-Contributing to Apache Commons VFS
-======================
-
-You have found a bug or you have an idea for a cool new feature? Contributing
code is a great way to give something back to
-the open source community. Before you dig right into the code there are a few
guidelines that we need contributors to
-follow so that we can have a chance of keeping on top of things.
-
-Getting Started
----------------
-
-+ Make sure you have a [JIRA account](https://issues.apache.org/jira/).
-+ Make sure you have a [GitHub account](https://github.com/signup/free).
-+ If you're planning to implement a new feature it makes sense to discuss
you're changes on the [dev
list](http://commons.apache.org/proper/commons-vfs/mail-lists.html) first. This
way you can make sure you're not wasting your time on something that isn't
considered to be in Apache Commons VFS's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
- + Clearly describe the issue including steps to reproduce when it is a bug.
- + Make sure you fill in the earliest version that you know has the issue.
-+ Fork the repository on GitHub.
-
-Making Changes
---------------
-
-+ Create a topic branch from where you want to base your work (this is usually
the master/trunk branch).
-+ Make commits of logical units.
-+ Respect the original code style:
- + Only use spaces for indentation.
- + Create minimal diffs - disable on save actions like reformat source code
or organize imports. If you feel the source code should be reformatted create a
separate PR for this change.
- + Check for unnecessary whitespace with git diff --check before committing.
-+ Make sure your commit messages are in the proper format. Your commit message
should contain the key of the JIRA issue.
-+ Make sure you have added the necessary tests for your changes.
-+ Run all the tests with `mvn clean verify` to assure nothing else was
accidentally broken.
-
-Making Trivial Changes
-----------------------
-
-For changes of a trivial nature to comments and documentation, it is not
always necessary to create a new ticket in JIRA.
-In this case, it is appropriate to start the first line of a commit with
'(doc)' instead of a ticket number.
-
-Submitting Changes
-------------------
-
-+ Sign the [Contributor License Agreement][cla] if you haven't already.
-+ Push your changes to a topic branch in your fork of the repository.
-+ Submit a pull request to the repository in the apache organization.
-+ Update your JIRA ticket and include a link to the pull request in the ticket.
-
-Additional Resources
---------------------
-
-+ [Contributing patches](http://commons.apache.org/patches.html)
-+ [Apache Commons VFS JIRA project
page](https://issues.apache.org/jira/browse/VFS)
-+ [Contributor License Agreement][cla]
-+ [General GitHub documentation](http://help.github.com/)
-+ [GitHub pull request
documentation](http://help.github.com/send-pull-requests/)
-+ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons)
-+ #apachecommons IRC channel on freenode.org
-
-[cla]:http://www.apache.org/licenses/#clas
+<!---
+ 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.
+-->
+<!---
+ +======================================================================+
+ |**** ****|
+ |**** THIS FILE IS GENERATED BY THE COMMONS BUILD PLUGIN ****|
+ |**** DO NOT EDIT DIRECTLY ****|
+ |**** ****|
+ +======================================================================+
+ | TEMPLATE FILE: contributing-md-template.md |
+ | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+ +======================================================================+
+ | |
+ | 1) Re-generate using: mvn commons-build:contributing-md |
+ | |
+ | 2) Set the following properties in the component's pom: |
+ | - commons.jira.id (required, alphabetic, upper case) |
+ | |
+ | 3) Example Properties |
+ | |
+ | <properties> |
+ | <commons.jira.id>MATH</commons.jira.id> |
+ | </properties> |
+ | |
+ +======================================================================+
+--->
+Contributing to Apache Commons VFS Project
+======================
+
+You have found a bug or you have an idea for a cool new feature? Contributing
code is a great way to give something back to
+the open source community. Before you dig right into the code there are a few
guidelines that we need contributors to
+follow so that we can have a chance of keeping on top of things.
+
+Getting Started
+---------------
+
++ Make sure you have a [JIRA account](https://issues.apache.org/jira/).
++ Make sure you have a [GitHub account](https://github.com/signup/free).
++ If you're planning to implement a new feature it makes sense to discuss your
changes on the [dev list](https://commons.apache.org/mail-lists.html) first.
This way you can make sure you're not wasting your time on something that isn't
considered to be in Apache Commons VFS Project's scope.
++ Submit a [Jira Ticket][jira] for your issue, assuming one does not already
exist.
+ + Clearly describe the issue including steps to reproduce when it is a bug.
+ + Make sure you fill in the earliest version that you know has the issue.
++ Find the corresponding [repository on
GitHub](https://github.com/apache/?query=commons-),
+[fork](https://help.github.com/articles/fork-a-repo/) and check out your
forked repository.
+
+Making Changes
+--------------
+
++ Create a _topic branch_ for your isolated work.
+ * Usually you should base your branch on the `master` or `trunk` branch.
+ * A good topic branch name can be the JIRA bug id plus a keyword, e.g.
`VFS-123-InputStream`.
+ * If you have submitted multiple JIRA issues, try to maintain separate
branches and pull requests.
++ Make commits of logical units.
+ * Make sure your commit messages are meaningful and in the proper format.
Your commit message should contain the key of the JIRA issue.
+ * e.g. `VFS-123: Close input stream earlier`
++ Respect the original code style:
+ + Only use spaces for indentation.
+ + Create minimal diffs - disable _On Save_ actions like _Reformat Source
Code_ or _Organize Imports_. If you feel the source code should be reformatted
create a separate PR for this change first.
+ + Check for unnecessary whitespace with `git diff` -- check before
committing.
++ Make sure you have added the necessary tests for your changes, typically in
`src/test/java`.
++ Run all the tests with `mvn clean verify` to assure nothing else was
accidentally broken.
+
+Making Trivial Changes
+----------------------
+
+The JIRA tickets are used to generate the changelog for the next release.
+
+For changes of a trivial nature to comments and documentation, it is not
always necessary to create a new ticket in JIRA.
+In this case, it is appropriate to start the first line of a commit with
'(doc)' instead of a ticket number.
+
+
+Submitting Changes
+------------------
+
++ Sign and submit the Apache [Contributor License Agreement][cla] if you
haven't already.
+ * Note that small patches & typical bug fixes do not require a CLA as
+ clause 5 of the [Apache
License](https://www.apache.org/licenses/LICENSE-2.0.html#contributions)
+ covers them.
++ Push your changes to a topic branch in your fork of the repository.
++ Submit a _Pull Request_ to the corresponding repository in the `apache`
organization.
+ * Verify _Files Changed_ shows only your intended changes and does not
+ include additional files like `target/*.class`
++ Update your JIRA ticket and include a link to the pull request in the ticket.
+
+If you prefer to not use GitHub, then you can instead use
+`git format-patch` (or `svn diff`) and attach the patch file to the JIRA issue.
+
+
+Additional Resources
+--------------------
+
++ [Contributing patches](https://commons.apache.org/patches.html)
++ [Apache Commons VFS Project JIRA project page][jira]
++ [Contributor License Agreement][cla]
++ [General GitHub documentation](https://help.github.com/)
++ [GitHub pull request
documentation](https://help.github.com/articles/creating-a-pull-request/)
++ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons)
++ `#apache-commons` IRC channel on `irc.freenode.net`
+
+[cla]:https://www.apache.org/licenses/#clas
+[jira]:https://issues.apache.org/jira/browse/VFS
Modified: commons/proper/vfs/trunk/NOTICE.txt
URL:
http://svn.apache.org/viewvc/commons/proper/vfs/trunk/NOTICE.txt?rev=1852193&r1=1852192&r2=1852193&view=diff
==============================================================================
--- commons/proper/vfs/trunk/NOTICE.txt (original)
+++ commons/proper/vfs/trunk/NOTICE.txt Sat Jan 26 00:21:31 2019
@@ -1,5 +1,5 @@
-Apache Commons VFS
-Copyright 2002-2017 The Apache Software Foundation
+Apache Commons VFS Project
+Copyright 2002-2019 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
Modified: commons/proper/vfs/trunk/README.md
URL:
http://svn.apache.org/viewvc/commons/proper/vfs/trunk/README.md?rev=1852193&r1=1852192&r2=1852193&view=diff
==============================================================================
--- commons/proper/vfs/trunk/README.md (original)
+++ commons/proper/vfs/trunk/README.md Sat Jan 26 00:21:31 2019
@@ -25,7 +25,7 @@
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:readme-md |
+ | 1) Re-generate using: mvn commons-build:readme-md |
| |
| 2) Set the following properties in the component's pom: |
| - commons.componentid (required, alphabetic, lower case) |
@@ -40,20 +40,22 @@
| |
+======================================================================+
--->
-Apache Commons VFS
+Apache Commons VFS Project
===================
-[](https://travis-ci.org/apache/commons-vfs)
+[](https://travis-ci.org/apache/commons-vfs2)
+[](https://coveralls.io/r/apache/commons-vfs2)
[](https://maven-badges.herokuapp.com/maven-central/org.apache.commons/commons-vfs2/)
+[](https://javadoc.io/doc/org.apache.commons/commons-vfs2/2.3)
Apache Commons VFS is a Virtual File System library.
Documentation
-------------
-More information can be found on the [Apache Commons VFS
homepage](https://commons.apache.org/proper/commons-vfs).
-The
[Javadoc](https://commons.apache.org/proper/commons-vfs/apidocs/index.html) can
be browsed.
-Questions related to the usage of Apache Commons VFS should be posted to the
[user mailing list][ml].
+More information can be found on the [Apache Commons VFS Project
homepage](https://commons.apache.org/proper/commons-vfs2).
+The
[Javadoc](https://commons.apache.org/proper/commons-vfs2/javadocs/api-release)
can be browsed.
+Questions related to the usage of Apache Commons VFS Project should be posted
to the [user mailing list][ml].
Where can I get the latest release?
-----------------------------------
@@ -65,7 +67,7 @@ Alternatively you can pull it from the c
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-vfs2</artifactId>
- <version>2.2</version>
+ <version>2.3</version>
</dependency>
```
@@ -90,7 +92,7 @@ See the `NOTICE.txt` file for required n
Donations
---------
-You like Apache Commons VFS? Then [donate back to the
ASF](https://www.apache.org/foundation/contributing.html) to support the
development.
+You like Apache Commons VFS Project? Then [donate back to the
ASF](https://www.apache.org/foundation/contributing.html) to support the
development.
Additional Resources
--------------------
Modified: commons/proper/vfs/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/commons/proper/vfs/trunk/pom.xml?rev=1852193&r1=1852192&r2=1852193&view=diff
==============================================================================
--- commons/proper/vfs/trunk/pom.xml (original)
+++ commons/proper/vfs/trunk/pom.xml Sat Jan 26 00:21:31 2019
@@ -154,10 +154,15 @@
<commons.jira.pid>12310495</commons.jira.pid>
<commons.scmPubUrl>https://svn.apache.org/repos/infra/websites/production/commons/content/proper/commons-vfs</commons.scmPubUrl>
- <commons.release.version>2.2</commons.release.version>
- <!--<commons.rc.version>RC1</commons.rc.version> -->
+ <commons.release.version>2.3</commons.release.version>
+ <!-- Commons Release Plugin -->
+ <commons.bc.version>2.2</commons.bc.version>
+ <commons.release.isDistModule>true</commons.release.isDistModule>
+ <commons.releaseManagerName>Gary Gregory</commons.releaseManagerName>
+ <commons.releaseManagerKey>86fdc7e2a11262cb</commons.releaseManagerKey>
+ <commons.rc.version>RC1</commons.rc.version>
<commons.release.name>commons-vfs-${commons.release.version}</commons.release.name>
- <commons.release.desc>(requires Java 1.7+)</commons.release.desc>
+ <commons.release.desc>(requires Java 8)</commons.release.desc>
<commons.binary.suffix /> <!-- TODO delete? -->
<!--
Modified: commons/proper/vfs/trunk/src/site/xdoc/download_vfs2.xml
URL:
http://svn.apache.org/viewvc/commons/proper/vfs/trunk/src/site/xdoc/download_vfs2.xml?rev=1852193&r1=1852192&r2=1852193&view=diff
==============================================================================
--- commons/proper/vfs/trunk/src/site/xdoc/download_vfs2.xml (original)
+++ commons/proper/vfs/trunk/src/site/xdoc/download_vfs2.xml Sat Jan 26
00:21:31 2019
@@ -26,22 +26,24 @@ limitations under the License.
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:download-page |
+ | 1) Re-generate using: mvn commons-build:download-page |
| |
| 2) Set the following properties in the component's pom: |
- | - commons.componentid (required, alphabetic, lower case) |
+ | - commons.componentid (required, alphabetic, lower case) |
| - commons.release.version (required) |
| - commons.release.name (required) |
| - commons.binary.suffix (optional) |
| (defaults to "-bin", set to "" for pre-maven2 releases) |
| - commons.release.desc (optional) |
| - commons.release.subdir (optional) |
+ | - commons.release.hash (optional, lowercase, default sha256) |
| |
- | - commons.release.2/3.version (conditional) |
- | - commons.release.2/3.name (conditional) |
- | - commons.release.2/3.binary.suffix (optional) |
- | - commons.release.2/3.desc (optional) |
- | - commons.release.2/3.subdir (optional) |
+ | - commons.release.[234].version (conditional) |
+ | - commons.release.[234].name (conditional) |
+ | - commons.release.[234].binary.suffix (optional) |
+ | - commons.release.[234].desc (optional) |
+ | - commons.release.[234].subdir (optional) |
+ | - commons.release.[234].hash (optional, lowercase, [sha256])|
| |
| 3) Example Properties |
| (commons.release.name inherited by parent: |
@@ -102,7 +104,7 @@ limitations under the License.
It is essential that you
<a href="https://www.apache.org/info/verification.html">verify the
integrity</a>
of downloaded files, preferably using the <code>PGP</code> signature
(<code>*.asc</code> files);
- failing that using the <code>MD5</code> hash (<code>*.md5</code>
checksum files).
+ failing that using the <code>SHA256</code> hash (<code>*.sha256</code>
checksum files).
</p>
<p>
The <a href="https://www.apache.org/dist/commons/KEYS">KEYS</a>
@@ -111,32 +113,32 @@ limitations under the License.
</p>
</subsection>
</section>
- <section name="Apache Commons VFS Project 2.2 (requires Java 1.7+)">
+ <section name="Apache Commons VFS Project 2.3 (requires Java 8)">
<subsection name="Binaries">
<table>
<tr>
- <td><a
href="[preferred]/commons/vfs2/binaries/commons-vfs-2.2.tar.gz">commons-vfs-2.2.tar.gz</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.2.tar.gz.md5">md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.2.tar.gz.asc">pgp</a></td>
+ <td><a
href="[preferred]/commons/vfs2/binaries/commons-vfs-2.3.tar.gz">commons-vfs-2.3.tar.gz</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.3.tar.gz.sha256">sha256</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.3.tar.gz.asc">pgp</a></td>
</tr>
<tr>
- <td><a
href="[preferred]/commons/vfs2/binaries/commons-vfs-2.2.zip">commons-vfs-2.2.zip</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.2.zip.md5">md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.2.zip.asc">pgp</a></td>
+ <td><a
href="[preferred]/commons/vfs2/binaries/commons-vfs-2.3.zip">commons-vfs-2.3.zip</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.3.zip.sha256">sha256</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/binaries/commons-vfs-2.3.zip.asc">pgp</a></td>
</tr>
</table>
</subsection>
<subsection name="Source">
<table>
<tr>
- <td><a
href="[preferred]/commons/vfs2/source/commons-vfs-2.2-src.tar.gz">commons-vfs-2.2-src.tar.gz</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.2-src.tar.gz.md5">md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.2-src.tar.gz.asc">pgp</a></td>
+ <td><a
href="[preferred]/commons/vfs2/source/commons-vfs-2.3-src.tar.gz">commons-vfs-2.3-src.tar.gz</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.3-src.tar.gz.sha256">sha256</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.3-src.tar.gz.asc">pgp</a></td>
</tr>
<tr>
- <td><a
href="[preferred]/commons/vfs2/source/commons-vfs-2.2-src.zip">commons-vfs-2.2-src.zip</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.2-src.zip.md5">md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.2-src.zip.asc">pgp</a></td>
+ <td><a
href="[preferred]/commons/vfs2/source/commons-vfs-2.3-src.zip">commons-vfs-2.3-src.zip</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.3-src.zip.sha256">sha256</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/vfs2/source/commons-vfs-2.3-src.zip.asc">pgp</a></td>
</tr>
</table>
</subsection>
Modified: commons/proper/vfs/trunk/src/site/xdoc/issue-tracking.xml
URL:
http://svn.apache.org/viewvc/commons/proper/vfs/trunk/src/site/xdoc/issue-tracking.xml?rev=1852193&r1=1852192&r2=1852193&view=diff
==============================================================================
--- commons/proper/vfs/trunk/src/site/xdoc/issue-tracking.xml (original)
+++ commons/proper/vfs/trunk/src/site/xdoc/issue-tracking.xml Sat Jan 26
00:21:31 2019
@@ -26,7 +26,7 @@ limitations under the License.
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:jira-page |
+ | 1) Re-generate using: mvn commons-build:jira-page |
| |
| 2) Set the following properties in the component's pom: |
| - commons.jira.id (required, alphabetic, upper case) |
@@ -43,35 +43,35 @@ limitations under the License.
-->
<document>
<properties>
- <title>Apache Commons VFS Issue tracking</title>
- <author email="[email protected]">Commons Documentation Team</author>
+ <title>Apache Commons VFS Project Issue tracking</title>
+ <author email="[email protected]">Apache Commons Documentation
Team</author>
</properties>
<body>
- <section name="Apache Commons VFS Issue tracking">
+ <section name="Apache Commons VFS Project Issue tracking">
<p>
- Apache Commons VFS uses <a href="http://issues.apache.org/jira/">ASF
JIRA</a> for tracking issues.
- See the <a href="http://issues.apache.org/jira/browse/VFS">Apache
Commons VFS JIRA project page</a>.
+ Apache Commons VFS Project uses <a
href="https://issues.apache.org/jira/">ASF JIRA</a> for tracking issues.
+ See the <a href="https://issues.apache.org/jira/browse/VFS">Apache
Commons VFS Project JIRA project page</a>.
</p>
<p>
- To use JIRA you may need to <a
href="http://issues.apache.org/jira/secure/Signup!default.jspa">create an
account</a>
+ To use JIRA you may need to <a
href="https://issues.apache.org/jira/secure/Signup!default.jspa">create an
account</a>
(if you have previously created/updated Commons issues using Bugzilla an
account will have been automatically
- created and you can use the <a
href="http://issues.apache.org/jira/secure/ForgotPassword!default.jspa">Forgot
Password</a>
+ created and you can use the <a
href="https://issues.apache.org/jira/secure/ForgotPassword!default.jspa">Forgot
Password</a>
page to get a new password).
</p>
<p>
If you would like to report a bug, or raise an enhancement request with
- Apache Commons VFS please do the following:
+ Apache Commons VFS Project please do the following:
<ol>
- <li><a
href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC&status=1&status=3&status=4">Search
existing open bugs</a>.
+ <li><a
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC&status=1&status=3&status=4">Search
existing open bugs</a>.
If you find your issue listed then please add a comment with your
details.</li>
<li><a href="mail-lists.html">Search the mailing list archive(s)</a>.
You may find your issue or idea has already been discussed.</li>
<li>Decide if your issue is a bug or an enhancement.</li>
- <li>Submit either a <a
href="http://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?pid=12310495&issuetype=1&priority=4&assignee=-1">bug
report</a>
- or <a
href="http://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?pid=12310495&issuetype=4&priority=4&assignee=-1">enhancement
request</a>.</li>
+ <li>Submit either a <a
href="https://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?pid=12310495&issuetype=1&priority=4&assignee=-1">bug
report</a>
+ or <a
href="https://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?pid=12310495&issuetype=4&priority=4&assignee=-1">enhancement
request</a>.</li>
</ol>
</p>
@@ -80,7 +80,7 @@ limitations under the License.
<ul>
<li>the more information you provide, the better we can help you</li>
<li>test cases are vital, particularly for any proposed
enhancements</li>
- <li>the developers of Apache Commons VFS are all unpaid volunteers</li>
+ <li>the developers of Apache Commons VFS Project are all unpaid
volunteers</li>
</ul>
</p>
@@ -92,9 +92,9 @@ limitations under the License.
<p>
You may also find these links useful:
<ul>
- <li><a
href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC&status=1&status=3&status=4">All
Open Apache Commons VFS bugs</a></li>
- <li><a
href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC&status=5&status=6">All
Resolved Apache Commons VFS bugs</a></li>
- <li><a
href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC">All
Apache Commons VFS bugs</a></li>
+ <li><a
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC&status=1&status=3&status=4">All
Open Apache Commons VFS Project bugs</a></li>
+ <li><a
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC&status=5&status=6">All
Resolved Apache Commons VFS Project bugs</a></li>
+ <li><a
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310495&sorter/field=issuekey&sorter/order=DESC">All
Apache Commons VFS Project bugs</a></li>
</ul>
</p>
</section>
Modified: commons/proper/vfs/trunk/src/site/xdoc/mail-lists.xml
URL:
http://svn.apache.org/viewvc/commons/proper/vfs/trunk/src/site/xdoc/mail-lists.xml?rev=1852193&r1=1852192&r2=1852193&view=diff
==============================================================================
--- commons/proper/vfs/trunk/src/site/xdoc/mail-lists.xml (original)
+++ commons/proper/vfs/trunk/src/site/xdoc/mail-lists.xml Sat Jan 26 00:21:31
2019
@@ -26,7 +26,7 @@ limitations under the License.
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:mail-page |
+ | 1) Re-generate using: mvn commons-build:mail-page |
| |
| 2) Set the following properties in the component's pom: |
| - commons.componentid (required, alphabetic, lower case) |
@@ -41,28 +41,28 @@ limitations under the License.
-->
<document>
<properties>
- <title>Apache Commons VFS Mailing Lists</title>
+ <title>Apache Commons VFS Project Mailing Lists</title>
<author email="[email protected]">Apache Commons Documentation
Team</author>
</properties>
<body>
<section name="Overview">
<p>
- <a href="index.html">Apache Commons VFS</a> shares mailing lists with
all the other
+ <a href="index.html">Apache Commons VFS Project</a> shares mailing
lists with all the other
<a href="http://commons.apache.org/components.html">Commons
Components</a>.
To make it easier for people to only read messages related to
components they are interested in,
the convention in Commons is to prefix the subject line of messages
with the component's name,
for example:
<ul>
- <li>[vfs] Problem with the ...</li>
+ <li>[vfs2] Problem with the ...</li>
</ul>
</p>
<p>
- Questions related to the usage of Apache Commons VFS should be posted
to the
+ Questions related to the usage of Apache Commons VFS Project should be
posted to the
<a href="http://mail-archives.apache.org/mod_mbox/commons-user/">User
List</a>.
<br />
The <a
href="http://mail-archives.apache.org/mod_mbox/commons-dev/">Developer List</a>
- is for questions and discussion related to the development of Apache
Commons VFS.
+ is for questions and discussion related to the development of Apache
Commons VFS Project.
<br />
Please do not cross-post; developers are also subscribed to the user
list.
<br />
@@ -76,10 +76,10 @@ limitations under the License.
</p>
</section>
- <section name="Apache Commons VFS Mailing Lists">
+ <section name="Apache Commons VFS Project Mailing Lists">
<p>
- <strong>Please prefix the subject line of any messages for <a
href="index.html">Apache Commons VFS</a>
- with <i>[vfs]</i></strong> - <i>thanks!</i>
+ <strong>Please prefix the subject line of any messages for <a
href="index.html">Apache Commons VFS Project</a>
+ with <i>[vfs2]</i></strong> - <i>thanks!</i>
<br />
<br />
</p>
@@ -99,12 +99,12 @@ limitations under the License.
<td>
<strong>Commons User List</strong>
<br /><br />
- Questions on using Apache Commons VFS.
+ Questions on using Apache Commons VFS Project.
<br /><br />
</td>
<td><a
href="mailto:[email protected]">Subscribe</a></td>
<td><a
href="mailto:[email protected]">Unsubscribe</a></td>
- <td><a
href="mailto:[email protected]?subject=[vfs]">Post</a></td>
+ <td><a
href="mailto:[email protected]?subject=[vfs2]">Post</a></td>
<td><a
href="http://mail-archives.apache.org/mod_mbox/commons-user/">mail-archives.apache.org</a></td>
<td><a
href="http://markmail.org/list/org.apache.commons.users/">markmail.org</a><br />
<a
href="http://www.mail-archive.com/[email protected]/">www.mail-archive.com</a><br
/>
@@ -117,12 +117,12 @@ limitations under the License.
<td>
<strong>Commons Developer List</strong>
<br /><br />
- Discussion of development of Apache Commons VFS.
+ Discussion of development of Apache Commons VFS Project.
<br /><br />
</td>
<td><a
href="mailto:[email protected]">Subscribe</a></td>
<td><a
href="mailto:[email protected]">Unsubscribe</a></td>
- <td><a
href="mailto:[email protected]?subject=[vfs]">Post</a></td>
+ <td><a
href="mailto:[email protected]?subject=[vfs2]">Post</a></td>
<td><a
href="http://mail-archives.apache.org/mod_mbox/commons-dev/">mail-archives.apache.org</a></td>
<td><a
href="http://markmail.org/list/org.apache.commons.dev/">markmail.org</a><br />
<a
href="http://www.mail-archive.com/[email protected]/">www.mail-archive.com</a><br
/>