Eclipselink.jar bundle - fix (#1496)

Signed-off-by: Radek Felcman <>
1 file changed
tree: 8cdf8c6adebcebd8e31f0a514b1132b60b0c96fa
  1. .github/
  2. bundles/
  3. dbws/
  4. etc/
  5. features/
  6. foundation/
  7. jpa/
  8. moxy/
  9. performance/
  10. project-admin/
  11. sdo/
  12. src/
  13. testing/
  14. utils/
  15. .gitattributes
  16. .gitignore
  17. .lgtm.yml
  19. findbugs-exclude.xml
  22. pom.xml

Language grade: Java Total alerts

EclipseLink master (3.1.x) Maven Central Jakarta Staging (Snapshots) Master Build Status

EclipseLink 3.0.0 Maven Central 3.0 Build Status

EclipseLink 2.7.x Maven Central 2.7.x  Build Status


The EclipseLink project's goal is to provide a complete persistence framework that is both comprehensive and universal. It will run in any Java environment and read and write objects to virtually any type of data source, including relational databases, XML, JSON, or EIS systems. EclipseLink will focus on providing leading edge support, including advanced feature extensions, for the dominant persistence standards for each target data source; Jakarta Persistence for relational databases, Jakarta XML Binding for XML, Jakarta Connectors for EIS and other types of legacy systems, and Service Data Objects (SDO).

This project is part of the EclipseLink project.


EclipseLink is dual licensed under an EPL 2.0 and EDL 1.0 license.


We use contribution policy, which means we can only accept contributions under the terms of Eclipse Contributor Agreement.


Issue/bug trackers

Hint: If it‘s possible, it helps if some test reproducer is attached to the new bug. If it’s not possible, attached entities and persistence.xml file should help too for JPA related bugs. For MOXy, entities and XML or JSON resources/files are welcome.