Re: [dali-dev] Latest non-compiling check-in

[Paul Fullbright <paul.fullbright@xxxxxxxxxx>]

Right now, it only adds the JPA facet to the project, which enables JPA 
UI support within the project.  Soonish, adding the facet will also add 
the generic JPA library (a user preference, similar to XDoclet) to the 
project classpath, and eventually, we'll have JPA support in "runtimes" 
such that each runtime will add its own JPA library to the project 
classpath (be it an enterprise runtime or an SE "runtime" such as 
Hibernate or TopLink Essentials, etc.)  Also, eventually, adding the JPA 
facet will add other project artifacts, such as persistence.xml or orm.xml.

- Paul


Max Rydahl Andersen wrote:
> ok - what does a "new JPA Project wizard" do ?
>
> (i'm mostly interested in what libraries it uses/setup)
>
> /max
>
> > All,
> >
> > I just checked in some code that does not compile unless you are 
> > working off of the WTP tip.  It's fine if you're not (I'm pretty 
> > sure), since the offending class is only involved with the new JPA 
> > Project wizard.  If you don't wish to work off the tip, you may still 
> > work off of the latest 1.5.1 build as long as you don't create JPA 
> > Projects by using this particular wizard.  You can still create JPA 
> > Projects by using the Utility Project wizard and choosing the 
> > "Utility JPA project with Java 5.0" config or by simply adding the 
> > JPA facet.
> >
> > - Paul
> > _______________________________________________
> > dali-dev mailing list
> > dali-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dali-dev
>
>
>
> ----
> Max Rydahl Andersen
> callto://max.rydahl.andersen
>
> Hibernate
> max@xxxxxxxxxxxxx
> http://hibernate.org
>
> JBoss a division of Red Hat
> max.andersen@xxxxxxxxx
> _______________________________________________
> dali-dev mailing list
> dali-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dali-dev