I’m finding that most projects I work on don’t use MyEclipse for development. I always then have the issue of trying to get them to work in MyEclipse.
So, as a test, I started a fresh test project working through the Spring tutorial at:
http://static.springframework.org/docs/Spring-MVC-step-by-step/part1.html
The problem I’m having with this tutorial is that the Ant build script can’t find the Spring libraries that get imported into the MyEclipse Web Project (when you “Add MyEcipse Capabilities” from the MyEclipse menu) and I can’t figure out how to set the classpath correctly in the Ant script so it will work.
So, my basic question is … when building a web app, should I opt to basically just use MyEclipse (so it can find everything and actually work) or forget MyEclipse’s built-in capabilities and just use Ant?
It seems so far that the two approaches are somewhat incompatible.
As another example of this disconnect between MyEclipse and the Ant approach, when I type in a simple Controller (Spring), there are no compile errors, but when running the Ant build task, I get “Cannot find symbol” on the
“return new ModelAndView(“hello.jsp”);” line of code (as well as others).
Again, this may be simple classpath problem that’s not right in the Ant script.
Look forward to any advice or suggestions.
Thanks.
— M