The project is cleaned before each export using proguard

I have very strange behavior with proguard. Here is the situation.

In eclipse, if I just run the export command, I get the following errors. Along with many mistakes can't find referenced class. Also, the number 241 below seems to move, sometimes its 179, 290, etc.

[2012-05-22 15:54:33 - x] Warning: there were 241 unresolved references to classes or interfaces.
[2012-05-22 15:54:33 - x]          You may need to specify additional library jars (using '-libraryjars').
[2012-05-22 15:54:33 - x] Warning: there were 36 unresolved references to program class members.
[2012-05-22 15:54:33 - x]          Your input classes appear to be inconsistent.
[2012-05-22 15:54:33 - x]          You may need to recompile them and try again.
[2012-05-22 15:54:33 - x]          Alternatively, you may have to specify the option 
[2012-05-22 15:54:33 - x]          '-dontskipnonpubliclibraryclassmembers'.
[2012-05-22 15:54:33 - x] java.io.IOException: Please correct the above warnings first.
[2012-05-22 15:54:33 - x]   at proguard.Initializer.execute(Initializer.java:321)
[2012-05-22 15:54:33 - x]   at proguard.ProGuard.initialize(ProGuard.java:211)
[2012-05-22 15:54:33 - x]   at proguard.ProGuard.execute(ProGuard.java:86)
[2012-05-22 15:54:33 - x]   at proguard.ProGuard.main(ProGuard.java:492)

But if I do a clean and then export, it will not show an error, but it will not output console output at all. This first export after cleaning will result in a file being executed. If I try to export immediately after the previous export, it will fail again with the above errors.

Additional Information -

My workspace path and git repo paths don't have spaces in them.

proguard.cfg , /eclipse, "keep"

, proguard ( SVN OS X).

git egit. Egit git.

TL; DR; proguard , , ?

+3

All Articles