Building a Studio from GitHub for WaveMaker || Part-5

Building your own Studio from sources takes the most effort to set up, but provides the most flexibility and control over the development environment. It is also the first step should you wish to get involved in open source software and contribute to the development of WaveMaker.

To build your own Studio, you will need the following:

The following are optional, but highly recommended:

To clone the repository, use the following git clone command:

You will want to use the 6.5.X branch:

https://github.com/SpringSource/wavemaker/tree/6.5.X

Use the git checkout command:

git checkout 6.5.X

The preceding git checkout command is used to switch your local copy to the 6.5.X branch. The 6.5.X branch is stable and contains any updates made to 6.5 since the 6.5.3 release. Tags for specific releases, such as 6.5.2, also exist should you want the source for a specific release version.

The master branch, on the other hand, is a work in progress for the next version, and may not be completely stable at any given moment. You generally will not want to use the master branch unless you know what you are doing and are comfortable dealing with the possible consequences. With that said, the master branch is an easy way to see the newest features and fixes in the WaveMaker project.
If you don't have or don't want to use a git client, you can download the source code as a .zip or .tar.gz file directly from GitHub. Using the git client has the advantage of being able to pull updates without having to download the whole source tree, and easily you can switch branches. Downloading as a bundle is an easy way to access the source code. If you just want to browse the source code without downloading it all, you can do so via the GitHub site, 

 https://github.com/ SpringSource/wavemaker.

The project README explains how to clone, build, and deploy WaveMaker. It is available at 

https://github.com/SpringSource/wavemaker/blob/master/README.md.

The in-place deployment to your own Tomcat lets you use your Tomcat installation. Using the inplace target option with a git clone workspace is the easiest way to update Studio without building an installation package. To use this feature, you will need the manager app-enabled with accounts that match those in /wavemaker-tools/src/main/resources/com/wavemaker/tools/project/app-deploy.xml.

That's it.

The Previews post: Installing locally using a release package for WaveMaker web-building tools || Part-4

Netxt Post: Setting up the examples for wavemaker tools || Part-5

Visit Web Tutorial regularly.