Bug 88972 - [Import/Export] Archive export does not allow path relative to workspace
Summary: [Import/Export] Archive export does not allow path relative to workspace
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-03-24 05:35 EST by Victor Toni CLA
Modified: 2019-09-06 16:12 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Toni CLA 2005-03-24 05:35:43 EST
I would like to create an export as an archive which should reside in one
project within the workspace. However unlike the JAR export an absolute path
must mut be entered.

This shouldn't be a necessity.
Comment 1 Victor Toni CLA 2006-02-05 11:13:43 EST
Is this on the roadmap for 3.2?
Comment 2 Karice McIntyre CLA 2006-02-05 19:44:13 EST
This is not a high priority item for 3.2 - you can workaround the problem by selecting the project's directory from the file chooser.  Perhaps you would be interested in submitting a patch for this (this bug is marked with keyword helpwanted)?

I took a quick look and it seems the jar export wizard's default directory is the workspace whereas the file system and archive export directory is the directory from which you ran eclipse.  I am not sure if this was by design or not.
Comment 3 Jakub Jurkiewicz CLA 2007-01-29 07:30:11 EST
So what should be the proper behavior? I believe that these two mechanisms of exporting as jar or archive should work in the same manner. Is there a need for a patch for this or maybe we leave it as it is now?
Comment 4 Markus Keller CLA 2007-03-23 11:28:14 EDT
See also bug 88975.
Comment 5 Susan McCourt CLA 2009-07-15 12:11:46 EDT
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:12:04 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.