So lets say I modify the toString method of a class in A. Then B when using the 
toString(), it gets the old value (the one before A was modified)

Also, I can uninstall A but B still works! And I’ve verified B.jar doesn’t 
include A classes or A.jar.

Thanks,

Kostas


From: Neil Bartlett <[email protected]<mailto:[email protected]>>
Date: Friday, 12 September 2014 16:49
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>, Konstantine Kougios 
<[email protected]<mailto:[email protected]>>
Subject: Re: bundle B can't see changes of classes of bundle A

Can you be more specific about what this phrase means: “bundle doesn’t see the 
change”? It’s best to describe exactly what behaviour you expected, then how 
the actual behaviour differed from that.

Kind regards,
Neil



On 12 September 2014 at 16:03:16, Konstantine Kougios 
([email protected]<mailto:[email protected]>) wrote:

Hi,

I am trying to sort out a very weird issue for a few hours now. I got 2 
bundles, A and B.

A has a class JsonObject and B has tests that run on the server (via 
sling-junit). So when I change a class in A and deploy it via 
mvn/mvn-sling-plugin , my B bundle doesn’t see the change. If I refresh B or 
stop/start B, again it doesn’t see the change of JsonObject. Only a mvn clean 
install fixes the issue.

I’ve checked both bundle jar files to see if there are duplicate classes or 
maybe B includes A.jar, but no, the jars seem proper.

Any ideas?

Thanks,

Kostas

Reply via email to