>> Since some projects raised concerns that they are unable to react to a >> changed packaging I propose we fix this >> by adding the missing 4.5.6 classes which were present in 4.5.5. >> >> Or we file new CQs for 4.5.7 which was released meanwhile in >> January and directly update to this newer maintenance release. > > ^ Sounds as best option to me.
Please take into account that beyond the missing packages, I think we should also ensure that we agree on a single httpclient version for the release train. In the past we've had hard to reproduce issues with faulty wiring and classloader problems when there were multiple versions present. This can happen when bundles expose types from the library in their own signatures and this way clients get exposed to the same types from different versions through different classloaders. For MPC this was the case in the past due to Userstorage SDK exposing httpclient API without having uses-declarations in its manifest. That should be fixed with https://git.eclipse.org/r/c/136312/, but I think other projects had similar issues. _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
