
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Linux 64 bit JDK 1.7 b24 (running 1.7 because of a Fedora Core 8 bug with Swing and X)
|
|
| Build: |
7,613
|
| Fixed in build: |
8,068
|
| Severity: |
High
|
I have a project with multiple modules. Each module has beans defined in it, and some modules can see the beans defined in other modules. I have the Spring facet configured for each module with the right set of spring beans xml files.
In build 7584, navigation is great – every occurence of every beans is detected and I can go between code and the spring XML files easily. In 7613, not all references to all beans are found. And it's not always the same beans that are missing references to their use in XML files, either, it's odd. This is a big problem because navigating back and forth between code and spring files is a big part of my day 
|
|
Description
|
I have a project with multiple modules. Each module has beans defined in it, and some modules can see the beans defined in other modules. I have the Spring facet configured for each module with the right set of spring beans xml files.
In build 7584, navigation is great – every occurence of every beans is detected and I can go between code and the spring XML files easily. In 7613, not all references to all beans are found. And it's not always the same beans that are missing references to their use in XML files, either, it's odd. This is a big problem because navigating back and forth between code and spring files is a big part of my day  |
Show » |
|