Project
IntelliJ IDEA
Priority
Normal
Type
Bug
Fix versions
No Fix versions
State
Fixed
Assignee
Alexey Kudravtsev
Subsystem
Editor. Code Completion
Affected versions
No Affected versions
Fixed in build
108.65  
  • Created by   Taras Tielkes
    4 years ago (22 May 2007 20:13)
  • Updated by   Evgeniy Schepotiev
    21 months ago (27 Apr 2010 16:27)
  • Jira: IDEADEV-17213
    (history, comments)
 
IDEA-38725 properties key reference provider still operates from data of all open projects
1
Issue is visible to: All Users
  The issue is visible to the selected user group only
This seems to be a regression of IDEA-38222.

To reproduce (could perhaps be simpler, but this is what I used):
1) Open multiple projects that contain resource bundles
2) Create following JSPX file in one of them:
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" xmlns="http://www.w3.org/1999/xhtml" version="2.0"
          xmlns:c="http://java.sun.com/jsp/jstl/core"
          xmlns:spring="http://www.springframework.org/tags"
          xmlns:fmt="http://java.sun.com/jstl/fmt">
<html>
  <body>
    <spring:message code=""/>
    <fmt:message key=""/>
  </body>
</html>
</jsp:root>

3) Add spring.jar and JSTL library dependencies.
4) Try completion for "code" or "key" attribute values in above fragment.

Observed results:
1) At the time of testing I had another project open. Some of the completion variants offered are only defined in properties files that are part of the other project.
2) Another curious thing was that completion suggestions for <fmt:message> are presented in "raw" style, while the suggestions for <spring:message> have an item icon and include defining bundle in completion proposal label.



Issue was resolved
Comments (4)
 
History
 
Linked Issues (?)
 
Taras Tielkes
  Taras Tielkes
22 May 2007 22:02
4 years ago
Added screenshot showing curious difference in completion popup styles between <spring:message> and <fmt:message>.

The completion proposals shown are both wrong, and seem to some from an IDEA plugin project that I had open at the same time as the current web project.
Taras Tielkes
  Taras Tielkes
25 May 2007 17:03
4 years ago
It also (still) broken in 6.0.6 EAP, but in a way that's even worse!

Selena 6963:
  • (Invalid) properties keys from other open projects are suggested, but marked red in the editor

6.0.6 EAP (#6184):
  • (Invalid) properties keys from other open projects are suggested
  • They are not marked red in the editor
  • Navigating such an invalid property key will actually open the properties file (from another open project) inside the current project (!?!)

I hope it's clear that this is "broken beyond belief" at the moment, making working on i18n web projects definitely "without pleasure".
Alexey Kudravtsev
  Alexey Kudravtsev
25 May 2007 19:38
4 years ago
Indeed. Sorry for that.
Taras Tielkes
  Taras Tielkes
25 May 2007 19:50
4 years ago
Alexey, thanks for fixing this so quickly.

Will the solution be included in 6.0.6?