Eclipse Community Forums: Java Development Tools (JDT) » 3M9

Home » Language IDEs » Java Development Tools (JDT) » 3M9 - very unstable (with 1.5)

3M9 - very unstable (with 1.5) [message #162560]

Thu, 03 June 2004 12:07

Eclipse User

Originally posted by: avinu.papayasoft.net

i had the following problems:

1. freezing of the IDE when trying to paste text. It was consistent with
that particular class.

2. classes that when i tried to save them, the save failed. Again - it
was consistent with the same class (a different one).

In both cases i tried to delete the class and recreate it - it didn't
help. i now have a problem - i need to work on those classes. i guess
i'll have to recreate a workspace and get the stuff from the cvs.
However - it maybe a bug that relates to the content of my code (im
using the 1.5 EA patch, so it might be related) and then it won't help.

Ah... i hope eclipse will start to stabilize and move toward the 1.5
instead of adding more and more marginal features....

Wouldn't you agree?

Re: 3M9 - very unstable (with 1.5) [message #162577 is a reply to message #162560]

Thu, 03 June 2004 12:50

Eclipse User

"avi tshuva" <avinu@papayasoft.net> wrote in message
news:c9nhtm$mif$1@eclipse.org...
>
> i had the following problems:
>
> 1. freezing of the IDE when trying to paste text. It was consistent with
> that particular class.
>
> 2. classes that when i tried to save them, the save failed. Again - it
> was consistent with the same class (a different one).
>
> In both cases i tried to delete the class and recreate it - it didn't
> help. i now have a problem - i need to work on those classes. i guess
> i'll have to recreate a workspace and get the stuff from the cvs.
> However - it maybe a bug that relates to the content of my code (im
> using the 1.5 EA patch, so it might be related) and then it won't help.
>
> Ah... i hope eclipse will start to stabilize and move toward the 1.5
> instead of adding more and more marginal features....
>
> Wouldn't you agree?
>

So help us out...log some bug reports with all the relevant details and your
reproduceable test cases.
Then we can fix the problems

Thanks
Darins

Re: 3M9 - very unstable (with 1.5) [message #162620 is a reply to message #162560]

Thu, 03 June 2004 13:34

Eclipse User

Originally posted by: akiezun.cuthis.mit.this.edu.andthis

avi tshuva wrote:
>
> i had the following problems:
>
> 1. freezing of the IDE when trying to paste text. It was consistent with
> that particular class.
>
> 2. classes that when i tried to save them, the save failed. Again - it
> was consistent with the same class (a different one).
>
> In both cases i tried to delete the class and recreate it - it didn't
> help. i now have a problem - i need to work on those classes. i guess
> i'll have to recreate a workspace and get the stuff from the cvs.
> However - it maybe a bug that relates to the content of my code (im
> using the 1.5 EA patch, so it might be related) and then it won't help.
>
> Ah... i hope eclipse will start to stabilize and move toward the 1.5
> instead of adding more and more marginal features....
>
> Wouldn't you agree?
>
Don't run eclipse on 1.5, it's not supported!
No wonder you have problems. You're running a pre-release software on a
beta jdk. Are you at least running a stable version of the OS?
:-)

BTW, I'm hacking and building 1.5 code on m9 not problem. But i'd never
even for a second consider _running_ m9 on 1.5 JRE.

cheers
a.

Re: 3M9 - very unstable (with 1.5) [message #162893 is a reply to message #162620]

Sat, 05 June 2004 05:07

Eclipse User

Adam Kiezun wrote:

> Don't run eclipse on 1.5, it's not supported!
> No wonder you have problems. You're running a pre-release software on a
> beta jdk. Are you at least running a stable version of the OS?
> :-)
>
> BTW, I'm hacking and building 1.5 code on m9 not problem. But i'd never
> even for a second consider _running_ m9 on 1.5 JRE.

I was running M8 on 1.5beta1 and it worked perfectly for me - still had
no chance to really try M9/beta2 combo.

Given such mindset, we would be still running Eclipse 2.0 on jdk 1.3
running windows 2000 - and who would file bugs against new releases ? ;)

Artur

Re: 3M9 - very unstable (with 1.5) [message #162901 is a reply to message #162577]

Sat, 05 June 2004 06:34

Eclipse User

Originally posted by: avinu.papayasoft.net

Darin Swanson wrote:
> "avi tshuva" <avinu@papayasoft.net> wrote in message
> news:c9nhtm$mif$1@eclipse.org...
>
>>i had the following problems:
>>
>>1. freezing of the IDE when trying to paste text. It was consistent with
>> that particular class.
>>
>>2. classes that when i tried to save them, the save failed. Again - it
>>was consistent with the same class (a different one).
>>
>>In both cases i tried to delete the class and recreate it - it didn't
>>help. i now have a problem - i need to work on those classes. i guess
>>i'll have to recreate a workspace and get the stuff from the cvs.
>>However - it maybe a bug that relates to the content of my code (im
>>using the 1.5 EA patch, so it might be related) and then it won't help.
>>
>>Ah... i hope eclipse will start to stabilize and move toward the 1.5
>>instead of adding more and more marginal features....
>>
>>Wouldn't you agree?
>>
>
>
> So help us out...log some bug reports with all the relevant details and your
> reproduceable test cases.
> Then we can fix the problems
>
> Thanks
> Darins
>
>

Ok.Let's try.Here's some info and plz tell me if u want me to try
something specific.

There was a class i imported, called StateTag. i tried to edit it, and
then save it. Eclipse popped up a Null pointer exception message.The
error log is full of errors and for this one in particular it says:
"Warning error in build" and "An exception stack trace could not be found".
plus:
eclipse.buildId=I200405211200
java.version=1.5.0-beta2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US

Another entry: "Exception occurred during problem detection:
java.lang.NullPointerException
at
org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.r esolveTypesFor(SourceTypeBinding.java:803)
at
org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.m ethods(SourceTypeBinding.java:696)
at
org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.g etMethods(SourceTypeBinding.java:586)
at
org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.g etExactMethod(SourceTypeBinding.java:522)
at
org.eclipse.jdt.internal.compiler.lookup.Scope.findExactMeth od(Scope.java:421)
at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod(Sco pe.java:1501)
at
org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveTyp e(MessageSend.java:285)
at
org.eclipse.jdt.internal.compiler.ast.LocalDeclaration.resol ve(LocalDeclaration.java:190)
at
org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclarat ion.resolveStatements(AbstractMethodDeclaration.java:382)
at
org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.reso lveStatements(MethodDeclaration.java:133)
at
org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclarat ion.resolve(AbstractMethodDeclaration.java:359)
at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolv e(TypeDeclaration.java:921)
at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolv e(TypeDeclaration.java:970)
at
org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclara tion.resolve(CompilationUnitDeclaration.java:280)
at org.eclipse.jdt.internal.compiler.Compiler.resolve(Compiler. java:562)
at
org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.p rocess(CompilationUnitProblemFinder.java:176)
at
org.eclipse.jdt.internal.core.CompilationUnit.buildStructure (CompilationUnit.java:145)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openabl e.java:183)
at
org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(Jav aElement.java:573)
at
org.eclipse.jdt.internal.core.CompilationUnit.makeConsistent (CompilationUnit.java:970)
at
org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation. executeOperation(ReconcileWorkingCopyOperation.java:58)
at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaMod elOperation.java:700)
at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperatio n(JavaModelOperation.java:739)
at
org.eclipse.jdt.internal.core.CompilationUnit.reconcile(Comp ilationUnit.java:1097)
at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrateg y.reconcile(JavaReconcilingStrategy.java:88)
at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrateg y.reconcile(JavaReconcilingStrategy.java:129)
at
org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrateg y.reconcile(CompositeReconcilingStrategy.java:86)
at
org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStr ategy.reconcile(JavaCompositeReconcilingStrategy.java:96)
at
org.eclipse.jface.text.reconciler.MonoReconciler.process(Mon oReconciler.java:76)
at
org.eclipse.jface.text.reconciler.AbstractReconciler$Backgro undThread.run(AbstractReconciler.java:200)
"

Re: 3M9 - very unstable (with 1.5) [message #162907 is a reply to message #162893]

Sat, 05 June 2004 06:36

Eclipse User

I run RC1 on 1.5.0b2 just as i runned all the eclipse builds on 1.5b1 as long
as 1.5b1 was around. I didn't find any problems with the combo eclipse/1.5
I did find quite a few other problems in 1.5b1 and b2 that i already reported
for example both beta's are not able to start our webstart application:
http://demo.servoy.com:8080

johan

Artur Biesiadowski wrote:
> Adam Kiezun wrote:
>
>> Don't run eclipse on 1.5, it's not supported!
>> No wonder you have problems. You're running a pre-release software on
>> a beta jdk. Are you at least running a stable version of the OS?
>> :-)
>>
>> BTW, I'm hacking and building 1.5 code on m9 not problem. But i'd
>> never even for a second consider _running_ m9 on 1.5 JRE.
>
>
> I was running M8 on 1.5beta1 and it worked perfectly for me - still had
> no chance to really try M9/beta2 combo.
>
> Given such mindset, we would be still running Eclipse 2.0 on jdk 1.3
> running windows 2000 - and who would file bugs against new releases ? ;)
>
> Artur

Re: 3M9 - very unstable (with 1.5) [message #163389 is a reply to message #162907]

Wed, 09 June 2004 07:50

Eclipse User

Right, this is up to you to live dangerously. But to be fair, you should
report such failures to the VM vendor.
FYI - looking at 1.5 libraries (when addressing strange Cheetah compiler
bugs) I observed quite a few exotic attribute values, which were not
following the spec (remember also that 3rd edition of the specs hasn't been
finalized yet).

However, if you can reproduce these with a stable JRE 1.4 release, then yes
we should definitely look into it.

"Johan Compagner" <jcompagner@j-com.nl> wrote in message
news:c9s797$ju0$1@eclipse.org...
> I run RC1 on 1.5.0b2 just as i runned all the eclipse builds on 1.5b1 as
long
> as 1.5b1 was around. I didn't find any problems with the combo eclipse/1.5
> I did find quite a few other problems in 1.5b1 and b2 that i already
reported
> for example both beta's are not able to start our webstart application:
> http://demo.servoy.com:8080
>
> johan
>
>
>
> Artur Biesiadowski wrote:
> > Adam Kiezun wrote:
> >
> >> Don't run eclipse on 1.5, it's not supported!
> >> No wonder you have problems. You're running a pre-release software on
> >> a beta jdk. Are you at least running a stable version of the OS?
> >> :-)
> >>
> >> BTW, I'm hacking and building 1.5 code on m9 not problem. But i'd
> >> never even for a second consider _running_ m9 on 1.5 JRE.
> >
> >
> > I was running M8 on 1.5beta1 and it worked perfectly for me - still had
> > no chance to really try M9/beta2 combo.
> >
> > Given such mindset, we would be still running Eclipse 2.0 on jdk 1.3
> > running windows 2000 - and who would file bugs against new releases ? ;)
> >
> > Artur

Previous Topic:	Breakpoint issues in M9
Next Topic:	Import files in M9

Goto Forum:

-=] Back to Top [=-

Current Time: Sun May 11 12:00:05 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter