It was so boring that in some cases you gave up on your fix because of all the annoying things you had to do.<\/p>\n
But wait, this time is over!
\n<\/p>\n
In this post, I will show you how to work as a developer on the eXo Tasks Add-on<\/strong> and how you can quickly contribute to this open-source project<\/strong> without installing anything on your laptop, thanks to Eclipse Che<\/strong><\/a> and Codenvy<\/strong><\/a>! (Unless you don\u2019t have a browser \ud83d\ude09 )<\/p>\n Codenvy<\/strong> is based on the open-source Eclipse Che project<\/strong> and can be extended and customized with Che plugins<\/strong>.<\/p>\n The eXo Tasks Add-on is a task management application<\/strong> that allows you to create and organize tasks in eXo Platform<\/strong>. If you want to know more about it, take a look at these two blog posts:<\/p>\n We are going to fix a very simple issue for the purposes of this demo. As you can see in the animated image below, when you want to edit a task description, you have to click on the dedicated rich editor area, but the focus is not set in the rich editor field.<\/p>\n Ok so now let\u2019s fix it!<\/p>\n The first step is to go to the eXo Task GitHub project<\/strong><\/a> and to click on the { ☁ } Developer Workspace<\/strong> button.<\/p>\n When clicking on the button, it calls a Codenvy Factory<\/strong><\/a>. A Factory is a template used to generate a new developer workspace from a consumer-friendly URL. We created one dedicated for eXo Tasks which allows to automatically load a ready-to-use development environment<\/strong>.<\/p>\n NOTE: You need a Codenvy account to be able to use it. An account is free and you can create one quickly with your GitHub or Google+ accounts, for example.<\/em><\/p>\n When the workspace starts up, the following steps are automatically executed:<\/p>\n You can follow these processes in the Terminal view<\/em> at the bottom of the screen, where you can also find the link to access your eXo Platform instance with the default username (root) and password (gtn):<\/p>\n NOTE: Even if the preview URL is there from the beginning, you need to wait until the end of the command to be able to click on it so that your eXo Platform instance is ready to use.<\/em><\/p>\n Eclipse Che and Codenvy allow you to create commands associated with your work space. As the eXo Tasks Add-on<\/strong> is a Maven project<\/strong>, there are some basic Maven commands available, like \u201cclean package<\/em>\u201d and \u201cclean test<\/em>\u201d. Starts the eXo Platform as a background process and displays the logs<\/p>\n Stops the Platform waiting for up to a few seconds for a process to end<\/p>\n Displays the platform.log content file in real time<\/p>\n Cleans up all the data to enable starting with a fresh instance<\/p>\n Builds the eXo Tasks project with Maven and installs it into (or updates it in) the eXo Platform installation with the eXo Add-on Manager.<\/p>\n <\/p>\n Like the previous command, and in addition starts the eXo Platform instance after successful installation of the Add-on<\/p>\n As you can see on the screenshot below, those commands, available via the Run > Commands<\/em> menu, can be easily updated:<\/p>\n These commands are enough to make you efficient in developing eXo Tasks out of the box, but you can also create your own commands. Feel free to create some and share them with us. We will be happy to improve the default commands based on your feedback.<\/p>\n Now we are ready to fix the bug:<\/p>\n Ok, the fix seems to be good, let\u2019s create a pull request \ud83d\ude42<\/p>\n To be able to create a pull request on GitHub, you first need to fill in the form on the Committer<\/em> screen via the menu entry Profile > Preferences > Git > Committer<\/em>:<\/p>\n Then, since the Task project has been checked out on the default Git branch (branch develop), you need to create a new branch. Let\u2019s name it \u201cfix\/TA-484\u201d here to follow eXo conventions, because we already have a JIRA opened for this bug<\/strong><\/a>:<\/p>\n Now you can use the Pull Request panel<\/strong> on the right of the screen to enter all the details for the pull request you want to create:<\/p>\n\n
Fix a bug in an eXo add-on, then build, install and test your code and create a PR with just \u2026 a browser!<\/h2>\n
![\"Fix](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image04.gif\")
<\/a><\/p>\nStart your developer workspace with one click<\/h3>\n
![\"Task](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image09.jpg\")
<\/a><\/p>\n![\"eXo](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image05.jpg\")
<\/a><\/p>\n\n
![\"eXo](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image00.png\")
<\/a><\/p>\nA closer look at the commands<\/h3>\n
\nIn addition, we have created some useful custom commands<\/strong>:<\/p>\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
![\"Useful](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image07.png\")
<\/a><\/p>\nFix a bug, and then build, install and test your code on an eXo Platform instance<\/h3>\n
![\"Fix](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image061.gif\")
<\/a><\/p>\nCreate a Pull Request<\/h3>\n
![\"Create](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image011.png\")
<\/a><\/p>\n\n
![\"New](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image021.png\")
<\/a><\/p>\n\n
![\"Pull](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image03_2.gif\")
<\/a>
\nNOTE: A fork of the project will be created on your GitHub account, so the first time Codenvy needs to access your account, a popup will ask you to validate some GitHub permissions.<\/em><\/p>\n
![\"Another](\"https:\/\/www.exoplatform.com\/blog\/wp-content\/uploads\/2016\/05\/image08.png\")
<\/a><\/p>\n