Import Upstream version 43

This commit is contained in:
zhouganqing 2022-11-18 09:39:11 +08:00
commit 8b2fd29a7a
13 changed files with 3218 additions and 0 deletions

105
BUILDING.txt Normal file
View File

@ -0,0 +1,105 @@
Notes on building/releasing Commons Parent
==========================================
These recipes should work.
Other recipes may suit other tastes!
This is the short form of "Releasing Commons Components"
http://commons.apache.org/releases/index.html
To perform the license release audit, a.k.a. "RAT check", run.
mvn apache-rat:check
Building for local repo:
-----------------------
mvn -N install
Snapshot deployment:
-------------------
mvn deploy
Preparing for release candidate:
-------------------------------
- Check for updates to plugins and dependencies.
- Ensure NOTICE has correct year.
- Ensure changes.xml is up to date; generate RELEASE-NOTES using non-SNAPSHOT version:
mvn changes:announcement-generate -Prelease-notes -Dchanges.version=nn
- Ensure pom.xml header comment agrees with changes for this release
- Regenerate CONTRIBUTING.md:
mvn commons:contributing-md
- Regenerate README.md:
mvn commons:readme-md
- Commit all changes to SVN
Creating release candidate tag:
------------------------------
- Checkout trunk in clean workspace:
svn co https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk commons-parent-<NN>-RC1
- cd commons-parent-<NN>-RC1
- Edit version in pom.xml to remove SNAPSHOT suffix
- Edit three SCM URLs to point to the future (non-RC) tag:
<connection>scm:svn:http://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-<NN></connection>
<developerConnection>scm:svn:https://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-<NN></developerConnection>
<url>http://svn.apache.org/viewvc/commons/proper/commons-parent/tags/commons-parent-<NN></url>
- Create tag in SVN from the updated workspace:
svn cp . https://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-<NN>-RC1 -m"Create <NN> RC1 tag"
(this ensures the trunk never sees the different URLs or released version)
Test build of tag:
-----------------
- mvn deploy -Duser.name=ASF-login-name -Prelease -Ptest-deploy
- Check the contents of target/deploy/org/apache/commons/commons-parent/<NN>
- should contain commons-parent-<NN>.pom, commons-parent-<NN>-site.xml and sigs/hashes
- also -src.tar.gz, -src.zip and sigs/hashes
Deploy RC to Nexus:
------------------
- Set up passwords in settings.xml (https://wiki.apache.org/commons/UsingNexus)
- Same command as above, but omitting -Ptest-deploy profile:
- mvn package deploy -Dassembly.attach=false -Duser.name=ASF-login-name -Prelease
Tidy and close Nexus staging area:
---------------------------------
- Login to Nexus: https://repository.apache.org/index.html
- Open "Staging Repositories", find the correct "Open" entry (check Summary tab in bottom panel)
- The message "No CLM data recorded" appears to be benign
- Open the bottom "Content" tab and navigate to the files
- Delete *.asc.md5 and *.asc.sha1 if present
- Checkout https://dist.apache.org/repos/dist/dev/commons/commons-parent
- Download the -src archives, their sigs and hashes, then delete them from Nexus.
- Commit the dist/dev/ folder
Close the staging area - Description: "Apache Commons Parent <NN> RC1"
Screen does not auto-refresh - you need to press refresh
Send round the release vote(lazy)
--------------------------------
Promote the Nexus staging area
------------------------------
Assuming the vote passes, login to Nexus and use the "Release" function
[If there was a problem identified, Drop the repo instead and start again]
Copy the RC Tag to final tag:
URL=https://svn.apache.org/repos/asf/commons/proper/commons-parent/
svn cp "$URL/tags/commons-parent-37-RC1" "$URL/tags/commons-parent-37" -m "Release commons-parent 37 based on RC1"
Publish the source files to
https://dist.apache.org/repos/dist/release/commons/commons-parent
Update site documentation
-------------------------
Please check that the site documentation is up to date
See:
https://svn.apache.org/repos/asf/commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml
This will need updating if any new features / profiles etc are added.
It does not list plugin or dependency versions.
However at the least please update the version details and URL at the start of the page.
Prepare next Release Cycle
--------------------------
Modify pom.xml with next SNAPSHOT version, remove second last history comment
Add next release tag in src/changes/changes.xml and commit changes to trunk

115
CONTRIBUTING.md Normal file
View File

@ -0,0 +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 Parent
======================
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](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 Parent'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. `COMMONSSITE-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. `COMMONSSITE-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 Parent JIRA project page][jira]
+ [Contributor License Agreement][cla]
+ [General GitHub documentation](https://help.github.com/)
+ [GitHub pull request documentation](https://help.github.com/send-pull-requests/)
+ [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/COMMONSSITE

202
LICENSE.txt Normal file
View File

@ -0,0 +1,202 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed 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.

5
NOTICE.txt Normal file
View File

@ -0,0 +1,5 @@
Apache Commons Parent
Copyright 2006-2018 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).

105
README.md Normal file
View File

@ -0,0 +1,105 @@
<!---
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: readme-md-template.md |
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
| 1) Re-generate using: mvn commons:readme-md |
| |
| 2) Set the following properties in the component's pom: |
| - commons.componentid (required, alphabetic, lower case) |
| - commons.release.version (required) |
| |
| 3) Example Properties |
| |
| <properties> |
| <commons.componentid>math</commons.componentid> |
| <commons.release.version>1.2</commons.release.version> |
| </properties> |
| |
+======================================================================+
--->
Apache Commons Parent
===================
[![Build Status](https://travis-ci.org/apache/commons-parent.svg?branch=master)](https://travis-ci.org/apache/commons-parent)
[![Coverage Status](https://coveralls.io/repos/apache/commons-parent/badge.svg?branch=master)](https://coveralls.io/r/apache/commons-parent)
[![Maven Central](https://maven-badges.herokuapp.com/maven-central/org.apache.commons/commons-parent/badge.svg)](https://maven-badges.herokuapp.com/maven-central/org.apache.commons/commons-parent/)
[![License](http://img.shields.io/:license-apache-blue.svg)](http://www.apache.org/licenses/LICENSE-2.0.html)
The Apache Commons Parent POM provides common settings for all Apache Commons components.
Documentation
-------------
More information can be found on the [Apache Commons Parent homepage](https://commons.apache.org/proper/commons-commons-parent).
The [JavaDoc](https://commons.apache.org/proper/commons-commons-parent/javadocs/api-release) can be browsed.
Questions related to the usage of Apache Commons Parent 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-commons-parent/download_commons-parent.cgi).
Alternatively you can pull it from the central Maven repositories:
```xml
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
<version>43</version>
</dependency>
```
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 clean test```.
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 Licence v2](https://www.apache.org/licenses/LICENSE-2.0).
See the `NOTICE.txt` file for required notices and attributions.
Donations
---------
You like Apache Commons Parent? 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/COMMONSSITE)
+ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons)
+ `#apache-commons` IRC channel on `irc.freenode.org`
[ml]:https://commons.apache.org/mail-lists.html

73
RELEASE-NOTES.txt Normal file
View File

@ -0,0 +1,73 @@
Apache Commons Parent 43
RELEASE NOTES
The Apache Commons Parent team is pleased to announce the release of Apache Commons Parent 43
The Apache Commons Parent POM provides common settings for all Apache Commons components.
Updates plugins and generally requires Java 7.
Changes in this version include:
Changes:
o maven-compiler-plugin 3.6.1 -> 3.6.2.
o maven-compiler-plugin 3.6.2 -> 3.7.0.
o jacoco-maven-plugin 0.7.7.201606060606 -> 0.7.9.
o maven-javadoc-plugin 2.10.4 -> 3.0.0 (Java 9 compatibility.)
o Update japicmp 0.9.3 -> 0.10.0.
o animal-sniffer-maven-plugin 1.15 -> 1.16.
o commons.findbugs.version 3.0.3 -> 3.0.5 (requires Java 7.)
o commons.clirr.version 2.7 -> 2.8.
o maven-surefire-plugin 2.19.1 -> 2.20.1.
o Add maven-failsafe-plugin 2.20.1 (to along with surefire.)
o felix:maven-bundle-plugin 3.0.1 -> 3.4.0 (requires Java 7.
o versions-maven-plugin 2.3 -> 2.5.
o japicmp-maven-plugin 0.10.0 -> 0.11.0.
o build-helper-maven-plugin 1.10 -> 3.0.0 (requires Maven 3 and Java 7.)
o wagon-ssh 2.10 -> 3.0.0.
o maven-site-plugin 3.6 -> 3.7 (fixes Java 9 builds; for migrating from 3.4 to 3.5.1, see https://maven.apache.org/components/plugins/maven-site-plugin/migrate.html)
Historical list of changes: http://commons.apache.org/commons-parent-pom.htmlchanges-report.html
For complete information on Apache Commons Parent, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons Parent website:
http://commons.apache.org/commons-parent-pom.html
-----------------------------------------------------------------------------
Apache Commons Parent 42
RELEASE NOTES
The Apache Commons Parent team is pleased to announce the release of Apache Commons Parent 42
The Apache Commons Parent POM provides common settings for all Apache Commons components.
Changes in this version include:
New features:
o new profiles to run coveralls coverage
reports via Travis using Jacoco or Cobertura respectively
Changes:
o maven-site-plugin 3.4 -> 3.6 (for migrating from 3.4 to 3.5.1, see https://maven.apache.org/components/plugins/maven-site-plugin/migrate.html)
o jacoco-maven-plugin : 0.7.6.201602180812 -> 0.7.7.201606060606
o commons-build-plugin : 1.6 -> 1.7
o maven-changes-plugin : 2.12 -> 2.12.1
o Update japicmp: 0.8.0 -> 0.9.1
o maven-compiler-plugin : 3.5.1 -> 3.6.0
o japicmp plugin no longer fail on "mvn site" (it requires target/*jar), use "mvn package site -Pjapicmp" to include its report
o japicmp-maven-plugin : 0.8.0 -> 0.9.3
o new property
commons.japicmp.breakBuildOnBinaryIncompatibleModifications
controls the breakBuildOnBinaryIncompatibleModifications
setting of japicmp
Historical list of changes: http://commons.apache.org/commons-parent-pom.html
For complete information on Apache Commons Parent, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons Parent website:
http://commons.apache.org/commons-parent-pom.html

1704
pom.xml Normal file

File diff suppressed because it is too large Load Diff

43
src/assembly/src.xml Normal file
View File

@ -0,0 +1,43 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
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.
-->
<assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd">
<id>src</id>
<formats>
<format>tar.gz</format>
<format>zip</format>
</formats>
<baseDirectory>${artifactId}-${version}-src</baseDirectory>
<fileSets>
<fileSet>
<includes>
<include>BUILDING.txt</include>
<include>LICENSE*</include>
<include>NOTICE*</include>
<include>RELEASE-NOTES.txt</include>
<include>pom.xml</include>
</includes>
</fileSet>
<fileSet>
<directory>src</directory>
</fileSet>
</fileSets>
</assembly>

489
src/changes/changes.xml Normal file
View File

@ -0,0 +1,489 @@
<?xml version="1.0"?>
<!--
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 also used by the maven-changes-plugin to generate the release notes.
Useful ways of finding items to add to this file are:
1. Add items when you fix a bug or add a feature (this makes the
release process easy :-).
2. Do a JIRA search for tickets closed since the previous release.
3. Use the report generated by the maven-changelog-plugin to see all
SVN commits. TBA how to use this with SVN.
To generate the release notes from this file:
mvn changes:announcement-generate -Prelease-notes [-Dchanges.version=nn]
then tweak the formatting if necessary
and commit
The <action> type attribute can be add,update,fix,remove.
-->
<document xmlns="http://maven.apache.org/changes/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/changes/1.0.0 http://maven.apache.org/xsd/changes-1.0.0.xsd">
<properties>
<title>Changes</title>
<author email="dev@commons.apache.org">Apache Commons developers</author>
</properties>
<!-- NOTE:
The description below is specially formatted so as to improve the layout of the generated release notes:
The parsing process removes all line feeds, replacing them with a single space.
The Velocity template in resources/templates has been enhanced to replace pairs of adjacent spaces
with a new-line in the release notes. (These spaces are ignored when displaying HTML).
If the output is not quite correct, check for invisible trailing spaces!
To suppress formatting of an action entry when generating release notes, add an empty date.
This does not affect the HTML changes report (in any case dates are not displayed by default)
N.B. The release notes template groups actions by type, and only extracts data for the current release.
The changes report outputs actions in the order they appear in this file.
-->
<body>
<release version="43" date="2018-01-02" description="Updates plugins and generally requires Java 7.">
<action type="update">maven-compiler-plugin 3.6.1 -> 3.6.2.</action>
<action type="update">maven-compiler-plugin 3.6.2 -> 3.7.0.</action>
<action type="update">jacoco-maven-plugin 0.7.7.201606060606 -> 0.7.9.</action>
<action type="update">maven-javadoc-plugin 2.10.4 -> 3.0.0 (Java 9 compatibility.)</action>
<action type="update">Update japicmp 0.9.3 -> 0.10.0.</action>
<action type="update">animal-sniffer-maven-plugin 1.15 -> 1.16.</action>
<action type="update">commons.findbugs.version 3.0.3 -> 3.0.5 (requires Java 7.)</action>
<action type="update">commons.clirr.version 2.7 -> 2.8.</action>
<action type="update">maven-surefire-plugin 2.19.1 -> 2.20.1.</action>
<action type="update">Add maven-failsafe-plugin 2.20.1 (to along with surefire.)</action>
<action type="update">felix:maven-bundle-plugin 3.0.1 -> 3.4.0 (requires Java 7.</action>
<action type="update">versions-maven-plugin 2.3 -> 2.5.</action>
<action type="update">japicmp-maven-plugin 0.10.0 -> 0.11.0.</action>
<action type="update">build-helper-maven-plugin 1.10 -> 3.0.0 (requires Maven 3 and Java 7.)</action>
<action type="update">wagon-ssh 2.10 -> 3.0.0.</action>
<action type="update">maven-site-plugin 3.6 -> 3.7 (fixes Java 9 builds; for migrating from 3.4 to 3.5.1, see https://maven.apache.org/components/plugins/maven-site-plugin/migrate.html)</action>
</release>
<release version="42" date="2016-12-29" description="Updates plugins">
<action type="update">maven-site-plugin 3.4 -> 3.6 (for migrating from 3.4 to 3.5.1, see https://maven.apache.org/components/plugins/maven-site-plugin/migrate.html)</action>
<action type="update">jacoco-maven-plugin : 0.7.6.201602180812 -> 0.7.7.201606060606</action>
<action type="update">commons-build-plugin : 1.6 -> 1.7</action>
<action type="update">maven-changes-plugin : 2.12 -> 2.12.1</action>
<action type="update">Update japicmp: 0.8.0 -> 0.9.1</action>
<action type="update">maven-compiler-plugin : 3.5.1 -> 3.6.0</action>
<action type="update">japicmp plugin no longer fail on "mvn site" (it requires target/*jar), use "mvn package site -Pjapicmp" to include its report</action>
<action type="update">japicmp-maven-plugin : 0.8.0 -> 0.9.3</action>
<action type="add">new profiles to run coveralls coverage
reports via Travis using Jacoco or Cobertura respectively</action>
<action type="update">new property
commons.japicmp.breakBuildOnBinaryIncompatibleModifications
controls the breakBuildOnBinaryIncompatibleModifications
setting of japicmp</action>
</release>
<release version="41" date="2016-08-15" description="Updates plugins and adds source compatibility profiles">
<action type="update">COMMONSSITE-89 - support both clirr and japicmp
Clirr report must now be explicitly enabled using src/site/resources/profile.clirr file or -Pclirr option</action>
<action type="update">maven-source-plugin 3.0.0 -> 3.0.1</action>
<action type="update">commons.rat.version 0.11 -> 0.12</action>
<action type="update">maven-javadoc-plugin 2.10.3 -> 2.10.4</action>
<action type="update">RAT: Exclude Eclipse local files and folders</action>
<action type="update">Changed ciManagement to Jenkins builds.apache.org</action>
<action type="update">Update Apache parent: 17 -> 18</action>
</release>
<release version="40" date="2016-04-30" description="Updates plugins and parent; fixes COMMONSSITE-87 and COMMONSSITE-82.
N.B. The assembly plugin now runs in the verify phase (it was previously run in the package phase). See COMMONSSITE-87.
This allows child poms to create additional jars to be added to the assembly.
This will affect child poms that rely on the assembly occurring in the package phase.
They will need to be amended to use the verify phase instead.">
<action type="update">Update Apache Parent POM : 16 -> 17</action>
<action type="update">COMMONSSITE-87 - ensure assembly plugin runs after all package phase plugins</action>
<action type="update">COMMONSSITE-82 - use Commons Skin 4.1 (site.xml)</action>
<action type="update">Require minimum of Maven 3.0.5</action>
<action type="update">maven-assembly-plugin : 2.5.5 -> 2.6</action>
<action type="update">maven-changes-plugin : 2.11 -> 2.12</action>
<action type="update">maven-clean-plugin : 2.6.1 -> 3.0.0</action>
<action type="update">maven-compiler-plugin : 3.3 -> 3.5.1</action>
<action type="update">maven-enforcer-plugin : 1.3.1 -> 1.4.1</action>
<action type="update">maven-source-plugin : 2.4 -> 3.0.0</action>
<action type="update">maven-surefire-plugin : 2.18.1 -> 2.19.1</action>
<action type="update">maven-project-info-reports-plugin : 2.8 -> 2.9</action>
<action type="update">maven-release-plugin : 2.5.2 -> 2.5.3</action>
<action type="update">animal-sniffer-maven-plugin : 1.11 -> 1.15</action>
<action type="update">build-helper-maven-plugin : 1.9.1 -> 1.10</action>
<action type="update">buildnumber-maven-plugin 1.3 -> 1.4 (supports git SCM now)</action>
<action type="update">clirr-maven-plugin : 2.6.1 -> 2.7</action>
<action type="update">commons-build-plugin : 1.4 -> 1.6</action>
<action type="update">felix:maven-bundle-plugin : 2.5.3 -> 3.0.0</action>
<action type="update">findbugs-maven-plugin : 3.0.0 -> 3.0.3</action>
<action type="update">jacoco-maven-plugin : 0.7.5.201505241946 -> 0.7.6.201602180812</action>
<action type="update">wagon-ssh : 2.8 -> 2.10</action>
</release>
<release version="39" date="2015-09-07" description="Uses a new location assembly location; updates plugins; allows Java 8 builds to use animal-sniffer.">
<action type="update">Update Compiler Plugin : 3.2 -> 3.3</action>
<action type="update">Update Build Helper Plugin : 1.8 -> 1.9.1</action>
<action type="update">Update Release Plugin : 2.5.1 -> 2.5.2</action>
<action type="update">Update Javadoc Plugin : 2.10.2 -> 2.10.3</action>
<action type="update">Update Jar Plugin : 2.5 -> 2.6</action>
<action type="update">Drop the "trunks-proper" profile</action>
<action type="update">Update animal-sniffer Plugin : 2.13 -> 2.14 (for Java7+ build profile)</action>
<action type="update">Move assembly to standard location. src/main => src/assembly/src.xml</action>
<action type="update">Update Jacoco Plugin : 0.7.4.201502262128 -> 0.7.5.201505241946</action>
</release>
<release version="38" date="2015-06-25" description="Fix bug in site Security link; update plugins">
<!-- List each change individually so the changes HTML report is easier to read -->
<action type="update">Fix URL for Security link</action>
<action type="update">Update Assembly Plugin : 2.5.3 => 2.5.5</action>
<action type="update">Update Cobertura Plugin : 2.6 => 2.7</action>
<action type="update">Update Jacoco Plugin : 0.7.2 => 0.7.4</action>
<action type="update">Update Javadoc Plugin : 2.10.1 => 2.10.2</action>
<action type="update">Update Surefire Plugin : 2.18 => 2.18.1</action>
</release>
<release version="37" date="2015-01-28" description="Update plugins, add Animal Sniffer and site-basic profile">
<!-- List each change individually so the changes HTML report is easier to read -->
<action type="update">Update minimum Maven prerequisite (as defined by Findbugs) 3.0 -> 3.0.1</action>
<action type="update">Update org.apache:apache 15 to 16 (nop for Commons: maven-compiler-plugin already contained source/target)</action>
<action type="update">Update Maven Project Info Reports Plugin : 2.7 => 2.8</action>
<action type="update">merged maven-3 profile into main body (Maven 2 is no longer supported)</action>
<action type="add">Added Animal Sniffer profile (active by default)</action>
<action type="update">renamed the profile jdk7-findbugs to jdk7-plugin-fix-version</action>
<action type="add">Allow to configure dependency excludes of bundle-plugin with commons.osgi.excludeDependencies</action>
<action type="add">Added property commons.changes.onlyCurrentVersion for changes plugin Jira report</action>
<action type="update">Update GPG Plugin : 1.5 => 1.6</action>
<action type="update">Update Antrun Plugin : 1.7 => 1.8</action>
<action type="add">Allow changes Jira report maxEntries to be overridden (default 100)</action>
<action type="add">Allow changes Jira report runOnlyAtExecutionRoot to be overridden</action>
<action type="add">Added site-basic profile to allow quick generation of the basic site docs</action>
</release>
<release version="36" date="2014-12-21" description="Update plugins, fix release-notes profile.">
<!-- List each change individually so the changes HTML report is easier to read -->
<action type="update">Update maven-jxr-plugin 2.4 to 2.5</action>
<action type="update">Update maven-surefire-plugin(s) 2.17 to 2.18</action>
<action type="update">Update maven-assembly-plugin 2.5 to 2.5.1</action>
<action type="update">Update maven-clean-plugin 2.6 to 2.6.1</action>
<action type="update">Update commons.wagon-ssh.version 2.6 to 2.8</action>
<action type="fix">Add announcementDirectory to release-notes profile.</action>
</release>
<release version="35" date="2014-10-22" description="Update plugins and maintenance">
<!-- List each change individually so the changes HTML report is easier to read -->
<action type="add">Add link to security page in general navigation section</action>
<action type="add">Added java-1.9 profile</action>
<action type="update">Suppress test Javadocs when building site</action>
<action type="update">Suppress test Javadocs</action>
<action type="update">Update JaCoCo to 0.7.2.201409121644</action>
<action type="update">Update maven-compiler-plugin 3.1 to 3.2</action>
<action type="update">Update maven-source-plugin 2.2.1 to 2.4</action>
<action type="update">Update maven-site-plugin 3.3 to 3.4</action>
<action type="update">Update maven-gpg-plugin 1.4 to 1.5</action>
<action type="update">Update maven-jar-plugin 2.4 to 2.5</action>
<action type="update">Update maven-release-plugin 2.4.2 to 2.5.1</action>
<action type="update">Update maven-bundle-plugin 2.4.0 to 2.5.3</action>
<action type="update">Update buildnumber-maven-plugin 1.2 to 1.3</action>
<action type="update">Update wagon-ssh 2.3 to 2.6</action>
<action type="update">Update maven-scm-publish-plugin 1.0 to 1.1</action>
<action type="update">Update jdepend-maven-plugin 2.0-beta-2 to 2.0</action>
<action type="update">Update apache-rat-plugin 0.10 to 0.11</action>
<action type="update">Update maven-clean-plugin 2.5 to 2.6.</action>
<action type="update">Update maven-changes-plugin 2.9 to 2.11</action>
<action type="update">Update maven-deploy-plugin 2.8.1 to 2.8.2</action>
<action type="update">Update maven-install-plugin 2.5.1 to 2.5.2</action>
<action type="update">Update maven-javadic-plugin 2.9.1 to 2.10.1</action>
<action type="update">Update apache 13 to 15</action>
<action type="update">Add property commons.findbugs.version.</action>
</release>
<release version="34" date="2014-04-16" description="
The main changes in this release are:
- Added Maven enforcer to ensure builds use Maven 3.0.0 or later
- Surefire 2.16 to 2.17
- scm-publish 1.0-beta to 1.0
- added java-1.8 profile
">
<!-- List each change individually so the changes HTML report is easier to read -->
<action type="update">Added java-1.8 profile</action>
<action type="update">maven-scm-publish-plugin 1.0-beta -> 1.0</action>
<action type="update">maven-surefire-plugin(s) 2.16 -> 2.17</action>
<action type="update">Added Maven enforcer to ensure builds use Maven 3.0.0 or later</action>
</release>
<release version="33" date="2014-02-14" description="
The main changes in this release are:
- Fixed Jacoco configuration syntax
- updated some plugins
">
<!-- List each change individually so the changes HTML report is easier to read -->
<action type="update">commons-skin 3 -> 4</action>
<action type="update">maven-deploy-plugin 2.7 -> 2.8.1</action>
<action type="update">maven-jxr-plugin 2.3 -> 2.4</action>
<action type="update">maven-install-plugin 2.4 -> 2.5.1</action>
<action type="update">maven-release-plugin 2.4.1 -> 2.4.2</action>
<action type="update">maven-surefire-plugin(s) 2.15 -> 2.16</action>
<action type="update">remote-resources-plugin 1.4 -> 1.5</action>
<action type="update">apache-rat-plugin 0.9 -> 0.10</action>
<action type="update">clirr-maven-plugin 2.5 -> 2.6.1</action>
<action type="update">cobertura-maven-plugin 2.5.2 -> 2.6</action>
<action type="update">jacoco-maven-plugin 0.6.3.201306030806 -> 0.6.4.201312101107</action>
<action type="update">Fixed JaCoCo configuration - syntax changed completely between 0.6.2.x and 0.6.3.x</action>
<!-- Note: the (major) syntax change is not documented AFAICT, and only the trunk docs are online for comparison. -->
<action type="update">Add commons.compiler.version property so compiler plugin version can be overridden if necessary</action>
<action type="update">Add source archive to Maven artifacts</action>
</release>
<release version="32" date="2013-07-01" description="
The main changes in this release are:
- added fix for Javadoc vulnerability (CVE-2013-1571, VU#225657) MJAVADOC-370
- updated some plugins
">
<!-- List each change individually so the changes html report is easier to read -->
<action type="update">maven-javadoc-plugin 2.9 -> 2.9.1</action>
</release>
<release version="31" date="2013-06-24" description="
The main changes in this release are:
- dropped unused 'rc' profile
- fixed the maven.compile[r] names
- updated some plugins and the RAT excludes list
">
<!-- List each change individually so the changes html report is easier to read -->
<action type="update">Dropped "rc" profile as no longer relevant</action>
<action type="update">maven-bundle-plugin 2.3.7 -> 2.4.0</action>
<action type="update">maven-surefire[-report]-plugin 2.14.1 -> 2.15</action>
<action type="fix" issue="COMMONSSITE-69">renamed properties maven.compile.* => maven.compiler.*</action>
<action type="update">Exclude .checkstyle and .fbprefs from RAT check</action>
</release>
<release version="30" date="2013-05-28" description="
The main changes in this release are RAT configuration changes:
- updated excludes: added .pmd and download_*.cgi
- changed excludes so child POM excludes will be appended to the parent list
- duplicated settings in build section so they apply to standalone invocations
Coverage tool:
Made JaCoCo an optional profile
Restored Cobertura as an optional profile
">
<!-- List updates separately so the changes html report is easier to read -->
<action type="update">cobertura-maven-plugin 2.5.2 reinstated</action>
<action type="update">jacoco-maven-plugin 0.6.2.201302030002 -> 0.6.3.201306030806</action>
<action type="update">rat-maven-plugin 0.8 -> 0.9</action>
<action type="update">maven-project-info-reports-plugin 2.6 -> 2.7</action>
</release>
<release version="29" date="2013-05-18" description="Replace Cobertura with JaCoCo; update plugin versions">
<action type="update">cobertura-maven-plugin 2.5.2 -> removed</action>
<action type="update">jacoco-maven-plugin -> 0.6.2.201302030002</action>
<action type="update">maven-surefire-plugin 2.13 -> 2.14.1</action>
<action type="update">maven-surefire-report-plugin 2.13 -> 2.14.1</action>
<action type="update">maven-changes-plugin 2.8 -> 2.9</action>
<action type="update">maven-compiler-plugin 3.0 -> 3.1</action>
<action type="update">maven-release-plugin 2.3.2 -> 2.4.1</action>
<action type="update">maven-site-plugin 3.2 -> 3.3</action>
<action type="update" date="">
The main change is the replacement of Cobertura with JaCoCo for test
coverage analysis. The former is not maintained anymore, has numerous
bugs and is extremely slow in some situations (typically generating
coverage reports for [math] took about 9 hours whereas standard tests
run in about 10 minutes). One important implication is that since
JaCoCo relies on setting an agent, it is triggered only if JDK used to
run the tests is at least Java 1.5 (this is automatically detected),
and it changes the argument line of surefire tests. If a component
also needs to adapt the surefire command line, it must add the
property ${argLine} to the argument line in order to preserve JaCoCo
settings. An example for this is Apache Commons IO, where the
maven-surefire-plugin setting must read as (note the use of the
${argLine} property):
&lt;plugins>
&lt;plugin>
&lt;groupId>org.apache.maven.plugins&lt;/groupId>
&lt;artifactId>maven-surefire-plugin&lt;/artifactId>
&lt;configuration>
&lt;forkMode>pertest&lt;/forkMode>
&lt;!-- limit memory size see IO-161 -->
&lt;!-- the ${argLine} preserves jacoco agent settings (see (see https://github.com/jacoco/jacoco/issues/44) -->
&lt;argLine>-Xmx25M ${argLine}&lt;/argLine>
...
&lt;/configuration>
&lt;/plugin>
...
&lt;/plugins>
</action>
</release>
<release version="28" date="2013-01-26" description="Update plugins">
<action type="update">
apache-parent-pom 9 -> 13
maven-surefire-plugin 2.12.3 -> 2.12.4
maven-surefire-report-plugin 2.12.3 -> 2.12.4
cobertura-maven-plugin 2.5.1 -> 2.5.2
buildnumber-maven-plugin 1.1 -> 1.2
</action>
<action type="update">
Also changed, but omitted from changes section in released version:
Added maven-scm-publish-plugin 1.0-beta-2
Removed timestamp from Javadoc output
Moved Cobertura from default to reporting profile
Renamed module sanselan => imaging
Added scm publishing properties
</action>
</release>
<release version="27" date="2012-09-24" description="Update plugins">
<action type="update">
update maven-site-plugin to 3.1 in reporting section
use properties for all reporting plugins to ensure consistency
maven-changes-plugin: 2.7.1 => 2.8 (fixes MCHANGES-285 SAXException parsing JIRA XML from JIRA 5.1)
maven-project-info-reports-plugin 2.5 -> 2.5.1
maven-resources-plugin 2.5 -> 2.6
maven-surefire-plugin 2.12.2 -> 2.12.3
maven-surefire-report-plugin 2.12.2 -> 2.12.3
</action>
</release>
<release version="26" date="2012-08-23" description="Update plugins">
<action type="update">
FELIX-3037 has been fixed so the profile java-1.5-detected is no longer needed
(in fact it causes problems, because it reverts bndlib to a version that is missing some required new methods)
</action>
<action type="update">
maven-changes-plugin: 2.6 => 2.7.1
maven-clean-plugin: 2.4.1 => 2.5
maven-compiler-plugin: 2.3.2 => 2.5.1
maven-project-info-reports-plugin: 2.4 => 2.5
maven-release-plugin: 2.2.2 => 2.3.2
maven-remote-resources-plugin: 1.2.1 => 1.3
maven-site-plugin: 3.0 => 3.1
maven-source-plugin: 2.1.2 => 2.2
maven-surefire-plugin: 2.12 => 2.12.2
maven-surefire-report-plugin: 2.12 => 2.12.2
org.codehaus.mojo:buildnumber-maven-plugin: 1.0 => 1.1
</action>
</release>
<release version="25" date="2012-??-??" description="Update plugins">
<action type="update">
Updated various plugin versions:
clirr-maven-plugin: 2.3 => 2.4
clirr and RAT added to pluginManagement so can override the version from Apache POM
Add changes and jira reports
</action>
</release>
<release version="24" date="2012-03-13" description="Update and add plugins">
<action type="update">
Updated various plugin versions:
antrun: 1.6 => 1.7
assembly: 2.2.1 => 2.3
jar: 2.3.2 => 2.4
release: 2.2.1 => 2.2.2
remote-resources: override Apache pom 9 with 1.2.1
commons-build: 1.3 => 1.4
bundle: 2.3.5 => 2.3.7; removed workround for Java 1.5 as no longer necessary
Added cobertura: 2.5.1 to reporting and buildManagement
surefire: 2.9 => 2.12
surefire-report: 2.9 => 2.12
Allow override of surefire-report aggregate setting using property commons.surefire-report.aggregate
javadoc: 2.8 => 2.8.1
rat: 0.7 => 0.8
wagon-ssh 1.0 => 2.2 (M3 only)
Deleted "ci" profile (does not apply with Nexus)
Add default project info reports: excluded license/plugins/plugin management
Add tests.jar and test-sources.jar to deployed files
</action>
</release>
<release version="23" date="2012-01-11" description="
The Maven3 site plugin has been updated to support ssh/scp for deployment
The buildNumber plugin now defaults to using SVN CLI, and does not run if buildNumber.skip=true
To use javasvn instead, use the profile: javasvn
">
<action dev="ggregory" type="add">
added java-1.7 profile
</action>
<action dev="ggregory" type="add">
added ssh/scp support to maven-site-plugin in Maven3
</action>
<action dev="sebb" type="update" due-to="Olivier Lamy">
moved buildNumber plugin to profile which is activated unless buildNumber.skip=true
changed buildNumber plugin default provider to CLI; added 'javasvn' profile as override
</action>
<action dev="sebb" type="update">
added aggregate:false to jxr plugin (aggregate is deprecated)
</action>
<action dev="sebb" type="update">
updated modules list, added: bcel, functor, jcs, ognl
</action>
</release>
<release version="22" date="2011-09-21" description="
Starting with version 22, the RAT plugin has changed Maven group and id,
so any existing configuration needs to be updated.
To fix component POMs, please change any occurrences of:
&lt;groupId>org.codehaus.mojo&lt;/groupId>
&lt;artifactId>rat-maven-plugin&lt;/artifactId>
to the new values:
&lt;groupId>org.apache.rat&lt;/groupId>
&lt;artifactId>apache-rat-plugin&lt;/artifactId>
">
<action dev="sebb" type="add">
Add commons.release.version and commons.rc.version for use in releasing commons parent
</action>
<action dev="sebb" type="add">
Add release-notes profile to generate RELEASE-NOTES.txt from changes.xml.
Added changes.xml and template release-notes.vm
</action>
<action dev="sebb" type="add">
Add pom description
</action>
<action dev="sebb" type="fix">
Added workround for bundle plugin 2.3.5 on Java 1.5 - replace embedded bndlib with previous version
</action>
<action dev="sebb" type="add">
Add buildnumber plugin and put build details into manifests.
</action>
<action dev="sebb" type="add">
Add Clirr report for all components
</action>
<action dev="sebb" type="update">
Update to site plugin 3.0 (usable by Maven 2 and Maven 3)
</action>
<action dev="sebb" type="fix">
Fix resources and testResource overrides to include the default directories.
Components which redefine these may no longer need to do so.
</action>
<action type="update">
Update to latest releases of plugins.
</action>
<action dev="sebb" type="remove">
Remove Maven IDEA plugin.
</action>
<action dev="sebb" type="update">
Update to Apache RAT plugin, and enable use as standalone goal.
</action>
<action dev="ggregory" type="add">
Add Javadoc link to Java EE.
</action>
</release>
</body>
</document>

View File

@ -0,0 +1,122 @@
## 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.
##
${project.name} ${version}
RELEASE NOTES
The ${developmentTeam} is pleased to announce the release of ${project.name} ${version}
$introduction.replaceAll("(?<!\015)\012", "
").replaceAll("(?m)^ +","")
## N.B. the available variables are described here:
## http://maven.apache.org/plugins/maven-changes-plugin/examples/using-a-custom-announcement-template.html
##
## Hack to improve layout: replace all pairs of spaces with a single new-line
$release.description.replaceAll(" ", "
")
## set up indent sizes. Only change indent1
#set($props=${project.properties})
#set($jiralen=$props.get("commons.jira.id").length())
## indent1 = POOL-nnnn:
#set($blanklen=$jiralen+6)## +6 for "-nnnn:"
## must be at least as long as the longest JIRA id
#set($blanks=" ")
#set($indent1=$blanks.substring(0,$blanklen))
## indent2 allows for issue wrapper
#set($indent2="$indent1 ")
##
#macro ( processaction )
## Use replaceAll to fix up LF-only line ends on Windows.
#set($action=$actionItem.getAction().replaceAll("\n","
"))
## Replace &lt; with < so can embed tag markup
#set($action=$action.replaceAll("&lt;","<"))
## use an empty date to mean don't format the entry
## TODO how to enable leading spaces without compromising html report
## unfortunately leading spaces are trimmed even from CDATA sections
#if ($actionItem.getDate() && $actionItem.getDate().length()==0)
$action
#else
## Fix up indentation for multi-line action descriptions
#set($action=$action.replaceAll("(?m)^ +",$indent2))
#if ($actionItem.getIssue())
#set($issue="$actionItem.getIssue():")
## Pad shorter issue numbers
#if ($issue.length() < $indent1.length())#set ($issue="$issue ")#end
#if ($issue.length() < $indent1.length())#set ($issue="$issue ")#end
#if ($issue.length() < $indent1.length())#set ($issue="$issue ")#end
#else
#set($issue=$indent1)
#end
#if ($actionItem.getDueTo())
#set($dueto=" Thanks to $actionItem.getDueTo().")
#else
#set($dueto="")
#end
o $issue ${action}$dueto
#end
#set($action="")
#set($issue="")
#set($dueto="")
#end
##
#if ($release.getActions().size() == 0)
No changes defined in this version.
#else
Changes in this version include:
#if ($release.getActions('add').size() !=0)
New features:
#foreach($actionItem in $release.getActions('add'))
#processaction()
#end
#end
##
#if ($release.getActions('fix').size() !=0)
Fixed Bugs:
#foreach($actionItem in $release.getActions('fix'))
#processaction()
#end
#end
##
#if ($release.getActions('update').size() !=0)
Changes:
#foreach($actionItem in $release.getActions('update'))
#processaction()
#end
#end
##
#if ($release.getActions('remove').size() !=0)
Removed:
#foreach($actionItem in $release.getActions('remove'))
#processaction()
#end
#end
## End of main loop
#end
Historical list of changes: ${project.url}changes-report.html
For complete information on ${project.name}, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache ${project.name} website:
${project.url}

View File

143
src/site/site.xml Normal file
View File

@ -0,0 +1,143 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
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.
-->
<project name="Apache Commons" xmlns="http://maven.apache.org/DECORATION/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/DECORATION/1.1.0 http://maven.apache.org/xsd/decoration-1.1.0.xsd">
<!-- N.B. all non-body elements are automatically inherited -->
<bannerLeft>
<name>Apache Commons</name>
<!--
! Even though the default site.vm template contains code to convert relative links, this is
! actually done before the content is passed to the template, for both site:site and site:stage.
! Unfortunately, this means that the conversion is done in the context of commons-parent, which
! contains the site.xml, rather than in the context of the project being built.
! This means that relative URLs are created with an additional ../ prefix.
! The work-round is to use a dummy absolute URL that can never be used, and then remove this
! as part of the template processing.
! See MSITE-559
-->
<src>http://dummy.invalid/$relativePath/images/commons-logo.png</src>
<alt>Apache Commons logo</alt>
<!--
! Similarly href entries are converted before they are passed to the template.
! In this case, we want the URL to remain absolute.
! The work-round is to use a dummy suffix that is removed by the template.
! This is due to be fixed in version 2.3 of the site plugin - see MSITE-159, MSHARED-189
! Or use site:stage which does not convert these links ...
-->
<href>http://commons.apache.org.remove.invalid/</href>
</bannerLeft>
<publishDate format="dd MMMM yyyy" position="left" />
<version position="left" />
<skin>
<groupId>org.apache.commons</groupId>
<artifactId>commons-skin</artifactId>
<version>4.1</version>
</skin>
<body>
<head>
<![CDATA[
<!-- Better display of <source> code sections -->
<!-- Note: the $relativePath reference is resolved by the template -->
<link rel="stylesheet" href="$relativePath/css/prettify.css" type="text/css" media="all" />
<script type="text/javascript" src="$relativePath/js/prettify.js"></script>
<script type="text/javascript">
window.onload=function() {
prettyPrint();
}
</script>
]]>
</head>
<!-- N.B. body links are automatically inherited -->
<links>
<item name="ApacheCon" href="http://www.apachecon.com/"/>
<item name="Apache" href="http://www.apache.org"/>
<item name="Commons" href="http://commons.apache.org/" />
</links>
<menu ref="reports" inherit="bottom" />
<menu name="Commons" inherit="bottom">
<item name="Home" href="http://commons.apache.org/" />
<item name="License" href="http://www.apache.org/licenses/"/>
<item name="Components" href="http://commons.apache.org/components.html" collapse="true">
<item name="Full list..." href="http://commons.apache.org/components.html" />
</item>
<item name="Sandbox" href="http://commons.apache.org/sandbox/index.html" collapse="true">
<item name="Full list..." href="http://commons.apache.org/sandbox/index.html" />
</item>
<item name="Dormant" href="http://commons.apache.org/dormant/index.html" collapse="true">
<item name="Full list..." href="http://commons.apache.org/dormant/index.html" />
</item>
</menu>
<!-- Should agree with commons-site -->
<menu name="General Information" inherit="bottom">
<item name="Security" href="http://commons.apache.org/security.html"/>
<item name="Volunteering" href="http://commons.apache.org/volunteering.html" />
<item name="Contributing Patches" href="http://commons.apache.org/patches.html" />
<item name="Building Components" href="http://commons.apache.org/building.html" />
<item name="Commons Parent Pom" href="http://commons.apache.org/commons-parent-pom.html" />
<item name="Commons Build Plugin" href="http://commons.apache.org/build-plugin/index.html" />
<item name="Releasing Components" href="http://commons.apache.org/releases/index.html" />
<item name="Wiki" href="http://wiki.apache.org/commons/FrontPage" />
</menu>
<!-- Should agree with commons-site -->
<menu name="ASF" inherit="bottom">
<item name="How the ASF works" href="http://www.apache.org/foundation/how-it-works.html" />
<item name="Get Involved" href="http://www.apache.org/foundation/getinvolved.html" />
<item name="Developer Resources" href="http://www.apache.org/dev/" />
<item name="Code of Conduct" href="http://www.apache.org/foundation/policies/conduct.html" />
<item name="Sponsorship" href="http://www.apache.org/foundation/sponsorship.html" />
<item name="Thanks" href="http://www.apache.org/foundation/thanks.html" />
</menu>
</body>
<!-- inherited -->
<poweredBy>
<!-- Add ApacheCon logo -->
<logo name="ApacheCon" href="http://www.apache.org/events/current-event.html"
img="http://www.apache.org/events/current-event-125x125.png"/>
<!-- Keep the default logo as well -->
<logo name="Maven" href="http://maven.apache.org/"
img="http://maven.apache.org/images/logos/maven-feather.png"/>
</poweredBy>
<!-- inherited -->
<custom>
<![CDATA[
<!-- @project.name@ will be replaced by the template; if we used ${project.name} it would pick up Commons Parent -->
<footer>
<div class="center">
Apache Commons, Apache @project.name@, Apache, the Apache feather logo, and the Apache Commons project logos are trademarks of The Apache Software Foundation.
All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</div>
</footer>
]]>
</custom>
</project>

112
src/test/pom.xml Normal file
View File

@ -0,0 +1,112 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
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.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
<version>40-SNAPSHOT</version>
<relativePath>../..</relativePath>
</parent>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent-test</artifactId>
<description>Dummy POM to make it easier to check whether plugins are up to date
All the plugins not already listed in the parent POM pluginManagement section
are listed here.
The following commands can then be used to check the versions:
mvn versions:display-dependency-updates -U
mvn versions:display-plugin-updates -U
</description>
<properties>
<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>
</properties>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>${commons.compiler.version}</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>animal-sniffer-maven-plugin</artifactId>
<version>${commons.animal-sniffer.version}</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>${commons.cobertura.version}</version>
</plugin>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>${commons.jacoco.version}</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jdepend-maven-plugin</artifactId>
<version>${commons.jdepend.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jxr-plugin</artifactId>
<version>${commons.jxr.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-publish-plugin</artifactId>
<version>${commons.scm-publish.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh</artifactId>
<version>${commons.wagon-ssh.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-report-plugin</artifactId>
<version>${commons.surefire-report.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>${commons.surefire.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>${commons.project-info.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>${commons.changes.version}</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
<version>${commons.findbugs.version}</version>
</plugin>
</plugins>
</pluginManagement>
</build>
</project>