Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Maven profiles

By default we just build a WAR package in qcadoo-src/mes/mes-application/target which you can configure to run on a servlet container of your choice. This does not include the qcadoo-tomcat module.  If we want to build a package that runs on an enabled Tomcat you have to add the -Ptomcat argument to the maven command.

You can also find some additional deployment profiles that use specific configuration files in the directory qcadoo-src/mes/mes-application/conf. To use a profile add the following argument when executing maven: -Dprofile=profile_name.

For example the binary release of Qcadoo is build using -Ptomcat argument. This is done using the below command in the directory qcadoo-src/mes:

mvn clean install -Ptomcat

the above will build the binary distribution to the qcadoo-src/mes/mes-application/tomcat-archiver/mes-application directory.

For developer testing you might want to also just run the build on jetty. To do this just use the following command:

mvn jetty:run -Dprofile=profile_name

We also use configuration and build profiles to do specific deployments on servers. For example to deploy a demo Qcadoo MES instance on our internal test server in Qcadoo Limited called emhyr we use the following command:

mvn clean deploy -Pemhyr,tomcat,compressResources -Dprofile=emhyr-demo

The -PcompressResources is and additional profile which makes the application resources take less size.

  • No labels