Studio generally does well to present tasks logically and intuitively. Deployment may be the task that can single-handedly do the most damage to that reputation due to the range of possible configuration elements that have not been abstracted out into the deployment dialog.
Some of the project configurations can only be updated outside the Studio or by using the resource manager, akin to the enabling of dependency injection in our examples by editing XML files. The classic example here is if your deployment environment requires a custom entry in the applications' web-app context, it can be added using
user-web.xml. However, you must manually edit
user-web.xml before generating the archive.
Spring profiles enable you to ...