This describes the scripts and Maven commands that can be used on a SkyVault Repository
extension project based on the Repository AMP archetype.
Scripts and commands:
| Command | Description |
|---|---|
| ./run.sh and run.bat | Linux/Mac and Windows scripts for running an embedded Tomcat with the
customized SkyVault.war (that is, with the Repo AMP applied) and the
flat file database H2. Access to SkyVault UI is via
http://localhost:8080/SkyVault. The username/password is admin/admin.
This script will also configure JVM memory and automatically setup Spring Loaded for hot
reloading of classes (it basically sets up MAVEN_OPTS for you). See
inside the script for further details. Warning: This script assumes that you
are developing for the SkyVault Community Edition. If you use an Enterprise Edition you
need to update the maven command in this script so it uses the
enterprise profile: mvn integration-test
-Pamp-to-war,enterprise.
|
| mvn compile SkyVault:refresh-repo | Compiles the source code and puts the class files and resources under
/target. Then makes a POST call to the SkyVault Repository web
application (SkyVault.war) to refresh the web script container. So
any changes that were made to web scripts should be visible after a page refresh.
Note: This command is typically used together with the
run.sh/bat script for Rapid Application Development
(RAD). The RAD process can be described like this:
|
| mvn package | Runs unit tests and packages AMP in ${project.build.directory}/${project.build.finalName}.amp. |
| mvn install | Like mvn package but also installs AMP in local Maven repository to be depended upon. |
| mvn test | Runs unit tests. |
| mvn install -DskipTests=true | Like mvn install but skips unit tests. |
| mvn install -Pamp-to-war | Like run.sh or run.bat but does not configure JVM memory and Spring Loaded if you have not configured it in MAVEN_OPTS. See set up MAVEN_OPTS. If you use the Enterprise edition see the next command. |
| mvn install -Pamp-to-war,enterprise | Like mvn install -Pamp-to-war but uses Enterprise artifacts. Note you need to have set up access to the private repository containing the Enterprise artifacts. |
| mvn clean -Ppurge | Removes H2 database (with metadata), alf_data (with content files and index files),
and log files. Useful to purge the development repo (by default self contained in
${project.basedir}/alf_data_dev). Note: This is an important
command to use if you change significant settings in your project. For example, if you
change the SkyVault edition from Community to Enterprise. It is important to purge
databases and other data that might otherwise be persisted.
Warning: The purge profile cannot be used together with the
amp-to-war profile.
|