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
The Apache Commons RNG project provides pure-Java implementation of pseudo-random generators.
53
54
54
55
Documentation
55
56
-------------
56
57
57
-
More information can be found on the [Apache Commons RNG homepage](https://commons.apache.org/proper/commons-rng). The Javadoc for each of the modules can be browsed:
58
+
More information can be found on the [Apache Commons RNG homepage](https://commons.apache.org/proper/commons-rng).
59
+
The [Javadoc](https://commons.apache.org/proper/commons-rng/commons-rng-docs/apidocs) for each of the modules can be browsed:
@@ -73,12 +75,12 @@ Alternatively, you can pull it from the central Maven repositories:
73
75
<dependency>
74
76
<groupId>org.apache.commons</groupId>
75
77
<artifactId>commons-rng-simple</artifactId>
76
-
<version>1.6</version>
78
+
<version>1.7</version>
77
79
</dependency>
78
80
<dependency>
79
81
<groupId>org.apache.commons</groupId>
80
82
<artifactId>commons-rng-sampling</artifactId>
81
-
<version>1.6</version>
83
+
<version>1.7</version>
82
84
</dependency>
83
85
```
84
86
@@ -98,7 +100,9 @@ There are some guidelines which will make applying PRs easier for us:
98
100
+ No tabs! Please use spaces for indentation.
99
101
+ Respect the existing code style for each file.
100
102
+ 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.
101
-
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```.
103
+
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
104
+
+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
105
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
102
106
103
107
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
104
108
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
Copy file name to clipboardExpand all lines: commons-rng-bom/README.md
+5-4Lines changed: 5 additions & 4 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,
@@ -46,7 +46,7 @@ the Bill of Materials (BOM) for dependency management:
46
46
<dependency>
47
47
<groupId>org.apache.commons</groupId>
48
48
<artifactId>commons-rng-bom</artifactId>
49
-
<version>1.6</version>
49
+
<version>1.7</version>
50
50
<type>pom</type>
51
51
<scope>import</scope>
52
52
</dependency>
@@ -62,7 +62,9 @@ There are some guidelines which will make applying PRs easier for us:
62
62
+ No tabs! Please use spaces for indentation.
63
63
+ Respect the existing code style for each file.
64
64
+ 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.
65
-
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```.
65
+
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
66
+
+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
67
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
66
68
67
69
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
68
70
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
API for client code that uses random numbers generators.
52
54
@@ -67,7 +69,7 @@ Alternatively, you can pull it from the central Maven repositories:
67
69
<dependency>
68
70
<groupId>org.apache.commons</groupId>
69
71
<artifactId>commons-rng-client-api</artifactId>
70
-
<version>1.6</version>
72
+
<version>1.8</version>
71
73
</dependency>
72
74
```
73
75
@@ -87,7 +89,9 @@ There are some guidelines which will make applying PRs easier for us:
87
89
+ No tabs! Please use spaces for indentation.
88
90
+ Respect the existing code style for each file.
89
91
+ 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.
90
-
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```.
92
+
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
93
+
+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
94
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
91
95
92
96
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
93
97
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
Pure Java implementations of random numbers generator algorithms.
52
54
Code in this module should not be used directly by applications; please use
@@ -71,7 +73,7 @@ Alternatively, you can pull it from the central Maven repositories:
71
73
<dependency>
72
74
<groupId>org.apache.commons</groupId>
73
75
<artifactId>commons-rng-core</artifactId>
74
-
<version>1.6</version>
76
+
<version>1.8</version>
75
77
</dependency>
76
78
```
77
79
@@ -91,7 +93,9 @@ There are some guidelines which will make applying PRs easier for us:
91
93
+ No tabs! Please use spaces for indentation.
92
94
+ Respect the existing code style for each file.
93
95
+ 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.
94
-
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```.
96
+
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
97
+
+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
98
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
95
99
96
100
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
97
101
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
@@ -44,7 +45,9 @@ There are some guidelines which will make applying PRs easier for us:
44
45
+ No tabs! Please use spaces for indentation.
45
46
+ Respect the existing code style for each file.
46
47
+ 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.
47
-
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```.
48
+
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
49
+
+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
50
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
48
51
49
52
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
50
53
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
Copy file name to clipboardExpand all lines: commons-rng-examples/README.md
+4-3Lines changed: 4 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,
@@ -48,7 +48,9 @@ There are some guidelines which will make applying PRs easier for us:
48
48
+ No tabs! Please use spaces for indentation.
49
49
+ Respect the existing code style for each file.
50
50
+ 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.
51
-
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```.
51
+
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
52
+
+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
53
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
52
54
53
55
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
54
56
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
Copy file name to clipboardExpand all lines: commons-rng-examples/examples-jmh/README.md
+4-3Lines changed: 4 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,
@@ -46,7 +46,9 @@ There are some guidelines which will make applying PRs easier for us:
46
46
+ No tabs! Please use spaces for indentation.
47
47
+ Respect the existing code style for each file.
48
48
+ 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.
49
-
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```.
49
+
+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
50
+
+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
51
+
+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
50
52
51
53
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
52
54
You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).
0 commit comments