- This topic has 33 replies, 6 voices, and was last updated 18 years, 5 months ago by Riyad Kalla.
-
AuthorPosts
-
cri_tsgMemberI have always had /src/main/java and /src/main/resources as “source” folders. And the “Add MyEclipse Web Capabilities” wizard will only allow /src/main and src/main/WEB-INF (bad idea!!) to be web root. I also removed /src/main/webapp as a source folder and made it the web root. Even then, jsp tags were still not recognized.
I may give Eclipse 3.2 and MyEclipse 5 a shot.
Thanks for all of your attention with this issue. I’ll be back if I cannot find a workable solution with the new configuration 😉
Morgan
Riyad KallaMemberMorgan,
I’m almost certain I could get your app working, can you zip it up and send it to me and I’ll put it into a MyEclipse project for you and send it back? If so, email it to support@genuitec.com ATTN Riyad with a link to this thread so I know why I’m getting it.
cri_tsgMemberRiyad,
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, refreshedNow 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
Riyad KallaMemberMorgan,
You know Maven2 support is a bright spot on our radar after we get 5.0 out the door, at that point this integration may flow together more seamlessly. Thanks for trying your project out with 5.0 and letting us know. -
AuthorPosts