Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
Developer
hagen
Posts: 100
Registered: ‎04-07-2009
My Device: Not Specified
Accepted Solution

Bad bug in the the Java plugin for Eclipse 1.1 beta!!!

It suddenly closes down without saving!!! I recommend that you never click help->Check for Updates.

Please use plain text.
Developer
simon_hain
Posts: 15,947
Registered: ‎07-29-2008
My Device: Z10 LE
My Carrier: O2 Germany

Re: Bad bug in the the Java plugin for Eclipse 1.1 beta!!!

i doubt that this is an error of the eJDE, more of an eclipse problem.

----------------------------------------------------------
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter
Please use plain text.
Developer
hagen
Posts: 100
Registered: ‎04-07-2009
My Device: Not Specified

Re: Bad bug in the the Java plugin for Eclipse 1.1 beta!!!

I made a new installation of the java pluging for eclipse 1.1 beta, and the bug still exists. If I press Strg + Space and then n eclipse closes without saving. Very awesome.

Please use plain text.
New Developer
mohkev
Posts: 26
Registered: ‎11-03-2009
My Device: BB Storm 2 9550 v5.0.0.713 (Platform 4.2.0.323)
My Carrier: Verizon

Re: Bad bug in the the Java plugin for Eclipse 1.1 beta!!!

Eclipse crashes when you check for updates?

Please use plain text.
Developer
Ted_Hopp
Posts: 1,305
Registered: ‎01-21-2009
My Device: Not Specified

Re: Bad bug in the the Java plugin for Eclipse 1.1 beta!!!

[ Edited ]

I'm not quite sure why you should "never click help->Check for Updates", but the issue of Eclipse suddenly closing down has been discussed several times in this forum. One thread that includes official RIM input is:

 

http://supportforums.blackberry.com/t5/Java-Development/Eclipse-crash/m-p/473333

 

This is also being discussed in the Eclipse Bugzilla system, where, as Simon noted above, it is generally considered to be an Eclipse problem. (See, for example, Eclipse bug #297279).




Solved? click "Accept as solution". Helpful? give kudos by clicking on the star.
Please use plain text.