Github user ameyjadiye commented on the issue:
https://github.com/apache/commons-text/pull/61
Because of low interest of community adapting this change i'm closing this
pull request.
http://markmail.org/message/mn2or73hqsz6oxo2
---
If your project is set up for it, you can
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-text/pull/61
Also note that currently this script only compiles and runs test. Rat,
clirr, findbugs and javadoc are not executed.
---
If your project is set up for it, you can reply to this email
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-text/pull/61
+1 for moving this discussion to the mailing list
---
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
Github user chtompki commented on the issue:
https://github.com/apache/commons-text/pull/61
Personally I'm a +0 to +1 on this, but @PascalSchumacher has a very valid
point. I try to subscribe to the thought that there should be a high bar to
sacrificing simplicity. So, with that in
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-text/pull/61
In my opinion this is overkill. I don't think commons-text needs to be
tested against the eclipse java compiler and early access version of java 8 and
9. The script looks difficult to
Github user chtompki commented on the issue:
https://github.com/apache/commons-text/pull/61
I'll get to this soon.
---
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
