Plug-in "ccw.core" was unable to instantiate class "ccw.editors.clojure.ClojureEditor".

[GoogleCodeExporter]

What steps will reproduce the problem?
1. This happened after updating a dependency in project.clj from 1.4.0 to 
1.6.0. 
2.
3.

What is the expected output? What do you see instead?
The editor will not open, but the project listing is still there (see issue 
542).
Trashing .metadata does fix this problem, but I thought you would still want to 
know about it.

What version of the product are you using? On what operating system?
CCW 0.31.0.STABLE001

Eclipse IDE for Java Developers
Version: 4.4.1.20140925-1820
Build id: 20140925-1800

AND (on two separate machines):

Eclipse Platform
Version: 4.4.0.v20140925-0400
Build id: M20140925-0400

Mac OS version 10.9.5

Please provide any additional information below.

See the stacktraces and project.clj attached.  Actually the stacktrace on 
opening all the different files in the project seem to be different, but I'm 
only including two stacktraces from the two different machines.

Original issue reported on code.google.com by nchubr...@gmail.com on 5 Dec 2014 at 10:21

Attachments:

• Eclipse-4.4.1-stacktrace.rtf
• Eclipse-4.4.0-stacktrace.rtf
• project.clj

[GoogleCodeExporter]

Hello,

I have released version 0.31.1 a couple hours after 0.31.0 to fix this issue. 

It is related to the workspace state in a subtle way: if you close eclipse with 
open editors, then the problem happens when starting eclipse. If you closed 
eclipse with no editor open, then no problem after eclipse restart. 
That's probably why, after having removed the .metatada, and thus gone back to 
a state where no editor is automatically reopened, you concluded that it was a 
sufficient solution (true). But not necessary. 

If you upgrade to CCW 0.31.1, the problem will be gone. 

Cheers

Original comment by laurent....@gmail.com on 6 Dec 2014 at 1:33

• Changed state: infoneeded

[GoogleCodeExporter]

Ah, my apologies for not checking before posting the issue!  I checked for
updates but must have done so in the gap.  But of course it said right
there on your site what the new version was.

Mind if I ask an unrelated question before I post an issue?  I have a very
old project with some outdated dependencies, which however are hard to fix
owing to API changes.  The project.clj shows an Eclipse red-x error:
"Leiningen Managed Dependencies issue: problem resolving following
dependencies: [org.mozilla/juniversalchardet "1.0.3"]"  (Before I updated
from Clojure 1.4 it was something different.)

I never changed anything in the dependencies and it worked fine in old
versions of CCW.  I don't know if this is an issue of old libraries
disappearing or something else.  In any case it doesn't stop me from
running the project.

I tried out Cursive on IntelliJ and didn't see any similar problem.  (I
have no idea why Cursive is so popular BTW: your CCW is so much more
polished.)

Original comment by nchubr...@gmail.com on 6 Dec 2014 at 2:13

[GoogleCodeExporter]

Hello,

for your dependency, I checked maven & clojars repos, and found nothing 
matching with the org.mozilla groupId:

http://search.maven.org/#search%7Cga%7C1%7Cjuniversalchardet 

https://clojars.org/search?q=juniversalchardet

So the dependency, to me, does not exist, and the message given by CCW is 
correct ?

Did I miss something?

Original comment by laurent....@gmail.com on 6 Dec 2014 at 5:37

[GoogleCodeExporter]

No, I don't think so.  I'm just confused as to why this became a problem
over time (I hadn't used the project in about a year).  Can
dependencies *disappear?
 *(And this isn't a direct dependency, since it's not in my project.clj.)

Original comment by nchubr...@gmail.com on 8 Dec 2014 at 12:36

[GoogleCodeExporter]

This dependency may have been added by another dependency author on the local 
cache of their machine, and they forgot that it does not exist outside their 
computer. 

You can try "alt + L L" and then type deps :tree to get the whole dependencies 
tree in the console output.

Original comment by laurent....@gmail.com on 8 Dec 2014 at 5:50

[GoogleCodeExporter]

Thank you for that command, it was very helpful!  I ended up getting
everything fixed thanks to that.

Original comment by nchubr...@gmail.com on 10 Dec 2014 at 10:02

[GoogleCodeExporter]

Original comment by laurent....@gmail.com on 18 Dec 2014 at 11:56

• Changed state: Invalid