- This topic has 24 replies, 5 voices, and was last updated 17 years, 8 months ago by
.
-
Posts
-
Start report
Hi there,
New version of myeclipse( 5.1ga ). Just downloaded it to try out on my project.
It seems the jsp editor has been screwed up. In the previous version all my jsp’s
validated just fine , I referenced things like <code>taglib prefix=”c” uri=”http://java.sun.com/jstl/core_rt” </code>
at the top of the jsp file and code completion and validation worked fine.Now I’ve just installed the new version and this functionality is now broken.
Oh yeah , I downloaded the version with the installer so clean installation, however I am using my old workspace.
Oh on a positive note , it feels like the new version runs slightly faster than the old one.
End report
Hi there,
Has anyone looked at this ? I’d like to start using the new version as soon as possible
because overall the validation is improved.…………. and again on the 16th , has anyone looked at this bug ?
I open my workspace using 5.01 and everything works fine.
I open my workspace using 5.1 and it doesn’t recognize the taglibs.
So there is probably a problem with your new build.
brianofiach,
Maybe there’s something wrong with your installation? I also upgraded (2 systems; 1 XP, 1 Debian) and taglibs are recognized in both JSP files as JSP documents (XML syntax). Of course, we also reference the .tld from the jar files.
Thanks for feedback, I’m going to create a new workspace / project / installation this evening and see if that works.
thx
briano’fiach
New project , new workspace , same problems , jsp editor handling of
taglibs is very poor in this release , dare say i a step backward.I would not recomend that anyone with my config ( maven jars ( worked
in previous version ) ) upgrade to 5.1 , not unless you like the bright
yellow of warnings markers everywhere and unable to find attribute for
taglib errors .More QA guys ….. take a look at it.
Can you post a sample JSP document that has the validation problems? We can try to replicate it on our side and report back what we find.
Brian,
First let me apologize for not catching this. The forum software marked this as “replied to” so I didn’t see it… grrrrAnyway onto the problem. Is your JAR an “external JAR” being added to your build path, or is it a JAR from either the current project or another project contained in your workspace? What about a User Library?
Hi there ,
I use maven2 for all my dependancy management so the jars are in
C:\Documents and settings\brianofiach\.m2\repositoryI have a variable
M2_REPOwhich points to this location you can see how this is set up in attached jpg image.
How I work with projects ….
1) First I define what jars the project needs ( jstl, standard, servlet etc ) in the maven pom.xml file.
2) Then I use the “mvn eclipse:eclipse” command to generate the .project and .classpath files .
3) Now I import the project into the eclipse workspace.
4) As the project progresses I add my extra jar dependencies into the pom.xml file and run the
“mvn eclipse:eclipse” command to keep my eclipse configuration up to date.5) Maven will not create config for web project / spring / hibernate config though. I need to manually
add and configure them for the project. However the “maven eclipse:eclipse” command will not
overwrite them.Using this technique it is easy for new developers to work with my projects.
On previous version ( 5.0 ga ) everything worked out ok using this methodology ( if you could call it a methodology ).
Major Advantages :
a) There is not a whole load of jars checked into our Source Control System.
b) It is easy to see the exact project dependancies.
c) It can create correct dependencies between eclipse projects.So you can see it is quite important for me ( and others besides ) that this approach continue to work.
I can provide you with a sample project if you like complete with workspace and a dummy maven repository.
This should give you everything you need to reproduce the problem at your side .
Email me your email address or a ftp server I can upload the files to.
contradictory error messages
1 http://img90.imageshack.us/my.php?image=jsp1ok9.jpg
Says it is an unknown tag
2 http://img120.imageshack.us/my.php?image=jsp2eq4.jpg
Hover gives information about the tag attributes.Brian,
If you take the JAR that contains the TLD, and remove it from your build path, then copy the JAR directly into the project and re-add it, do the warning markers go away?We had an issue in the past where JAR’s that are external to the Workspace get processed differently than JAR files inside the workspace which were causing the TLD parser to not run. We had corrected that, but this may be another permutations of this issue that we need to address.
Yes I have done this , the problem markers now go away.
It appears that the external JAR tld bug is back.
I guess I gotta wait for the next version , it is too messy to maintain two
dependancy systems.Any idea when the bugfix release will be out ? Another month , or longer ?
