<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div>FYI, can anyone on this list respond to dave?</div><div><br></div><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Hi Heiko,<br><br>I've been following various discussions about the deployment scanner and the content repository for a while, and it doesn't seem like there's a clear answer. What do you think about it?<span class="Apple-converted-space"> </span><br><br>I've seen people asking on Stack Overflow whether they are safe to use both deployment methods, and I know that I've laid some foundations to the docs by suggesting that the scanner is a developer tool, and not for production. This surprised some of our consulting team recently, who suggested that customers will use the scanner for app deployments in a production environment.<span class="Apple-converted-space"> </span><br><br>Do you have any thoughts on this?<span class="Apple-converted-space"> </span><br><br>Dave</span></blockquote></div><br></body></html>