- This topic has 9 replies, 3 voices, and was last updated 15 years, 7 months ago by
.
-
Posts
-
I was trying to do a straightforward upgrade of Subclpse 1.4.8 to 1.6.2 when I noticed after updating to 7.5 ME that the SOFTWARE UPDATE MANAGER IS MISSING.
You have GOT to be kidding – how the hell am I supposed to update any of my software the straightforward Eclipse-ish easy way when the feature to easily upgrade any existing or new plug in is MISSING???
C’mon. I’ve just about had it with ME upgrades breaking things or “improving” through that Pulse piece of junk that doesn’t allow easy updating of plug ins not found in the Pulse catalog (if you notice, the Subclpse plug listed is NOT the most recent – if you can’t keep yoru catalog current with what is out there, your Pulse explorer is USELESS).
Now I have to manually stuff the right Subclipse plug stuff for 1.6.2 version into the plugin adn features directories and hoping it works just fine afterwards – WISH ME LUCK..
Sure enough, just as I anticipated, luck be damned. It seems that the 7.5 upgrade I was lured into performing in order to get an update manager has completely screwed up my ant target builds with a new & shiny “Error starting modern compiler problem”. Apparently, things are a little different on ME 7.5 – see http://www.myeclipseide.com/PNphpBB2-viewtopic-t-17956-postdays-0-postorder-asc-start-15.html.
A re-configuring of external tools to run the same JRE as the workspace appears to get me past this new & latest hurdle. I hope my original Subclipse problem is fixed – wish me luck…
I was trying to do a straightforward upgrade of Subclpse 1.4.8 to 1.6.2 when I noticed after updating to 7.5 ME that the SOFTWARE UPDATE MANAGER IS MISSING.
You have GOT to be kidding – how the hell am I supposed to update any of my software the straightforward Eclipse-ish easy way when the feature to easily upgrade any existing or new plug in is MISSING???
Since MyEclipse 7.0 we have hidden the Classic updater as it was replaced by our Pulse-based update/install mechanism. You can re-enable it by going to Prefs > General > Capabilities… this isn’t new behavior (more than 6 months).
C’mon. I’ve just about had it with ME upgrades breaking things or “improving” through that Pulse piece of junk that doesn’t allow easy updating of plug ins not found in the Pulse catalog (if you notice, the Subclpse plug listed is NOT the most recent – if you can’t keep yoru catalog current with what is out there, your Pulse explorer is USELESS).
You can use Pulse to install software from *any* update site, the catalog is just a handy seed, you just click “Add” to register new update sites and then the content is included in the full software listing window and you are able to use the quick-filter to find whatever you want. The Pulse Manager is an enhancement to the default update mechanism in Eclipse, it doesn’t remove *any* functionality.
Sure enough, just as I anticipated, luck be damned. It seems that the 7.5 upgrade I was lured into performing in order to get an update manager has completely screwed up my ant target builds with a new & shiny “Error starting modern compiler problem”. Apparently, things are a little different on ME 7.5 – see http://www.myeclipseide.com/PNphpBB2-viewtopic-t-17956-postdays-0-postorder-asc-start-15.html.
MyEclipse updated it’s JRE from 1.5.0_11 to 1.6.0_13, what likely happened is you had some hard references to the older JRE set in your Ant runtime configurations and you just set those back to workbench default and it’s fine now.
This would occur if you had a standard Eclipse install and bumped your JDK on your host machine and relaunched, again, no magic here just an unfortunate side effect of runtime configurations.
Thanks for the tip on getting the classic updater back.
I tried using Pulse to add an update link for Subclipse, but could not find how in the heck to do this. So, without an update manager, I did the old school thing and updated Subclipse manually. The end result was bumping into the “Modern compiler” problem upon building, which was solved by setting the JRE to the workstation for ant. Unformatunately, this builds a non-runnable target because I have a JDK 1.5 runtime (getting “class id” errors).
So, How in the heck do I tell ant to build with JDK 1.5 without bumping into the “Modern compiler” problem again? For that matter, how do you adjust the whole workstation to run with JDK 1.5?
lhale,
I believe Ant, when creating default runtime configurations (Run As > Ant) will pickup the default JRE for the workspace. This is *typically* the JRE that runs MyEclipse, in 7.0 and 7.1 this was 1.5.0_11 and in 7.5 and beyond it will be 1.6.0_13 — if you go to Prefs > Java > Installed JREs, you can set the workbench default JRE. Any existing ant runtime configs will need to be updated (or erased and re-created if you want) to pickup that pref.
To address the adding of the subclipse update site, I’ve screenshotted my flow for you, hopefully it helps clarify how to use that UI (maybe we should make it more intuitive?):
Looks like I previously added a Subclupse 1.6.x under Personal Sites using Pulse, but the problem was that the resulting upgrade never happened (I was still stuck at 1.4.8 after upgrading).
That’s the problem with MyEclipse – There’s a MyEclipse->Prefs and there’s a Window->Prefs. Now, which one do you think I tried to change the workspace’s JRE? One would think that choosing the MyEclipse choice would be the right one, but that would be wrong (and non-intuitive).
Anyways, I already see my Installed JRE from before the 7.5 upgrade (JRE 5.0.3) and all the execution environments (except for JavaSE-1.6) are set to JRE 5.0.3. So, if the workbench default JRE is already set to JRE 5.0.3, then you’re telling me I need to get rid of the current ant setup and hopefully the new one will pipck up the JRE 5.0.3 preference?
I always get that “Error starting modern compiler” message when I set my ant JRE to something other than the workspace default – how the hell do I get rid of this nonsense when trying to run ant @ JRE 5? I’ve already been through the Window->Prefs stuff – what’s next?????
There’s a MyEclipse->Prefs and there’s a Window->Prefs. Now, which one do you think I tried to change the workspace’s JRE? One would think that choosing the MyEclipse choice would be the right one, but that would be wrong (and non-intuitive).
Hmmm that’s true, that is confusing. The MyEclipse > Prefs is just a filtered view of the entire preference dialog only showing MyEclipse preferences.
Window > Prefs shows you an unfiltered view of the entire workbench preferences.
Anyways, I already see my Installed JRE from before the 7.5 upgrade (JRE 5.0.3) and all the execution environments (except for JavaSE-1.6) are set to JRE 5.0.3. So, if the workbench default JRE is already set to JRE 5.0.3, then you’re telling me I need to get rid of the current ant setup and hopefully the new one will pipck up the JRE 5.0.3 preference?
If you go to Prefs > Java > Installed JREs, the default JRE is the one with the checkmark next to it any *new* runtime configurations will pick this to run with. You can also go to the external tools menu and open the dialog there and check what your ant configurations are set to run using to make sure they are set to “Workbench default”
I always get that “Error starting modern compiler” message when I set my ant JRE to something other than the workspace default – how the hell do I get rid of this nonsense when trying to run ant @ JRE 5? I’ve already been through the Window->Prefs stuff – what’s next?????
I just found this link (http://www.pitr.net/index.php/2006/12/17/error-starting-modern-compiler/) do you have a JAVA_HOME environment variable setting by chance that points at something different than the default JRE you have set in MyEclipse?
Ant actually honors those env vars, so it’s possible it’s screwing with it’s execution when it attempts to fire off the modern compiler.
I do want to clarify that we don’t instrument Ant in any way — this would all be occurring in standard Eclipse as well as it’s all the same mechanisms.
I already went the route of Java prefs and external tools to verify they were at JRE 5.0.3. However, your mention of JAVA_HOME showed that I do have it set to a JRE 5.0.5, which is different from the workspace flavor. Once I re-set the workspace JRE to the 5.0.05 flavor pointed to by JAVA_HOME, my ‘modern compiler’ error went away. Thanks for that suggestion.
