Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipselink-dev] Fwd: Re: NEW DEPENDENCY - Re: JPA 2.1 Entity Listener Injection Check-in

FYI: In case you are having problems with getting the dependency.

-------- Original Message --------
Subject: 	Re: [eclipselink-dev] NEW DEPENDENCY - Re: JPA 2.1 Entity Listener
Injection Check-in
Date: 	Mon, 07 Jan 2013 19:03:04 -0500
From: 	David Minsky <david.minsky@xxxxxxxxxx>
To: 	Tom Ware <tom.ware@xxxxxxxxxx>

Hey Tom,

Sharing my experience, in case people come to you with any difficulties:

The only way I could get (2.) to work (even using a brand new install of Eclipse
Juno SR-1 and an update, plus a new workspace to test) was to edit the Running
Platform (target definition) and explicitly add the folder ${eclipse_home}\dropins

Dropping the Orbit jar into plugins or dropins wouldn't work for me. It simply
wouldn't show up in the list of content or plugins. Tried basically everything,
permissions, read-only, re-downloading, re-packaging, even using the jar that
Maven grabbed from the command-line build. This is both with a new install of
Eclipse and my existing install.

Still, managed to hack this to get it to work for me.


On 07/01/2013 12:02 PM, Tom Ware wrote:
BTW, this check in adds a new dependency to the Eclipse Core project. (the
command line build will automatically pick it up).

To get the dependency, you have to options

1. Get the cdi.api_1.0.0 project from orbit
2. Copy cdi.api_1.0.0.v201105160744.jar to your Eclipse dropins directory and
refresh you target platform.  (Window - Preferences - Plug-in Development -
Target Platform - Reload)


On 07/01/2013 10:40 AM, Tom Ware wrote:

Checked in initial code to master stream.

Initial code has had injection manually tested and passed the JPA and Core LRGs.

Reviewed by Chris Delahunt

Still to come:

- some work on PreDestroy support
- automated testing
eclipselink-dev mailing list

Back to the top