All, I have read several books (ie Head First Java & Head First Design Patterns) and most of the Sun �Learning the Java Language� tutorial. I�m pretty comfortable saying that I can make a Package of classes or a JAR and use it to produce results. I�ve done quite a bit of that over the last few weeks using the JDK and the compiler via command line.
Now, I�m ready to start something �Real�. My problem is that I can�t figure out how to get Eclipse to work with my file paths and publish files to the directories I choose. And the one time I did get it to work, it wouldn�t compile my Spring MVC controllers because it couldn�t resolve the Type �Controller� which is in the Spring library which I had in my /WEB-INF/lib folder.
The frustrating thing is that I have demo apps that were working fine and using the same directory structure for classes and the Spring JAR(s) but mine would not work.
I�m using Tomcat 5.0 and a 1.5 JRE. I would like to have my file structure in the Tomcat webapps folder to be /WEB-INF/classes, /WEB-INF/lib, WEB_INF/src, /WEB-INF/jsp.
I cant seem to get eclipse to manage my file creation, compilation and publication. It is putting stuff all over the place and I cant make sense of what it is doing.
Is there something I can read that will show me how to properly make a project in Eclipse that will put the compiled classes in the right directory and use the Spring library as I need it to.
In several cases I have seen people mention plugins for Tomcat but I don�t know where to start and which ones are better than others.
We have a forum specifically dedicated to "IDEs, Version Control, and Other Tools". I'm going to move this question there where the right people will look at it.
I can tell you right off that you should not feel like this is your fault -- Eclipse's idea of how to do this kind of thing is just crazy. It can all be made to work just fine, but not until you learn to think like Eclipse, which, for most people, is not the way they usually think.
This brings back such strong memories of my first battles with Eclipse
The key thing to bear in mind is that in Eclipse, it's all about the "project". The project properties (Project menu, select properties) will become your constant companion. In particular the "Java Build Path" section.
The arrangement of files and directories in your project workspace is not particularly significant, but what IS significant is which directories you have marked as "Source" in the project properties, and which jars you have added to the "Libraries" tab.
You were exactly right. My problem was partially what I was creating my workspace in the wrong place and also that I didn�t have all of my libraries mapped in the Build Path. Once I realized and understood what was going on I was writing classes and testing them in no time.
grapes are vegan food pellets. Eat this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!