Jan 22, 2009

Maven Problems

I still have not found a solution to the NoClassDefFoundError-problem, but a workaround. The workaround is to execute the code in NetBeans, or another IDE than Eclipse. When doing a release, I encountered yet another problem. This time it was Maven that issued a build error. The output from Maven looks like this:

....
[proguard] Warning: library class cldcunit.runner.ReflectionTestCaseHelper exte
nds or implements program class cldcunit.runner.BaseTestCaseHelper
[proguard] Warning: library class cldcunit.runner.ReflectionTestCaseHelper depe
nds on program class junit.framework.TestMethod
[proguard] Warning: library class cldcunit.runner.ReflectionTestCaseHelper depe
nds on program class junit.framework.TestMethod
[proguard] Warning: library class cldcunit.runner.ReflectionTestCaseHelper depe
nds on program class junit.framework.TestMethod
[proguard] Warning: library class cldcunit.runner.ReflectionTestCaseHelper depe
nds on program class junit.framework.Test
[proguard] Warning: there were 5 instances of library classes depending on prog
ram classes.
[proguard] You must avoid such dependencies, since the program classes
will
[proguard] be processed, while the library classes will remain unchang
ed.
[proguard] Error: Please correct the above warnings first.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Obfuscation failed (result=1)

What does this mean? To me it seems like ProGuard has found a problem with CLDCUnit. So this leaves me with still another issues that delays my release of a new Microlog version. Not good!

No comments: