*We already use Maven* , with the correct dependencies - but the wizard only lists the JPA 3.0 support if there is a suitable library available on the Tools Libraries screen.
On 23 November 2023 20:53:52 GMT, "Matthias Bläsing" <mblaes...@doppel-helix.eu.INVALID> wrote: >Hi Stephen, > >Am Donnerstag, dem 23.11.2023 um 00:09 +0000 schrieb Stephen G. Parry: >> >> 1. There are no JPA 3.1 libraries in the Libraries list. Without a >> suitable entry in the list, JPA 3.1 does not appear as an option in the >> wizards, e.g. the Persistence Unit wizard. The project dependencies seem >> to have no effect on this. This can be worked around by creating a new >> library entry yourself and adding the jakarta persistence API, >> EclipseLink and Jakarta Activation API, plus javadocs and sources. This >> is a fiddly process. > >my advice: teach your students how to include the right dependencies >from maven. A minimal pom.xml should be doable and opens options for >the future. > >You can open an issue about this, but if you don't fix it yourself >there is a pretty high likelyhood, that no one else will do it. > >> 2. If you do add the library entry, The new API is 'unlocked', but is >> incorrectly identified in the dropdown of the persistence unit wizard as >> EclipseLink (JPA 3.0) > >You mean it should be JPA 3.0+? I have some doubts that the wizard >create anything that is not compatible wiht 3.0 and 3.1. > >Greetings > >Matthias > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org >For additional commands, e-mail: dev-h...@netbeans.apache.org > >For further information about the NetBeans mailing lists, visit: >https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
