Caution: In this restricted "Fossies" environment the current HTML page may not be correctly presentated and may have some non-functional links.
Alternatively you can here view or download the uninterpreted raw source code.
A member file download can also be achieved by clicking within a package contents listing on the according byte size field.
By now, I've invested a fair amount of time in ProGuard. You can help
by providing feedback! If you have problems, bugs, bug fixes, ideas,
encouragements, etc., please get in touch:
we provide professional support for ProGuard. If you find ProGuard useful
and you would like to have some professional backing, this is the place to
The help forum (at SourceForge) is the right place to ask
questions about any problems you might have configuring and running
ProGuard. At this time, I can generally only assist other open source
projects though. If you're working on commercial software, please consider
our professional support above.
The bug tracking page (at SourceForge) allows you to submit
and consult bug reports. Please make sure the reports are complete and
concise. If I can't reproduce the problem, I most likely can't fix it
The feature request page (at SourceForge) allows you to
submit and consult feature requests. I generally have my own road map in
mind, but this is the place express your interest in new and existing
The download section at SourceForge and the project page at FreshMeat offer the possibility to
subscribe to the announcements of new releases. They are the most
efficient way to stay abreast of the latest developments.
For anything that doesn't fall in the above categories, you can mail me
I can't promise a swift answer, or any answer at all, for that matter, but I
like seeing any constructive comments.
ProGuard isn't a typical open source project, in the sense that I am
not looking for code contributions. Developing on my own allows me to
do things my way, without the overhead and compromises associated with larger