On Tue, Apr 28, 2015 at 8:51 AM, Alan Snyder wrote:
> Why not just postpone issuing the message until a task is attempted
> that needs the JDK?
Agreed.
But I guess it would require updating such tasks since it is likely that
such tasks today will likely just error out by not being able to load a
Why not just postpone issuing the message until a task is attempted that needs
the JDK?
> On Apr 28, 2015, at 6:42 AM, Jan Matèrne (jhm) wrote:
>
> I could implement a "suppress system property"
> (ant.suppress.toolsjar.warning).
> But I am not convinced of that idea ...
>
> What do the oth
I could implement a "suppress system property"
(ant.suppress.toolsjar.warning).
But I am not convinced of that idea ...
What do the other committers think of that?
Jan
> -Ursprüngliche Nachricht-
> Von: David J. B. Hollis [mailto:dhol...@aandoconsultancy.ltd.uk]
> Gesendet: Dienstag, 28
I wrote in the original email that I set JAVA_HOME which is why I was
asking, it seemed strange that it was using the wrong directory.
-Original Message-
From: Soni, Ashish IN BLR STS [mailto:ashish.s...@siemens.com]
Sent: Tuesday, April 28, 2015 00:41
To: user@ant.apache.org; gruener.hei
Hi Jan,
The DITA Open Toolkit uses ANT to build docs. This is a question that comes up
occasionally on the DITA Users forum.
A number of document CMS products use the DITA Open Toolkit, so a large number
of Technical Authors can potentially see this message.
If it could be suppressed, I'm sure
I thought using a custom Logger could solve your problem.
That logger would simply supress special messages.
But after failing tests I searched for that message:
Locator.getToolsJar() prints directly to SYSO:
public static File getToolsJar() {
... try to find tools.jar
if (!tool
