However, used properly, profiles can be used while still preserving project portability. As such, profiles can easily lead to differing build results from different members of your team. They modify the POM at build time, and are meant to be used in complementary sets to give equivalent-but-different parameters for a set of target environments (providing, for example, the path of the appserver root in the development, testing, and production environments). Profiles are specified using a subset of the elements available in the POM itself (plus one extra section), and are triggered in any of a variety of ways. To address these circumstances, Maven supports build profiles. And at still other times, you may even need to include a whole plugin in the build lifecycle depending on the detected build environment. Under other circumstances, a slightly different dependency set will be required, and the project's artifact name may need to be adjusted slightly. Under certain conditions, plugins may need to be configured with local filesystem paths. However, sometimes portability is not entirely possible. Among other things, this means allowing build configuration inside the POM, avoiding all filesystem references (in inheritance, dependencies, and other places), and leaning much more heavily on the local repository to store the metadata needed to make this possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |