rherrmann / eclipse-extras Goto Github PK

I just wondered, as 'F11' is the launch-latest short-cut for the debug mode and 'CTRL+F11' is the launch latest short-cut for the run mode in Eclipse whether it would stand to reason to use a similar combination that allows preselection of the launch mode when opening the launch dialog. This means 'ALT+F11' would open the dialog with debug mode selection and 'CTRL+ALT+F11' would preselect the run mode. Just a spontaneous idea...

The 'quick launch dialog' should list all available launch configurations and allow to Run/Debug/Profile the selected item.

• list recently used launch configurations first, like the 'Open Type' dialog does
• provide an 'Edit' button to open the launch configuration dialog for the current selection
• check supported launch-modes of selected launch-configuration against default launch-mode and override default launch-mode accordingly

According to the Guidelines for Eclipse Logos & Trademarks the name 'Eclipse Extras' may conflict with paragraph 2c of the Proper Usage of "Eclipse" Trademark and Logo section.

Therefore, rename all user-visible labels, artifact names, etc. to 'Extras for Eclipse'

• Ensure that multiple (parallel) test runs can be handled
• Provide a preference page to enable/disable the JUnit status bar contribution
• Update README.md
• Format numbers with thousands-separator

Including Archive Utilities into Extras for Eclipse.would simplify maintenance, e.g. single marketplace entry, single build, single repository, etc.

Like all other Extras features, the archive utilities would also remain a separate feature that can be installed on its own.

Hi there,

I'm thinking of the following use case: I have a class which implements Serializable and therefore needs a serialVersionUID. Eclipse offers to generate one, everything's fine.

Now, in theory, this field should be updated whenever the class is changed. But this is a manual process and therefore, one tends to forget this step.

Wouldn't it be great if our IDE handles this? For example, everytime I save a class, the IDE generates a new serialVersionUID, for example based on the current timestamp so it is readable. Maybe this could be implemented as a new save action?

Probably I'm too stupid, but I have not been able to install eclipse-extras from eclipse marketplace. I've tried on two different machines from different networks but the installation process stops on this dialog page:

Note that there is no error log entry. You can hit the confirm button as often as you wish, the Finish button will not be enabled. Any ideas?

The working set would determines the projects that it contains based on a name pattern. See also the corresponding Platform/UI feature request.

This is how the progress bar looks after the test-run has terminated

The launch dialog should have an option that, when enabled, causes a possibly running launch to be terminated before starting the selected one so that at most one process of a certain launch configuration is running at a time.

Take care to not interfere with launch configuration types that have a 'terminate before launch' option built-in (e.g. RAP/RWT launch configurations)

Hide the JUnit status bar and then try to show it again. No way, the JUnit status bar remains invisible.
This seems to be a regression in Platform/UI 4.x, the same steps work as expected in 3.8.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=459904

To work around this bug, resize the workbench window and the JUnit status bar will re-appear.

The Start Launch Configuration Dialog should offer a means to terminate all currently running instances of the selected launch configuration(s).

Possible approaches

• a context menu that terminates all currently running instances of the selected launch configurations
• a key binding, e.g. Shift+Return that first terminates currently running applications and then (re-) launches the selected launch configurations

Since Eclipse Neon, there is a Toggle Full Screen mode command that also uses the Alt+F11 key binding (see this bug for details: https://bugs.eclipse.org/bugs/show_bug.cgi?id=491572)

After renaming a launch config from the launch dialog and returning back, the old launch config is still visible.

Follow these steps to reproduce

1. open the launch dialog
2. select a test and select Edit...
3. change the name of the launch configuration
4. select Apply and then Close

Only after changing the filter text, the orphan launch config vanishes.

See this SO question for the technical background.

Hey,

I really like you extras :) I was trying to update my Eclipse Oomph script (I was missing the new working set feature) but I'm somehow unable to install your bundles. Just to make sure that the guy in front of the keyboard isn't causing the issue with the oomph script I tried a regular install "Help -> Install New Software...", but the same issue ...

I made some screenshots using Eclipse Neon:

Thanks for your plugins :)

Konstantin

Steps:

1. close the JUnit Status Bar
2. start a long running test suite
3. go to Window > Preferences > Java > JUnit > JUnit Status Bar to show the status bar again

-> The number of executed tests is counted from that point in time when the status bar is shown and will never reach the total number of tests.

This is a regression, introduced by fixing #49

The currently used black text on red background is difficult to read.

If an editor has an IPathEditorInput or IURIEditorInput the command should delete the corresponding file from the local file system.

One of the bigest annoyances when it comes to viewing images in Eclipse is that images within jar or war or archive files cannot be viewed.

Therefore, provide a simple editor, that is associated to commonly used image file extensions (e.g. gif, tiff, jpeg, bmp, and the like) and allows to show the image.

Follow these steps to reproduce

1. open the launch dialog
2. select a test and select Edit...
3. change the name of the launch configuration
4. select Apply and then Close
   An error dialog like the one below is shown:

Either set this option automatically when the JUnit StatusBar is shown or allow to easily control this option, e.g. though a context menu on the status bar.

See

InstanceScope.INSTANCE.getNode(JUnitCorePlugin.CORE_PLUGIN_ID).putBoolean(JUnitPreferencesConstants.SHOW_ON_ERROR_ONLY, checked);

Even though this is a weird test suite setup, I've seen this in the wild:

@RunWith(Suite.class)
@SuiteClasses({ SubTestSuite.class, FooTest.class })
public class MasterTestSuite {
}

@RunWith(Suite.class)
@SuiteClasses({ FooTest.class })
public class SubTestSuite {

}

public class FooTest {
    @Test
    public void testSomething() {
        fail("Not yet implemented");
    }
}

Running the MasterTestSuite will execute testSomething twice. The JUnit progress meter, however, will show 1 / 2, indicating the one of two tests have been executed.

Ctrl+Shift+V?

Start a (longer running) test suite and drag the JUnit progress bar to another location within the status bar. After dropping it, the progress bar is blank is isn't redrawn any more.

If a new test (suite) is launched the progress bar works as expected.

The reason herefore is that a new contribution item is created at the new location and an already running test suite is not picked up by the progress bar.

Sometimes you have launch configs with the same name among different projects, e.g. a trunk- and a branch-project. Within the launch dialog, we cannot distinguish between them yet.

To align with other codeaffine projects, the build should be migrated from Codeship to Travis.

With the Java Debug option 'Suspend VM' enabled, all threads are suspended when a brakpoint is hit. To resume the process, all threads need to be resumed individually.

A 'Resume All' command could help here in that it resumes all threads of the currently selected process.

well, the JUnit status bar contribution is visible but with a very small height (~ 7 pixels)

Seems related to these Eclipse bugs

• Bug 183003 - [Trim] widget contributions are of fixed heights
• Bug 466609 - [Contributions] Status bar contributions are cut off