Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 209207

Summary: Export to remote file system (EFS)
Product: [Eclipse Project] PDE Reporter: Lee Surprenant <lmsurpre>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: curtis.windatt.public, jeffmcaffer, mober.at+eclipse
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Lee Surprenant CLA 2007-11-08 10:57:38 EST
DSDP currently adds to the export project menu, allowing users to export their files to a remote filesystem.  When working with plugin/bundle developement (via PDE), it is usually possible to export each project as a deployable plugin/bundle.  This feature allows more rapid bundle development by combining the packaging and deploying of bundles into one step.  I think this would be a very useful feature when writing plugins and bundles for a remote system (headless device in my case).  The proposed addition would either extend the PDE export wizards to allow remote filesystem developement, or the addition of something like "Export... -> Other -> Deployable plug-ins and fragments to a Remote file system"
Comment 1 Martin Oberhuber CLA 2010-09-22 10:22:39 EDT
Cleaning up DSDP/DSDP bucket.

Since "remote access" is standardized via EFS, I'm putting this into PDE for consideration.
Comment 2 Curtis Windatt CLA 2010-09-22 10:32:34 EDT
Is this bug asking for an option in the current export wizard to set the destination as a remote file location?
Comment 3 Lee Surprenant CLA 2010-09-22 14:46:37 EDT
Martin, thanks for re-surfacing this.

Curtis, yes.  Thanks for clearing up the title.

The idea was to allow users to define a 'target platform' for each remote device, then provision a platform-specific set of bundles ('target platform' + workspace plugins) to that device through this export option.

PDE already allows users to export their target platform to disk, so we are close.
The idea was to model it on the "Export to Remote Filesystem" wizard added by the 'Remote Systems Explorer'.  Adding PDE support like this would make it a little quicker and easier to do embedded OSGi development for target devices...(eg. http://www.gumstix.net/wiki/index.php?title=Eclipse_on_Gumstix_for_new_users).

That said, I'm not sure if it is really worth an extra option in the main PDE export wizard(s)...this is why I reported it against DSDP.
Comment 4 Jeff McAffer CLA 2010-09-22 15:28:26 EDT
If you are looking to export a full running system to the remote device would it be simpler/possible to mount the device as a file system on the dev machine and then just export?  Getting the stuff actually running involves more than just getting the bundles there. the bundles need to be configured etc. (e.g., writing the config.ini or bundles.info files if using equinox).

Pushing the whole target there would, in many cases be challenging as it would often have more than you need.
Comment 5 Lee Surprenant CLA 2010-09-22 15:47:53 EDT
(In reply to comment #4)
> If you are looking to export a full running system to the remote device would
> it be simpler/possible to mount the device as a file system on the dev machine
> and then just export?
Yeah, this is what I ended up doing most of the time.  I guess the counter-argument is that not all systems can be easily mounted (to or from).  Isn't this the reason for having RSE and Export to Remote File System?  Also, would be nice to do it all from the IDE (after all, its not too hard just to FTP the files over, either).

> Getting the stuff actually running involves more than
> just getting the bundles there. the bundles need to be configured etc. (e.g.,
> writing the config.ini or bundles.info files if using equinox).
Yes, this is a good point.  I was just after the bundle provisioning step, but maybe something could be done to help manage the config as well...assuming that is p2 territory?

> Pushing the whole target there would, in many cases be challenging as it would
> often have more than you need.
I prefer my target platforms lean and mean, but I see your point.
Comment 6 Lee Surprenant CLA 2010-09-22 16:17:36 EDT
After thinking a bit more, maybe what I was after was ability to provision a 'product' to a system with a given environment (os, architecture, etc.), rather than focusing specifically on target platform.  Either way, I don't do much embedded work any more, so feel free to handle the feature request however you feel makes sense.
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:19:09 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 8 Julian Honnen CLA 2019-09-09 02:24:21 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.