znerd/optipng-ant-task

Apache Ant task for creating optimized PNG images using OptiPNG.

optipng-ant-task's Issues

Refactor to allow functionality outside Ant

It would be nice if the OptiPNGTask would use an external Ant-independent class for invoking OptiPNG, so that that class can also be used from Java classes directly, without the need for the Ant runtime classes.
Such a class is not available in v0.2.

The "try" option does not work in v0.1

The "try" option has no effect in v0.1. It should work as documented in the README file instead.

Optipng change to stderr

As of version 0.7, optipng has changed their default output to using STDERR for everything. See the changelog here (search for STDERR)

http://optipng.sourceforge.net/history.txt

What this means is the optipng-ant-task will no longer work, because the file src/com/pensioenpage/jynx/optipng/OptiPNGTask.java around line 496 looks for any output to stderr and assumes that means the process failed.

The logic needs to be changed to account for this upstream change in optipng.

Add "overwrite" option

Add an "overwrite" option, similar to the "overwrite" option on the standard Ant COPY task.

Support 'level' option

OptiPNG supports the configuration of an optimizaton level via an option -o. The default value of this option is 2, while all integer values in the range 0 to 7 are supported.

This option should also be supported by the OptiPNG Ant task. It's not in v0.2.

Support 'fix' option

OptiPNG supports a fix option, which enables error recovery.

This parameter should also be supported by the Ant task. It's not supported in v0.2.

Support 'quiet' option

Currently, every invocation of the optipng-ant-task sends one message to standard output when running without the -verbose or -quiet Ant options.

It should be possible to suppress this message by passing quiet="true" or quiet="yes" to the task.

The message should then go to the MSG_VERBOSE level instead. So that if the task gets quiet="true", but Ant gets the -verbose option, still all the log messages are sent to the output.

This functionality is not in v0.2.

Source and destination directories cannot be the same

Looking at the code, the source and target directories can probably not be the same without causing some serious errors. This should be looked into and resolved, if necessary.