| Re: [dali-dev] JPA 2.1 EclipseLink 2.5 |
|
Mea culpa: I was using the DTP Juno release (1.10) because, when I saw the WTP download page listing a pre-req of DTP 1.10.1RC3, I did not read it carefully enough and missed that final ".1" before the "RC3" and took the Juno code, assuming the "RC3" was for the Juno release. Between those two versions, DTP bumped the allowable range for o.e.help.base from 4.0.0) to 5.0.0), which fixes the problem. The world [temporarily] makes sense again. :-) (i.e. I was wondering, "How, exactly, would the Smoke Tests pass???" :-) ) Brian -------- Original Message --------
Did you ever try to execute with this target? :-) The plug-in o.e.help.base upped its version from 3.6.100 in M2 to 4.0.0 in M3. As a result, lots of plug-ins do not load, cascading eventually to o.e.jpt.jpa.ui not loading. Rats! :-) On 11/14/2012 7:52 AM, Karen Butzke
wrote:
Everyone needs to update their target workspace to the WTP M3 build. I have referenced the 2.5 eclipselink-orm.xsd in org.eclipse.jpt.common.eclipselink.core plugin-xml. If you haven't already, I recommend changing several PDE problems to errors instead of warnings. Under 'Plugin Development' -> 'Compilers' -> 'References' change 'References to non-existent classes' and 'References to non-existent resources' to Error. _______________________________________________ dali-dev mailing list dali-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/dali-dev |