Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Che/Roadmap/380

< Che‎ | Roadmap
Revision as of 09:00, 24 March 2015 by Dmi3.kuleshov.gmail.com (Talk | contribs) (Created page with "'''Redesign of the runner / machine panel''' *Multi-machine panel *Behavior of templates + history *Improvements to output of Application URL *Improvements in the output of th...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Redesign of the runner / machine panel

  • Multi-machine panel
  • Behavior of templates + history
  • Improvements to output of Application URL
  • Improvements in the output of the console

Rework Project Type framework

  • Clear structure of PT parts and constraints
  • Simplify registration of PT extension related components
  • Due to strict logic of PT constraints simplify client side components logic (for instance Project create Wizard)
  • Add pluggable ProjectType related mechanism for launching Project API methods post- (and pre-) actions.

Import project from local file system

Import local project from file system maven into workspace. Load the project from a local repository. In the local file system you have a maven project. You want to be able to do an import of an existing file system where there is a root maven project directory. For example in stand alone IDEs, the ability to import a local maven project, will copy the project into the Codenvy workspace. Should be able to point to a directory, import, detect that it is maven and any sub-modules. The directory will be on the same machine that is running Che. For UX, need some sort of file browser / navigator to navigate to a directory on the local machine.

Back to the top