- This topic has 26 replies, 8 voices, and was last updated 17 years, 10 months ago by
.
-
Posts
-
Update: The bug still exists in 5.1.1. It does not happen when I open a file called “build.xml 51342” because Eclipse correctly connects this with the Ant Buildfile editor.
I just tried opening the pom.xml file that you guys had mentioned in 5.5M2 and opened it with no issues. Can you help me reproduce this bug at my end. I simply tried opening the porn.xml in the MyEclipse XML editor. Am I missing something ?
For the last time: You must open the file from the Subversion Repository Explorer of the Subclipse plugin. The XML itself is good, my guess is it’s the filename (pom.xml 51238 <- Note the number!) which breaks the editor.
You can’t replicate the issue locally because when you rename the file, Eclipse doesn’t recognize it as XML anymore. So I think this is an issue between three parties: Subclipse tells Eclipse “this is XML” and “the filename is ‘pom.xml 51238′”. Eclipse opens the XML editor and passes the filename on. The XML editor sees the filename and thinks: What the f***??
Hi Aaron,
Thank you for your patience. I was able to reproduce this bug at my end as well. I’m going to file this as a bug for my dev team. Ill get back to you with an update as soon as possible.+1 for a fix for this issue – see https://www.genuitec.com/forums/topic/error-when-opening-myeclipse-xml-editor/#post-273849
Can we have an estimate?
I’ve started a new thread asking whether a forum is the right way to track bugs. If you agree or disagree, please leave your message there.
Can you please create a document which compiles a list of things that are planned for 6.1? The status bar which we had on the old website plus the page showing all the bugs/features that have been or are being resolved, were planned to be included, etc. was really helpful to see quickly which issued would be addressed without having to harass you guys from support.
Can you please create a document which compiles a list of things that are planned for 6.1?
The list for 6.1 hasn’t been finalized yet. I’ll provide what info I can for features that are ‘absolutely’ in, but it’s not uncommon for that list of items to change all the way up until delivery window.
So now there will never likely be a flat list of “This is what to bank on for release XYZ”.
If you look at Eclipse, you can see that there are four parts of the release document which contain features for that release: Done, in work, planned and “maybe”. This makes it easy to see what will be in here, what will probably be in there and how the chances are. If it’s a big change and it’s in “maybe”, well, then better don’t hold your breath. With 6.0, I had no idea you were working on it and what might be in it until I found out about M1. And then, I still didn’t knew what was in it. So just compile the information in this way and make sure it is easy to find. That’s all I want.
