https://bz.apache.org/bugzilla/show_bug.cgi?id=63248
--- Comment #2 from Jaikiran Pai ---
I had a look at the patch and it looks mostly fine to me. Except this bit:
> +if (ftp.sendCommand("FEAT") != 211) {
> +log("Failed to issue Feat Command: ", Project.MSG_WARN);
I read
https://bz.apache.org/bugzilla/show_bug.cgi?id=63252
--- Comment #2 from Jaikiran Pai ---
I had a look at the patch. Upon the "idle" timeout being reached, as you note,
you trigger a command from the client, which happens to be:
> The command used to trigger a data connection is a LIST on the
https://bz.apache.org/bugzilla/show_bug.cgi?id=63259
Jaikiran Pai changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
This is an automated email from the ASF dual-hosted git repository.
jaikiran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant.git
The following commit(s) were added to refs/heads/master by this push:
new 0259c0b bz-63259 Don't check the FTP file for
https://bz.apache.org/bugzilla/show_bug.cgi?id=63071
william.rup...@oracle.com changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #2
https://bz.apache.org/bugzilla/show_bug.cgi?id=63438
--- Comment #4 from Mikhail T. ---
(In reply to Jaikiran Pai from comment #3)
> But before getting to any of that
Let's implement the fixes in parallel with -- rather than after -- figuring
out, why JDK is the way it is...
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=63438
--- Comment #3 from Jaikiran Pai ---
What I meant in my previous reply was that, based on the documentation of the
javadoc tool shipped in the JDK (the one which we use in that task), I don't
expect that tool to fail with an error in first
https://bz.apache.org/bugzilla/show_bug.cgi?id=63438
--- Comment #2 from Mikhail T. ---
(In reply to Jaikiran Pai from comment #1)
> However, I'm unsure why the javadoc tools errors out in such cases
It errors out because of the explicit "failonerror=true" in the
element :)
The quick-dirty
https://bz.apache.org/bugzilla/show_bug.cgi?id=63438
--- Comment #1 from Jaikiran Pai ---
I was able to reproduce this. The javadoc tool seems to error out and exit with
a non-zero exit code when it cannot resolve a "reference". You can, in fact,
find 26 "reference not found" errors which match
