moliva / studio-utils

studio-utils

Installation

• Clone this repo to your favorite location:

git clone https://github.com/moliva/studio-utils.git ~/.studio-utils

• Add to your ~/.bashrc, ~/.zshrc or ~/.profile file the following:

source ~/.studio-utils/studio.sh

Usage

The available commands are the following:

• buildstudio: runs a STUDIO_BUILD_COMMAND in the current repository and receives an optional list of parameters to be appended to the command and fires a notification whenever the build is finished (only for Mac). The command is set by default to:

export STUDIO_BUILD_COMMAND="mvn clean package"

• openstudio: runs a just built version of Studio based on the code repository. This functions expects that a mvn package has been run previously.
• setdebugforstudio: sets the remote debugging line to the built product INI file
• unsetdebugforstudio: unsets the remote debbuging line
• editstudioproductini: tries to open an editor for the built Studio INI file. Note: The edit function requires that an EDITOR is set as env variable referencing to the executable file or the command, depending on the use. Example:

export EDITOR=vim
# or in a Mac, this could also be possible
export EDITOR=$HOME/Applications/Atom.app/Contents/MacOS/Atom

Each of the above commands work in two different ways:

• either by calling them without arguments where the repository will be taken from the context of the current directory, echoing an error message whenever it cannot find one: mule-tooling/..$ openstudio
• or by passing the name of the directory of the repository to be used: $ openstudio mule-tooling-2 This requires the WS_HOME env variable to be set to the path where all the respositories are cloned as shown in the following example.

~
├── repos # <-- WS_HOME=~/repos
│   ├── mule-tooling
│   ├── mule-tooling-2
│   ├── mule-tooling-3
│   ...
...