Bugzilla – Full Text Bug Listing
| Summary: | Need documentation for EclipseLink build locally | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Kevin Yuan <kevin.yuan> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | tom.ware | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Kevin Yuan
I agree there are issues with the bnd process. The intent had been to check-in Bnd after we recieved CQ approval and remove the manual manifest generation option in the build, but the CQ approved version of Bnd has a bug that renders it unusable. We could submit another CQ, but it is a long process. It is also possible that in the future we will want to upgrade to a newer version of bnd to get new features, and have to start the process once again. Therefore, after discussed this with some other comitters and Peter, we've decided to move now to requiring bnd. If bnd is not found an error message will display saying that it is needed, where to get it, and give an option to be able to run without it, by using the checked-in manifest we currently use for Eclipse-based development. Created attachment 167980 [details]
fixes to reuire bnd and self-document usage.
This patch modifies the existing OSGi bundle projects build files to require the use of BND, and document how to install it along with other options.
merged patch. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |