Difference between revisions of "Maven settings and profiles"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 1: Line 1:
Profiles available for the PubMan and common_services build process:
Profiles available for the PubMan and common_services build process:
The first three profiles mark the kind of the artifact. This may be PuRe PubMan instance (env-pure) or an OpenSource PubMan instance (env-opensource) or an NIMS PubMan instance (env-nims). A classifer is used to show the kind of instance, e.g. pubman-ear-pure.ear for an PuRe instance. Exactly one ore none of this profiles may be activated. The env-opensource profile is the default one.  
 
The first three profiles mark the kind of the artifact. Depending of the activated profile a PuRe PubMan instance or an OpenSource PubMan instance or an NIMS PubMan instance (env-nims) are built. A classifer is used to show the kind of the instance, e.g. pubman-ear-pure.ear for an PuRe instance. Exactly one ore none of these three profiles may be activated. The env-opensource profile is the default one.  
* env-opensource
* env-opensource
* env-pure
* env-pure

Revision as of 08:31, 22 October 2014

Profiles available for the PubMan and common_services build process:

The first three profiles mark the kind of the artifact. Depending of the activated profile a PuRe PubMan instance or an OpenSource PubMan instance or an NIMS PubMan instance (env-nims) are built. A classifer is used to show the kind of the instance, e.g. pubman-ear-pure.ear for an PuRe instance. Exactly one ore none of these three profiles may be activated. The env-opensource profile is the default one.

  • env-opensource
  • env-pure
  • env-nims
  • env-testing-continuum
  • env-jrebel-build
  • integration-tests
  • wildfly