- This topic has 9 replies, 2 voices, and was last updated 17 years, 9 months ago by Lance Drake.
-
AuthorPosts
-
Lance DrakeMemberFor some reason – I am now getting XDoclet errors – I just installed MacOSX 10.4.9 8P2127 – Is anyone else seeing a similar problem?
Thanks!
Lance Drake
Lance DrakeMemberWell – the errors do continue to be a problem – and things were going so well for such along time.
ERRORS LIST MAY BE SEEN AT: http://www.drake.org/test/JSF_errors.gif
So – I did a complete re-install – and the situation remains the same. Any idea if this is a MacOSX problem or is there some Eclipse config particular I am missing?
Please advise.
Thank you!
Lance Drake
Scott AndersonParticipantLance,
It looks like your MyEclipse install has been disabled, based on the erro messages. That’s really peculiar. Did your “full re-install” include Eclipse? In a separate folder? And a new MyEclipse instance that points to it? In any event, the install is the issue at this point; disabled plugins are not good.
Lance DrakeMemberHi Scott – Hey thanks for the quick response – this is a big deal at my desk.
I trashed the original eclipse folder AND the MyEclipse folder, as well. I downloaded fresh copies and first installed Eclipse 3.2.1 and then the 5.1 GA version of MyEclipse. I am assuming that your suggestion about something going wrong with the installer is correct. IS there anything I can do to insure the disabled plug-in: “com.genuitec.eclipse.jsf” can be activated?
Scott AndersonParticipantLance,
Two things come to mind. First, try restarting Eclipse with the -clean commanline option. This causes the plugin cache to be rebuilt and can often correct various startup problems like this. To do that on the Mac, you have to dig down into Eclipse.App and modify the XML file that is used to launch the application. I forget it’s name, since I’m not a Mac user”, but it’s in there and relatively obvious. The -clean option should be the first one so the commandline that gets executed will look like “eclipse -clean …rest of args”. In addition, please use a *new* workspace with the first restart and see if the error log items reoccur. Using a new workspace is critical; please don’t open on your existing one as we’re trying to isolate the issue. If there are errors logged, please email the file at <workspace>/.metadata/.log to support at myeclipseide.com and include the URL for this thread so we can follow up once we’ve reviewed it.
Scott AndersonParticipantLance,
Two things come to mind. First, try restarting Eclipse with the -clean commanline option. This causes the plugin cache to be rebuilt and can often correct various startup problems like this. To do that on the Mac, you have to dig down into Eclipse.App and modify the XML file that is used to launch the application. I forget it’s name, since I’m not a Mac user”, but it’s in there and relatively obvious. The -clean option should be the first one so the commandline that gets executed will look like “eclipse -clean …rest of args”. In addition, please use a *new* workspace with the first restart and see if the error log items reoccur. Using a new workspace is critical; please don’t open on your existing one as we’re trying to isolate the issue. If there are errors logged, please email the file at <workspace>/.metadata/.log to support at myeclipseide.com and include the URL for this thread so we can follow up once we’ve reviewed it.
Lance DrakeMemberEGAD! It appears you have solved the problem! The file in question is located at:
<path to eclipse folder>/eclipse/eclipse.app/contents/MacOS/eclipse.ini
By editing the file to look like this:
-clean -vmargs -Dosgi.splashLocation=/Developer/MyEclipse Enterprise Workbench 5.1.0 GA/eclipse/MyEclipseSplash.bmp -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Xbootclasspath/p:../../../plugins/org.eclipse.jdt.debug_3.2.1.r321_v20060731/jdi.jar -Xms128m -Xmx512m -XX:PermSize=64M -XX:MaxPermSize=128M -Dorg.eclipse.swt.internal.carbon.smallFonts -Dorg.eclipse.swt.internal.carbon.noFocusRing
…then restarting Eclipse – NO MORE ERRORS! – Huzzah!, I shouted, Huzzah!
BTW – I have since edited that initial ‘-clean’ line back OUT of the file and restarted – all is well.
WOW I can now get on with the day – THANK YOU VERY MUCH!
Lance DrakeMemberWell – I may have been a little quick to call this one a done-deal. Life in eclipse-land is certainly better – but there’s more JSF plugin nonsense going on.
More to follow…
Scott AndersonParticipantLet’s move the followups to another thread so it will get the attention it deserves. I’m going to close this one since the initial issue was resolved.
Lance DrakeMemberHi Scott,
The thread to which I will post my follow-up will be named ‘JSF & Saxon Problem Follow-up’
Thanks, Lance
-
AuthorPosts