1. Create a Maven Java EE 6 web application
2. Create an Entity class - while going through the wizard, create a persistence unit with EclipseLink 2.0 as the provider.
3. Open pom.xml
You will see that EclipseLink was added with version 2.0.0-RC1 (non-final).
This can not be fixed for NB 6.8 FCS as EL 2.0 final is not available, but should be fixed in 6.8 patch
It will mean maven project may contain final eclipselink jars if server is set after pu creation when jee/j2se projects will contain rc1.
May different versions in maven project and on gf3 side cause problems also?
(if gf3 will use rc1 and will not include eclipselink final in some patch)
EclipseLink 2.0 has been released, it seems to be the same build as RC1 (20091127-r5931). So we don't need to worry about the bits themselves; the only thing that should change is the Maven URL: http://ftp.ing.umu.se/mirror/eclipse/rt/eclipselink/maven.repo/org/eclipse/persistence/eclipselink/2.0.0/
mark as fixed in 6.9 for now
Integrated into 'main-golden', will be available in build *200912111937* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: fix #178064 - changed eclipselink.jar url
The fix has been ported into the release68_fixes repository.