Hey Bryan, See if you can send an excerpt of the bundle:headers to show the proper imports. If this is a bug then they're going to need plenty of info.
Thanks Stephen -- Stephen Kahmann Software Engineer iNovex Information Systems, Inc. 937-321-1923 [email protected] Confidentiality Notice: This message is intended for the sole use of the individual to whom it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this communication is not the intended recipient or the employee or agent responsible for delivering the communication to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete this message. From: Bryan Miller Sent: Friday, July 10, 2015 3:08 PM To: [email protected] Reply To: [email protected] Subject: Deploying Multiple Version of Bundles Hello, I am trying to deploy multiple version of two sets of bundles and am running into issues. Bundle A version 1.0.0-SNAPSHOT requires: Bundle B version [1,2) Bundle C version [1,2) Bundle A version 2.0.0-SNAPSHOT requires: Bundle B version [2,3) Bundle C version [2,3) When I deploy Bundle A, B, and C version 1.0.0-SNAPSHOT and Bundle A,B, and C version 2.0.0-SNAPSHOT, Bundle A, regardless of version, will only wire to Bundle B or C if it was the most recently deploye bundle. For example if I deploy Bundle A(1.0.0-SNAPSHOT), then Bundle B (1.0.0-SNAPSHOT), then Bundle C(1.0.0-SNAPSHOT), then Bundle A(2.0.0-SNAPSHOT), then Bundle B(2.0.0-SNAPSHOT), then Bundle C(2.0.0-SNAPSHOT) This causes Bundle A(2.0.0-SNAPSHOT) to work, and Bundle A(1.0.0-SNAPSHOT) to give class cast exceptions. This also happens in reverse, if the 2.0.0-SNAPSHOT bundles are deployed first, the 1.0.0-SNAPSHOT bundles work and the 2.0.0-SNAPSHOT bundles have class cast exceptions. -- Bryan Miller
