Can't open CFM/CFC files??

269 views
Skip to first unread message

Bryan Stevenson

unread,
Jul 22, 2008, 2:44:32 PM7/22/08
to cfeclip...@googlegroups.com
Hey All,

OK....just installed Eclipse 3.4 on a Win XP Pro virtual machine
(running in VirtualBox on an Ububtu Hardy 8.04 host OS). I then
installed CFEclipse 1.3.1.1.

I added some projects (with folders linked to the file system) and tried
to open some of the files in those projects. For every CFM or CFC file
I try and open, Eclipse gives me this error:

"Could not open the editor: Editor could not be initialized"

Here's the error output:

java.lang.NoClassDefFoundError:
org/eclipse/ui/internal/editors/text/JavaFileEditorInput
at
org.cfeclipse.cfml.editors.CFDocumentProvider.setDocumentContent(CFDocumentProvider.java:175)
at
org.cfeclipse.cfml.editors.CFDocumentProvider.createDocument(CFDocumentProvider.java:87)
at
org.eclipse.ui.editors.text.FileDocumentProvider.createElementInfo(FileDocumentProvider.java:734)
at
org.eclipse.ui.texteditor.AbstractDocumentProvider.connect(AbstractDocumentProvider.java:398)
at
org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(AbstractTextEditor.java:3990)
at
org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(StatusTextEditor.java:190)
at
org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1325)
at org.eclipse.ui.texteditor.AbstractTextEditor
$19.run(AbstractTextEditor.java:3025)
at
org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:446)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:354)
at org.eclipse.jface.window.ApplicationWindow
$1.run(ApplicationWindow.java:758)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at
org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:755)
at
org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2483)
at
org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(AbstractTextEditor.java:3043)
at
org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:3070)
at
org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:799)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:643)
at
org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594)
at
org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:266)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729)
at org.eclipse.ui.internal.WorkbenchPage.access
$11(WorkbenchPage.java:2721)
at org.eclipse.ui.internal.WorkbenchPage
$10.run(WorkbenchPage.java:2673)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2643)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:646)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:605)
at
org.eclipse.ui.actions.OpenFileAction.openFile(OpenFileAction.java:99)
at
org.eclipse.ui.actions.OpenSystemEditorAction.run(OpenSystemEditorAction.java:99)
at
org.eclipse.ui.views.navigator.OpenActionGroup.runDefaultAction(OpenActionGroup.java:125)
at
org.eclipse.ui.views.navigator.MainActionGroup.runDefaultAction(MainActionGroup.java:329)
at
org.eclipse.ui.views.navigator.ResourceNavigator.handleOpen(ResourceNavigator.java:716)
at org.eclipse.ui.views.navigator.ResourceNavigator
$6.open(ResourceNavigator.java:443)
at org.eclipse.jface.viewers.StructuredViewer
$2.run(StructuredViewer.java:820)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at
org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818)
at
org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079)
at org.eclipse.jface.viewers.StructuredViewer
$6.handleOpen(StructuredViewer.java:1183)
at
org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257)
at org.eclipse.jface.util.OpenStrategy
$1.handleEvent(OpenStrategy.java:297)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.ui.internal.editors.text.JavaFileEditorInput
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:481)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 72 more


So the first line seems to indicate a missing class.....not sure what to
do about it though....any ideas??

TIA

Cheers
-


Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
phone: 250.480.0642
fax: 250.480.1264
cell: 250.920.8830
e-mail: br...@electricedgesystems.com
web: www.electricedgesystems.com

Notice:
This message, including any attachments, is confidential and may contain
information that is privileged or exempt from disclosure. It is intended
only for the person to whom it is addressed unless expressly authorized
otherwise by the sender. If you are not an authorized recipient, please
notify the sender immediately and permanently destroy all copies of this
message and attachments.

Dan Wilson

unread,
Jul 22, 2008, 3:03:47 PM7/22/08
to cfeclip...@googlegroups.com
Bryan,

start Ecipse from the command line using the -clean option..


c:\eclipse\eclipse.exe -clean

(you'll need to put your own directory path to the eclipse.exe executable..)


DW
--
"Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew."

Guillaume Apollinaire quotes

Sonny Savage

unread,
Jul 22, 2008, 3:14:03 PM7/22/08
to cfeclip...@googlegroups.com
You should also check your Java version.  CFE requires 1.5 or higher.  You can specify the JRE to use on the command line as described here:
http://trac.cfeclipse.org/cfeclipse/wiki/CommandLine
Or, you can put it in your eclipse.ini, as described here:
http://trac.cfeclipse.org/cfeclipse/wiki/PerformanceSettings

Bryan Stevenson

unread,
Jul 22, 2008, 3:38:53 PM7/22/08
to cfeclip...@googlegroups.com
Thanks Dan.....but no love on that one.

-closed Eclipse
-ran the appropriate command in the command prompt
-Eclipse opened
-tried to open CFC and got the same error

Any other ideas?

TIA

Cheers
-


Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
phone: 250.480.0642
fax: 250.480.1264
cell: 250.920.8830
e-mail: br...@electricedgesystems.com
web: www.electricedgesystems.com

Notice:
This message, including any attachments, is confidential and may contain
information that is privileged or exempt from disclosure. It is intended
only for the person to whom it is addressed unless expressly authorized
otherwise by the sender. If you are not an authorized recipient, please
notify the sender immediately and permanently destroy all copies of this
message and attachments.


On Tue, 2008-07-22 at 15:03 -0400, Dan Wilson wrote:
> c:\eclipse\eclipse.exe -clean


Stephen Davison

unread,
Jul 22, 2008, 5:14:04 PM7/22/08
to CFEclipse Users
You might try a more recent version of CFE (e.g. 1.3.1.6) instead of
1.3.1.1

On Jul 22, 1:38 pm, Bryan Stevenson <br...@electricedgesystems.com>
wrote:

Bryan Stevenson

unread,
Jul 22, 2008, 5:24:14 PM7/22/08
to cfeclip...@googlegroups.com

>
On Tue, 2008-07-22 at 14:14 -0700, Stephen Davison wrote:
> You might try a more recent version of CFE (e.g. 1.3.1.6) instead of
> 1.3.1.1
>

hmmm....OK...so I got the ltest stable release through the Eclipse
updater....so how do I get 1.3.1.6?

Thanks

Bryan Stevenson

unread,
Jul 22, 2008, 5:45:31 PM7/22/08
to cfeclip...@googlegroups.com
nevermind....found it (been a while since I used Eclipse....some options
have moved...hehe).

The upgrade to 1.3.1.6 hasn't solved the issue....just created a new one
when opening CFM/CFC files...error is now:

Could not open the editor. org.eclipse.jface.text.Document cannot be
cast to org.cfeclipse.cfml.editors.ICFDocument.

Any thoughts?

Cheers
-


Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
phone: 250.480.0642
fax: 250.480.1264
cell: 250.920.8830
e-mail: br...@electricedgesystems.com
web: www.electricedgesystems.com

Notice:
This message, including any attachments, is confidential and may contain
information that is privileged or exempt from disclosure. It is intended
only for the person to whom it is addressed unless expressly authorized
otherwise by the sender. If you are not an authorized recipient, please
notify the sender immediately and permanently destroy all copies of this
message and attachments.

Bryan Stevenson

unread,
Jul 22, 2008, 5:49:09 PM7/22/08
to cfeclip...@googlegroups.com
On Tue, 2008-07-22 at 15:14 -0400, Sonny Savage wrote:
> You should also check your Java version. CFE requires 1.5 or higher.
> You can specify the JRE to use on the command line as described here:
> http://trac.cfeclipse.org/cfeclipse/wiki/CommandLine
> Or, you can put it in your eclipse.ini, as described here:
> http://trac.cfeclipse.org/cfeclipse/wiki/PerformanceSettings
>

Hey Sonny,

Thanks for the links. I altered eclipse.ini and no difference :-(

Sonny Savage

unread,
Jul 22, 2008, 6:13:42 PM7/22/08
to cfeclip...@googlegroups.com
I could swear that's the error when the wrong JRE is being used... are you sure you put the correct path?  Double check where it is installed on your machine.

Bryan Stevenson

unread,
Jul 22, 2008, 6:25:56 PM7/22/08
to cfeclip...@googlegroups.com
LOL...I'm not that new Sonny.....but thanks for being thourough;-)

Here's what I have (just in case):

-vm
C:\Program Files\Java\jre1.6.0_7\bin\javaw.exe
then other vm settings follow as per the links you sent

I double checked and sure enough Java resides at:
C:\Program Files\Java\jre1.6.0_7\bin\javaw.exe

As you'll see by my most recent mail....I upgraded CFECLIPSE to 1.3.1.6
and have a new error (but still can't open a CFM/CFC file).

TIA

Cheers
-


Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
phone: 250.480.0642
fax: 250.480.1264
cell: 250.920.8830
e-mail: br...@electricedgesystems.com
web: www.electricedgesystems.com

Notice:
This message, including any attachments, is confidential and may contain
information that is privileged or exempt from disclosure. It is intended
only for the person to whom it is addressed unless expressly authorized
otherwise by the sender. If you are not an authorized recipient, please
notify the sender immediately and permanently destroy all copies of this
message and attachments.


Bryan Stevenson

unread,
Jul 22, 2008, 6:43:36 PM7/22/08
to cfeclip...@googlegroups.com
Time to eat my hat ;-)

I just knew as soon as I said "I'm not that new" I'd find something
totally stupid....and I was right ;-)

The new error is simply because my projects are on remote machines via
mapped drives....I forgot to map them first!!!

I guess I was so focused on the problem I forgot the basics.....and last
time I used Eclipse it handled this situation with a different error.

Just one of those days I guess ;-)

Thanks for hanging in there with me guys

Cheers
-


Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
phone: 250.480.0642
fax: 250.480.1264
cell: 250.920.8830
e-mail: br...@electricedgesystems.com
web: www.electricedgesystems.com

Notice:
This message, including any attachments, is confidential and may contain
information that is privileged or exempt from disclosure. It is intended
only for the person to whom it is addressed unless expressly authorized
otherwise by the sender. If you are not an authorized recipient, please
notify the sender immediately and permanently destroy all copies of this
message and attachments.


Andrew Scott

unread,
Jul 22, 2008, 8:37:57 PM7/22/08
to cfeclip...@googlegroups.com
When are people going to read that CFEclipse 1.3.1.1 is not compatible with
Eclipse 3.2 and above?

I suppose the thought of grabbing the latest CFEclipse version was not in
your arsenal of thought patterns either?

--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273

Rick Faircloth

unread,
Jul 23, 2008, 7:54:45 AM7/23/08
to cfeclip...@googlegroups.com
My, but aren't we grumpy today...

Sonny Savage

unread,
Jul 23, 2008, 8:59:22 AM7/23/08
to cfeclip...@googlegroups.com
Mark D may have to chime in on this one....

Have you tried pointing at a new workspace?

My eclipse.ini was pointing at the 1.5 JRE, so I switched it to 1.6.  I'm still not getting the error that you are.  Here's what I have:
-startup
plugins\org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.100.v20080509-1800
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm
C:\Program Files\Java\jre1.6.0_07\bin\javaw.exe
-vmargs
-Xms40m
-Xmx256m

Bryan Stevenson

unread,
Jul 23, 2008, 11:04:24 AM7/23/08
to cfeclip...@googlegroups.com

> On Wed, 2008-07-23 at 10:37 +1000, Andrew Scott wrote:
> When are people going to read that CFEclipse 1.3.1.1 is not compatible
> with
> Eclipse 3.2 and above?
>

Well thanks for the kind words and implication that I'm an idiot
Andrew....

Just FYI...

I dloaded and installed Eclipse classic from the Eclipse site (of course
no mention of CFEClipse compatibility in the dload process).

Then I ran Eclipse and went through the software update process. That
initially provided me with one option...CFEclipse 1.3.1.1. Again....no
mention of compatability with Eclipse.

So Mr. everyone's an idiot.....

Where exactly in the standard dload and install process for Eclipse and
then CFEclipse is one suppose to be informed about compatibility
issues??

>
> I suppose the thought of grabbing the latest CFEclipse version was not
> in
> your arsenal of thought patterns either?
>


Of course I wanted the latest version and as is the case with most
software updaters, I expected I would be presented with the:

a) latest stable release (guess not as I know have 1.3.1.6)
b) bleeding edge version


If there is such a big issue with 3.2 + and 1.3.1.1, then the updater
should STOP that combo.

Jim Priest

unread,
Jul 23, 2008, 11:35:42 AM7/23/08
to cfeclip...@googlegroups.com
On Wed, Jul 23, 2008 at 11:04 AM, Bryan Stevenson
<br...@electricedgesystems.com> wrote:
> I dloaded and installed Eclipse classic from the Eclipse site (of course
> no mention of CFEClipse compatibility in the dload process).

Nor should there be - while CFEclipse is a plugin - Eclipse certainly
can't provide installation instructions for every plugin available.

> Then I ran Eclipse and went through the software update process. That
> initially provided me with one option...CFEclipse 1.3.1.1. Again....no
> mention of compatability with Eclipse.

I'm curious what installation directions did you follow to install?
I agree there are a few places with installation instructions which I
need to clean up and point to one place.

> Of course I wanted the latest version and as is the case with most
> software updaters, I expected I would be presented with the:
>
> a) latest stable release (guess not as I know have 1.3.1.6)
> b) bleeding edge version

If you follow the instructions outlined on the CFEclipse site:
http://www.cfeclipse.org/download.cfm

It does mentions selecting the 'stable' option and then picking the
latest version. It's been awhile since I've actually installed
everything from scratch. If you can provide any insight on how that
process can be made more intuitive - please let us know and we'll try
to update things.

The Eclipse setup process can be intimidating for new users and we
want to make it as easy as possible!

Jim

Bryan Stevenson

unread,
Jul 23, 2008, 12:14:43 PM7/23/08
to cfeclip...@googlegroups.com
Hey Jim.....glad to help out....replies below....
-


Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
phone: 250.480.0642
fax: 250.480.1264
cell: 250.920.8830
e-mail: br...@electricedgesystems.com
web: www.electricedgesystems.com

Notice:
This message, including any attachments, is confidential and may contain
information that is privileged or exempt from disclosure. It is intended
only for the person to whom it is addressed unless expressly authorized
otherwise by the sender. If you are not an authorized recipient, please
notify the sender immediately and permanently destroy all copies of this
message and attachments.


On Wed, 2008-07-23 at 11:35 -0400, Jim Priest wrote:
> On Wed, Jul 23, 2008 at 11:04 AM, Bryan Stevenson
> <br...@electricedgesystems.com> wrote:
> > I dloaded and installed Eclipse classic from the Eclipse site (of course
> > no mention of CFEClipse compatibility in the dload process).
>
> Nor should there be - while CFEclipse is a plugin - Eclipse certainly
> can't provide installation instructions for every plugin available.

Yep...that was definately meant to be sarcastic ;-)

>
> > Then I ran Eclipse and went through the software update process. That
> > initially provided me with one option...CFEclipse 1.3.1.1. Again....no
> > mention of compatability with Eclipse.
>
> I'm curious what installation directions did you follow to install?
> I agree there are a few places with installation instructions which I
> need to clean up and point to one place.

The ones you've provided a link to
below....http://www.cfeclipse.org/download.cfm

>
> > Of course I wanted the latest version and as is the case with most
> > software updaters, I expected I would be presented with the:
> >
> > a) latest stable release (guess not as I know have 1.3.1.6)
> > b) bleeding edge version
>
> If you follow the instructions outlined on the CFEclipse site:
> http://www.cfeclipse.org/download.cfm
>
> It does mentions selecting the 'stable' option and then picking the
> latest version. It's been awhile since I've actually installed
> everything from scratch. If you can provide any insight on how that
> process can be made more intuitive - please let us know and we'll try
> to update things.

....and this is where things got confused.

I'd suggest doing it all from scratch as it appears that Eclipse 3.4 has
altered the software updater. I added the CFEclipse URL to the updater
and then looked for what I was after. I read the bit about "stable
release", but I had no such option. So I naturally picked what was
presented to me (1.3.1.1) and went with it.

It was only after someone mentioned 1.3.1.6 yesterday that i went back
to the updater to see if I could find any other available versions.

So it seems like the basics of the process are still outlined in the
dload instructions, a 2nd pass of the process with Eclipse 3.4 may give
you the finer details to update the instructions ;-)

Most notably...there is no longer anywhere to select a "stable"
option ;-)

>
> The Eclipse setup process can be intimidating for new users and we
> want to make it as easy as possible!

Definately!! My biggest issue when I first used CFEclipse was the
concept of projects (having used HomeSite and CF Studio for years).
Having some upfront info on comparisons of how things work in file base
editors vs. project based ones

1) search options change quite a bit

2) How to setup projects so they can be easily/quickly refreshed. This
can be really bad on remote projects. I've found it best to create a
project folder and then add each folder in an application as linked
folders under it so each linked folder can be refreshed individually
instead of just adding the root application folder and having to refresh
the whole thing.

Thanks for keeping the wiki et al up-to-date Jim!

Cheers

>
> Jim
>
> >


Jim Priest

unread,
Jul 23, 2008, 12:20:56 PM7/23/08
to cfeclip...@googlegroups.com
On Wed, Jul 23, 2008 at 12:14 PM, Bryan Stevenson
<br...@electricedgesystems.com> wrote:
> I'd suggest doing it all from scratch as it appears that Eclipse 3.4 has
> altered the software updater. I added the CFEclipse URL to the updater
> and then looked for what I was after. I read the bit about "stable

Gotcha! I'll try to find some time this week to do a fresh install
w/3.4 and document the steps and update things...

Jim

Sonny Savage

unread,
Jul 23, 2008, 12:35:18 PM7/23/08
to cfeclip...@googlegroups.com
I'd like to add that in 3.4, when I installed CFE, the auto-update process kept prompting me to install the beta version.  I, like Bryan, don't see a way to toggle this.

Peter J. Farrell

unread,
Jul 23, 2008, 2:37:00 PM7/23/08
to CFEclipse Users
I fixed it by using the 1.3.2beta of CFEclipse. Here's a quick blog
post about how I resolved it:
http://blog.maestropublishing.com/index.cfm?mode=entry&entry=50E6BC04-1372-3F66-70C30F4A35A0BA4D

Andrew Scott

unread,
Jul 23, 2008, 11:22:23 PM7/23/08
to cfeclip...@googlegroups.com
Google it?

In the last 12 months, there has been enough information posted around the traps about how 1.3.1.1 is not compatible.

Also a quick google search would have also netted the result that there is a newer version... Also if you got 1.3.1.1 instead of 1.3.1.5 then this needs to be reported as a bug.

I have always got the 1.3.1.5 for all installes of Eclipse / CFEclipse.

Also if you googled, you would have noticed that the JVM is also extremely important as well when running Eclipse.

Now I know that your situation turned out different. But here is a few more FYI's for anyone else that is running Eclipse.

If you are having issues it is recommended that from time to time you delete or use a new workspace. Or better still delete everything in the workspace, this has caught a lot of people out over the years. Why because sometimes something gets corrupt and Eclipse just plots along until something broken shows up.

Always double check that the version of Eclipse that you are running, is indeed running on the correct JVM.

Now the one thing I have noticed on the CFEclipse.org website (someone can correct me if I am wrong) but it an assumption that we all know what we are doing. So maybe somewhere in the site it should explain that to run Eclipse/CFEclipse Vx.y.z one needs to use these minimum requirements.

Even though google can answer that, there should be a precise attempt to minimise the support questions in these situations.

@Jim - What do you think?

Andrew Scott

unread,
Jul 23, 2008, 11:27:16 PM7/23/08
to cfeclip...@googlegroups.com

Jim,

I made this statement in a previous post. But have typed it here again, for
easier clarification.

I am not sure as I haven't browsed the wiki/trac for a little while. But it
seems that the same thing is always being asked.

Am I running the right JVM version, how do I know the latest stable version
and what are the minimum requirements.

And for posterity older version should be listed, for anyone who isn't
running the latest version with all minimum requirements for JVM etc.

As much as the information has changed and improved on the WIKI, the
important things like minimum requirements for the plugin are not discussed.

What do you think Jim?

--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273


-----Original Message-----
From: cfeclip...@googlegroups.com
[mailto:cfeclip...@googlegroups.com] On Behalf Of Jim Priest
Sent: Thursday, 24 July 2008 1:36 AM
To: cfeclip...@googlegroups.com

Andrew Scott

unread,
Jul 23, 2008, 11:29:53 PM7/23/08
to cfeclip...@googlegroups.com
Weird...

I installed Eclipse 3.4 on 3 machines, and installed CFEclipse via the
update mechanism built into Eclipse.

Yes it has changed, but it still works ok.

Also what version of Eclipse is being installed? There are at least 4
different builds of Eclipse that one can download from Java, J2EE etc.

And guess what? I have not had a problem getting the latest stable build of
cfeclipse.


--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273


-----Original Message-----
From: cfeclip...@googlegroups.com
[mailto:cfeclip...@googlegroups.com] On Behalf Of Jim Priest

Sent: Thursday, 24 July 2008 2:21 AM
To: cfeclip...@googlegroups.com

Andrew Scott

unread,
Jul 23, 2008, 11:31:18 PM7/23/08
to cfeclip...@googlegroups.com

Hmmm...

 

As stated in another post, with me and the 3 installs of Eclipse 3.4 and CFEclipse 1.3.1.6 I have always seen Stable and is it bleeding Edge versions.

 

Seems like some very weird shit happening on your machines?

 

 

--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613
9015 8628
Mobile: 0404 998 273

 

 

 

From: cfeclip...@googlegroups.com [mailto:cfeclip...@googlegroups.com] On Behalf Of Sonny Savage


Sent: Thursday, 24 July 2008 2:35 AM
To: cfeclip...@googlegroups.com

Michael Benner

unread,
Jul 23, 2008, 11:43:56 PM7/23/08
to cfeclip...@googlegroups.com
I just did a fresh install today with 3.4 and the update site. I had to uncheck show only current version. When I did that ALL versions then showed up and it let me pick any of them. If you can't find that check box let me know and I will send a screencast or something. 

Mike Benner
pipelineSuite.com

Jim Priest

unread,
Jul 24, 2008, 8:13:06 AM7/24/08
to cfeclip...@googlegroups.com
On Wed, Jul 23, 2008 at 11:27 PM, Andrew Scott

>
> Am I running the right JVM version, how do I know the latest stable version
> and what are the minimum requirements.
>
> And for posterity older version should be listed, for anyone who isn't
> running the latest version with all minimum requirements for JVM etc.
>

Well - on the Wiki home page there is the 'recommended' setup:

Current CFEclipse Version: 1.3.1.6
Recommended:
Eclipse Version: 3.3
Java 1.5+

I'm not sure if that's really changed considering the problems most
people have with 3.4 and the beta of CFE?

I could add an 'older version matrix' but not sure of the value of
pointing people back towards earlier versions... Anyone see any
benefit of that?

Does anyone purposely run an older version of CFE? If so - why?

Jim

Mike Henke

unread,
Jul 24, 2008, 8:43:04 AM7/24/08
to CFEclipse Users
I tried switching JVMs and thought I was using the correct one with
the eclipse.ini but checking Help --> About Eclipse SDK-->
Configuration Details button iIt listed Eclipse as using the old JVM.
I eventuall resolved the issue but you may want to re-check the Config
Details to make sure which JVM Eclipse is using.

Bryan Stevenson

unread,
Jul 24, 2008, 11:09:38 AM7/24/08
to cfeclip...@googlegroups.com
Andrew....the point you missed is that one should not have to search to
find such apparently serious compatibility issues when installing
software. If it's that bad there should be a damn big warning message
or the combination of versions should be stopped at the application
level (i.e. the Eclipse software updater).

...and BTW...I did check Google and did NOT see anything obvious...thus
posting to this list ;-)

Cheers
-


Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
phone: 250.480.0642
fax: 250.480.1264
cell: 250.920.8830
e-mail: br...@electricedgesystems.com
web: www.electricedgesystems.com

Notice:
This message, including any attachments, is confidential and may contain
information that is privileged or exempt from disclosure. It is intended
only for the person to whom it is addressed unless expressly authorized
otherwise by the sender. If you are not an authorized recipient, please
notify the sender immediately and permanently destroy all copies of this
message and attachments.


Andrew Scott

unread,
Jul 25, 2008, 12:47:58 AM7/25/08
to cfeclip...@googlegroups.com
Jim,

Requirements and recommendations are 2 different things.... Yes!!

If it was me, I would add the requirements minimum from now on. And I guess
overtime, as new releases come and go, the information could be there for
prosperity.

--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273


-----Original Message-----
From: cfeclip...@googlegroups.com
[mailto:cfeclip...@googlegroups.com] On Behalf Of Jim Priest
Sent: Thursday, 24 July 2008 10:13 PM
To: cfeclip...@googlegroups.com
Subject: [cfeclipse-users] Re: Can't open CFM/CFC files??

Charlie Griefer

unread,
Jul 25, 2008, 12:50:42 AM7/25/08
to cfeclip...@googlegroups.com
On Thu, Jul 24, 2008 at 9:47 PM, Andrew Scott <andrew...@aegeon.com.au> wrote:

Jim,

Requirements and recommendations are 2 different things.... Yes!!

If it was me, I would add the requirements minimum from now on. And I guess
overtime, as new releases come and go, the information could be there for
prosperity.

Hey sign me up for some of that there prosperity!

--
A byte walks into a bar and orders a pint. Bartender asks him "What's wrong?" Byte says "Parity error." Bartender nods and says "Yeah, I thought you looked a bit off."

Jim Priest

unread,
Jul 25, 2008, 7:51:44 AM7/25/08
to cfeclip...@googlegroups.com
Problem is the 'requirements' fluctuate wildly esp. when you start
tossing in other plugins like Flexbuilder, etc... I'm a bit swamped
right now but I'll put it on my todo list :)

Maybe another option would be a 'works for me' page on the wiki where
people could post their setups (including other plugins) and if it
works for them (and if they had to hack anything to make it work)

Jim

Mike Henke

unread,
Jul 25, 2008, 9:29:07 AM7/25/08
to CFEclipse Users
Not sure if this helps but I noticed Mylyn does this for dealing with
different versions of Eclipse

The update site will vary depending on the version of Eclipse you are
using.
Eclipse 3.2: http://download.eclipse.org/tools/mylyn/update/e3.2
Eclipse 3.3: http://download.eclipse.org/tools/mylyn/update/e3.3
Eclipse 3.4: http://download.eclipse.org/tools/mylyn/update/e3.4
Reply all
Reply to author
Forward
0 new messages