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 new web project 2. Create a JPA Entity in this project => When invoking code completion on the JPA API classes in this entity, Javadoc does not show up.
When I investigated more, i realized that the EclipseLink-GlassFish-v3 library was pointing to a Javadoc file from an old NB build, which no longer exists on my disk. When I updated this link, things started working. It looks like possibly the declaration in ~userdir/build.properties was not updated when I switched to a new build (property libs.EclipseLink-GlassFish-v3.javadoc). Still should be investigated.
I just tried to create web project on gf3, add new entity (with pu creation), I see javadoc for EntityManager, @GeneratedValue, @Id, @Entity etc. EclipseLink-GlassFish-v3 library isn't added to the project in this case.
I'm using 6.8 release installation for verification. Do you have wrong reference in 6.8 user dir?
and in build.properties I have {nb installation folder}/enterprise6/docs/javaee6-doc-api.zip
for libs.EclipseLink-GlassFish-v3.javadoc
Ok, now I know what are the exact steps to reproduce: 1. Install NetBeans and start it with a fresh user dir 2. Create a web project 3. Create an entity class, notice that Javadoc for e.g. javax.persistence.Entity appears correctly. 4. Shut down NetBeans 5. Rename the directory containing the NetBeans installation 6. Start up NetBeans from the new location, with the same userdir 7. Javadoc for javax.persistence.Entity is not found. When you open ~userdir/build.properties, notice that most references to the IDE installation have been updated automatically to the new location, except a few: libs.EclipseLink-GlassFish-v3.javadoc libs.Java-EE-GlassFish-v3.javadoc libs.restlib_gfv3ee6.javadoc So this is why the Javadoc does not appear. Looks like there will be the same problem for REST - cc'ing Milan.
I see EclipseLink-Glassfishv3 is maintained in glassfish.javaeev module. Vince is it yours? push back if in your opinion I should look.
may be eclipselink-gf library addition should be dropped as we have eclipselink bundled with base ide.
looks like web project on gf use this javadoc, when j2se project with eclipselink provider use libs.eclipselink.javadoc from bundled eclipselink library and I have no javadoc for @Entity in web project ans have one in j2se project at the same time.
tried to comment //ensureEclipseLinkSupport(glassfishRoot); in JavaEEServerModuleFactory and I don't have libs.EclipseLink-GlassFish-v3.* properties any more but still have valid javadoc as ee6 javadoc is widely used in ejb/web modules, but as EclipseLink-GlassFish-v3 isn't my implementation it's good to know if anybody know about any possible side effects. one good side effect I know there will be only one eclipselink library in Add Library list, but I have only 4 libraries in this list in recent code, may be something was changed in trunk.
*** Bug 178898 has been marked as a duplicate of this bug. ***
I just marked another bug as a dupe of this, but I'm starting to think it's not the same. My "build.properties" is pointing to the correct Netbeans 6.8 javadocs files for J2EE.
I just unmarked issue 178898 as being a dupe - there are similarities, but they are different. The root cause might be similar. Please take the time to read my latest comments on that issue.
http://hg.netbeans.org/web-main/rev/2c9ea32c631d
Integrated into 'main-golden', will be available in build *201004070201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/2c9ea32c631d User: Vince Kraemer <vkraemer@netbeans.org> Log: #178665: missing javadoc when install moved