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. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

Java Development

Reply
Developer
rcmaniac25
Posts: 1,789
Registered: ‎04-28-2009
My Carrier: Verizon

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

I had that problem while doing a lot of debugging. I resolved it by restarting my computer. Now I only get it when debugging Android apps, BlackBerrys fine.

------------------------------------------------------------
Three simple rules:
1. Please use the search bar before making new posts.
2. Kudo posts that you find helpful.
3. If a solution has been found for your post, mark it as solved.
--I code too much. Well, too bad.
Please use plain text.
Developer
dx22
Posts: 402
Registered: ‎11-26-2010

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

[ Edited ]

I have been using the plugin v1.3 for some time and here are the issues I noticed:

 

 

  1. While in debug perspective you can't see the values of the variables. It shows that all of them are null. Usually I can see the values in the Varables tab(positioned in the upper right part of the screen by default) or if I keep the mouse pointer over a variable in the code(a tooltip appears). This really bothers me since it makes a big part of running the program in debug mode pointless! Should we expect a fix for this any time soon?
  2. From time to time the debugger just freezes. If i am on a certain line of code and press F6 to move to the next it just freezes - no exception, in the threads tab it shows that all threads are running but i never get to see the debugger move to the next line. And this isn't some line of code with blocking operations, I am talking about the most common lines like int i = 0; Very strange!
  3. Very often it happens that when I attach a real device and start in debug mode the debugger just won't start - it just stays "in progress" in eclipse and the device doesn't seem to recognize any debugger attached. Usually after such thing happens I am unable to stop the debugger manually because it just won't stop no matter what i do. I have to restart the eclipse.
All the tests are made while debugging with real devices - i don't use the simulator much. I have 5 different bb devices and i see the issues mentioned with each one of them.
Besides these issues I am still happy to see that rim is putting effort in this project! After a few fixes it will be just fine.

 

----------------------------------------------------------------------
Press the button to give kudos if I helped you :smileyhappy:
Please use plain text.
Developer
ekke
Posts: 908
Registered: ‎04-08-2010
My Carrier: vodafone

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

yesterday I noticed a problem with Torch 9800 Simulator

 

if Tilt to Landscape then I wasn't able to click on buttons or in fields

seems the Simulator still thinks it's in Portrait mode

-------------------------------------------------------------------------------
ekke (independent software architect, rosenheim, germany)

BlackBerry Elite Developer
International Development Mobile Apps BlackBerry 10 Cascades
Cascades - Workshops / Trainings / Bootcamps

Open Source Enthusiast
blog: http://ekkes-corner.org videos: https://vimeo.com/ekkescorner/videos
bb10-development: http://appbus.org Twitter: @ekkescorner
Please use plain text.
Developer
calgacus
Posts: 237
Registered: ‎07-20-2010

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

 


kwallis wrote:

Hi calgacus.  Where do you see that error?  Is it a dialog brought up by the simulator?  Do you see it in Eclipse itself?  Can you please also check your processes to see if there are any other fledge.exe processes running?

 

Thanks!


I tried it out at home again this weekend and found the same message and crash happening often, ususally even before I start stepping through code.  My app is 99% complete but there is still a bug or two and  a little UI tweaking to be done.  is there another way to debug this stuff without the eclipse plugin?

 

Please use plain text.
Developer
calgacus
Posts: 237
Registered: ‎07-20-2010

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

Can these apps be developed/debugged from a command line system with ant scripts?

Please use plain text.
Developer
calgacus
Posts: 237
Registered: ‎07-20-2010

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

[ Edited ]

Just a   tip, I have found that performance and stability  has improved since removing all my watch expressions in debug mode.  Gotta fatten stuff up with messages to do watches.

Please use plain text.
Developer
dkonigs
Posts: 202
Registered: ‎07-25-2008

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

Yes, to some extent.  BlackBerry Ant Tools provides a set of Ant tasks for running all the BlackBerry build tools.  However, for me, this is only useful for automated builds outside my usual development environment.

 

I still do all my coding/testing using the Eclipse plugin (stuck at v1.1 until they fix the bugs in v1.3), but I have a Hudson (now called Jenkins) based build server that uses Ant to create the distributable builds of my application.

Please use plain text.
Developer
ekke
Posts: 908
Registered: ‎04-08-2010
My Carrier: vodafone

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

great to hear someone is using Jenkins (Hudson) to deploy BB projects

 

why not blogging how you're using BB Ant Tools with Jenkins ?

-------------------------------------------------------------------------------
ekke (independent software architect, rosenheim, germany)

BlackBerry Elite Developer
International Development Mobile Apps BlackBerry 10 Cascades
Cascades - Workshops / Trainings / Bootcamps

Open Source Enthusiast
blog: http://ekkes-corner.org videos: https://vimeo.com/ekkescorner/videos
bb10-development: http://appbus.org Twitter: @ekkescorner
Please use plain text.
New Developer
wayneuroda
Posts: 10
Registered: ‎09-28-2009

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

Hi MSohm,

 

Can you please make the component packs available as offline installers? Is this possible? I manage several developers and having them all use the update site is a waste of time and bandwidth, also the downloads frequently fail for us (not sure why, maybe because of geography (Australia)) so using an offline install package for the component pack (4.5.0) would be much more convenient.

 

Thanks!

Please use plain text.
Developer
Marc_Paradise
Posts: 155
Registered: ‎01-22-2010
My Carrier: AT&T

Re: BlackBerry Java Plug-in for Eclipse 1.3.0 released!

 


gbeukeboom wrote:

Hi dkonigs,

 

RE: Library build errors:


C:\Eclipse\plugins\net.rim.ejde.componentpack4.6.0_4.6.0.23\components\lib\net_rim_api.jar(net_rim_bb_addressbook.cod): Error!: Duplicate definition for 'net.rim.device.apps.api.addressbook.AddressBook' found in: C:\Eclipse\plugins\net.rim.ejde.componentpack4.5.0_4.5.0.28\components\lib\net_rim_api.jar(net_rim_bb_addressbook.cod)

 


I just tested and reproduced this issue and will bring it up to development. In the meantime I have found that if all projects use the same BlackBerry Java SDK to build the issue goes away so this is a potential workaround.

 

 

Regards,


 

Is there any update for this?  When we need to debug/test on multiple plaform versions, having all projects using the same SDK is not really a good option. For example, i have seven projects i my workspace: 1 resource, 1 main app, and 5 platform-specific libraries.  Following this advice, in order to debug for any one paltform version, I need to edit my project settings for all of the affected libraries.  And I can rule out entirely quickly checking running different simulator versions from within eclipse, since I need to edit configuration before launching each time.

 



Try out BBSSH, a free Blackberry SSH client.
  • If you like my post, please let me know by Liking it!
  • If my post solved your problem please click on the Accept as Solution button.

Please use plain text.