This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
1. Create a Maven web project (Java EE 6, GlassFish 4 target server) 2. Create a persistence unit in this project, use "Hibernate (JPA 2.0)" persistence provider => pom.xml contains the following: <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-core</artifactId> <version>3.6.10.Final</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> <version>3.6.10.Final</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-commons-annotations</artifactId> <version>3.2.0.Final</version> </dependency> This is an outdated version, the latest version should be used instead.
3.6.10 in 7.4 is jpa 2.0 provider, we can't bundle 3.6.10 for framework support and some latest 4.x for persistence purpose in my opinion, in general we can say we supply only one main provider as latest - eclipselink and other providers may be either not latest or not bundled at all. maven have some specific issues also, I'll check after a few days.
> we can't bundle 3.6.10 for framework support Did you mean "we can't bundle 4.x"? In that case I am thinking if enhancement issue 231443 could help - we would continue to physically bundle 3.6.10, but the IDE would also have the knowledge of 4.x via the "Maven only library" described in the issue above, and this library would be offered in the persistence providers combo box.
yes, "can't" was about 4.x and it wasn't "can't" completely but with a lot of time resources. but now I'm not sure, it may be easier but I need more time to verify anyway. regarding library binded to hibernate provider, it may not be possible without #171973 fix. if "maven only" will have the same jpa version as bundled one, only one will be chosen but if maven one will be jpa 2.1 both may be shown and are used.
With no much resources we can't update with each new release, I would like to update after hibernate with jpa2.1 support release. also current use case "1. Create a Maven web project (Java EE 6, GlassFish 4 target server) 2. Create a persistence unit in this project, use "Hibernate (JPA 2.0)" will not work anyway, because gf4 do not support neither 3.x nor 4.x hibernate as jpa2.0 provider.
we have a strong dependency on hibernate tools, with the issue like https://bugzilla.redhat.com/show_bug.cgi?id=867418 I have to stay with 4.1.1 hibernate for now, attempt to update to 4.2.6 failed because of the issue, it may be a problem for 4.3/5.x update also.
I'm figting with pojo generation now and have some classloader issues, my custom classloader isn't used at all, wonder if https://hibernate.atlassian.net/browse/HHH-7084 may be related and it may be a stopper in this case as one issue cause 4.1.1- usage when another force 4.1.4+
should be updated now to 4.2.6 but have to keep some old jars for framework support. need to look at future development of hibernate-tools is there will be any to remove obsolete parts.
better to file separate task for artifact jars