Difference between revisions of "Maven settings and profiles"
Jump to navigation
Jump to search
Siedersleben (talk | contribs) |
Siedersleben (talk | contribs) |
||
| 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. | |||
* env-opensource | |||
* env-pure | * env-pure | ||
* env-nims | * env-nims | ||
* env-testing-continuum | * env-testing-continuum | ||
* env-jrebel-build | * env-jrebel-build | ||
* integration-tests | * integration-tests | ||
* wildfly | * wildfly | ||
Revision as of 08:24, 22 October 2014
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.
- env-opensource
- env-pure
- env-nims
- env-testing-continuum
- env-jrebel-build
- integration-tests
- wildfly