[
https://issues.apache.org/jira/browse/CLOUDSTACK-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475876#comment-13475876
]
David Nalley commented on CLOUDSTACK-340:
-----------------------------------------
I think Edison's intent is to say that 'ant deploy-server' is a developer
environment command, and expects ant debug next
End users would use something like waf install, or install from RPMs created
from waf, and use service cloud-mgmt start to start cloudstack
Personally I dislike this workflow - IMO developers should be using the same
workflow to build/manage cloudstack development instances as the RPMs will, and
end users will if they compile from source, and hope that our move to maven
will fix this issue.
> Tomcat config files broken after ant deploy-server
> --------------------------------------------------
>
> Key: CLOUDSTACK-340
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-340
> Project: CloudStack
> Issue Type: Bug
> Components: Install and Setup
> Affects Versions: pre-4.0.0
> Environment: Centos 5.6
> Reporter: John Kinsella
> Labels: ant, wscript
> Fix For: pre-4.0.0
>
>
> Looks like something should be performing substitution before config files
> are deployed, but this isn't happening:
> # ant deploy-server
> (completes without error)
> # /etc/init.d/cloud-management restart
> Stopping cloud-management: [ OK ]
> /etc/cloud/management/tomcat6.conf: line 73: @MSCONF@/classpath.conf: No such
> file or directory
> Starting cloud-management: chown: `@MSUSER@:@MSUSER@': invalid user
> touch: cannot touch `@MSLOGDIR@/catalina.out': No such file or directory
> chown: `@MSUSER@:@MSUSER@': invalid user
> /etc/rc.d/init.d/tomcat6: line 179: @MSLOGDIR@/catalina.out: No such file or
> directory
> [FAILED]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
