NetBeans Forums
| View previous topic :: View next topic |
| Author |
Message |
originalbryan
Joined: 27 Apr 2009
Posts: 7
|
 Posted: Thu May 07, 2009 1:42 pm Post subject: package XXX does not exist. Package XXX does exit. |
 |
|
Hi all,
I believe this topic has halfway been covered before, but I didn't see anyone with this type of issue.
I have a java file calling
| Code: | import com.icesoft.faces.async.render.OnDemandRenderer;
import com.icesoft.faces.async.render.RenderManager;
import com.icesoft.faces.async.render.Renderable;
import com.icesoft.faces.component.ext.RowSelectorEvent;
import com.icesoft.faces.component.jsfcl.data.CachedRowSetSortableDataModel;
import com.icesoft.faces.webapp.xmlhttp.PersistentFacesState;
import com.icesoft.faces.webapp.xmlhttp.RenderingException; |
The editor complains on each of those that "package PACKAGE_NAME does not exist". I can see the package under Projects -> MyProjectName -> Libraries -> icefaces.jar. Also, the app builds, deploys, and runs perfectly.
My question is why NetBeans is continuing to complain about this. As you might imagine, supposedly missing packages results in some wild error highlighting and is making development difficult.
Using NetBeans IDE 6.5.1 with only the ICEfaces plugins added. |
|
| Back to top |
|
 |
Jiri Prox
Posted via mailing list.
|
| Posted: Tue May 12, 2009 3:28 pm Post subject: package XXX does not exist. Package XXX does exit. |
|
|
Hi,
this is bug - the internal cache is probably broken. The quick
workaround for this issue is to clear the cache and let it be
regenerated. To do so just locate your userdir and delete
{userdir}/var/cache/index directory. It will be regenerated with correct
content. If the problem persists or appears again please file a new
issue providing as many info as you can (project type, JDK version,
library jars etc...)
Thanks
Jirka
originalbryan wrote:
| Quote: | Hi all,
I believe this topic has halfway been covered before, but I didn't see anyone with this type of issue.
I have a java file calling
Code:
import com.icesoft.faces.async.render.OnDemandRenderer;
import com.icesoft.faces.async.render.RenderManager;
import com.icesoft.faces.async.render.Renderable;
import com.icesoft.faces.component.ext.RowSelectorEvent;
import com.icesoft.faces.component.jsfcl.data.CachedRowSetSortableDataModel;
import com.icesoft.faces.webapp.xmlhttp.PersistentFacesState;
import com.icesoft.faces.webapp.xmlhttp.RenderingException;
The editor complains on each of those that "package PACKAGE_NAME does not exist". I can see the package under Projects -> MyProjectName -> Libraries -> icefaces.jar. Also, the app builds, deploys, and runs perfectly.
My question is why NetBeans is continuing to complain about this. As you might imagine, supposedly missing packages results in some wild error highlighting and is making development difficult.
Using NetBeans IDE 6.5.1 with only the ICEfaces plugins added.
|
|
|
| Back to top |
|
|
qkrijger
Joined: 27 Jul 2009
Posts: 9
|
| Posted: Sat Aug 01, 2009 10:58 am Post subject: |
|
|
I confirmed that this issue exists in 6.7 as well. It bugged ( ) me pretty much until I found this post, but clearing the cache dir fixed it. After, Netbeans rescans classpaths and projects. So thanks for you posts here!
In my case, the issue arose after I moved (by refactor) a package of my library into another package in the same library. The funny thing is that "clean and build" continues to work , but run does not, due to compilation errors. |
|
| Back to top |
|
|
Petr Dvorak
Posted via mailing list.
|
| Posted: Sat Aug 01, 2009 8:53 pm Post subject: package XXX does not exist. Package XXX does exit. |
|
|
| Quote: | The funny thing is that "clean and build" continues to work , but
|
run does not, due to compilation errors.
Maybe it is because the "Compile on Save" feature is turned on (open
project properties and see the Compiling section - there is a control to
disable it CoS). I believe the Run action uses different class files
than the ones created by Clean&Build when CoS is on (which is correct,
when you think about it)...
--pd
qkrijger wrote:
| Quote: | I confirmed that this issue exists in 6.7 as well. It bugged () me pretty much untill I found this post, but clearing the cache dir fixed it. After, Netbeans rescans classpaths and projects. So thanks for you posts here!
In my case, the issue arose after I moved (by refactor) a package of my library into another package in the same library. The funny thing is that "clean and build" continues to work , but run does not, due to compilation errors.
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
