894123 wrote:Thats an Eclipse thing I sometimes suffer from too (before Eclipse 3.7, haven't suffered it in the latest version yet). Generally cleaning all projects will solve it. Note that this is usually a cascaded effect when you have project modules that depend on each other through workspace resolution; when a module fails to compile for whatever reason, it temporarily drops off the classpath of a module that depends on it and you get classpath errors there as well.
I'm developing a JavaEE system with several applications on a Weblogic AS (10.3.5) using Eclipse indigo with OEPE plugin. I turned my computer off, turned it back on, started the eclipse, and all of a sudden I get class-path errors all over the place (didn't change a thing).
How should I set the class-path when using JavaEE technology in Eclipse?Maven is good for any kind of project type, but especially JavaEE projects because the dependency hierarchy tends to be complicated. Note that you are talking about the classpath for compilation/test purposes. Runtime classpath is of course controlled by the container.
894123 wrote:nothing takes too much time to learn, what you mean to say is that you did not want to invest the time. I highly recommend you do though. I direct you to my article about basic Maven usage:
I tried to use Maven once and my impression was that it might be a good tool, but it takes to much time and effort to learn it and use it properly. But maybe it's worth another shot.