Well, “standalone” CCW is still Eclipse under the hood, right? What I suspect 
here is that it packaged a stripped down Eclipse that is no longer capable of 
updating itself past some change that the Eclipse project made. I’d recommend 
installing an up-to-date version of Eclipse itself, then installing an 
up-to-date version of CCW *as a plugin* and then I think you’ll have more luck 
going forward.

 

You can reuse the same workspace location so the newly-installed Eclipse + CCW 
plugin combo should pick up all your settings and projects and so on.

 

(FWIW, I’ve seen similar problems with other projects that offered both a 
bundled Eclipse install and a plugin install: at some point the bundled install 
just breaks due to Eclipse updates – using a plugin is nearly always a safer 
option, in my experience)

 

Sean Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


 

On 5/5/16, 9:16 PM, "Fluid Dynamics" <clojure@googlegroups.com on behalf of 
a2093...@trbvm.com> wrote:

 

On Thursday, May 5, 2016 at 7:45:39 PM UTC-4, Luc wrote:

I remember this problem but this is
an eclipse bug if my memory is not
failing. They had removed Marketplace
by mistake.

Are you using the latest version of Eclipse ?

Luc P.


It's *standalone* CCW 0.28.0 trying to update itself to 0.34.0. There's no 
separate Eclipse to separately update first. I have tried selecting each item 
in the updater thingy separately, one at a time, and updating them, only 
stopping if it says the component is already up to date, and all of them are 
now up to date except the top two CCW-specific ones, which have the dependency 
error. I also tried mass-selecting everything at once and clicking update. So 
no, there's nothing it seems that I can "update first" and then update the rest 
to make it work.

If they "had" removed something by mistake, some time ago, doesn't that imply 
that they realized their error and put it back a nearly-as-long time ago, and 
therefore the problem should no longer exist?

 

 

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to