Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: When a jardesc has already been saved, the "Desctination file" attribute is completely useless and even harms. Where else should it be saved to, other than to itself. There should be at least the possibility to select "save to itself" or something like that and this should be autoselected after it has first been saved. Many times I just copy/paste a jardesc and forget to adjust this value. Then the new jardesc overwrites the original jardesc when executed, which you don't always see before it's too late. Additionally it doesn't make much sense to automatically select the .classpath and .project files to be included in a jar file. Marvin More information:
>Additionally it doesn't make much sense to automatically select the .classpath >and .project files to be included in a jar file. Please file only one bug per bug report.
(In reply to comment #1) > >Additionally it doesn't make much sense to automatically select the .classpath > >and .project files to be included in a jar file. > Please file only one bug per bug report. > ok, you can ignore the "Additionally..." point in this report. I have created a separate report for it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=276700 Marvin
This bug is still valid for 3.6. Are there any plans to address it some day?
>This bug is still valid for 3.6. The bug is in version 3.4, so please don't change that. >Are there any plans to address it some day? No.
I am a bit confused. The bug may be in 3.4, but also applies to 3.6, which is much more important here, since 3.4 is pretty irrelevant nowadays. Can you tell me a reason, why this bug isn't gonna be addressed? Do you want it that way? And if you do, why? It is a pretty dumb behavior to write the file name in the file itself, because when the file (the jardesc) is copied, this information is wrong and the original file will be overwritten.
We always set the version to the one where the bug has its first appearance. That the bug is open is already indicating that it's still present in the latest version. >Can you tell me a reason, why this bug isn't gonna be addressed? Not enough resources and more important things to do. Feel free to provide a good quality patch.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
Just reopening for the records. Maybe I will provide a patch.
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. -- The automated Eclipse Genie.
