- This topic has 7 replies, 4 voices, and was last updated 19 years, 6 months ago by
.
-
Posts
-
Trying to change and save plugin.xml [1] opened from Text Editor gives messagebox warning:
———————————————-
“Save Resource in Non-Workbench encoding
———————————————–
plugin.xml will be saved in “UTF-8″ encoding which is not the current workbench encoding. This can result in conflicts with other tools. Continue anyway?”
The choices are:”Yes/No”
———————————————–
Meanwhile menu Edit–>Encoding
shows UTF-8 marked with all options gray/inactiveIt happens after opening and closing plugin.xml in
– MyEclipse XML Editor
since I already saved without this warning this file before (and without using MyEclipse XML Editor)It happens in Eclipse2.1.0 with MyEclipse Enterprise Workbench 2.7.101 (that I am to use though I have also installed Eclipse3.1 with MyEclipse on the same workstation), Windows XP Pro, SP1
[1]
plugin.xml copy-pasted from browser from
http://www.eclipse.org/articles/Article-Your%20First%20Plug-in/YourFirstPlugin.htmlWith MyEclipse 3.x and later you can change the default encoding from Window > Preferences > MyEclipse > Editors > XML to match your default system encoding.
I am sorry if I wrote ambiguously. My question is about Eclipse2.1.0 with MyEclipse Enterprise Workbench 2.7.101
Does your reply imply that MyEclipse does has no backward support?
I am sorry if I wrote ambiguously. My question is about Eclipse2.1.0 with MyEclipse Enterprise Workbench 2.7.101
Actually you were clear, I just don’t have an install of MyEclipse 2.x handy on this machine and I know in the 3.8.0 release we replaced ALL of our editors, so I don’t recall in 2.7.101 if we supported changing the encoding or where the setting was. If this is very important and you cannot upgrade, let me know and I’ll install a test copy of the old release and take a look.
There are areas like grapical workflow editors using of GEF with EMF, if to mention only the top of the iceberg, where docs, samples are mainly for Eclipse2.x.
I believe lagging of docs, exmaples, bugs resolution behind is quite determining situation with OpenSource products that follows from their biz model (and mentality). If u bet on such kind of IDE/product, then u just cannot assume in any reasonable way reliable use use the latest releases. Development doesn’t migrate even with well supported .NET! … or I can send u somewhen to Cobol and PL/1 (there are estimates that 80% of all apps in the world)
Besides the main doc, examples in the area [1] relies on Free EclipseUML. It works in Eclipse2.x and doesn’t catch in Eclipse3.x. Since it is free, my post about this problem in Omondo support forum is also flying in free air [2].
I have, at least, concurrent 8 Eclipses on one home PC and employment PC and I even do not support anything or anybody yet (but just make efforts to reproduce docs).
I do not choose my work preferences (platforms and tools), they are given to me by employer and to employer by client and to client by [censored].
It would have been nice if u also have Eclipse2.x on your PCs.
[1].
William Moore, David Dean, Anna Gerber, Gunnar Wagenknecht, Philippe Vanderheyden
IBM Redbook (with code em Eclipse 2.0, 2.10, 2.1.1)
Eclipse Development using the Graphical Editing Framework and the Eclipse Modeling Framework
http://publib-b.boulder.ibm.com/redbooks.nsf/RedpieceAbstracts/sg246302.html?Open
Em HTML:
http://www.redbooks.ibm.com/redbooks/SG246302/wwhelp/wwhimpl/java/html/wwhelp.htm
[2]
Guennadi Vanine
Post: “Free EclipseUML breaks EMF code samples in Eclipse3.1”
http://www.forum-omondo.com/viewtopic.php?t=827Guennadi,
From first hand experience with GEF (and not so first hand experience with EMF) I know that almost everything you read in the documentation for 2.x will also work on their 3.x counterparts. I occasionally refer to the redbook you mention in [1], I can assure you the fundamentals are the same and all the code will work with the latest versions of GEF (and quite very with EMF too – but I haven’t used that too much).
Sanity check: You do not need to know GEF or EMF to *use* eclipse, but only if you intend writing eclipse plugins using the two. If the latter is the case, I find it odd that you would restrict yourself to Eclipse 2 – we have frequent requests for Eclipse 3.2 which is still in the milestone stage. But, maybe your employer has other reasons :). Though API compatability is pretty decent usually, this is not the case with binary compatability and you could run into serious issues if you attempt to run a 2.x plugin on Eclipse 3.x with associated GEF and EMF versions.
RE: EclipseUML – did you download the free version for Eclipse 3.1? I guess you did, but I’m not sure how their version numbers work.
I have, at least, concurrent 8 Eclipses on one home PC and employment PC and I even do not support anything or anybody yet (but just make efforts to reproduce docs).
You do not want to know how many installations I have on mine 😉 But Eclipse 2 is not one of them.
As Riyad said, if you still need assistance, he’s the man 🙂
Best,
Brian.Hi, Brian,
did you download the free version for Eclipse 3.1
I clearly mentioned this fact in this post, cited [1], [2] on EclipseUML Free Ed.
I have corresponding downloads and installations, enabled or disabled, in all my Eclipses.I know that almost everything you read in the documentation for 2.x will also work on their 3.x counterparts
I do not read, but run adjustes, i.e. with changes, sample [1, chapter 7]
You do not need to know GEF or EMF to *use* eclipse
This knowledge, I beleived, is obligatory prerequisite in order even to read (if not speaking about running) anything from [1]
but only if you intend writing eclipse plugins using the two
I have not consulted with my leadership whether I can unveil the details of my project… but I thought it was more than dpecific from context.
we have frequent requests for Eclipse 3.2 which is still in the milestone stage
Eclipse3.2 first release is scheduled for June, 2006 and I wish to pass my condolences to any companies and their’s developers targeting it.
I really appreciate the scale of the trouble they are inThe question is for whom u target your ptroduct? For university students or for any commercial developers ALSO?
you could run into serious issues if you attempt to run a 2.x plugin on Eclipse 3.x with associated GEF and EMF versions.
My question was connected with operation of changes saving changes to the source codes that implies to their default auto-recompilation in Eclipse. I do not see how u could jump to such guess and what is the sense to run binary plug-ins from [1].
From what u wrote I clearly see that u have never given a try to the sample code from [1] in any conjunction with EMF models in Eclipse3.1+ and I couldn’t understand the rationale on this deviation from my original problem with MyEclipse.
You do not want to know how many installations I have on mine 😉 But Eclipse 2 is not one of them.
Somehow I’ve got the feel that u understand the incompatibilities between versions and I couldn’t get why u insist in avoiding any backward support with previous platforms
Sad to hear that MyEclipse support INSISTS ON AVOIDING any backward support (of previous platforms)
Guennadi,
Sad to hear that MyEclipse support INSISTS ON AVOIDING any backward support (of previous platforms)
We’re not trying to avoid supporting older products. It’s unfortunate, but the 2.7 series likely had a bug with with way the XML editor handled the encodings, which is causing the error you’re experiencing. Unfortunately, that platform is out of active development since Eclipse 3.0 shipped 1.5 years ago. At some point we simply can’t afford to keep updating multiple product streams (as is the case with all companies) so we discontinue updates to the product as the user base shrinks. Exacerbating the problem is that Eclipse 3.0 plugins are not backward compatible to Eclipse 2.1 so support would require a complete parallel development and build infrastructure which we simply no longer have.
