Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix two minor OSGi metadata issues caused by upgrade to bundleplugin …
…3.5.0: * _versionpolicy instruction should now be _consumer-policy * forked builds (like the 'no_aop' munged build) will now attempt to merge in headers from the main jar. This overwrites the custom 'no_aop' headers so we need to exclude Bundle-Name and Import-Package from this merging in the core build to keep those 'no_aop' differences. Neither of these issues stop someone from deploying Guice 4.2 on OSGi. It's just the first issue means they'd have to deploy a specific version of Guava. Versions after 23.x wouldn't be allowed due to an unnecessarily strict range, because our relaxed policy wasn't picked up. Whereas the second issue is more cosmetic and is about preserving the custom 'no_aop' name and its simpler imports.
- Loading branch information