You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
(the "License"); you may not use this file except in compliance with
7
7
the License. You may obtain a copy of the License at
8
8
9
-
http://www.apache.org/licenses/LICENSE-2.0
9
+
https://www.apache.org/licenses/LICENSE-2.0
10
10
11
11
Unless required by applicable law or agreed to in writing, software
12
12
distributed under the License is distributed on an "AS IS" BASIS,
@@ -61,11 +61,11 @@ Making Changes
61
61
62
62
+ Create a _topic branch_ for your isolated work.
63
63
* Usually you should base your branch from the `master` branch.
64
-
* A good topic branch name can be the JIRA bug ID plus a keyword, for example,`COMMONSSITE-123-InputStream`.
64
+
* A good topic branch name can be the JIRA bug ID plus a keyword, e.g.`COMMONSSITE-123-InputStream`.
65
65
* If you have submitted multiple JIRA issues, try to maintain separate branches and pull requests.
66
66
+ Make commits of logical units.
67
67
* Make sure your commit messages are meaningful and in the proper format. Your commit message should contain the key of the JIRA issue.
68
-
* For example, `[COMMONSSITE-123] Close input stream earlier`
68
+
* For example, `[COMMONSSITE-123] Close input stream sooner`
69
69
+ Respect the original code style:
70
70
+ Only use spaces for indentation; you can check for unnecessary whitespace with `git diff` before committing.
71
71
+ 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.
@@ -68,7 +68,7 @@ Alternatively, you can pull it from the central Maven repositories:
68
68
<dependency>
69
69
<groupId>org.apache.commons</groupId>
70
70
<artifactId>commons-release-plugin</artifactId>
71
-
<version>1.9.0</version>
71
+
<version>1.9.1</version>
72
72
</dependency>
73
73
```
74
74
@@ -90,7 +90,7 @@ There are some guidelines which will make applying PRs easier for us:
90
90
+ 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.
91
91
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
92
92
+ Before you pushing a PR, run `mvn` (by itself), this runs the default goal, which contains all build checks.
93
-
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false`
93
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
94
94
95
95
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
96
96
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
Copy file name to clipboardExpand all lines: RELEASE-NOTES.txt
+44Lines changed: 44 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,47 @@
1
+
Apache Commons Release Plugin 1.9.1 Release Notes
2
+
------------------------------------------------
3
+
4
+
The Apache Commons Release Plugin team is pleased to announce the release of Apache Commons Release Plugin 1.9.1.
5
+
6
+
This document contains the release notes for Apache Commons Release Plugin.
7
+
8
+
Apache Maven Mojo for Apache Commons Release tasks.
9
+
10
+
Version 1.9.1.
11
+
12
+
13
+
14
+
Fixed Bugs
15
+
----------
16
+
17
+
* Migrate site generation templates to https://maven.apache.org/xsd/xdoc-2.0.xsd. Thanks to Gary Gregory.
18
+
* Remove -nouses directive from maven-bundle-plugin. OSGi package imports now state 'uses' definitions for package imports, this doesn't affect JPMS (from org.apache.commons:commons-parent:80). Thanks to Gary Gregory.
19
+
20
+
Changes
21
+
-------
22
+
23
+
* Bump org.apache.commons:commons-parent from 79 to 85 #376. Thanks to Gary Gregory, Dependabot.
24
+
* Bump org.apache.commons:commons-build-plugin from 1.14.1 to 1.16.0 #355. Thanks to Dependabot, Arnout Engelen, Gary Greggory.
25
+
* Bump commons-codec:commons-codec from 1.17.2 to 1.19.0 #357. Thanks to Dependabot, Gary Gregory.
26
+
* Bump org.codehaus.plexus:plexus-velocity from 2.2.0 to 2.2.1 #372. Thanks to Dependabot, Gary Gregory.
27
+
* Bump commons-io:commons-io from 2.18.0 to 2.20.0. Thanks to Gary Gregory, Dependabot.
28
+
* Bump org.apache.commons:commons-collections4 from 4.5.0-M3 to 4.5.0. Thanks to Gary Gregory.
29
+
* Bump maven.dependency.version from 3.9.9 to 3.9.11 #383. Thanks to Gary Gregory, Dependabot.
30
+
31
+
32
+
Historical list of changes: https://commons.apache.org/proper/commons-release-plugin//changes.html
33
+
34
+
For complete information on Apache Commons Release Plugin, including instructions on how to submit bug reports,
35
+
patches, or suggestions for improvement, see the Apache Commons Release Plugin website:
<actiontype="fix"dev="ggregory"due-to="Gary Gregory">Migrate site generation templates to https://maven.apache.org/xsd/xdoc-2.0.xsd.</action>
30
30
<actiontype="fix"dev="ggregory"due-to="Gary Gregory">Remove -nouses directive from maven-bundle-plugin. OSGi package imports now state 'uses' definitions for package imports, this doesn't affect JPMS (from org.apache.commons:commons-parent:80).</action>
0 commit comments