| NoClassDefFoundError IProgressMonitor 3.2M4 [message #296594] |
Tue, 27 December 2005 14:44  |
Eclipse User |
|
|
|
Originally posted by: kandkw.yahoo.com
I am creating a standalone Java Application. This problem appeared when I
upgraded from
3.1.1 to 3.2M4. I am running java (build 1.5.0_06-b05).
I did not see org/eclipse/core/runtime/IProgressMonitor in
org.eclipse.core.runtime_3.2.0.v20051208.jar
I looked at Bugzilla Bug 116520, but that did not seem applicable.
I probably have some setup error, but I don't know what it is. Any
suggestions or requests for more info are welcome.
I also get a popup saying "Could not find the main class. Program will exit"
The full text of the error is
java.lang.NoClassDefFoundError: org/eclipse/core/runtime/IProgressMonitor
Exception in thread "main"
|
|
|
|
|
| Re: NoClassDefFoundError IProgressMonitor 3.2M4 [message #296663 is a reply to message #296657] |
Thu, 29 December 2005 12:41  |
| Eclipse User |
|
|
|
Originally posted by: kandkw.yahoo.com
I have both a 3.1.1 and 3.2M4 eclipse install, both pointed at the same
workspace. The only
difference is the jars in the classpath. Obviously I have two separate
versions of my
build.xml. Build and run work in 3.1.1, only build works in 3.2M4
The only change to the source code was to comment out a small section of
code that
set a background image (why I want 3.2M4).
The class that contains main extends ApplicationWindow
Is there anything else I could look at/do?
"OhPun" <kandkw@yahoo.com> wrote in message
news:dp1013$6rb$1@utils.eclipse.org...
>I removed the current eclipse install, deleted the source, removed
>.metadata from the workspace,
> resintalled eclipse 3.2M4, downloaded source from CVS, reconfigured
> workspace.
> Then I got the same problem.
>
> Oddly enough if I run a .jnlp with the 3.1.1 jars (compiled against 3.2M4)
> it works.
>
> "Alex Blewitt" <automatic@javalobby.org> wrote in message
> news:26660713.1135761933575.JavaMail.root@cp1.javalobby.org...
>> How did you upgrade? Did you just unzip the contents over your previous
>> install, or put it in a new location?
>>
>> I'd expect there to be problems if you put it in the same place, or used
>> the same workspace. Either try starting it with eclipse -clean (sometimes
>> helps), or get rid of your old 3.1.1 install and then unzip 3.2 instead.
>> You might have to delete the .metadata directory in your workspace too.
>>
>> Alex.
>
>
|
|
|
|
| Re: NoClassDefFoundError IProgressMonitor 3.2M4 [message #296675 is a reply to message #296674] |
Thu, 29 December 2005 18:24 |
| Eclipse User |
|
|
|
Originally posted by: kandkw.yahoo.com
Actually I don't care about 3.1.1. I'm using it because it works. I'd rather
upgrade to 3.2 and
leave 3.1.1 behind. But I can't do that until I prove the project will run
under 3.2
Actually the metadata is from 3.2 and I'm running 3.1.1. However the
question still remains,
after removing all .metadata and starting from scratch with 3.2, why does it
compile, but
produce NoClassDefFoundError IProgressMonitor when run?
I will try a separate workspace, but I suspect the same problem will happen
again. I will let you know
tomorrow.
"Alex Blewitt" <automatic@javalobby.org> wrote in message
news:17259543.1135898119802.JavaMail.root@cp1.javalobby.org...
> The problem is almost certainly that you're sharing a workspace between
> the 3.1.1 and 3.2 clients. The .metadata directory is something that
> stores plugin-specific data for each plugin, and these change in the major
> releases. Whilst it's possible that going from 3.1->3.2 will cause some of
> the data structures to be updated on demand, they certainly won't be
> downgradable if you then run the 3.1 system again.
>
> Instead, it's much better if you have two separate workspaces (and hence
> separate .metadata directories); then, if you want to share projects
> between the two, don't put the project in the workspace but in a shared
> location outside of it. In other words, have something like:
>
> Eclipse_3-1\workspace
> Eclipse_3-2\workspace
> Shared\MyProject
> Shared\MyOtherProjecy
>
> That way the .metadata won't be shared, which will certainly be the cause
> of some of your problems. Whether it fixes them all or not, I can't say.
>
> Alex.
|
|
|
|
| Re: NoClassDefFoundError IProgressMonitor 3.2M4 [message #296703 is a reply to message #296674] |
Fri, 30 December 2005 18:00 |
| Eclipse User |
|
|
|
Originally posted by: kandkw.yahoo.com
I tried two separate workspaces. 3.1.1 works perfectly, 3.2 gives me the
same error.
"Alex Blewitt" <automatic@javalobby.org> wrote in message
news:17259543.1135898119802.JavaMail.root@cp1.javalobby.org...
> The problem is almost certainly that you're sharing a workspace between
> the 3.1.1 and 3.2 clients. The .metadata directory is something that
> stores plugin-specific data for each plugin, and these change in the major
> releases. Whilst it's possible that going from 3.1->3.2 will cause some of
> the data structures to be updated on demand, they certainly won't be
> downgradable if you then run the 3.1 system again.
>
> Instead, it's much better if you have two separate workspaces (and hence
> separate .metadata directories); then, if you want to share projects
> between the two, don't put the project in the workspace but in a shared
> location outside of it. In other words, have something like:
>
> Eclipse_3-1\workspace
> Eclipse_3-2\workspace
> Shared\MyProject
> Shared\MyOtherProjecy
>
> That way the .metadata won't be shared, which will certainly be the cause
> of some of your problems. Whether it fixes them all or not, I can't say.
>
> Alex.
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 1.09523 seconds
Home