Bug 500427 - passing archive files to launcher should open SmartImport wizard, or select existing project
Summary: passing archive files to launcher should open SmartImport wizard, or select e...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 500388
Blocks:
  Show dependency tree
 
Reported: 2016-08-29 10:07 EDT by Mickael Istria CLA
Modified: 2019-03-08 04:55 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2016-08-29 10:07:00 EDT 
+++ This bug was initially created as a clone of Bug #500388 +++

the use case is the if some user tries `./eclipse /path/to/project.zip` in CLI, they get Eclipse IDE as ready as possible to work with the folder. Showing the Smart Import wizard so user only has to apply to get started with their project in Eclipse IDE.
Comment 1 Mickael Istria CLA 2019-03-08 04:54:37 EST 
I'm marking this one as WONTFIX by lack of interest in it.
Most end-users do first unzip content they receive (it makes everything easier), so I think the case of a end user willing `./eclipse blah.zip` to work is very anecdotical. For reference VSCode doesn't handle it neither.
What could be more interesting if we want to better cover the scenario of end-users opening a zip in Eclipse IDE would be to have a "smart-ish" editors listing the content of the zip, and providing a nice and very accessible button to "Import zip content as project into workspace".