Community
Participate
Working Groups
All files with package org.eclipse.persistence.internal.jpa.metamodel couldn't be loaded on Glassfish-v3 when using "org.eclipse.persistence.jpa_2.1.0.qualifier.jar". That's because this package was missed within "Export-Package" in MANIFEST.MF file for this jar. By the way, this jar file is under \\trunk\plugins.
the problem is that manifests are either generated at buildtime using bnd, or if bnd is not found the build generates manually. The manual generation will always be wrong (but should work in most cases). The problem in this case is that builds are being done without bnd.
Kevin, This specific bug needs to be closed as the build process is working as designed. However, I agree it is not optimal. 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. So I'd like you to open a new bug stating that the build effectively requires bnd due to errors in the manual process, and it isn't well documented. I can then basically respond to that bug with a similar reply and use that bug to make the necessary build modifications. thanks. -Eric
Closing again. Kevin opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=312104 to address process concerns.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
