bundle B can't see changes of classes of bundle A
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
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 (konstantine.koug...@akqa.com) 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
Re: bundle B can't see changes of classes of bundle A
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 njbartl...@gmail.commailto:njbartl...@gmail.com Date: Friday, 12 September 2014 16:49 To: users@felix.apache.orgmailto:users@felix.apache.org users@felix.apache.orgmailto:users@felix.apache.org, Konstantine Kougios konstantine.koug...@akqa.commailto:konstantine.koug...@akqa.com 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 (konstantine.koug...@akqa.commailto:konstantine.koug...@akqa.com) 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
Re: bundle B can't see changes of classes of bundle A
I found the issue, it was a problem in one of my bundle’s pom file, it did Export-Package a root level package and this made maven include ALL classes for that package into the jar (not only the ones of the bundle but classes from other bundles)! Is that to be considered a bug of maven-bundle-plugin or just my bad? Thanks, Kostas From: Neil Bartlett njbartl...@gmail.commailto:njbartl...@gmail.com Date: Friday, 12 September 2014 16:58 To: users@felix.apache.orgmailto:users@felix.apache.org users@felix.apache.orgmailto:users@felix.apache.org, Konstantine Kougios konstantine.koug...@akqa.commailto:konstantine.koug...@akqa.com Subject: Re: bundle B can't see changes of classes of bundle A How do you perform the bundle update? If you do not refresh packages, then bundle B will remain wired to the old version of bundle A… this is true even if you uninstall bundle A. After any mutation of the set of installed bundles, it is essential to perform a package refresh. Regards, Neil On 12 September 2014 at 16:52:36, Konstantine Kougios (konstantine.koug...@akqa.commailto:konstantine.koug...@akqa.com) wrote: 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 njbartl...@gmail.commailto:njbartl...@gmail.com Date: Friday, 12 September 2014 16:49 To: users@felix.apache.orgmailto:users@felix.apache.org users@felix.apache.orgmailto:users@felix.apache.org, Konstantine Kougios konstantine.koug...@akqa.commailto:konstantine.koug...@akqa.com 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 (konstantine.koug...@akqa.commailto:konstantine.koug...@akqa.com) 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
iPojo @Stereotype annotated annotation from separate bundle
Hi, Is the usage of a @Stereotype annotated annotation from another bundle supported? It doesn't seem to work even though the package is properly exported and imported. The docs only say: If the stereotyped annotation is directly in the manipulated module, no problems: any front-end will work as expected. If not, the different manipulator's front-end have variable support for the stereotype feature. This is not very clear to me and to be honest I'm no sure what a manipulator's front-end is. Regards, Milen -- http://about.me/milen
