| Get rid of Errors when not using Eclipse's Compiler? [message #77250] |
Thu, 17 July 2003 13:19  |
Eclipse User |
|
|
|
Originally posted by: ehansen.convergentnet.com
I'm using an external build tool (external Ant) as my primary build tool,
but I'm having issues with Eclipse showing errors in my classes because of
class dependencies that should be fine.
For example, I have a bunch of EJBs. I'm using XDoclet to generate the
Remote, Local, RemoteHome and LocalHome classes in a separate directory.
I've added that directory to the build path, but Eclipse still flags
references to those classes (in my EJB implementation classes and the
servlets that call them) because it can't resolve them.
Why doesn't Eclipse recognize that I've added that folder to my build path?
When I run Ant on the build.xml, everything compiles fine, but it renders
the error flagging in Eclipse useless if legitimate problems are buried
beneath lots of incorrectly flagged errors.
Sometimes if I restart eclipse or edit/resave the classes that references
the generated classes, the errors go away, but not always. If I create a
source tree with the directory that holds the autogenerated classes in the
build path (but before the first run of Xdoclet which generates them) I see
error (which I would expect). I would expect them to go away, though, after
I run Ant/XDoclet the first time and those classes are generated.
Surely anyone who has EJBs that use autogenerated code would see the same
type of problem... Does anyone know a solution to this?
Thanks,
Erik
|
|
|
| Re: Get rid of Errors when not using Eclipse's Compiler? [message #77266 is a reply to message #77250] |
Thu, 17 July 2003 13:42  |
| Eclipse User |
|
|
|
Eclipse needs to find out that things have changed...that is that you have
added the auto-generated source.
The easiest option is to use the integrated Ant support and set it to
refresh the project (recursing sub-directories) after you have generated the
source.
Alternately, you can manually refresh the project hierarchy using either F5
or use the context menu for the project > Refresh
HTH
Darins
"Erik Hansen" <ehansen@convergentnet.com> wrote in message
news:bf6lq9$e1m$1@eclipse.org...
> I'm using an external build tool (external Ant) as my primary build tool,
> but I'm having issues with Eclipse showing errors in my classes because of
> class dependencies that should be fine.
>
> For example, I have a bunch of EJBs. I'm using XDoclet to generate the
> Remote, Local, RemoteHome and LocalHome classes in a separate directory.
> I've added that directory to the build path, but Eclipse still flags
> references to those classes (in my EJB implementation classes and the
> servlets that call them) because it can't resolve them.
>
> Why doesn't Eclipse recognize that I've added that folder to my build
path?
> When I run Ant on the build.xml, everything compiles fine, but it renders
> the error flagging in Eclipse useless if legitimate problems are buried
> beneath lots of incorrectly flagged errors.
>
> Sometimes if I restart eclipse or edit/resave the classes that references
> the generated classes, the errors go away, but not always. If I create a
> source tree with the directory that holds the autogenerated classes in the
> build path (but before the first run of Xdoclet which generates them) I
see
> error (which I would expect). I would expect them to go away, though,
after
> I run Ant/XDoclet the first time and those classes are generated.
>
> Surely anyone who has EJBs that use autogenerated code would see the same
> type of problem... Does anyone know a solution to this?
>
> Thanks,
> Erik
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03285 seconds
Home