Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Hermes JPQL Parser Bundles

Just FYI. Build and Tests seem to have run fine., so I've deleted the foundation/org.eclipse.persistence.core.jpql fragment project.

All it's functionality is part of core now.


On 26/04/2012 6:54 PM, Eric Gwin wrote:
I've made an initial transaction for this.
The parent pom no longer builds core.jpql; the core manifest includes 1 new package for export, and imports hermes (optionally), and the core.jpa package has been added to the core src dir.

If the build goes as expected I will be deleting the core.jpql component project tomorrow.


On 25/04/2012 11:21 AM, Tom Ware wrote:
Hi All,

  As you probably know, we recently changed our JPQL parser from the ANTLR-based version that shipped in EclipseLink 2.3.x and prior releases to our new Hermes Parser which we share with the Dali project.

  Hermes currently ships as two bundles.

1. The org.eclipse.persistence.jpa.jpql bundle - this is the Hermes parser used by EclipseLink and Dali.  It has no dependencies on other EclipseLink code.

2. The org.eclipse.persistence.core.jpql fragment - this is glue code that makes use of the Hermes parser to build queries at EclipseLink runtime.

  Since Hermes is now the default parser, it does not make sense that part of it be maintained in a fragment.  I propose we move the all the org.eclipse.persistence.core.jpql code to our core bundle.

The following bug has been entered to track this suggestion.

If you have concerns, please add comments to the bug.

eclipselink-dev mailing list

eclipselink-dev mailing list

Back to the top