1) The items should check, whether is there defined the jstl core library, if
not then add the <%@taglib %> directive with the definition
2)When there is already jstl core defined on the page, then the items should
find out the appropriate prefix. The prefix doesn't have to be "c".
fixable in 5.5
*** Issue 67457 has been marked as a duplicate of this issue. ***
moving opened issues from TM <= 6.1 to TM=Dev
Reproduced on 6.1 dev build.
Reopened, 2) doesn't work, is library has other prefix than "c", ide inserts another import with "c" prefix.
This may happen only if JSP parser has problem to parse the page.
Please provide example JSP file and steps how to reproduce it.
There may be racing condition in one corner case: when user adds code from palette, then renames prefix of newly
inserted taglib, and then inserts another code from palette. Old taglib prefix may be used for newly inserted code in
this case. This is caused by JSP parser (the speed of parser and caching). This scenario is corner case, most developers
won't change taglib prefix directly after insertion. This behavior is confirmed by QA (dkolar). New issue may be created
for this corner case.
The fix has been ported into the release61_fixes branch.