Community
Participate
Working Groups
I have about 30 projects and I use 'Export' feature to Jar them, but when I move from one to another I right click on a project and choose export and I have to select what jar to output to, it would be GREAT if Eclipse could remember what the last jar was so I could have it preselected once I right click on a project and choose export (and choose JAR).
JAR export is provided by the JDT component.
yeah I know, did you read what the description? I use the JAR export that isn't the issue!
Works for me using R3.0 with the following steps: 1. select Java project1 in Package Explorer 2. context menu Export... 3. JAR file 4. click Next 5. select a JAR file to export 6. Finsh IMPORTANT: ensure it completes: if you press cancel or there's an error the wizard will not store the preferences. 7. select Java project2 2. context menu Export... 3. JAR file 4. click Next ==> last JAR file is selected If you still have a problem with this using R3.0 then please reopen and provide exact steps to reproduce.
It records the LAST jar not the last jar for that project. I have my list of projects in my project explorer and if I right click on any one of them and choose "Export..." I can then select JAR and then when the next screen comes up the jar file and location that is selected is the last jar I jarred something too, not the last jar that project had been jarred to. So it would be nice if Eclipse could remember the jar that EACH project was last jarred too and have that come up by default...
Adapting summary. Moving to Platform UI for general comment: Eclipse wizards currently store the last used/entered values (globally) and not per project. If we offer to store values per project then this should be for all wizards and eventually a preference.
This is potentially an interesting use of project preferences if we choose to support them in the workbench in 3.1.
Copying Duong, Preferences component owner.
Prakash is now responsible for watching bugs in the [Wizards] component area.
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.
