xmlgraphics-batik-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46926] [PATCH] More control over RasterizerTask output files
Date Wed, 22 Apr 2009 14:22:16 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46926


Martin von Gagern <Martin.vGagern@gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #23422|0                           |1
        is obsolete|                            |




--- Comment #3 from Martin von Gagern <Martin.vGagern@gmx.net>  2009-04-22 07:22:14
PST ---
Created an attachment (id=23529)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23529)
Patch version 3

(In reply to comment #2)
> From the main "build.xml" file:
> 
>   If you are going to be doing development you may want to create a file
>   called 'build.properties' with the line 'debug=on' in it.  This will 
>   turn on the generation of debugging information when compiling Batik.
> 
> I'm not sure if it would be a good idea to make this here also but, at least,
> creating a property "debug" and using 'debug="${debug}"' instead (for
> coherency with the main build file) looked like a good idea. :-)

Did that, and also loaded the build.properties from the batik root directory.

> Finally, I believe the patch should also address some documentation regarding
> the newly introduced features.

Sure. I finally found the time to write a few words about this.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org


Mime
View raw message