From 34c5613659fb37341ba1efc14b53e7ba4f4c1e65 Mon Sep 17 00:00:00 2001 From: Gary Gregory Date: Sat, 2 Dec 2023 10:10:42 -0500 Subject: [PATCH] Prepare release candidate --- CONTRIBUTING.md | 230 +++++++++++++-------------- NOTICE.txt | 2 +- README.md | 223 ++++++++++++++------------ RELEASE-NOTES.txt | 71 ++++++++- pom.xml | 9 +- src/changes/changes.xml | 2 +- src/changes/release-notes.vm | 8 +- src/site/xdoc/download_validator.xml | 28 ++-- src/site/xdoc/issue-tracking.xml | 2 +- src/site/xdoc/mail-lists.xml | 50 +++--- 10 files changed, 358 insertions(+), 267 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c52ef41fb..5d2f36006 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,115 +1,115 @@ - - -Contributing to Apache Commons Validator -====================== - -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 Validator'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` branch. - * A good topic branch name can be the JIRA bug id plus a keyword, e.g. `VALIDATOR-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. `VALIDATOR-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 Validator 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/VALIDATOR + + +Contributing to Apache Commons Validator +====================== + +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 Validator'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` branch. + * A good topic branch name can be the JIRA bug id plus a keyword, e.g. `VALIDATOR-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. `VALIDATOR-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 Validator 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/VALIDATOR diff --git a/NOTICE.txt b/NOTICE.txt index 78a1f9813..917dd18f8 100644 --- a/NOTICE.txt +++ b/NOTICE.txt @@ -1,5 +1,5 @@ Apache Commons Validator -Copyright 2001-2023 The Apache Software Foundation +Copyright 2002-2023 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (https://www.apache.org/). diff --git a/README.md b/README.md index 0b64e05c7..06a1b173f 100644 --- a/README.md +++ b/README.md @@ -1,107 +1,120 @@ - - -Apache Commons Validator -=================== - + + +Apache Commons Validator +=================== + [![Java CI](https://github.com/apache/commons-validator/actions/workflows/maven.yml/badge.svg)](https://github.com/apache/commons-validator/actions/workflows/maven.yml) -[![Coverage Status](https://codecov.io/gh/apache/commons-validator/branch/master/graph/badge.svg)](https://app.codecov.io/gh/apache/commons-validator) -[![Maven Central](https://maven-badges.herokuapp.com/maven-central/commons-validator/commons-validator/badge.svg?gav=true)](https://maven-badges.herokuapp.com/maven-central/commons-validator/commons-validator/?gav=true) -[![Javadocs](https://javadoc.io/badge/commons-validator/commons-validator/1.7.svg)](https://javadoc.io/doc/commons-validator/commons-validator/1.7) +[![Coverage Status](https://codecov.io/gh/apache/commons-validator/branch/master/graph/badge.svg)](https://app.codecov.io/gh/apache/commons-validator) +[![Maven Central](https://maven-badges.herokuapp.com/maven-central/commons-validator/commons-validator/badge.svg?gav=true)](https://maven-badges.herokuapp.com/maven-central/commons-validator/commons-validator/?gav=true) +[![Javadocs](https://javadoc.io/badge/commons-validator/commons-validator/1.8.0.svg)](https://javadoc.io/doc/commons-validator/commons-validator/1.8.0) [![CodeQL](https://github.com/apache/commons-validator/actions/workflows/codeql-analysis.yml/badge.svg)](https://github.com/apache/commons-validator/actions/workflows/codeql-analysis.yml) - -Apache Commons Validator provides the building blocks for both client side validation and server side data validation. - It may be used standalone or with a framework like Struts. - -Documentation -------------- - -More information can be found on the [Apache Commons Validator homepage](https://commons.apache.org/proper/commons-validator). -The [Javadoc](https://commons.apache.org/proper/commons-validator/apidocs) can be browsed. -Questions related to the usage of Apache Commons Validator should be posted to the [user mailing list][ml]. - -Where can I get the latest release? ------------------------------------ -You can download source and binaries from our [download page](https://commons.apache.org/proper/commons-validator/download_validator.cgi). - -Alternatively, you can pull it from the central Maven repositories: - -```xml - - commons-validator - commons-validator - 1.7 - -``` - -Contributing ------------- - -We accept Pull Requests via GitHub. The [developer mailing list][ml] is the main channel of communication for contributors. -There are some guidelines which will make applying PRs easier for us: -+ No tabs! Please use spaces for indentation. -+ Respect the code style. -+ 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. -+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```. - -If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas). -You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md). - -License -------- -This code is under the [Apache License v2](https://www.apache.org/licenses/LICENSE-2.0). - -See the `NOTICE.txt` file for required notices and attributions. - -Donations ---------- -You like Apache Commons Validator? Then [donate back to the ASF](https://www.apache.org/foundation/contributing.html) to support the development. - -Additional Resources --------------------- - -+ [Apache Commons Homepage](https://commons.apache.org/) -+ [Apache Issue Tracker (JIRA)](https://issues.apache.org/jira/browse/VALIDATOR) -+ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons) -+ `#apache-commons` IRC channel on `irc.freenode.org` - -[ml]:https://commons.apache.org/mail-lists.html +[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/apache/commons-validator/badge)](https://api.securityscorecards.dev/projects/github.com/apache/commons-validator) + +Apache Commons Validator provides the building blocks for both client side validation and server side data validation. + It may be used standalone or with a framework like Struts. + +Documentation +------------- + +More information can be found on the [Apache Commons Validator homepage](https://commons.apache.org/proper/commons-validator). +The [Javadoc](https://commons.apache.org/proper/commons-validator/apidocs) can be browsed. +Questions related to the usage of Apache Commons Validator should be posted to the [user mailing list][ml]. + +Getting the latest release +-------------------------- +You can download source and binaries from our [download page](https://commons.apache.org/proper/commons-validator/download_validator.cgi). + +Alternatively, you can pull it from the central Maven repositories: + +```xml + + commons-validator + commons-validator + 1.8.0 + +``` + +Building +-------- + +Building requires a Java JDK and [Apache Maven](https://maven.apache.org/). +The required Java version is found in the `pom.xml` as the `maven.compiler.source` property. + +From a command shell, run `mvn` without arguments to invoke the default Maven goal to run all tests and checks. + +Contributing +------------ + +We accept Pull Requests via GitHub. The [developer mailing list](https://commons.apache.org/mail-lists.html) is the main channel of communication for contributors. +There are some guidelines which will make applying PRs easier for us: ++ No tabs! Please use spaces for indentation. ++ Respect the existing code style for each file. ++ 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. ++ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```. + +If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas). +You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md). + +License +------- +This code is licensed under the [Apache License v2](https://www.apache.org/licenses/LICENSE-2.0). + +See the `NOTICE.txt` file for required notices and attributions. + +Donating +-------- +You like Apache Commons Validator? Then [donate back to the ASF](https://www.apache.org/foundation/contributing.html) to support development. + +Additional Resources +-------------------- + ++ [Apache Commons Homepage](https://commons.apache.org/) ++ [Apache Issue Tracker (JIRA)](https://issues.apache.org/jira/browse/VALIDATOR) ++ [Apache Commons Slack Channel](https://the-asf.slack.com/archives/C60NVB8AD) ++ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons) ++ `#apache-commons` IRC channel on `irc.freenode.org` + +Apache Commons Components +------------------------- + +Please see the [list of components](https://commons.apache.org/components.html) diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt index 395eeb12b..1ae27eda7 100644 --- a/RELEASE-NOTES.txt +++ b/RELEASE-NOTES.txt @@ -1,5 +1,72 @@ - Apache Commons Validator 1.7 - RELEASE NOTES +Apache Commons Validator 1.8.0 +RELEASE NOTES + +The Apache Commons Validator team is pleased to announce the release of Apache Commons Validator 1.8.0. + +Apache Commons Validator provides the building blocks for both client side validation and server side data validation. +It may be used standalone or with a framework like Struts. + +For complete information on Apache Commons Validator, including instructions on how to submit bug reports, +patches, or suggestions for improvement, see the Apache Commons Validator website: + +http://commons.apache.org/proper/commons-validator/ + +Download page: http://commons.apache.org/proper/commons-validator/download_validator.cgi + +Changes in this version include: +=============================== + +New features: +o Add github/codeql-action. Thanks to Dependabot, Gary Gregory. +o VALIDATOR-486: Add new countries to IBAN list: DJ, RU #88. Thanks to tatiana-scda, Gary Gregory. +o Add IBANValidator.Validator.getRegexValidator(). Thanks to Arnaud Fournier, Gary Gregory. +o Add RegexValidator.getPatterns(). Thanks to Arnaud Fournier, Gary Gregory. +o Add country codes listed as other countries and territories in the IBAN registry for Finland: AX. Thanks to Gary Gregory, rossmills3, sebbASF. +o Add country codes listed as other countries and territories in the IBAN registry for France: GF, GP, MQ, RE, PF, TF, YT, NC, BL, MF, PM, WF. Thanks to Gary Gregory, rossmills3, sebbASF. +o Add country codes listed as other countries and territories in the IBAN registry for United Kingdom: IM, JE, GG. Thanks to Gary Gregory, rossmills3, sebbASF. +o Add ValidatorAction.setClassName(String) and deprecate setClassname(String). Thanks to Gary Gregory. + +Fixed Bugs: +o Update Javadoc for InetAddressValidator isValid #76 Thanks to Gennaro Napolitano. +o VALIDATOR-479: Fix typo in /routines/package-summary.html #79. Thanks to Gyoo. +o Use JUnit 5 assertThrows() #92, #93, #94, #95. Thanks to John Patrick. +o [StepSecurity] ci: Harden GitHub Actions #136. Thanks to step-security-bot, Gary Gregory. +o Javadoc typos #144. Thanks to Andrés Torres. +o Precompile regular expression in InetAddressValidator.isValidInet6Address(String). Thanks to Gary Gregory. +o Fix SpotBugs [ERROR] Medium: Class org.apache.commons.validator.routines.CreditCardValidator$1 defines non-transient non-serializable instance field ccr [org.apache.commons.validator.routines.CreditCardValidator$1] In CreditCardValidator.java SE_BAD_FIELD. Thanks to Gary Gregory. +o Fix SpotBugs [ERROR] High: Class org.apache.commons.validator.ValidatorAction defines non-transient non-serializable instance field validationMethod [org.apache.commons.validator.ValidatorAction] In ValidatorAction.java SE_BAD_FIELD. Thanks to Gary Gregory. +o Fix SpotBugs [ERROR] High: Found reliance on default encoding in org.apache.commons.validator.ValidatorAction.readJavascriptFile(String): new java.io.InputStreamReader(InputStream) [org.apache.commons.validator.ValidatorAction] At ValidatorAction.java:[line 428] DM_DEFAULT_ENCODING. Thanks to Gary Gregory. +o Fix SpotBugs [ERROR] Medium: Inconsistent synchronization of org.apache.commons.validator.ValidatorAction.jsFunction; locked 62% of time [org.apache.commons.validator.ValidatorAction, org.apache.commons.validator.ValidatorAction, org.apache.commons.validator.ValidatorAction, org.apache.commons.validator.ValidatorAction, org.apache.commons.validator.ValidatorAction, org.apache.commons.validator.ValidatorAction, org.apache.commons.validator.ValidatorAction] Unsynchronized access at ValidatorAction.java:[line 340]Unsynchronized access at ValidatorAction.java:[line 358]Synchronized access at ValidatorAction.java:[line 393]Synchronized access at ValidatorAction.java:[line 394]Synchronized access at ValidatorAction.java:[line 459]Synchronized access at ValidatorAction.java:[line 461]Synchronized access at ValidatorAction.java:[line 462] IS2_INCONSISTENT_SYNC. Thanks to Gary Gregory. +o Port tests to JUnit 5. Exception: DomainValidatorStartupTest. Thanks to Gary Gregory. +o Use singletons in org.apache.commons.validator.CreditCardValidator. Thanks to Gary Gregory. + +Changes: +o Bump Java from 7 to 8. Thanks to Gary Gregory. +o Bump actions/cache from 2 to 3.0.11 #71, #84. #90, #91. Thanks to Dependabot, Gary Gregory. +o Bump actions/checkout from 2.3.1 to 3.0.2, #38, #47, #70. Thanks to Dependabot, Gary Gregory. +o Bump actions/setup-java from 1.4.0 to 3.6.0 #42, #72, #98. Thanks to Dependabot, Gary Gregory. +o Bump actions/upload-artifact from 3.1.0 to 3.1.1 #96. Thanks to Dependabot. +o Bump junit from 4.13 to 5.9.1 Vintage #44. Thanks to Dependabot, Gary Gregory. +o Bump maven-pmd-plugin from 3.13.0 to 3.19.0 #69, #77, #80, #81. Thanks to Dependabot. +o Bump commons-parent from 52 to 65 #83, #107, #111, #132. Thanks to Gary Gregory, Dependabot. +o Bump japicmp-maven-plugin from 0.15.3 to 0.15.7. Thanks to Gary Gregory. +o Bump maven-antrun-plugin from 3.0.0 to 3.1.0 #74. Thanks to Dependabot. +o Bump commons-csv from 1.6 to 1.10.0 #118. Thanks to Gary Gregory, Dependabot. +o Bump japicmp-maven-plugin from 0.15.7 to 0.16.0. Thanks to Gary Gregory. +o Bump commons-logging:commons-logging from 1.2 to 1.3.0. Thanks to Gary Gregory. + +Removed: +o Remove FindBugs, SpotBugs is in use #87. Thanks to John Patrick, Gary Gregory. + +Historical list of changes: http://commons.apache.org/proper/commons-validator/changes-report.html + +Enjoy! +-Apache Commons Validator team + +============================================================================= + +Apache Commons Validator 1.7 +RELEASE NOTES The Apache Commons Validator team is pleased to announce the release of Apache Commons Validator 1.7 diff --git a/pom.xml b/pom.xml index f2eabc16a..918acde3a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ commons-validator commons-validator - 1.8-SNAPSHOT + 1.8.0-SNAPSHOT Apache Commons Validator Apache Commons Validator provides the building blocks for both client side validation and server side data validation. @@ -40,10 +40,11 @@ validator org.apache.commons.validator - 1.7 - RC2 + 1.8.0 + 1.8.1 + RC1 (requires JDK ${maven.compiler.target}) - 1.6 + 1.7 VALIDATOR 12310494 UTF-8 diff --git a/src/changes/changes.xml b/src/changes/changes.xml index c506452be..3305f3dce 100644 --- a/src/changes/changes.xml +++ b/src/changes/changes.xml @@ -64,7 +64,7 @@ The type attribute can be add,update,fix,remove. --> - + Update Javadoc for InetAddressValidator isValid #76 diff --git a/src/changes/release-notes.vm b/src/changes/release-notes.vm index ab20c18e4..80f898d6f 100644 --- a/src/changes/release-notes.vm +++ b/src/changes/release-notes.vm @@ -15,10 +15,10 @@ ## specific language governing permissions and limitations ## under the License. ## - ${project.name} ${version} - RELEASE NOTES +${project.name} ${version} +RELEASE NOTES -The ${developmentTeam} is pleased to announce the release of ${project.name} ${version} +The ${developmentTeam} is pleased to announce the release of ${project.name} ${version}. $introduction.replaceAll("(?SHA512 hash (*.sha512 checksum files).

- The KEYS + The KEYS file contains the public PGP keys used by Apache Commons developers to sign releases.

-
+
- - - + + + - - - + + +
commons-validator-1.7-bin.tar.gzsha512pgpcommons-validator-1.8.0-bin.tar.gzsha512pgp
commons-validator-1.7-bin.zipsha512pgpcommons-validator-1.8.0-bin.zipsha512pgp
- - - + + + - - - + + +
commons-validator-1.7-src.tar.gzsha512pgpcommons-validator-1.8.0-src.tar.gzsha512pgp
commons-validator-1.7-src.zipsha512pgpcommons-validator-1.8.0-src.zipsha512pgp
diff --git a/src/site/xdoc/issue-tracking.xml b/src/site/xdoc/issue-tracking.xml index 454f027dc..a8636b52e 100644 --- a/src/site/xdoc/issue-tracking.xml +++ b/src/site/xdoc/issue-tracking.xml @@ -85,7 +85,7 @@ limitations under the License.

- For more information on subversion and creating patches see the + For more information on creating patches see the Apache Contributors Guide.

diff --git a/src/site/xdoc/mail-lists.xml b/src/site/xdoc/mail-lists.xml index 0654e3c0b..1466d3bc0 100644 --- a/src/site/xdoc/mail-lists.xml +++ b/src/site/xdoc/mail-lists.xml @@ -59,9 +59,9 @@ limitations under the License.

Questions related to the usage of Apache Commons Validator should be posted to the - User List. + User List.
- The Developer List + The Developer List is for questions and discussion related to the development of Apache Commons Validator.
Please do not cross-post; developers are also subscribed to the user list. @@ -70,8 +70,10 @@ limitations under the License. to subscribe.

- Note: please don't send patches or attachments to any of the mailing lists. + Note: please don't send patches or attachments to any of the mailing lists; + most of the lists are set up to drop attachments. Patches are best handled via the Issue Tracking system. + If you have a GitHub account, most components also accept PRs (pull requests). Otherwise, please upload the file to a public server and include the URL in the mail.

@@ -105,10 +107,11 @@ limitations under the License. Subscribe Unsubscribe Post - mail-archives.apache.org - markmail.org
- www.mail-archive.com
- news.gmane.org + + lists.apache.org + + + www.mail-archive.com @@ -123,10 +126,11 @@ limitations under the License. Subscribe Unsubscribe Post - mail-archives.apache.org - markmail.org
- www.mail-archive.com
- news.gmane.org + + lists.apache.org + + + www.mail-archive.com @@ -141,8 +145,10 @@ limitations under the License. Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
+ + lists.apache.org + + www.mail-archive.com @@ -152,14 +158,16 @@ limitations under the License. Commons Commits List

- Only for e-mails automatically generated by the source control sytem. + Only for e-mails automatically generated by the source control system.

Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
+ + lists.apache.org + + www.mail-archive.com @@ -191,11 +199,11 @@ limitations under the License. Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
- old.nabble.com
- www.mail-archive.com
- news.gmane.org + + lists.apache.org + + + www.mail-archive.com