• Problem deleting a project right after it is created, need to make sure the UI is refreshed
• Problems with the log file actions getting NPEs

LibertyDebugTest needs to be updated:

• Don't pass in contextroot when creating project anymore
• Use Dockerfile instead of Dockerfile-lang

For a Microclimate connection it should only cache the host and port. Anything else could change if the user stops Microclimate and starts a new one.

Update the project log support:

• filter out logs named "-"
• support projectLogsListChanged event

Add support for creating new Microclimate projects in Eclipse

Some actions can support multiple selections such as delete, show all/hide all logs (it would not list individual logs in this case), refresh, etc.

Some project types do not support the application monitor so the action to open the app monitor should not show or be disabled for these project types. Wait for the capabilities to include this information before fixing this.

There should be some generic icon for languages/projects that don't have a matching icon

The location is too long to include in the console name for log files so remove for now until a better way of showing it is found.

Trying to create a new project sometimes results in a read timeout. Set the timeout explicitly in HttpUtil.

When a new project is created, make sure the connection is expanded in the Microclimate explorer view so the projects can be seen.

Similar to the action on a Microclimate connection to open the Microclimate UI's create project page, there should be an action for opening the import project page.

Update the plugin and feature versions for the 19.01 release.

The update code should not continue if the project is disabled. Also, need to update a project when it is found to be enabled again.

In the New Microclimate Connection wizard , after entering your host and clicking Test Connection (which succeeds) the Next Button is enabled, despite there being no next page.

Reproduced on Linux with February 2019 Microclimate Eclipse Tools GA.

Project create support was added to the tools and the tests should be using the same methods that the UI invokes instead of the internal ones it was using to create projects.

Update the plugin and feature versions for the 19.02 release.

Retrieve the set of log files from Microclimate for a project and allow the user to display any or all of those log files. For older versions of Microclimate the previous mechanism where there is one app log and one build log (except for Node.js) per project needs to be maintained.

Update the test cases to check the new log files.

The message that shows for a connection when there are no projects should say "Right click and select Open New Project Page" to match the menu item instead of "... Open Create Project Page".

I ran into a situation where some Microclimate applications that were deleted are still showing in the view. This should not happen because there should be a deleted event when an application is removed and whenever Eclipse is restarted a fresh list of applications is retrieved. It would still be better, however, to make sure the app lists are in sync and remove any applications that don't show in the list returned by Microclimate.

Add test cases to cover auto build and validation.

With high contrast mode enabled the first column of the template table in the new project wizard is displayed with a grey background:

The show all and hide all logs actions need icons as well as the main Show log files menu item.

In the DeleteProjectAction it checks that the path of the project in Eclipse is the same as the path of the project in Microclimate to decide whether to delete the Eclipse project when the Microclimate project is deleted. It should compare files instead of paths though so that it works on Windows.

Improve the delete message to make it clear that the project and all of its source files will be deleted from the Microclimate workspace.

Run refresh actions in a job so they don't hold up the UI.

When deleting a project, the UI gets blocked by the delete confirmation dialog until the delete operation completes. This probably means that we are doing the delete in the main UI thread. Consider to move it a background job instead given that the delete operation can sometimes takes long.

The tests wait for all jobs to be finished when importing a Microclimate project into Eclipse. This includes waiting for Maven build jobs which can take some time. Turning off auto build helps speed up the tests quite a bit.

Support the new microclimate API for validation:

POST /api/v1/projects/{id}/validate
POST /api/v1/projects/{id}/validate/generate

When switching the project from debug mode to run mode it goes through the usual states: stopping, stopped, starting but the final state is debugging instead of running.

The problem is that the started event:

message: projectStatusChanged
data: {
"projectID": "82eb2070-264f-11e9-b3c3-cd8ce10e8088",
"appStatus": "started"
}

is coming before the restart event with the mode:

message: projectRestartResult
data: {
"projectID": "82eb2070-264f-11e9-b3c3-cd8ce10e8088",
"status": "success",
"startMode": "run",
"ports": {
"exposedPort": "32801",
"internalPort": "9080"
}
}

So the tools should be doing a refresh on the project in the view when the restart event is received.

Add a CHANGELOG.md file to keep track of significant enhancements and bug fixes.

When a new Microclimate project is created, import it into Eclipse by default. Can have a checkbox on the wizard that is selected by default.

Instead of opening the Microclimate project overview page in a browser, add support for a native overview page.

The screen reader does not read the project template group name in the new project wizard. Tabbing from the project name field goes directly to the filter text field and the reader just reads: "Type filter text". It skips the "Project Template" group name so the user would not know what to do here. Use a read only text field instead of a group name so that the reader picks it up.

Various improvements to the Node.js debug dialogs.

Add a show on content change action to the toolbar for project consoles.

For Node.js projects a debugger is not attached through Eclipse but rather it (helps) launch a debug session in a Chromium based browser. So the Attach Debugger label should be changed to reflect this.

Add support for debugging Node.js projects.

The workspace needs to be refreshed after a build so that changes to build artifacts can be seen in the project explorer view.

The environment api returns a socket_namespace value that should be appended to the URI.

Get the context root and update it on a refresh and on project changed events.