Run/Debug Settings Bug?
I have noticed this for quite a while now - I dont know if this is a bug or a "feature".
In Ariadna, if I righ-click on a class or UnitTest that I have never run before and choose "Run" or "Debug" a new entry would be added to the Run/Debug/UnitTest list for that project.
However, if I do this now in Aurora, rather than add, it replaces an existing one.
Currently, I have to manually "Edit Entries" in order to have more than one.
Is this a bug or is there a good reason for this?
-Nick
Please sign in to leave a comment.
It is a feature: when you run/debug with right-clicking on application/test
temporary configuration created. When you run/debug with right-click next
time IDEA removes existing temporary configuration and creates new one. You
may make temporary configuration persistent with "Save XXX" action in
configuration dropdown or in configuration editor dialog ("Copy
configuration" action become "Save configuration" for temporaries)
--
Best regards,
Dmitry Peshehonov
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"
"Nick Minutello" <no_mail@jetbrains.com> wrote in message
news:15595918.1069945666346.JavaMail.javamailuser@localhost...
or a "feature".
>
before and choose "Run" or "Debug" a new entry would be added
to the Run/Debug/UnitTest list for that project.
>
replaces an existing one.
one.
>
>
Why do we have this feature?
I would much prefer to manually remove these configurations than manually add/save them because I add much more frequently than I remove....
Is there something I am missing?
-Nick
I think that is exactly the intention: when fixing a certain bug on often needs to run a specific test for a short period of time, but doesn't bother it the next day. This feature safes you from having to clean the list on a regular basis.
If your style of work is different may be there is need for another configuration option.
Robert
Nick Minutello wrote:
Why do you permanently save the test configurations?
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
one often needs to run a specific test for a short period of time
Ok, I get you.
But, If they are truly transient run/debug configurations - then perhaps we shouldnt persist their cfg at all (keep their cfg for the life of the run/debug pane only...). After all, what meaning does the "last-run" cfg have a day or so later if it was only temporary?
IOW, make the saving of a run/debug cfg explicit - perhaps have a little button or a popup "Keep this cfg for later".
The problem I keep having is that I forget to save my important run/debug cfg's - and then I am always over-writing them with a little noddy one that I am using for testing out an idea.
Also, when I am giving a training course, I write many little "main" programs to illustrate points - and keep overwriting the run/dbg cfg I want to keep... and sometimes I want to go back to them - and they are no longer there.
Is there any way we could make this distinction clearer?
I now know I am meant to "Save" - but I know I will frequently forget... can we make the necesity to save more prominant?
Cheers,
Nick
See above : http://www.intellij.net/forums/thread.jsp?nav=false&forum=22&thread=56729&start=0&msRange=15#634269
Nick Minutello wrote:
Is there any reason why you can't just go back to the class and "Run" or
"Debug" it again? I.e. Are you doing any extra work to setup the
configuration that you are losing? If so, perhaps the configuration
should be automatically saved if any changes are made to it.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
|
|Is there any reason why you can't just go back to the
|class and "Run" or "Debug" it again?
|
No, not really. Its just that:
a) I keep looking in the Run/Debug drop-down list only to find that it is not there
b) I just felt that was slow - but re-examining it again, its not that bad (the confirm settings step seems to have gone away now?)....
c) occasionally, I do edit the settings (-verbose:gc) or change the parameters etc
I think its perhaps not 100% clear that its "temporary" - probably accentuated by the fact that its not how I am used to (Ariadna) working...
-Nick
Releated request http://www.intellij.net/tracker/idea/viewSCR?publicId=20460
--
Best regards,
Dmitry Peshehonov
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"
"Nick Minutello" <no_mail@jetbrains.com> wrote in message
news:32859152.1069962116809.JavaMail.javamailuser@localhost...
>
>
>
we shouldnt persist their cfg at all (keep their cfg for the life of the
run/debug pane only...). After all, what meaning does the "last-run" cfg
have a day or so later if it was only temporary?
>
button or a popup "Keep this cfg for later".
>
cfg's - and then I am always over-writing them with a little noddy one that
I am using for testing out an idea.
>
programs to illustrate points - and keep overwriting the run/dbg cfg I want
to keep... and sometimes I want to go back to them - and they are no longer
there.
>
can we make the necesity to save more prominant?
>
Nick Minutello wrote:
It's an option in the settings dialog. One of the checkboxes at the
bottom allows you to turn off showing the settings dialog when you run a
configuration (temporary or not). I normally have it turned off because
I hardly ever change the settings of my configurations.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
>> It's an option in the settings dialog.
Yes. It has always been there no?
But even if you have it checked, the right-lick-run doesnt bring it up (only if you click on the green toolbar "play" button)
-Nick
Nick Minutello wrote:
>>>It's an option in the settings dialog.
Since at least 3.0 (which is when I first started using IDEA).
Right-click->Run is supposed to be a
quickly-run-this-class-which-has-a-main-method action which is different
from the green play button's run-this-configuration action.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
Actually, I have changed my mind now :)
Now that I know how it is meant to work, I actually prefer the way it works now.
It still needs to be a little obvious to the unaware - but I agree with the mode of operation.
Cheers,
-Nick