Community
Participate
Working Groups
Build ID: M20060629-1905 Steps To Reproduce: 1. Activate Mylar in Package Explorer 2. Open a resource file (this on is not under the src folder, but a resource folder - using Maven Std Directory Structure) 3. Edit the resource file 4. Notice that the Package Explorer is not updated to show the xml file
Created attachment 55877 [details] screen shoot showing the bug/problem screen shoot showing the bug/problem
I can not reproduce with the default XML editor in the Eclipse SDK, so please try this to figure out if the problem is the particular XML editor (btw, which editor is it?): * Deactivate task * Open the XML file with the "Text Editor" * Activate a new task * Do the Ctrl+Shift+R way of opening and see if it shows up.
Mik, I believe I'm using the standard XML Editor that comes with Eclipse SDK (Open With context menu only says "XML Editor"). I tried the steps with Text Editor, the file opened up in the text editor when the task was active but it was not added to the task context. Where do you want me to go next? I really hope that this is a bug, so that I'm not taking your time...
There is no XML editor in Eclipse SDK. You must be using something else, like XML editor from the WTP.
Eugene, that is correct. I use the XML editor that comes with WTP.
Jimisola: just fyi, it's not likely that we can look at WTP-specific integration problems until after Eclipse 3.3M6 and the corresponding WTP release go out. But if you're interested in looking into this we could take a patch.
Will investigate further post 2.0.
I cannot reproduce this with Mylyn 2.0 and the Europa version of the WTP XML editor. I don't have all of WTP installed but I am using the XML editor. Please reopen if this is still happening with the latest.
Created attachment 101984 [details] Test project I have managed to reproduce the issue with the Ganymede M7 packages and Spring IDE installed (2.0.4.v20080311444). These steps work for me: 1. Create a new workspace 2. Import the project in the workspace 3. Switch to Java perspective 4. Create a new local task 5. Open the spring.xml file with Ctrl+Shift+R 6. Notice how the file doesn't appear in the Package Explorer view
One small correction: step 4 should be "4. Create a new local task and activate it". I also tested with Spring IDE 2.0.5.v200805121800 and I can still reproduce it. I should mention that the file appears in the package explorer unless it is listed in Project properties -> Spring -> Beans support.
Reopening to investigate.
I can't reproduce this with the Mylyn 3.0 RCs. Are you using the Spring IDE Mylyn integration?
Yes, I am using the Spring IDE Mylyn integration.
Steffen: please investigate.
It looks like the underlying problem here is that the element becomes interesting in one model (i.e., the Spring structure model) so it fails to become interesting in another model (i.e., the resource model). This is another manifestation of bug 213661. Note that with an empty context, you should be able to Alt+click to the spring.xml file in the Package Explorer and have it appear that way. In other words, which ever model you select it first in, it will be stuck using. I'll investigate either handling adaptation to resources better, or supporting multiple models in this way, for 3.0.1, or if it's too big a change for 3.1. Marking as P2 since this is pretty confusing.
*** Bug 265280 has been marked as a duplicate of this bug. ***
*** Bug 271117 has been marked as a duplicate of this bug. ***
*** Bug 271353 has been marked as a duplicate of this bug. ***
This issue been reported two years ago and has 3 duplicates. Is there are plans to fix this very distracting issue?
We'll take a pass through milestone planning this week and take the number of votes and duplicates into account when prioritizing.
(In reply to comment #20) > We'll take a pass through milestone planning this week and take the number of > votes and duplicates into account when prioritizing. > Steffen, all: I'm very glad to hear this is getting looked at once again. I encounter this problem frequently and it is quite a distraction. Let me know if there's any info I can contribute to help resolution.
Thanks Chris. Shawn was just recently promoted to committer status and is planning to take a closer look at this problem as part of the current release cycle.
(In reply to comment #22) > Thanks Chris. Shawn was just recently promoted to committer status and is > planning to take a closer look at this problem as part of the current release > cycle. > Nice. Here's another repro detail (not sure if anyone has mentioned it yet in the thread above): Environment: STS 2.0.1 with latest Mylyn weekly updates. Scenario one: 1. create a spring config file in an existing project 2. register that file as a spring bean definition. 3. activate a task context 4. ctrl-shift-r to open the new spring config file 5. notice that the file opens in the editor, but does not show up in the package explorer (i.e.: is not part of the active mylyn context) Scenario two: 1. Repeat steps 1-3 above 2. Navigate to the new spring config file using the package explorer 3. Double-click on the spring config file to open it. 4. Notice that the file opens in the editor as expected, and *is* added to the mylyn context appropriately (i.e.: shows up in the package explorer, etc.) HTH, - Chris
The current release that is available from the weekly site includes the fix for this problem. Please try it out and let us know if there are any problems.
Marking this resolved. Please re-open this bug if you still have problems after installing the latest weekly build of Mylyn.
There is a problem with a popup. Submission may take some time and I often switch to some other editor and start typing something, so any popup that jump out would break my typing. I wonder if it is better to show info in the editor title area, maybe a link for opening info dialog or a tooltip.
(In reply to comment #26) > There is a problem with a popup. Submission may take some time and I often > switch to some other editor and start typing something, so any popup that jump > out would break my typing. > > I wonder if it is better to show info in the editor title area, maybe a link for > opening info dialog or a tooltip. Eugene, what popup are you talking about or was this comment intended for another bug?
(In reply to comment #27) > Eugene, what popup are you talking about or was this comment intended for > another bug? Sorry about this, the comment was for another bug indeed.
*** Bug 251545 has been marked as a duplicate of this bug. ***
*** Bug 183106 has been marked as a duplicate of this bug. ***
*** Bug 264593 has been marked as a duplicate of this bug. ***
Reopening as requested. I still seeing spring context files disappearing from the Package Explorer view even when they are marked as landmark.
Since this is now almost two year old and significant changes have been made, please open a new bug to describe the problem you are experiencing and provide steps to reproduce. It helps us track changes made for a particular release. Thanks and sorry for the inconvenience.
