| indirectly references the missing type ( compiler error) - [message #75969] |
Tue, 15 July 2003 04:30  |
Eclipse User |
|
|
|
Originally posted by: amalyova.hotmail.com
Hello,
When compiling my classes I get the following error
This compilation unit indirectly references the missing type
org.apache.commons.lang.exception.NestableException (typically some required
class file is referencing a type outside the classpath)
I realise that the error occurs because a class in one of the included jars
that I reference in my code is referencing a class in a jar that is not
included in the build path of my project, however there is absolutelly no
reason why that should be reported as an error. In my case, not only does a
compiler report it as an error, but it also prevents all the other classes
from compiling.
I tried desabling all error reporting in a compiler settings under
Preferences, but that did nothing.
Also, I could just find whatever commons jar that is being referenced and
include it in the build path, but that is almost a cheap way out of a
problem the will surely come back to haunt me again. What I really hope for
is an answer to why the compiler in eclipse behaves this way and how to make
it STOP.
My env is : win xp, eclipse 2.1.1 , java 1.4.1
Thank you for any help
Alex
|
|
|
| Re: indirectly references the missing type ( compiler error) - [message #99488 is a reply to message #75969] |
Sun, 28 September 2003 14:09  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-nohack.sneakemail.com
--____LPHMXLZMXOMRLFKSEJCW____
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Alex,
I have just started experiencing the same thing due to a 3rd party Jar for =
SAP that includes the same unresolvable references. I was wondering if =
you managed to resolve the build situation or not?
Cheers,
-Lyndon-
>>> alex m<amalyova@hotmail.com> 7/15/2003 4:30:26 AM >>>
Hello,
When compiling my classes I get the following error
This compilation unit indirectly references the missing type
org.apache.commons.lang.exception.NestableException (typically some =
required
class file is referencing a type outside the classpath)
I realise that the error occurs because a class in one of the included =
jars
that I reference in my code is referencing a class in a jar that is not
included in the build path of my project, however there is absolutelly no
reason why that should be reported as an error. In my case, not only does =
a
compiler report it as an error, but it also prevents all the other classes
from compiling.
I tried desabling all error reporting in a compiler settings under
Preferences, but that did nothing.
Also, I could just find whatever commons jar that is being referenced and
include it in the build path, but that is almost a cheap way out of a
problem the will surely come back to haunt me again. What I really hope =
for
is an answer to why the compiler in eclipse behaves this way and how to =
make
it STOP.
My env is : win xp, eclipse 2.1.1 , java 1.4.1
Thank you for any help
Alex
--____LPHMXLZMXOMRLFKSEJCW____
Content-Type: multipart/related; boundary="____WHPEPQYSAQXEHDGESJXG____"
--____WHPEPQYSAQXEHDGESJXG____
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1226" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma; COLOR: #000000">
<DIV>Alex,</DIV>
<DIV> </DIV>
<DIV>I have just started experiencing the same thing due to a 3rd party =
Jar for SAP that includes the same unresolvable references. I was =
wondering if you managed to resolve the build situation or not?<BR></DIV>
<DIV>Cheers,</DIV>
<DIV>-Lyndon-<BR>>>> alex m<amalyova@hotmail.com> 7/15/2003 =
4:30:26 AM >>><BR></DIV>
<DIV style=3D"COLOR: #000000"><BR><BR><BR>Hello,<BR>When compiling my =
classes I get the following error<BR><BR>This compilation unit indirectly =
references the missing type<BR>org.apache.commons.lang.exception.NestableEx=
ception (typically some required<BR>class file is referencing a type =
outside the classpath)<BR><BR>I realise that the error occurs because a =
class in one of the included jars<BR>that I reference in my code is =
referencing a class in a jar that is not<BR>included in the build path of =
my project, however there is absolutelly no<BR>reason why that should be =
reported as an error. In my case, not only does a<BR>compiler report it as =
an error, but it also prevents all the other classes<BR>from compiling.<BR>=
<BR>I tried desabling all error reporting in a compiler settings under<BR>P=
references, but that did nothing.<BR>Also, I could just find whatever =
commons jar that is being referenced and<BR>include it in the build path, =
but that is almost a cheap way out of a<BR>problem the will surely come =
back to haunt me again. What I really hope for<BR>is an answer to why the =
compiler in eclipse behaves this way and how to make<BR>it STOP.<BR><BR>My =
env is : win xp, eclipse 2.1.1 , java 1.4.1<BR><BR>Thank you for any =
help<BR> Alex<BR><BR><BR><BR><BR><BR></DIV></BODY><=
/HTML>
--____WHPEPQYSAQXEHDGESJXG____--
--____LPHMXLZMXOMRLFKSEJCW____--
|
|
|
Powered by
FUDForum. Page generated in 0.03641 seconds
Home