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.
Build: NetBeans IDE 6.0.1 dev (Build 200801100000) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b02 OS: Windows XP, 5.1, x86 User Comments: 1) Added postgre driver jar to project
Created attachment 55556 [details] stacktrace
definitely not core problem - reassigning to IDE, I have no idea where issues about compapp module belongs... java.lang.ClassNotFoundException: org.netbeans.modules.compapp.projects.base.queries.SameDriveCollocationQuery
reassigning to enterprise/compapp
Build: NetBeans IDE Dev (Build 20080212092625) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Linux, 2.6.22-14-generic, i386 User Comments: -go to open project -select websvc.kit from nb module hg.nb.org/main => CNFE
Created attachment 56598 [details] stacktrace
I think this has been fixed in SOA.
I still can reproduce this issue with latest build. Steps to reproduce: 1. Click "New > New Project". 2. Select "Web" and "Web Application". Click Next. 3. Enter project name, choose application server and set J2EE Version to "Java EE 5". Click Next. 4. Check "Project shared with other users" checkbox. Result: ClassNotFoundException arises. I built IDE from fresh sources.
Chikkala, could you take a look at this one?
I can not reproduce the bug. I have tested this with dev build Product Version: NetBeans IDE Dev (Build 200803021202) Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Netbeans\nbdev\userdir also I have build ide from source on March 04th ( using ant -Dconfig.cluster=soa ) and tested. I can not reproduce in either builds. Please check with the current build and see if this is still a problem and provide steps to reproduce or attach the project that can be used to reproduce this problem.
I still can reproduce it with latest sources. Note that I use not build from www.netbeans.org, I build IDE from fresh sources on my machine. Then do: 1. Start IDE. 2. Add GlassFish. 3. Click "New > New Project". 4. Select "Web" and "Web Application". Click Next. 5. Enter project name, choose application server and set J2EE Version to "Java EE 5". Click Next. 6. Check "Project shared with other users" checkbox. Result: ClassNotFoundException arises.
Please provide these details 1. Where did you get your netbeans sources from? I am also building netbeans from source and my sources are from the mercurial repository (hg.netbeans.org) 2. How are you buidling. I mean which clster configuration you are building? all, j2ee or soa? I am building the source using "soa" cluster configuration. 3. which glassfish version you are using?
I do following: hg clone http://hg.netbeans.org/main/ cd main ant I use GlassFish, which is bundled with latest developers version of NetBeans: GlassFish V2 UR1.
I just updated my sources (hg fetch) and did a fresh build as you mentioned (cd main; ant) and used glassfish v2 u1. I could not reproduce the bug. It works for me. My netbeans after fresh build is Product Version: NetBeans IDE Dev (Build 080306) Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\home\chikkala\dev\nb\main\nb_all\test\userdir Please let me know what is your configuration and can you list the files and directories in your nb installation path ( nbbuild\netbeans\**\* )? Are you starting the netbeans with fresh userdir?
OK. Now I also can't reproduce this issue. I had a problem with sanity tests and therefore I decided to remove all sources and clone repository again. After this I wasn't able to reproduce this issue. Probably there were some old problems, which weren't removed with hg. Thanks for patience. ;)
Verified with build 080307.
Reopening - reproduced in NetBeans IDE 6.1 (Build 200809240102) http://statistics.netbeans.org/exceptions/detail.do?id=125399
Can't reproduce. Most likely due to old userdir content from previous NetBeans versions. To fix, use a brand new userdir.
Following the Steps to Reproduce, I did not encounter the problem with 4/2/09 build