Bug 158271 - [Wizards] Jar Packager is resized (to default) on each run
Summary: [Wizards] Jar Packager is resized (to default) on each run
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-22 04:41 EDT by Victor Toni CLA
Modified: 2019-09-06 15:37 EDT (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 Victor Toni CLA 2006-09-22 04:41:21 EDT 
Each time I call the Jar Packager it is resized to its (too small) default.
Most projects I am working on have many pakages and this kind of resetting is pretty annoying especially because I have a rather large screen which.

Steps to reproduce:
1. Open Jar Packager
2. Resize Jar Packager window
3. 'Finish'
4. Open Jar Packager
5. Jar Packager window has again the default size


Actually it's not only the Jar Packager but other windwows show the same behavior too. I could add these to this bug if wanted when it strikes me again.
Comment 1 Martin Aeschlimann CLA 2006-10-04 08:36:59 EDT 
The size of the wizard is decided by the wizard dialog (in platformn.ui)
Comment 2 Karice McIntyre CLA 2006-10-04 17:14:04 EDT 
Could you attach a screenshot of the problem?
Comment 3 Boris Bokowski CLA 2009-11-26 16:19:18 EST 
Prakash is now responsible for watching bugs in the [Wizards] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:32:53 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 5 Eclipse Webmaster CLA 2019-09-06 15:37:28 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.