Clean Code for ds/org.eclipse.pde.ds.tck#2178
Conversation
|
Hi @eclipse-pde-bot — thank you for your contribution! The Eclipse Contributor Agreement (ECA) check has failed for this pull request due to one of the following reasons:
To resolve this, please:
Once done, push a new commit (or rebase) to re-trigger the ECA validation. If you believe you've already completed these steps, please double-check your account settings or report an issue to Eclipse Foundation Helpdesk. Thanks again for your contribution! |
ea4d800 to
5919c6f
Compare
d7641d8 to
716318d
Compare
716318d to
5d5de3d
Compare
There was a problem hiding this comment.
Pull request overview
Cleans up the org.eclipse.pde.ds.tck bundle metadata as part of broader formatting/dependency hygiene for the DS TCK project.
Changes:
- Removes the
Import-Packageheader from the DS TCK bundle manifest.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Bundle-Version: 1.0.0.qualifier | ||
| Import-Package: org.osgi.framework, | ||
| org.osgi.service.component, | ||
| org.osgi.service.component.propertytypes, | ||
| org.osgi.service.log | ||
| Service-Component: OSGI-INF/org.osgi.impl.bundle.component.annotations.HelloWorld10.xml, |
There was a problem hiding this comment.
Removing the Import-Package header entirely means this bundle will not be wired to any org.osgi.* packages at runtime. Since this project unpacks and builds the OSGi DS annotations TCK sources during the Maven build (see pom.xml unpack-dependencies + PDE build), the compiled classes are very likely to reference org.osgi.framework / DS / Log APIs and will fail with ClassNotFoundException at runtime if these packages are not imported. Please restore the required Import-Package entries (or switch to an automated manifest generation approach that computes them from the built classes) so the bundle resolves its API dependencies correctly.
The following cleanups were applied:
The following Manifest cleanups where applied: