Community
Participate
Working Groups
I'm working on a project where we're writing a bunch of web services. We run all of the tiers in "development mode" inside of eclipse. It works well, but we have 4 debug configurations we start when we want to start a debug session. It would be nice if, on the Run->Debug... dialog, it allowed you to multi- select a few debug configurations, and then click the "Debug" button. Right now, if you multi-select debug configurations, it greys out the Debug button. If it let me click it and then just started all of the debug configurations selected, that would be really useful for us. Thanks!
Deferred. The proper solution is open for debate: * A scripting language to create a macro to launch mutiple configs * multi-select * A launch config type which is a container of configs to launch (you could contribute this yourself if this is urgent)
*** Bug 41168 has been marked as a duplicate of this bug. ***
*** Bug 115058 has been marked as a duplicate of this bug. ***
Reopening. I spent an hour on this and will attach my current patch to this bug so that I don't lose it. I intend to finish the patch someday...
Created attachment 84023 [details] work in progress
*** Bug 221144 has been marked as a duplicate of this bug. ***
*** Bug 113221 has been marked as a duplicate of this bug. ***
*** Bug 228091 has been marked as a duplicate of this bug. ***
We might want to split out a core API for launching multiple configs vs. the UI for launching multiple configs. This will enable clients that do not need the UI (such as launch shortcuts) to use the multi-launch API .
*** Bug 232949 has been marked as a duplicate of this bug. ***
(In reply to comment #10) > *** Bug 232949 has been marked as a duplicate of this bug. *** > Nice to see that someone is working on it, but it looks like I have to wait for a long time before this feature is added. :( (The original bug was reported in 2003 if I understand the history?)
Created attachment 109715 [details] patch This patch works for me, but it is still a little rough around the edges. ;-) - The multi-launch will always be sequential (not parallel). - Progress reporting seems not quite right, and I haven't tested if you can cancel. - There are no fancy pre-launch builds and the like, the action just goes ahead and launches what you have selected. - The launch dialog will not be closed for you when you multi-launch, but it probably should. Feedback from the Debug team would be welcome. Do you think this is a feature you would want to have?
Hurray. It makes me very happy to see that this might be solved in a near future. I've been waiting for a feature like this for at least 4 years.
(In reply to comment #13) > Hurray. It makes me very happy to see that this might be solved in a near > future. I've been waiting for a feature like this for at least 4 years. Thanks - but what exactly would you use it for? Are you looking for sequential execution, or parallel execution of multiple launch configurations? If sequential, does the order matter for your use case?
(In reply to comment #14) > (In reply to comment #13) > > Hurray. It makes me very happy to see that this might be solved in a near > > future. I've been waiting for a feature like this for at least 4 years. > > Thanks - but what exactly would you use it for? Are you looking for sequential > execution, or parallel execution of multiple launch configurations? If > sequential, does the order matter for your use case? > I'm a consultant and have seen the need for this at many different clients. All of my clients are creating distributed server side systems where you normally need to start several different servers (java applications) when you want to test or debug. The start order isn't important but you must start all of them. It's a very tedious task to do it right now. What do you mean by sequential? I guess that it isn't waiting for a termination before it continues to launch the next one? Sequential is fine for me if that means that one thread is launching one VM and then continues to launch the next one while the first one is still executing. (Just as if I had launched one in the menu, and then launched the second one and so on)
(In reply to comment #12) > Created an attachment (id=109715) [details] > patch > > This patch works for me, but it is still a little rough around the edges. ;-) > > - The multi-launch will always be sequential (not parallel). > - Progress reporting seems not quite right, and I haven't tested if you can > cancel. > - There are no fancy pre-launch builds and the like, the action just goes ahead > and launches what you have selected. > - The launch dialog will not be closed for you when you multi-launch, but it > probably should. > > Feedback from the Debug team would be welcome. Do you think this is a feature > you would want to have? > Well done, the patch almost does what I need. Here is my use case for the multi-launch feature. I work on program analyses which usually have to be run with different configurations on various benchmark programs. Every launch runs a new JVM with the target program and a specific configuration. The multi-launch should run every selected launch sequentially, i.e., the next launch is executed after the previous is terminated, otherwise memory consumption would kill the machine. The actual sequence in which selected launches are executed isn't that important, though it would be nice if it could be defined.
Ah. Sounds like we have different cases in that case. Launching a new application after termination of the previous wouldn't help me at all :(
I agree with Kaj. I see few use cases where you would want to launch sequencially. In my case I need to run up several server components, which open sockets and talk amongst themselves. I can see other cases, where someone may want to run up mock servers etc. All would require launching many processes in parallel.
Created attachment 109794 [details] patch with parallel and sequential multi-launch Actually, I need this for sequential launches (like Jan) - when doing a build submission, I would like to multi-select a number of JUnit launch configurations and have them all executed, one after another. Some of these tests are UI tests that are sensitive to other applications running at the same time. This new patch supports both parallel and sequential multi-launching.
(In reply to comment #16) > Well done, the patch almost does what I need. What exactly is missing?
(In reply to comment #20) > (In reply to comment #16) > > Well done, the patch almost does what I need. > > What exactly is missing? > Well, I could think of more additions to that feature, such as named groups of launches, but if this isn't a call for the next killer feature it works for me. Thanks a lot!
Thanks Boris! Your patch works great. Like Jan, I'd really like to be able to save (ideally ordered) groups of launch configurations, but what you have so far is already a huge improvement.
Please note comment #9 and dup'ed bug 228091. The attached patch is only at the UI layer and does not appear to solve this related issue when calling debug core API. Please let me know if you plan to attach another patch that resolves both issues, or if we should reopen bug 228091 for more investigation.
Tim - not sure if this will help your case, but I was planning to attach another patch that used a different approach, one that would allow you to define multi-launches as a separate launch configuration type.
Thanks, Boris. Hard to say whether it will help without fully understanding what that means, but I'll look at any patch posted. My basic issue is multiple prompts/inconsistency when a launch shortcut triggers two launches (either consecutive or parent/child) that are conceptually one action for the user.
*** Bug 294713 has been marked as a duplicate of this bug. ***
This is not JDT specific.
I'm an end user and I use Eclipse Galileo build 20090920-1017. How do I get the patch applied to my eclipse?
Try the steps from here: http://www.eclipse.org/eclipse/debug/get_involved.php#writing_code - good luck! If you need help overcoming obstacles, I would recommend the #eclipse channel on http://wiki.eclipse.org/IRC or the forums, for example: http://www.eclipse.org/forums/index.php?t=thread&frm_id=11& .
Created attachment 177951 [details] A plug-in project to show a basic workflow Hello, In addition to the great job you have done, we were able to implement a basic workflow (a specific launch configuration to chain configurations) on top of debug components; ie to save the multiple selection to launch. Please find attached a plug-in project to demonstrate our purpose. To use it, you have to import the project into your workspace then to run an Eclipse application. In the runtime eclipse, you will have to open the dialog of launch configurations to find the new type "basic workflow". After creating several launch configurations of different types, create a new launch configuration of type "basic workflow" then you will be able to load existing launch configurations (existing limitation, recursion is not allowed so a configuration of a basic workflow is not available in list of launch configurations).
Of course, if you like it, you just have to export the plug-in project in your eclipse to install it properly. Regards Gabriel
CDT solution for a similar problems is Bug 270671 or http://wiki.eclipse.org/CDT/User/NewIn60#Debug_and_Launch - It is a a top level launch "Launch Group" - User can edit the launch sequence - parallel/sequential/mixed launching. - User can edit the sequence order. Can edit wait period between sequential launches. - Can mix debug/run/profile launch configurations. There're no dependency on CDT capabilities and you can simultaneously launch any launch configurations. It could be possible to pull out of CDT launch plugin, may be to promote to platform?
+1 to promote the CDT plug-in, it looks good !
Created attachment 179099 [details] Patch to extract the multi launch from CDT project Here is a first attempt to cut links to other CDT project and obtain an autonomous plug-in. Could review it, please ? Regards, Gabriel
Nice, want to have to. 2$ when it is out. http://www.bidforfix.com/ Anyone else would pay extra for this feature?
Could be an easy addition to migrate the CDT feature.
Sigh, I've been waiting for this feature for ages. I still have to manually start 10+ launch configurations every time I want to test/debug the system.
Another use case for the sequential workflow is having to run multiple maven (m2e build's) run configurations. To deploy a change to my development environment I have to 1) use m2e process a pom.xml that builds a JAR component X 2) use m2e process a pom.xml that runs maven-assembly-plugin to assemble component X into a specific directory structure Y 3) use a plain java run configuration that execs an installer that processes Y and uploads Y into tcp server. So my ideal workflow implementation would include a way to check the return code of steps #1 and #2 to make sure things were successful and if so keep going to the next step.
Has anyone looked at reviewing the patch from Comment 34? Especially for unit test launches, I run into a need for this feature in almost every project I work on in recent years.
Another year gone by, no response from Platform Debug team. Sad. Who is monitoring Platform-Debug-Inbox?
(In reply to Eric Rizzo from comment #40) > Another year gone by, no response from Platform Debug team. Sad. > Who is monitoring Platform-Debug-Inbox? Attached "patch" in Comment 34 only deletes stuff from CDT. It's not a separate plug-in or patch for Platform Debug. If someone can provide a patch for Platform Debug, we will be able to work on integrating it but we don't have resources to work on the patch.
Can someone explain in one line what is the status of the this bug/feature? I read few comments but not sure whether this task is completed or not. However, I see the status as "ASSIGNED"
(In reply to Naveen Potnuru from comment #42) > Can someone explain in one line what is the status of the this bug/feature? > I read few comments but not sure whether this task is completed or not. > However, I see the status as "ASSIGNED" The Eclipse platform 4.7 M4 [1] has support for _Launch Groups_ with features similar to those outlined in comment #32. Not sure though whether or not this completes this bug. [1] https://www.eclipse.org/eclipse/news/4.7/M4/
(In reply to Rüdiger Herrmann from comment #43) > (In reply to Naveen Potnuru from comment #42) > > Can someone explain in one line what is the status of the this bug/feature? > > I read few comments but not sure whether this task is completed or not. > > However, I see the status as "ASSIGNED" > > The Eclipse platform 4.7 M4 [1] has support for _Launch Groups_ with > features similar to those outlined in comment #32. Not sure though whether > or not this completes this bug. > > [1] https://www.eclipse.org/eclipse/news/4.7/M4/ Yes, Bug 492788 has added the feature of creating Launch groups. I am closing this bug, please create a new one with specific requirements not covered by Bug 492788 and Bug 508420. *** This bug has been marked as a duplicate of bug 492788 ***
