Bugzilla – Full Text Bug Listing
| Summary: | Remove deprecated OSGi Support | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Shaun Smith <shaun.smith> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | edwin.tang, eric.gwin |
| Version: | unspecified | Flags: | eric.gwin:
documentation+
eric.gwin: kepler+ |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Shaun Smith
The simplest initial steps would include not building or shipping the bundles. It is a very easy thing to stop shipping them. Removing them from the build is a logical next step and is also fairly simple. I just need to know exactly what to stop shipping/building. are we talking the o.e.p.osgi bundle? Tom mentioned equinox and weaving, so I want to verify. I believe our current default is Gemini is it not? Removing the code linkage to the deprecated OSGi support is something Tom would need to do however. After speaking with Peter, then Tom it looks like the o.e.p.jpa.osgi, o.e.p.jpa.equinox, and o.e.p.equinox.weaving jars need to be removed from the build. So as a first step, I am removing those three jars from the build, our P2 features, install bundles, eclipselink.jar, and our maven publishing. removed o.e.p.jpa.osgi, o.e.p.jpa.equinox, o.e.p.jpa.equinox.weaving from build, PublishToMaven, and P2 generation. Also removed unnecessary definitions associated with them. Also had to exclude: org.eclipse.persistence.testing.tests.jpa.deployment.CompositeEnumerationTest and comment out references to it in org.eclipse.persistence.testing.tests.jpa.FullRegressionTestSuite in order for the jpa.test build to complete successfully. After tonight's build the code can be removed from the repository. The Nightly QA matrix has failures as a result. eclipselink.osgi.test can either be adapted to Gemini or removed from the nightly testing entirely (I don't know that adapting makes any sense as I'd assume that similar tests are already run for our Gemini support). Full removal will need to wait until QA can remove the test execution from the nightly automation scripts. Just made a change on the automation scripts. Now the nightly testing does not execute the OSGi tests anymore. 2.5.0 no longer ships or builds the bundles, but the code is still in the repo. Should it be removed before closing this bug? closing as I have opened bug# 404478 to track removal of the code from the codebase. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |