 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Rick Guest
|
Posted: Thu Sep 09, 2004 5:32 pm Post subject: imports not being found by JBuilder |
|
|
I have a project that we recieved from another company. When I bring up the jubuilder project it does not have visability to any of the classes in the project. For example:
package foo
import foo.bigdog <--jbuilder marks this as an error, but if I were to type import foo, it see the package and class.
in the Project Properites I have the path as C:project and foo is a subdir and bigdog is a .java file in that dir
Which setting am I missing?
Thanks for your help in advance
|
|
| Back to top |
|
 |
Gillmer J. Derge [TeamB] Guest
|
Posted: Thu Sep 09, 2004 6:03 pm Post subject: Re: imports not being found by JBuilder |
|
|
Rick wrote:
| Quote: | in the Project Properites I have the path as C:project and
foo is a subdir and bigdog is a .java file in that dir
|
Where in Project Properties do you have the C:project path? It should
be one of the source paths for your project. On the "Paths" page and
the "Source" tab.
If that's already correct, try compiling bigdog and see if the problem
goes away. Some parts of JBuilder, especially the little red squiggly
lines for errors, seem to insist on class files instead of source files.
--
Gillmer J. Derge [TeamB]
|
|
| Back to top |
|
 |
Rick Guest
|
Posted: Thu Sep 09, 2004 6:38 pm Post subject: Re: imports not being found by JBuilder |
|
|
Ok, that makes sense for the classes that are .java, however, for me, JBuilder still will not see an imported .jar file that I have included in the Required Libraries. I have this commons-lang-2.0.jar included, but when I try and complie it tells me that this import is invalid.
import org.apache.commons.lang.StringUtils;
But, if I type the line above the little help box shows me all the way down to the class.
I remeber when I used JBuilder a long time ago that it had a cache that needed to be cleaned out to fixed compile issues. Could that be the reason?
Thanks
"Gillmer J. Derge [TeamB]" <spam (AT) gillmerderge (DOT) com> wrote:
| Quote: | Rick wrote:
in the Project Properites I have the path as C:project and
foo is a subdir and bigdog is a .java file in that dir
Where in Project Properties do you have the C:project path? It should
be one of the source paths for your project. On the "Paths" page and
the "Source" tab.
If that's already correct, try compiling bigdog and see if the problem
goes away. Some parts of JBuilder, especially the little red squiggly
lines for errors, seem to insist on class files instead of source files.
--
Gillmer J. Derge [TeamB]
|
|
|
| Back to top |
|
 |
Rick Guest
|
Posted: Thu Sep 09, 2004 6:52 pm Post subject: Re: imports not being found by JBuilder |
|
|
What I found was that eventhough I had imported the JAR file if it was included with other JAR files JBuilder would not "see" it and complie.
To fix my probelm I imported the jar in a seperated include
"Rick" <rick_ferrel (AT) yahoo (DOT) com> wrote:
| Quote: |
Ok, that makes sense for the classes that are .java, however, for me, JBuilder still will not see an imported .jar file that I have included in the Required Libraries. I have this commons-lang-2.0.jar included, but when I try and complie it tells me that this import is invalid.
import org.apache.commons.lang.StringUtils;
But, if I type the line above the little help box shows me all the way down to the class.
I remeber when I used JBuilder a long time ago that it had a cache that needed to be cleaned out to fixed compile issues. Could that be the reason?
Thanks
"Gillmer J. Derge [TeamB]" <spam (AT) gillmerderge (DOT) com> wrote:
Rick wrote:
in the Project Properites I have the path as C:project and
foo is a subdir and bigdog is a .java file in that dir
Where in Project Properties do you have the C:project path? It should
be one of the source paths for your project. On the "Paths" page and
the "Source" tab.
If that's already correct, try compiling bigdog and see if the problem
goes away. Some parts of JBuilder, especially the little red squiggly
lines for errors, seem to insist on class files instead of source files.
--
Gillmer J. Derge [TeamB]
|
|
|
| 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
|
|