I'm having issues too. Tried to revert back to 1.3.4 and it won't let me either. At this point, I have no CFEclipse working on my machine (even went to a new install of Eclipse to make sure). Running Ganymede (3.4.2)
--
For more information on CFEclipse visit: cfeclipse.org
For support, FAQ and tips and tricks visit: trac.cfeclipse.org
You are subscribed to the Google Groups "CFEclipse Users" group.
To post send email to: cfeclip...@googlegroups.com
To unsubscribe send email to: cfeclipsIe-use...@googlegroups.com
For more options, visit this group online: http://groups.google.com/group/cfeclipse-users?hl=en
Eclipse v3.5.2
CFEclipse v1.3.7.201002282356
If you removed the CFEclipse folders, have you tried doing an "eclipse
-clean"?
Raffaele
--
For more information on CFEclipse visit: cfeclipse.org
For support, FAQ and tips and tricks visit: trac.cfeclipse.org
You are subscribed to the Google Groups "CFEclipse Users" group.
To post send email to: cfeclip...@googlegroups.com
To unsubscribe send email to: cfeclipse-use...@googlegroups.com
Close Eclipse if it's running.
Go into your "plugins" directory and remove all the cfe directories
(or move to backup folder).
Repeat with the "features" directory.
Restart Eclipse with -clean argument.
Then you can re-install, and de-select the "only show latest version"
to pick the previous one.
--
And when you do an update in Eclipse, is there any core eclipse stuff
that shows as update-able?
Gracias!
:Den
--
We live at a time when man believes himself fabulously capable of
creation, but he does not know what to create.
Jose Ortega y Gasset
--
Thanks Sandra!
Interesting. That's the same version I ran my test against. Works
fine (on Win7), besides taking a second update to pull down MXUnit.
Whoops, spoke too soon, looks like I'm getting that bundle error too,
when I try to create a new CFML project.
> When it broke for me the first time, I ended up creating an entirely new
> Eclipse module with a new workspace. I updated everything first and then
> tried to install the new version. It didn't work. As Dan pointed out the
> jar file seems to only have features.xml in it.
> which looks like the updater in cfeclipse only had the file from
> http://www.cfeclipse.org/update-preview/features/ in it rather than the one
> from http://www.cfeclipse.org/update-preview/plugins possibly?
Hrm, looking at the jars, all seems right. There's a feature jar
(with feature.xml) in features/ and a plugin jar in plugins/, and the
plugin jar looks like it has what it should.
I wonder if this is a network or proxy caching issue? Sometimes it
seems like eclipse doesn't pick up the changed site.xml file.
I think there are two errors here, one with the start-up help pop-up,
and the other with maybe a bad download or cache deal.
I've pushed another build to http://cfeclipse.org/update-nightly with
what I *think* is a fix for the start-up pop-up, maybe you could try
it out for me and holler if it fixes you up?
Thanks mucho!
:Den
--
Coming to understand a painting or a symphony in an unfamiliar style,
to recognize the work of an artist or school, to see or hear in new
ways, is as cognitive an achievement as learning to read or write or
add.
Nelson Goodman
--
-Dan