Eclipse Community Forums: Newcomers » Trouble with remote Java development on Beaglebone Black

Home » Newcomers » Newcomers » Trouble with remote Java development on Beaglebone Black

Trouble with remote Java development on Beaglebone Black [message #1441921]

Fri, 10 October 2014 07:17

Eclipse User

I'm trying to use Eclipse (on Mac) for remote Java development onto a Debian Beaglebone Black. This is my first attempt at using the Remote System stuff.

I chose Linux and the SSH options when setting up the Remote System connection.

My initial test project was successful, but as I have added code I've seen a variety of puzzling errors. The most common is :
"The project was not built since the source file <something>.java could not be read"
The file is always one of my java files, but it's not always the same one. Refreshing and cleaning the project will generally change the error to a different file.

I can always open the file in Eclipse, both from the Package Explorer and the Remote System Explorer.

And, I can use Eclipse to edit happily, and build from the command line on the Beaglebone, but I can't use Eclipse to build.

I'd welcome any help in understanding what is going wrong and how to fix it.

Thanks!
Richard

Re: Trouble with remote Java development on Beaglebone Black [message #1442260 is a reply to message #1441921]

Fri, 10 October 2014 17:35

Eclipse User

On 10/10/2014 06:49 AM, Richard Sewell wrote:
> I'm trying to use Eclipse (on Mac) for remote Java development onto a
> Debian Beaglebone Black. This is my first attempt at using the Remote
> System stuff.
>
> I chose Linux and the SSH options when setting up the Remote System
> connection.
>
> My initial test project was successful, but as I have added code I've
> seen a variety of puzzling errors. The most common is :
> "The project was not built since the source file <something>.java could
> not be read"
> The file is always one of my java files, but it's not always the same
> one. Refreshing and cleaning the project will generally change the error
> to a different file.
>
> I can always open the file in Eclipse, both from the Package Explorer
> and the Remote System Explorer.
>
> And, I can use Eclipse to edit happily, and build from the command line
> on the Beaglebone, but I can't use Eclipse to build.
>
> I'd welcome any help in understanding what is going wrong and how to fix
> it.
>
> Thanks!
> Richard

How did you install Eclipse? Where did you install it? Where are your
putting your workspace or project files?

Re: Trouble with remote Java development on Beaglebone Black [message #1442280 is a reply to message #1442260]

Fri, 10 October 2014 18:17

Eclipse User

I unpacked 'Eclipse IDE for Java EE Developers' into Applications on the Mac, and I run Eclipse.app from there.

My workspace is in a folder under my Documents folder, so the path is Documents/clientname/workspace.
There is a .project file in Documents/clientname/workspace/RemoteSystemsTempFiles/BEAGLEBONE_RPS/root/projectname

On the Beaglebone, there's a .project file in ~root/projectname.

In both cases, the .project file has src, lib and so on as siblings.

Does that sound right ?

Thanks for your help,
Richard

Re: Trouble with remote Java development on Beaglebone Black [message #1444226 is a reply to message #1442280]

Mon, 13 October 2014 16:35

Eclipse User

I've had another tinker today, but without any improvement.

I've got no experience of this remote mechanism, I'd love to know if it was generally reliable or cranky. I'm not sure if I should be looking for a problem in how I've set it up, or if this is a symptom of a networking problem, or if remote debugging is generally undependable. Any background at all would be welcome.

Thanks,
Richard

Re: Trouble with remote Java development on Beaglebone Black [message #1444289 is a reply to message #1444226]

Mon, 13 October 2014 18:52

Eclipse User

On 10/13/2014 02:35 PM, Richard Sewell wrote:
> I've had another tinker today, but without any improvement.
>
> I've got no experience of this remote mechanism, I'd love to know if it
> was generally reliable or cranky. I'm not sure if I should be looking
> for a problem in how I've set it up, or if this is a symptom of a
> networking problem, or if remote debugging is generally undependable.
> Any background at all would be welcome.
>
> Thanks,
> Richard

Richard,

I've hesitated making suggestions because I'm not completely sure what
it is you wish to do. However, here is an article (really more random
notes) I wrote sometime ago on using Eclipse to debug a remote application.

http://www.javahotchocolate.com/tutorials/eclipse-debugging.html

Re: Trouble with remote Java development on Beaglebone Black [message #1447032 is a reply to message #1444289]

Fri, 17 October 2014 13:33

Eclipse User

Russell - thanks.

What I want to do is use Eclipse on Mac to do Java development and debugging remotely on a Beaglebone Black.

When I first started (and my project was tiny) I did see it work. I could edit code (which was really resident on the Beaglebone) in Eclipse on the Mac, build it, see build errors and fix them, and so on.

Some time later, with a bigger project, I started seeing a variety of puzzling errors like the ones I described above, and I've been unable to get back to a clean state in which I could build from Eclipse. I can still edit in Eclipse, but I have to build from the BB command line.

So, what I want to do is, make it work like it used to... Smile

But I don't know if that means doing something to my Remote System connection, or debugging the transport in some way, or throw my project away and make a clean one.

Is that any clearer ?

Thanks,

Richard

Previous Topic:	Eclipse wont start (yet another thread)
Next Topic:	VERY urgent help required ASAP

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 04 00:44:39 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter