71dc4475a9
During code evolution might be the case then someone will want to rename some property. This brings a couple of problems like support of old property name in external plugins and support old configuration values in code with the new property name. To cover these cases there is a file che_aliases.properties that contains old names of all existed properties. It has such format current_name =old_name, very_old_name. In this case will be such binding. Always current_name = current_value if old_name property exist it will be binded to old_value, and current_name = old_value and very_old_name = old_value if very_old_name property exist it will be binded to very_old_value, and current_name = very_old_value and old_name = very_old_value NOTE: its prohibited to use a different name for same property on the same level. From the example above - you can use environment property CHE_CURRENT_NAME and CHE_OLD_NAME. But you can use it on a different level, for instance, environment property and system property. |
||
|---|---|---|
| .github | ||
| .mvn | ||
| agents | ||
| assembly | ||
| core | ||
| dashboard | ||
| dockerfiles | ||
| docs | ||
| ide | ||
| infrastructures | ||
| multiuser | ||
| plugins | ||
| selenium | ||
| wsagent | ||
| wsmaster | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CUSTOMIZING.md | ||
| Chefile | ||
| LICENSE | ||
| NUMBERING.md | ||
| README.md | ||
| pom.xml | ||
README.md
Eclipse Che - Eclipse Next-Generation IDE
https://www.eclipse.org/che/. Next-generation Eclipse platform, developer workspace server and cloud IDE. Che defines workspaces that include their dependencies including embedded containerized runtimes, Web IDE, and project code. This makes workspaces distributed, collaborative, and portable to run anywhere on a desktop or a server ... Read More
Getting Started
You can run Che in the public cloud, a private cloud, or install it on any OS. Che has been tested on Ubuntu, Linux, MacOS and Windows. The step by step guide will get you going along with our docs.
The che repository is where we do development and there are many ways you can participate, for example:
- Submit bugs and feature requests and help us verify them
- Review source code changes
- Improve docs
Customizing
There are many ways to customize Che out-of-the-box including stacks, templates, commands, IDE extensions, server-side extensions plugins, assemblies, RESTful APIs, and editors.
Contributing
If you are interested in fixing issues and contributing directly to the code base, please see How to Contribute. It covers:
Feedback
- Support: You can ask questions, report bugs, and request features using GitHub issues.
- Public Chat: Join the public eclipse-che Mattermost channel to discuss with community and contributors.
- Roadmap: We maintain the roadmap on the wiki.
- Weekly Meetings: Join us in our Che community meeting every second monday.
License
Che is open sourced under the Eclipse Public License 1.0.