The root cause, IMHO, is having failValidation=false configured in the
pom.xml. This way, when you introduce a new problem your only option to
notice it is if you visually scan mvn's output. As evident by the current
state of the build, not everyone notices these.
A more robust approach would be to
Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/54
[![Coverage
Status](https://:/builds/12097991/badge)](https://:/builds/12097991)
Coverage decreased (-0.02%) to 97.308% when pulling
**f9177e204d608e7fa708d57fabf0029746f7774a on
Github user coveralls commented on the issue:
https://github.com/apache/commons-rng/pull/3
[![Coverage
Status](https://:/builds/12095968/badge)](https://:/builds/12095968)
Coverage remained the same at 96.934% when pulling
**fc42e1d03ef2232ee243d9a1a7cd2db37b22ba14 on C0
Github user C0rWin commented on the issue:
https://github.com/apache/commons-rng/pull/3
reverify
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Hi,
Can you please take a look on PRs which suppose to handle both issues?
On Fri, Jun 23, 2017 at 1:35 AM, Gilles
wrote:
> Github and Maven experts, please have a look at the
> following issues:
> https://issues.apache.org/jira/browse/RNG-38
>
PR #1:
https://github.com/apache/commons-
GitHub user C0rWin opened a pull request:
https://github.com/apache/commons-rng/pull/4
Rng 31
Maven assembly plugin is not able to produce checksums while assembles
artifacts, added checksum artifact which will generate checksums by running
```
mvn clean assembly:singl
GitHub user C0rWin opened a pull request:
https://github.com/apache/commons-rng/pull/3
Rng 38
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/C0rWin/commons-rng RNG-38
Alternatively you can review and apply these changes as the
Hi.
Github and Maven experts, please have a look at the
following issues:
https://issues.apache.org/jira/browse/RNG-38
https://issues.apache.org/jira/browse/RNG-31
Regards,
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@
Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/54
[![Coverage
Status](https://:/builds/12093960/badge)](https://:/builds/12093960)
Coverage decreased (-0.02%) to 97.306% when pulling
**2dfadf4f8b51ae65d1b1b1f17afa3387b908c31f on
GitHub user ameyjadiye opened a pull request:
https://github.com/apache/commons-text/pull/54
TEXT-93: RandomStringGenerator accepts a list of valid characters
Added selectFrom feature :
```
selectFromList(char[] chars)
selectFromList(List charList)
```
You can merge
FYI, to whom can take the time to fix this.
When I run 'mvn clean install', I get:
[INFO] --- maven-checkstyle-plugin:2.15:check (default) @
commons-configuration2 ---
[INFO] There are 23 errors reported by Checkstyle 6.1.1 with
C:\vcs\svn\apache\commons\trunks-proper\configuration/conf/checkstyl
Am 22.06.2017 um 21:36 schrieb Gary Gregory:
> But why use an older version of Jackson? ;-)
This was the version that was referenced by the patch. I did not check
against the most recent version. Maybe the original author can answer this?
Oliver
>
> Gary
>
> On Thu, Jun 22, 2017 at 10:40 AM,
But why use an older version of Jackson? ;-)
Gary
On Thu, Jun 22, 2017 at 10:40 AM, wrote:
> Author: oheger
> Date: Thu Jun 22 17:40:53 2017
> New Revision: 1799599
>
> URL: http://svn.apache.org/viewvc?rev=1799599&view=rev
> Log:
> Updated dependency to jackson-databind.
>
> Also moved new dep
Github user asfgit closed the pull request at:
https://github.com/apache/commons-text/pull/50
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Am 21.06.2017 um 22:07 schrieb Gary Gregory:
> Why use an old version of Jackson?
Thanks for the catch. Version updated.
Oliver
>
> Gary
> -- Forwarded message --
> From:
> Date: Jun 21, 2017 13:01
> Subject: svn commit: r1799506 - in
> /commons/proper/configuration/trunk/src
Github user developerSid closed the pull request at:
https://github.com/apache/commons-fileupload/pull/1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user developerSid commented on the issue:
https://github.com/apache/commons-fileupload/pull/1
I just checked the code out, and this has already been fixed. Looks like
the change I wanted to try and get into upstream was done on 3/16/2011 by
Wiedmann. I'm going to close this.
Github user developerSid commented on the issue:
https://github.com/apache/commons-fileupload/pull/1
I totally agree this was a pretty botched pull request. How would you like
me to handle this once I get it fixed? Leave this thread open and comment here
with the new pull request?
> On Jun 22, 2017, at 4:38 AM, Amey Jadiye wrote:
>
> +1 agreed with Emmanuel, better we park/close this issue for now. Its very
> trivial and can be pull whenever there will be actual requirement.
>
> Regards,
> Amey
>
>> On Thu, Jun 22, 2017, 1:50 PM Emmanuel Bourg wrote:
>>
>>> Le 22/06/
+1 agreed with Emmanuel, better we park/close this issue for now. Its very
trivial and can be pull whenever there will be actual requirement.
Regards,
Amey
On Thu, Jun 22, 2017, 1:50 PM Emmanuel Bourg wrote:
> Le 22/06/2017 à 06:28, Bruno P. Kinoshita a écrit :
>
> > But would be good to find s
Le 22/06/2017 à 06:28, Bruno P. Kinoshita a écrit :
> But would be good to find someone, maybe a bioinformatician, that could
> confirm if it would be useful, and give a few use cases, for that.
What about waiting for someone with an actual and sensible use case to
request the inclusion of palin
21 matches
Mail list logo