Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/58
[![Coverage
Status](https://coveralls.io/builds/12601363/badge)](https://coveralls.io/builds/12601363)
Coverage increased (+0.06%) to 98.222% when pulling
Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/58
[![Coverage
Status](https://coveralls.io/builds/12601363/badge)](https://coveralls.io/builds/12601363)
Coverage increased (+0.06%) to 98.222% when pulling
Github user TheRealHaui commented on the issue:
https://github.com/apache/commons-text/pull/58
You're welcome!
Here we go regarding the exception detection code style.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
On Fri, Jul 28, 2017 at 5:40 AM, Rob Tompkins wrote:
>
> > On Jul 27, 2017, at 12:53 PM, Gary Gregory
> wrote:
> >
> > We have not in the past forced a major version and Maven coordinate
> change
> > when updating the Java platform. We could do that
Github user ameyjadiye commented on the issue:
https://github.com/apache/commons-text/pull/59
@chtompki , I'm testing same on my Commons Text fork , that shell file need
a bit modification for Commons , will raise PR.
---
If your project is set up for it, you can reply to this
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-text/pull/59
Looks like a very complex setup.
But the actual travis report looks good:
https://travis-ci.org/jacoco/jacoco/builds/255021437?utm_source=github_status_medium=notification
Github user chtompki commented on the issue:
https://github.com/apache/commons-text/pull/59
Get a load of this:
https://github.com/jacoco/jacoco/blob/master/.travis.sh
https://github.com/jacoco/jacoco/blob/master/.travis.yml
---
If your project is set up for it, you can reply
Github user asfgit closed the pull request at:
https://github.com/apache/commons-text/pull/59
---
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
Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/59
[![Coverage
Status](https://coveralls.io/builds/12598637/badge)](https://coveralls.io/builds/12598637)
Coverage remained the same at 98.163% when pulling
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/commons-text/pull/59
add oraclejdk9 to travis configuration
add maven java9 profile:
- use maven-javadoc-plugin version 3.0.0-M1, because versions below 3.0.0
do not work on java 9
- skip
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
I'll try to get to it today.
---
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
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
I'll try to get to it today.
---
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
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
@chtompki Any progress on this one?
---
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
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
@chtompki Any progress on this one?
---
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
Hi.
On Fri, 28 Jul 2017 11:34:48 -, ericbarnh...@apache.org wrote:
NUMBERS-13: Complex() passes all tests and meets all the C99
standards. This issue is closed.
Thanks for this work! :-)
Do you think of adding some info (in Javadoc, or in a "User guide")
about the new functionality
Hi Eric.
Changing
0 -> 0.0
is not necessary, and since the latter is less esthetically pleasing,
why bother?
And, as usual, we should avoid mixing different types of changes in
the same commit.
Regards,
Gilles
On Fri, 28 Jul 2017 11:34:47 -, ericbarnh...@apache.org wrote:
Repository:
> On Jul 28, 2017, at 8:32 AM, Amey Jadiye wrote:
>
> Thanks, I'm taking Commons Text as my test guineapig for jacoco style
> implementation , once confident in implementation we can move it to other
> components.
>
Sounds good to me.
> Regards,
> Amey
>
>> On Jul
> On Jul 27, 2017, at 12:53 PM, Gary Gregory wrote:
>
> We have not in the past forced a major version and Maven coordinate change
> when updating the Java platform. We could do that of course.
I’m a tad surprised by this. It feels like updating the minimum accommodated
> On Jul 27, 2017, at 10:39 PM, Gary Gregory wrote:
>
> You don't have karma to use what in the UI? I do not see a "move" kind of
> operation, only "new" ops.
That’s a good question. I suppose that I’m not certain what I should be able to
see vs what I shouldn’t in the
Thanks, I'm taking Commons Text as my test guineapig for jacoco style
implementation , once confident in implementation we can move it to other
components.
Regards,
Amey
On Jul 28, 2017 5:39 PM, "Rob Tompkins" wrote:
>
> > On Jul 27, 2017, at 4:10 PM, Amey Jadiye
> On Jul 27, 2017, at 4:10 PM, Amey Jadiye wrote:
>
> Hi Rob,
>
> If this is still pending I would like to pickup this task. If docker is not
> much helpful OR we need to wait for it I think we should try what jacoco
> did. what do you think ?
Sure. That makes sense to
21 matches
Mail list logo