For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 8 replies, 3 voices, and was last updated 13 years, 4 months ago by
.
-
Posts
-
I recently moved from myE 10.6 to 10.7 on a new machine. I moved over the entire project, and all the project resources are in the same locations, etc.
When I edit a JSP that includes some tag libraries, the tag library will not resolve in the JSP editor, though the jar containing the TLD is part of the build path via being specified in the Maven Dependencies. I can open this jar and clearly see the TLD is there and should resolve.
I have tried the -clean startup, as well as doing a clean build, and nothing will clear up all these JSP errors.
When I use code completion in the jsp editor, I cannot see any of the TLDS that are a part of the build path, so something is not right.
The project worked perfectly on 10.6. What would cause it to stop resolving TLDs that are clearly part of the build path?
Thanks!
n0bounds,
Sorry that you are seeing this issue.
Can you please answer some more questions for us ?
1. Can you please share the Build Id from Help > About MyEclipse Edition > Build Id ?
2. Does the web.xml reference the TLD files ?
3. Can the project be deployed successfully?
4. Can you please try to open the JSP with Web Page Editor and check if the issue occurs ?
5. If the issue exists, then please attach the POM letting us know of a dependency that contains the unresolved TLD.Version: 10.7.1
Build id: 10.7.1-20130201The web.xml does not reference the TLDs. It never did, and it used to work fine.
The project deploys just fine.
The issue seems to occur in any editor I select, JSP, HTML, Web Page editor, etc.
Find my pom attached. It is complaining about not being able to find struts2 tags, which are definitely showing up under my maven dependency jar files.
n0bounds,
Thanks for the information. I’ve been unable to replicate the problem with the pom you attached. Is it possible for you to construct a simple maven web project that exhibits this problem, and attach it as an archive? In this way, we’ll have a better chance of replicating the issue. There have been no changes to that area between 10.6 and 10.7.1, so it’s difficult to understand how this can happen.
Sorry for the inconvenience.
The same project has also lost all the SVN version control operations. All the .svn directories are still there, but at the top level of the project it says it is unversioned. Any idea how to get it back to thinking it is versioned and connected to SVN?
I was able to resolve the jsp problem by doing the following.
– remove all dependencies from the pom.xml and saving
– cleaning the project
– putting the dependencies back, saving
– visiting jsps marked with errors, and redoing any one of the erroneous taglib declarations. – Fixing one fixes them all.@n0bounds wrote:
The same project has also lost all the SVN version control operations. All the .svn directories are still there, but at the top level of the project it says it is unversioned. Any idea how to get it back to thinking it is versioned and connected to SVN?
never mind, figured this one out too. had to reinstall subclipse and blow away my eclipse version cache file.
n0bounds,
Thanks for persevering and sorting out these problems. I’m glad you’re back working again. I’m afraid that I can’t offer any explanation for what went wrong there. Without being able to replicate the problems, we might have to mark this down as a mystery! Feel free to PM me the original project for further investigation, otherwise you seem to be all set now.
