Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Sun Sep 05, 2010 5:02 pm Post subject: How utterly weird... |
|
|
Razed local copy, got a new one from SVN. Lost a few cosmetic changes.
On 5 September 2010 18:18, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | A project has decided not to compile...
It gives me the following message:
C:\Documents and Settings\Owen Thomas\My Documents\NetBeansProjects\AgentDevice\nbproject\build-impl.xml:896: The following error occurred while executing this line:
C:\Documents and Settings\Owen Thomas\My Documents\NetBeansProjects\AgentDevice\nbproject\build-impl.xml:957: The following error occurred while executing this line:
java.io.FileNotFoundException: C:\Documents and Settings\Owen Thomas\My Documents\ClientDeviceMedia\nbbuild.xml (The system cannot find the path specified)
|
|
| Back to top |
|
 |
Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Sun Sep 05, 2010 5:04 pm Post subject: How utterly weird... |
|
|
Why might my editor be telling me, quite out of the blue, that it cannot find a class defined in another package.
I have changed absolutely nothing. It was working fine when I shut NB down, and now that I have restarted it, I am being given an arbitrary error...
The project won't build.
Why!?
|
|
| Back to top |
|
 |
Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Sun Sep 05, 2010 5:07 pm Post subject: How utterly weird... |
|
|
I appear to have fixed it. I renamed the Class. NetBeans said a NullPointerException was thrown, and that I should report this as a bug to the bug reporting authority. I didn't do this. I then noticed that the name of the class had changed but the name of the file hadn't (or was it vice versa - who knows), so I changed the class name. The reference error in the other source files disappeared.
On 5 September 2010 12:33, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | Okay, I have a class, say X, that I have implemented in project 1. In project 2, I have included project 1 as an external project import and used class X in class Y defined in project 2. The editor is currently showing a wavy red line underneath the import of class X in class Y, and is showing a wavy red line elsewhere in the same, and any other source file that uses class X in project 2.
For years, this arrangement worked without incident. It works without incident for all the thousands of other like arrangements that rely on an identical structure.
Project 2 builds fine, so some thing is not working in NetBeans.
What do I do to get NetBeans to behave properly?
On 5 September 2010 11:57, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | No, my error, it builds fine, yet the editor is telling me that a class doesn't exist.
Why!?
On 5 September 2010 11:55, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | Why might my editor be telling me, quite out of the blue, that it cannot find a class defined in another package.
I have changed absolutely nothing. It was working fine when I shut NB down, and now that I have restarted it, I am being given an arbitrary error...
The project won't build.
Why!?
|
|
| Back to top |
|
 |
Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Sun Sep 05, 2010 5:11 pm Post subject: How utterly weird... |
|
|
Okay, I have a class, say X, that I have implemented in project 1. In project 2, I have included project 1 as an external project import and used class X in class Y defined in project 2. The editor is currently showing a wavy red line underneath the import of class X in class Y, and is showing a wavy red line elsewhere in the same, and any other source file that uses class X in project 2.
For years, this arrangement worked without incident. It works without incident for all the thousands of other like arrangements that rely on an identical structure.
Project 2 builds fine, so some thing is not working in NetBeans.
What do I do to get NetBeans to behave properly?
On 5 September 2010 11:57, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | No, my error, it builds fine, yet the editor is telling me that a class doesn't exist.
Why!?
On 5 September 2010 11:55, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | Why might my editor be telling me, quite out of the blue, that it cannot find a class defined in another package.
I have changed absolutely nothing. It was working fine when I shut NB down, and now that I have restarted it, I am being given an arbitrary error...
The project won't build.
Why!?
|
|
| Back to top |
|
 |
Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Sun Sep 05, 2010 5:12 pm Post subject: How utterly weird... |
|
|
I believe it to b vice versa because I didn't have to re-rename (un-rename) the file.
On 5 September 2010 13:44, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | I appear to have fixed it. I renamed the Class. NetBeans said a NullPointerException was thrown, and that I should report this as a bug to the bug reporting authority. I didn't do this. I then noticed that the name of the class had changed but the name of the file hadn't (or was it vice versa - who knows), so I changed the class name. The reference error in the other source files disappeared.
On 5 September 2010 12:33, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | Okay, I have a class, say X, that I have implemented in project 1. In project 2, I have included project 1 as an external project import and used class X in class Y defined in project 2. The editor is currently showing a wavy red line underneath the import of class X in class Y, and is showing a wavy red line elsewhere in the same, and any other source file that uses class X in project 2.
For years, this arrangement worked without incident. It works without incident for all the thousands of other like arrangements that rely on an identical structure.
Project 2 builds fine, so some thing is not working in NetBeans.
What do I do to get NetBeans to behave properly?
On 5 September 2010 11:57, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | No, my error, it builds fine, yet the editor is telling me that a class doesn't exist.
Why!?
On 5 September 2010 11:55, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | Why might my editor be telling me, quite out of the blue, that it cannot find a class defined in another package.
I have changed absolutely nothing. It was working fine when I shut NB down, and now that I have restarted it, I am being given an arbitrary error...
The project won't build.
Why!?
|
|
| Back to top |
|
 |
Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Sun Sep 05, 2010 5:12 pm Post subject: How utterly weird... |
|
|
A project has decided not to compile...
It gives me the following message:
C:\Documents and Settings\Owen Thomas\My Documents\NetBeansProjects\AgentDevice\nbproject\build-impl.xml:896: The following error occurred while executing this line:
C:\Documents and Settings\Owen Thomas\My Documents\NetBeansProjects\AgentDevice\nbproject\build-impl.xml:957: The following error occurred while executing this line:
java.io.FileNotFoundException: C:\Documents and Settings\Owen Thomas\My Documents\ClientDeviceMedia\nbbuild.xml (The system cannot find the path specified)
|
|
| Back to top |
|
 |
Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Sun Sep 05, 2010 5:28 pm Post subject: How utterly weird... |
|
|
No, my error, it builds fine, yet the editor is telling me that a class doesn't exist.
Why!?
On 5 September 2010 11:55, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | Why might my editor be telling me, quite out of the blue, that it cannot find a class defined in another package.
I have changed absolutely nothing. It was working fine when I shut NB down, and now that I have restarted it, I am being given an arbitrary error...
The project won't build.
Why!?
|
|
| Back to top |
|
 |
sergej
Joined: 18 Aug 2008 Posts: 99 Location: Cremona (ITALY)
|
Posted: Sun Sep 05, 2010 5:33 pm Post subject: How utterly weird... |
|
|
Sometimes it happens to me also to see wrong error indicators.
I perform a clean/build to be sure NB is wrong; then, if compilation is OK and errors are
again alive and well, I shut down NB, go to ${HOME}/.netbeans/6.9/var/cache/index (under Linux)
and delete contents from the index folder; then I restart NB, which recreates it's cache.
Sergio
On Sun, 2010-09-05 at 18:43 +1000, Owen Thomas wrote:
| Quote: | Razed local copy, got a new one from SVN. Lost a few cosmetic changes.
On 5 September 2010 18:18, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | A project has decided not to compile...
It gives me the following message:
C:\Documents and Settings\Owen Thomas\My Documents\NetBeansProjects\AgentDevice\nbproject\build-impl.xml:896: The following error occurred while executing this line:
C:\Documents and Settings\Owen Thomas\My Documents\NetBeansProjects\AgentDevice\nbproject\build-impl.xml:957: The following error occurred while executing this line:
java.io.FileNotFoundException: C:\Documents and Settings\Owen Thomas\My Documents\ClientDeviceMedia\nbbuild.xml (The system cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:268)
at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:177)
at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:82)
The path should read:
C:\Documents and Settings\Owen Thomas\My Documents\NetBeansProjects\ClientDeviceMedia\nbbuild.xml
Where do I tell NB to use this path, and why, if one can hazard a guess, has it changed?
Owen. | | Quote: | On 5 September 2010 13:45, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | | I believe it to b vice versa because I didn't have to re-rename (un-rename) the file. | | | Quote: | | Quote: | On 5 September 2010 13:44, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | | I appear to have fixed it. I renamed the Class. NetBeans said a NullPointerException was thrown, and that I should report this as a bug to the bug reporting authority. I didn't do this. I then noticed that the name of the class had changed but the name of the file hadn't (or was it vice versa - who knows), so I changed the class name. The reference error in the other source files disappeared. | | | | Quote: | | Quote: | | Quote: | On 5 September 2010 12:33, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | Okay, I have a class, say X, that I have implemented in project 1. In project 2, I have included project 1 as an external project import and used class X in class Y defined in project 2. The editor is currently showing a wavy red line underneath the import of class X in class Y, and is showing a wavy red line elsewhere in the same, and any other source file that uses class X in project 2.
For years, this arrangement worked without incident. It works without incident for all the thousands of other like arrangements that rely on an identical structure.
Project 2 builds fine, so some thing is not working in NetBeans.
What do I do to get NetBeans to behave properly? | | | | | Quote: | | Quote: | | Quote: | | Quote: | On 5 September 2010 11:57, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| Quote: | No, my error, it builds fine, yet the editor is telling me that a class doesn't exist.
Why!? | | | | | | Quote: | | Quote: | | Quote: | | Quote: | | Quote: | On 5 September 2010 11:55, Owen Thomas <address-removed ([email]address-removed[/email])> wrote:
| | | | |
--
Radical collocation: the cries of a moribund socio-pathology. It's time to take telework seriously.
www.cliquespace.net
Clique Space(TM) Facebook Group: http://www.facebook.com/group.php?gid=81335296379
Owen's Garden of Thought: http://owenpaulthomas.blogspot.com/
The Technical Position of the Clique Space Concept: http://telework.ning.com/forum/attachment/download?id=2143918%3AUploadedFile%3A3987
|
|
|
| Back to top |
|
 |
djohnson Posted via mailing list.
|
Posted: Sun Sep 05, 2010 6:20 pm Post subject: How utterly weird... |
|
|
I have occasionally had a problem like this when I have made changes in
"project 1" - the editor shows errors in "project 2" wherever project 1
classes are referenced yet it compiles fine.
Usually I can fix it by turning on "Build projects in classpath" in the
libraries properties of project 2 and doing a clean and build. Once or
twice I had to manually remove the project 1 jar file from the lib
directory of project 2 then do a clean & build.
Good luck.
David Johnson
On Sun, 2010-09-05 at 12:33 +1000, Owen Thomas wrote:
| Quote: | Okay, I have a class, say X, that I have implemented in project 1. In
project 2, I have included project 1 as an external project import and
used class X in class Y defined in project 2. The editor is currently
showing a wavy red line underneath the import of class X in class Y,
and is showing a wavy red line elsewhere in the same, and any other
source file that uses class X in project 2.
For years, this arrangement worked without incident. It works without
incident for all the thousands of other like arrangements that rely on
an identical structure.
Project 2 builds fine, so some thing is not working in NetBeans.
What do I do to get NetBeans to behave properly?
On 5 September 2010 11:57, Owen Thomas <address-removed>
wrote:
No, my error, it builds fine, yet the editor is telling me
that a class doesn't exist.
Why!?
On 5 September 2010 11:55, Owen Thomas
<address-removed> wrote:
Why might my editor be telling me, quite out of the
blue, that it cannot find a class defined in another
package.
I have changed absolutely nothing. It was working fine
when I shut NB down, and now that I have restarted it,
I am being given an arbitrary error...
The project won't build.
Why!?
Owen.
--
Radical collocation: the cries of a moribund
socio-pathology. It's time to take telework seriously.
www.cliquespace.net
Clique Space(TM) Facebook Group:
http://www.facebook.com/group.php?gid=81335296379
Owen's Garden of Thought:
http://owenpaulthomas.blogspot.com/
The Technical Position of the Clique Space Concept:
http://telework.ning.com/forum/attachment/download?id=2143918%3AUploadedFile%3A3987
--
Radical collocation: the cries of a moribund socio-pathology.
It's time to take telework seriously.
www.cliquespace.net
Clique Space(TM) Facebook Group:
http://www.facebook.com/group.php?gid=81335296379
Owen's Garden of Thought: http://owenpaulthomas.blogspot.com/
The Technical Position of the Clique Space Concept:
http://telework.ning.com/forum/attachment/download?id=2143918%
3AUploadedFile%3A3987
--
Radical collocation: the cries of a moribund socio-pathology. It's
time to take telework seriously.
www.cliquespace.net
Clique Space(TM) Facebook Group:
http://www.facebook.com/group.php?gid=81335296379
Owen's Garden of Thought: http://owenpaulthomas.blogspot.com/
The Technical Position of the Clique Space Concept:
http://telework.ning.com/forum/attachment/download?id=2143918%
3AUploadedFile%3A3987 |
|
|
| Back to top |
|
 |
Owen Thomas
Joined: 20 Sep 2008 Posts: 147
|
Posted: Mon Sep 06, 2010 5:17 pm Post subject: How utterly weird... |
|
|
Something nice that NetBeans did for me was to record the changes that didn't make it to SVN in its Local History of the relevant source files.
On 6 September 2010 04:18, djohnson <address-removed ([email]address-removed[/email])> wrote:
| Quote: | I have occasionally had a problem like this when I have made changes in
"project 1" - the editor shows errors in "project 2" wherever project 1
classes are referenced yet it compiles fine.
Usually I can fix it by turning on "Build projects in classpath" in the
libraries properties of project 2 and doing a clean and build. Once or
twice I had to manually remove the project 1 jar file from the lib
directory of project 2 then do a clean & build.
Good luck.
David Johnson
On Sun, 2010-09-05 at 12:33 +1000, Owen Thomas wrote:
| Quote: | Okay, I have a class, say X, that I have implemented in project 1. In
project 2, I have included project 1 as an external project import and
used class X in class Y defined in project 2. The editor is currently
showing a wavy red line underneath the import of class X in class Y,
and is showing a wavy red line elsewhere in the same, and any other
source file that uses class X in project 2.
For years, this arrangement worked without incident. It works without
incident for all the thousands of other like arrangements that rely on
an identical structure.
Project 2 builds fine, so some thing is not working in NetBeans.
What do I do to get NetBeans to behave properly?
On 5 September 2010 11:57, Owen Thomas <address-removed ([email]address-removed[/email])>
wrote:
|
|
| 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
|
|
|
|
|
|
| |
| |
|
| | |