Riyad,
I installed Eclipse 3.2RC7 and MyEclipse 5.0 Milestone 1 and I got it to work. If things should change, I’ll let you know.
Here’s what I did:
– removed /src/main/webapp as a source folder
– added web project capability
– /src/main/webapp is web root folder
– did not add any jars, etc.
– added /src/main/webapp back as a source folder
– Unchecked “Allow output folders for source folders”, then changed target folder for all source folders to match maven’s output location (/target).
– closed the project
– copied all required tlds to /WEB-INF/tld, to match the <taglib-location> in web.xml.
– re-opened project, refreshed
Now the JSP editor recognizes all tld files that are referenced, as long as they exist in the
/src/main/webapp/WEB-INF/tld folder. This is what did not work in Eclipse/MyEclipse 3.1/4.1.1.
Ideally, Eclipse/MyEclipse/Maven would have better integration to the point where all dependencies specified in Maven’s pom files would be recognized by editors/builders/etc.
Maven is smart enough to ignore the tld files in the /src/../WEB-INF directory, so it doesn’t impact my build process or the generated artifacts.
I think that this is a simple enough work-around that it is acceptable for most cases. However, for anyone else reading this thread, it’s important to note that that if you update struts or any other third-party tag library and you are using Maven, then don’t forget to copy the new jars from your maven repo to the src/main/webapp/WEB-INF/tld file. Otherwise you may not get the most updated intellisense or editor validation.
Thanks for all your help with this Riyad.
Morgan