deployToDir can't be anything but build dir

Steps to reproduce

The current 1.4 and trunk build dir still use the -DdeployTo paramater. However setting this to anything but the current build directory results in an incomplete build. Only the libraries deployed to /lib/ seem to use this.

other files should be deployed to deployTo as well


Tobias Wunden
May 28, 2012, 10:59 AM

Hi David, this seems to be a documentation bug rather than a software problem. The -DdeployTo support is only intended to support deployment of the libraries (external and matterhorn) to a certain location, not the configuration files. The reasoning behind this is that a developer will check out from trunk, configure a local runtime environment, then build and deploy to that environment. If config files were to be deployed from the trunk version as well, local modifications would be overwritten everytime you build (and deploy), if you start making the configuration changes in your local checkout, chances are that they will end up being committed here and there.

If you have a good solution for this, please let us know. Otherwise I suggest to clearly state in the documentation that -DdeployTo only deals with libraries for the abovementioned reason.

David Horwitz
May 28, 2012, 11:02 AM

+1 that seems a good and quick solution

Tobias Wunden
January 8, 2013, 3:48 PM

Closing this since David agreed to the current practice.

Fixed, no review needed


David Horwitz


David Horwitz


Incorrectly Functioning With Workaround

Tags (folksonomy)


Fix versions

Affects versions