[
http://opencast.jira.com/browse/MH-8843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30820#comment-30820
]
Tobias Wunden commented on MH-8843:
-----------------------------------
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.
> deployToDir can't be anything but build dir
> -------------------------------------------
>
> Key: MH-8843
> URL: http://opencast.jira.com/browse/MH-8843
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Distribution
> Affects Versions: 1.4
> Reporter: David Horwitz
> Fix For: 1.4
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
