Hi,
I'm looking on the project and since I'm pretty unfamiliar w/ inner ASF
processing, was wondering what currently missing to be able to release
first version of commons-rng?
Just trying to understand the process and probably to fill up the JIRA with
appropriate tasks which are necessary to
On Thu, 11 Aug 2016 21:07:05 +0300, Artem Barger wrote:
How do you differ between core and tools? What should be included in
each? Do you mean to further split up current commons-rng?
Not split the _current_ codebase (which is "core").
If non-core tools (e.g. syntactic sugar like "Stream"s or
Hi all,
after the failed votes for RC1 and RC2 a new RC has been created. There
has been further tweaking of the checkstyle configuration to solve build
problems on Java 1.6.
Configuration 2.1 RC3 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration
How do you differ between core and tools? What should be included in each? Do
you mean to further split up current commons-rng?
Sounds possible once decided how you'd like to divide it.
Отправлено с iPhone
> 11 авг. 2016 г., в 20:44, Gilles написал(а):
>
> On
On Thu, 11 Aug 2016 09:02:34 +0300, Artem Barger wrote:
11 авг. 2016 г., в 2:08, Rob Tompkins
написал(а):
I would guess that we would want to be compatible with the oldest
version of Java possible dictated out of necessity. By that I mean if
there's something of
Since this is my first open source any small task would be quite
helpful for me to get started. I am quite comfortable with Java and
C++ programming languages.
I am sorry if this conversation may seem a bit out of context from mailing list.
Regards,
Utsav Oza
> On Jul 31, 2016, at 3:03 PM, Rob Tompkins wrote:
>
> I figured that I would run an analogous test to the original with isParsable
> and createNumber, and I ran into the following:
>
> System.out.println(NumberUtils.isParsable("+2")); > false
>
Commons parent 41 has been released. Commons parent is the maven parent of
most commons components.
This release includes plugin version updates and two new profiles to support
source compatibility checking.
Details can be found at the commons parent site:
> 11 авг. 2016 г., в 2:08, Rob Tompkins написал(а):
>
> I would guess that we would want to be compatible with the oldest version of
> Java possible dictated out of necessity. By that I mean if there's something
> of considerable substance that a newer version affords us,