[brianofiach]

“jsp editor does not detect tld files stored in project jars” : Your support staff deleted my posting

Some background.

This bug was introduced in an update to myeclipse.

I notified your staff imediately and spent a lot of my own time tracking down the cause.

I was told that the bug would be fixed in the next release.

It was not fixed.

The support staff fobbed me off with some spoofing about Maven support appearing in a future release.

I wrote back a message complaining that the issue was not being dealt with professionaly.

My post was deleted.

So my last reply to that post has gone unanswered for the last week so I am creating a new post.

Perhaps you can give me a satisfactory reply to the following questions ?

a) The bug which you introduced 4 months ago and still haven’t fixed ( which prevent teams from using maven ) .

b) Why my reply was deleted without any explanation or reply.

Thank you

Bryan[/list]

[Riyad Kalla]

Bryan,
I personally didn’t delete any such post and I know I personally pushed through 2 fixes for taglib autocomplete/validation issues that made it into the 5.1.1 build last week because of users (I believed you were one of them) demanding the fixes.

Can I ask you for a thread or a quick description of exactly the bug that you were running into? I see the text description but that could mean a lot of things… JARs exported from dependent Java projects? External JARs? User Library JARs? etc.

I’ll try and setup whatever scenario you outline on my end and see if that was included in the 5.1.1 fixes.

Again I’m sorry if your thread did die, there would be absolutely no reason for that to ever happen.

[brianofiach]

Ok Riyad, I hope that this time the bug gets actioned property because I’m getting tired of filing the same bug report again and again.
On the other hand thank you for taking the time to reply to me.

Here is the bug.

I have a workspace variable , it is called M2_REPO, it points to the following location c:\documents and settings\user1\.m2\repo\

My (autogenerated) .classpath file contains a number of entries referencing this variable.

Here is some samples …

<classpathentry kind=”var” path=”M2_REPO/taglibs/standard/1.1.2/standard-1.1.2.jar” sourcepath=”M2_REPO/taglibs/standard/1.1.2/standard-1.1.2-sources.jar”/>
<classpathentry kind=”var” path=”M2_REPO/javax/servlet/jstl/1.1.2/jstl-1
.1.2.jar” sourcepath=”M2_REPO/javax/servlet/jstl/1.1.2/jstl-1.1.2-sources.jar”/>
etc etc … another 50 entries.

As you can see everything is defined through this variable (M2_REPO).

Now on eclipse 5.0 this works without any problems whatsoever.

But a bug was introduce in the following version which breaks this.

On higher versions if a jar file is declared in this fashion then jsp validation and autocompletion no longer works.

Simple as that : Jsp validation and autocompletion does not work when the jar file is referenced via an environmental variable.

So autogenerated , centralised configuration management no longer works.

So I can not use a higher version when I am working in a team environment.

I downloaded and tried the latest version 5.5m1 and the bug was still in that version.

I appreciate you looking into this matter.

Thanks

Bryan

[Riyad Kalla]

Bryan,
I actually got autocomplete and validation to work, so it’s possible I did the wrong steps here. Double-check me please:

1) Went to build path, created a new variable called “TEST_VAR” that pointed to my JSF 1.2 /lib dir on my drive.
2) Added the var and clicked “Extend” and selected both jsf-api and jsf-impl JARs and added them to my ubuild path.
3) Added a single JSP page using the JSF template, and attempted autocomplete for the f: tag.

Here’s my system info:

*** Date:
Tuesday, March 6, 2007 7:32:06 AM MST

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_08

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.1.0 GA
Build id: 20061111-5.1.0-GA

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 5.1.0 GA
Build id: 20061111-5.1.0-GA

Eclipse Graphical Editing Framework

Version: 3.2.1.v20060921
Build id: 20060921-1617

Eclipse Platform

Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx
Build id: M20060921-0945

Eclipse RCP

Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq
Build id: M20060921-0945

Eclipse Java Development Tools

Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC-
Build id: M20060921-0945

Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945

Eclipse Project SDK

Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ
Build id: M20060921-0945

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Java\myeclipse-5.1\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
844_88
-vm
C:\Java\myeclipse-5.1\jre\bin\javaw.exe

Attachments:

You must be logged in to view attached files.

[brianofiach]

Ok I have done more research on it the following pictures is my bug report , I prepared it before I saw these latest screenshots .

I will post it without reading your post because I want to go to sleep now. I will read your post at lunch tomorrow.

[brianofiach]

What was allready agreed to be the cause of the defect :

MyEclipse JSP editor fails to resolve taglib references from within jars files contained
outside the users workspace .All other functionality works in an acceptable fashion .

STEPS TO REPRODUCE DEFECT :

The central directory is “C:\doc + settings\users\username\.m2\repository” , the variable
which references this path is called ${M2_REPO} .

All of the jar files in the .classpath file are referenced in the following fashion .

“M2_REPO/cglib/cglib/2.1/cglib-2.1.jar”

SYMPTOMS OF DEFECT :

JSP Taglib Validation does not function correctly .

RESULT OF DEFECT :

The user experiences difficulty reading the text on
the screen .

The yellow warning messages make the editor text hard
to read .

The graphical editing of web pages is now no longer working correctly .

I have to read the DTD or XSD of the XML file now myself manually .

Proper xml editing functionality is esential for a java developer .

So it has a difficult impact upon our way of working .

TIMELINE OF THIS DEFECT :

Works correctly : MyEclipse version N.o

MyEclipse JSP Design Support
Version: 5.0.1
Build id: 20060810-5.0.1-GA

Does not work correctly : MyEclipse version N.o

MyEclipse JSP Design Support
Version: 5.4.100
Build id: 20070123-5.5.0-Milestone1

The defect was not present in fall 2006, it was reported imediately upon discovery .

The last developer release in January still contained the defect .

The current date is the 8th March 2007 .

[brianofiach]

Hi there , I have tested

Version: 5.1.1 GA
Build id: 20070302-5.1.1-GA

at home and at work

and I have tested MyEclipse 5.5 M1
both at home and at work

And they both fail to validate , wierd eh ?

I have taken screen shots do you have an email address I can send them to ?

[Riyad Kalla]

You can PM them to me and be sure to include a link to this thread for refrence please.

[Riyad Kalla]

MyEclipse JSP editor fails to resolve taglib references from within jars files contained
outside the users workspace .All other functionality works in an acceptable fashion .

This was not the case for me, in my example the JSF JARs I’m using are no where near my workspace directory and as you see they are resolving correctly.

I have to read the DTD or XSD of the XML file now myself manually .

Proper xml editing functionality is esential for a java developer .

So it has a difficult impact upon our way of working .

I don’t understand the XML notes here… I thought we were discussing the JSP taglib issue? (If we are, that’s fine, please just clarify the issue… is this something else you are reporting?)

I also want to point out in your screenshot, the warning is marked under your use of the JSTL “c” tag… but in the screenshot of your biuld path, JSTL seems to be in your project, and not comming from the M2_REPO location… do you possibly have duplicate JARs in your build path possibly with differening URIs?

[brianofiach]

Apologies for the rushed report , I just dumped those images in there without really describing
what they represent .

To clarify :

Part 1) References to XML in my reply .

I meant to say , I have to read the taglib definition file in order to find out which properties a
particular taglib has.

That is because I’m working a lot on Java Server Faces as well and I tend to think of the jsp’s
as XML files . There is hardly any html in there anymore .

Part 2) Build path jars .

The reason the jars are pictured sitting directly on the build path instead of using the maven
$M2_REPO variable is that .

I had it earlier in the session set the classpath variable to an extension of the $M2_REPO variable.
When the yellow lines appeared and it became faulty I switched to directly referencing the jar files
but none the less the errors remained and the jsp validation / auto completion failed.

Part 3) Version conflicts .

I checked my build against the other projects for version conflicts and found none.
I manage the version numbers centrally via maven so I never get different versions
on the path , ( well very rarely ). This is one of the principle advantages of Maven .

So to summarise :

We’ve been on this bug for a while without getting anywhere and I don’t really have a lot of free
time to work on it.

However I have some free time soon , I’m planning to buy a new system soon. I’ll be setting up a
system from scratch so it will be an ideal time to try an reproduce this bug on a fresh copy of Windows .

Can you check and tell me what have you found is the best version number to test with ?

Thanks.

Bryan

[Riyad Kalla]

Part 1) References to XML in my reply .

I meant to say , I have to read the taglib definition file in order to find out which properties a
particular taglib has.

That is because I’m working a lot on Java Server Faces as well and I tend to think of the jsp’s
as XML files . There is hardly any html in there anymore .

As these pages JSP Documents? That may be part of the issues…

We’ve been on this bug for a while without getting anywhere and I don’t really have a lot of free
time to work on it.

However I have some free time soon , I’m planning to buy a new system soon. I’ll be setting up a
system from scratch so it will be an ideal time to try an reproduce this bug on a fresh copy of Windows .

I know what you mean it’s really frustrating that I’m not able to reproduce the issue you are seeing because it’s leaving you in a lurch and I’m not really sure where I’m going wrong with my testing…

Can you check and tell me what have you found is the best version number to test with ?

For now it’s our 5.1.1 release using the All-In-One installer. We will be releasing 5.5M2 soon and then 5.5 GA in April

[brianofiach]

Hi ,

I’ve found the cause of this bug. Should have been the first thing I’d check but Java app’s usually don’t choke on whitespace these days.

Anyhow , when using classpath variables to define external resources MyEclipse does not correctly read tld files if the variable itself contains whitespaces.

e.g

c:\m2\repository\standard\standard-1.2.jar | works

but

c:\Documents and Settings\usename\m2\repository\standard\standard-1.2.jar | does not work

Thanks for taking the time to look through this with me , I guess that’s something for the eclipse guys to look at.

Bryan

[Riyad Kalla]

Bryan,
Great catch… testing right now…

[Riyad Kalla]

I’m happy and sad at the same time… I cannot reproduce that issue either, please see below.

Attachments:

You must be logged in to view attached files.

[brianofiach]

what version of the JDK are you using ?

[Author]

Posts