Re: Early Access builds for JDK 8u122 b02 , JDK 9 & JDK 9 with Project Jigsaw b140 are available on java.net

2016-10-28 Thread Stefan Bodewig
On 2016-10-27, Tomas Zezula wrote: > Hi Stefan, >> On 24 Oct 2016, at 17:49, Stefan Bodewig wrote: >> On 2016-10-24, Tomas Zezula wrote: >>> I suppose you are using the JDK9 Jake build >>> (http://hg.openjdk.java.net/jigsaw/jake/) which prohibits >>> AccessibleObject.setAccessible even on typ

[GitHub] ant issue #26: corrected comments

2016-10-28 Thread bodewig
Github user bodewig commented on the issue: https://github.com/apache/ant/pull/26 Many thanks, Jeff! --- 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

[GitHub] ant pull request #26: corrected comments

2016-10-28 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ant/pull/26 --- 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 enabled

Re: ant wrapper script testing

2016-10-28 Thread Johan Corveleyn
On Fri, Oct 28, 2016 at 10:41 PM, Johan Corveleyn wrote: ... > Yes, that works perfectly! On Solaris 11, with your latest version of > the ant wrapper. When I run your test.sh, with the test.xml, I get > exactly the correct output. > > However, with esc_tool=awk it fails. Don't know why yet, but t

[GitHub] ant pull request #26: corrected comments

2016-10-28 Thread jwadamson
GitHub user jwadamson opened a pull request: https://github.com/apache/ant/pull/26 corrected comments Finally figured out why some behaviors were present. Originally thought sed was trimming whitespace in its output. I had not known that subshell output capture via either `` or

Re: ant wrapper script testing

2016-10-28 Thread Johan Corveleyn
On Wed, Oct 26, 2016 at 4:16 PM, Jeff Adamson wrote: > > I am feeling pretty good as the introduction of the newline to the printf > does not fundamentally change much about the updated processing. My main > concern was if that additional newline was going to make it into the final > arguments as