...
Below is a screenshot for a typical Windows installation.
Build Configuration - Maven tab
This is the most complex of the tabs. What we're doing here is telling moves how to run maven.
- The Maven Command entry should be left as mvn (unless you're doing some really weird shenanigans)
- Check the Run Maven with Debug Output? checkbox if you want REALLY VERBOSE maven log files. Checking this causes mvn to be run with the -e and -X options. It is useful when you're having maven problems, as it will show stack traces and lots of logging. It's annoying when you're not having maven problems, so I suggest leaving it unchecked initially.
- Max Maven Build Time (in seconds) is SUPPOSED to kill a build if it hasn't completed in a certain time. This is not yet implemented... but might be some day.
- MIT Maven Repository (containing releases) should be the location of the MIT Maven release repository. Moves uses this to find released components and display them in the GUI. (Note that this field will hopefully go away in a future release, but for now it's critical, and for now, the default value *https://maven-mit-edu.ezproxyberklee.flo.org/nexus/content/groups/saisGroupRepo/*
should be just fine). - mit-release-plugin version. Moves uses the plugin edu.mit.maven.plugins:mit-release-plugin. The latest version can be found by browsing the MIT Maven repository.
- Maven System Properties can be left blank for local development environments.
- Maven Environment Variables are needed because on some OS's when you spawn a new shell, it may or may not inherit Environment Variables from OC4J's runtime environment. So what we are doing here is making sure the environment variables JAVA_HOME, SVN_SSH, M2_HOME, MAVEN_OPTS, PATH and SVN_SSH are set up correctly. (Usually you can find these from your own command shell and copy them over. The screen-shot below shows some typical values for a windows environment.