-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Easy Installation of Development Environment #110
Comments
+1 great idea. Is anybody in the community willing to help us getting it started? Thanks. On Mar 31, 2016, at 11:00 PM, Amit Kumar Mondal <notifications@github.commailto:notifications@github.com> wrote: To ease the setup of Development Environment, an Oomph Catalogue can be provided. Many eclipse projects, for instance, E4 Tools, EMF provide Oomph Catalogues for a hassle free development environment setup. Another solution could be to create an Yatta Profile to package an Eclipse Installation which abstracts all the required steps for Development Environment setup. You are receiving this because you are subscribed to this thread. |
For my personal use, I have created an Yatta Profile which comprises all the necessary plugins and the bundles from a specific branch (kura2) for the Development Environment setup. You can find it in https://marketplace.yatta.de/. |
Thanks Amit, that’s great. @dave - can we advertise this in the Kura web site? @amit - is the Yatta Profile something that can be automated with the Kura build so we can have this automatically created in every build? -Marco On Apr 2, 2016, at 7:45 PM, Amit Kumar Mondal <notifications@github.commailto:notifications@github.com> wrote: For my personal use, I have created an Yatta Profile which comprises all the necessary plugins and the bundles from a specific branch (kura2) for the Development Environment setup. You can find it in https://marketplace.yatta.de/. — |
So far what I have explored, I couldn't find any such maven integration to create automated build for a Yatta Profile. But if there is a change in the specified kura branch, for instance, new bundles are added, then all the bundles including the new ones will automatically be imported while setting up new development environment. For instance, the Yatta Profile that I have created tracks kura2 branch and if a new developer wants to setup development environment for the first time, this Yatta Profile will automatically import all the existing projects from kura2 branch. |
If we create a yotta profile on the master branch, we should be able to have a it following the product releases. Would that work? On Apr 3, 2016, at 12:43 AM, Amit Kumar Mondal <notifications@github.commailto:notifications@github.com> wrote: So far what I have explored, I couldn't find any such maven integration to create automated build for a Yatta Profile. But if there is a change in the specified kura branch, for instance, new bundles are added, then all the bundles including the new ones will automatically be imported while setting up new development environment. For instance, the Yatta Profile that I have created tracks kura2 branch and if a new developer wants to setup development environment for the first time, this Yatta Profile will automatically import all the existing projects from kura2 branch. — |
Yeah, we can create an Yatta Profile on the Master branch as well, so that in the following releases it would track the released changes on the branch. That would work. |
Hi Amit, I just tried the profile and it worked great! Very cool stuff. Maybe we should setup a profile for the master and develop branch. I would be happy to promote this on the Kura website. One question, the profile seems to tie the Kura source code location to the Eclipse installation directory. Is that configurable? It is not a big deal, it was just a bit confusing for me. Thanks and let me know if I can help get this rolling. Thanks, On Apr 4, 2016, at 06:17, Amit Kumar Mondal <notifications@github.commailto:notifications@github.com> wrote: Yeah, we can create an Yatta Profile on the Master branch as well, so that in the following releases it would track the released changes on the branch. That would work. — |
Hi Dave, As you suggested, I have created two Yatta Profiles for master as well as develop branches, following a minimalistic approach to install least number of plugins needed for the Development Environment setup. https://marketplace.yatta.de/profiles/4d0a - Develop As the profile is tied to the branch provided in the configuration, it clones the complete repository in its Eclipse installation folder. I couldn't find any such configurable property to set the location. If I find any way to configure this, I would update the profiles then. |
Please do find the new updated Yatta Profiles for Kura Development Environment setup. https://marketplace.yatta.de/profiles/X4Wj - develop branch These profiles now perform all the manual tasks (importing projects, building the target platform, building all the bundles, setting up custom target platform and so on) automatically. Now contributors can setup their development environment very easily (within 2-3 clicks). I believe these profiles would definitely help future contributors. |
Use profiles to new web page. |
@dwoodard1 Can we close or postpone this? |
@dwoodard1 I think so. |
I think this is solved by PR #320 using the Eclipse Installer. |
Closing this issue. We now have a Yatta profile and Oomph installer for Kura. Any issues with these methods should be tracked separately. |
To ease the setup of Development Environment, an Oomph Catalogue can be provided. Many eclipse projects, for instance, E4 Tools, EMF provide Oomph Catalogues for a hassle free development environment setup.
Another solution could be to create an Yatta Profile to package an Eclipse Installation which abstracts all the required steps for Development Environment setup.
The text was updated successfully, but these errors were encountered: