proguard there were 5 instances of library classes depending on program classes

[karsten]

Since today I get during the proguard processing:

[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.

[Vlad Skarzhevskyy]

Hi Karsten
Do you have scope 'provided' for cldcunit-se in your maven pom?
Also exclude library cldcunit-se from proguard processing for J2ME application.
See the build for module 'bluecove-tester' in bluecove as example how
to do this.

So you have only one warning:
Note: junit.framework.TestCase: can't find dynamically referenced
class cldcunit.runner.ReflectionTestCaseHelper

--
Vlad

[karsten]

On 28 Dez., 02:03, "Vlad Skarzhevskyy" <skarzhevs...@gmail.com> wrote:
> Hi Karsten
>  Do you have scope 'provided' for cldcunit-se in your maven pom?

Yes.

>  Also exclude library cldcunit-se from proguard processing for J2ME application.
>  See the build for module 'bluecove-tester' in bluecove as example how

OK.