<div dir="ltr">Great suggestions for us moving forward w/ 'abcd'<div><br></div><div>@Leo can you file an EPIC on AGDIGGER JIRA instance, where each of the four suggestions is its own issue ?</div><div><br></div><div>Thx,</div><div>Matthias</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 18, 2016 at 11:57 AM, Ali Ok <span dir="ltr"><<a href="mailto:aliok@redhat.com" target="_blank">aliok@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><b style="font-size:12.8px">Log files<br></b>Right now it automatically saves the command output into a text file, but it wouldn't need to since you can always use a pipe to to that like "abcd buid > build.log" or "abcd build | tee build.log".</blockquote></span><div>+1.</div><div>Leave it to the user how to save the logs.</div><span class=""><div><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><br><b>Build config file<br></b>An optional hidden yaml/json file ".digger" or ".abcd" that would have some information for the CLI such as the build type and platform ("andoid" and "gradle" for example) in the future this could also specify a different build version or path to use.</blockquote></span><div><div>You mean in projects, right? Like travis.yml file.</div><div><br></div><div><span class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><b>Setup command</b> </blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><b></b>A setup command to set default configurations "abcd setup" such as default android debug keystore config, android home path, cordova path, etc.</blockquote></span><div>I think saving these things into ~/digger-config.yml would be great.</div></div><div><br></div><div>+1 on the others too.</div><div> </div></div><div>Awesome suggestions Leonardo!</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Tue, Oct 18, 2016 at 12:04 PM, Leonardo Rossetti <span dir="ltr"><<a href="mailto:lrossett@redhat.com" target="_blank">lrossett@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hello,<div><br></div><div>I was thinking on some enhancements around the CLI usage:</div><div><br></div><div><b>Log files</b></div><div>Right now it automatically saves the command output into a text file, but it wouldn't need to since you can always use a pipe to to that like "abcd buid > build.log" or "abcd build | tee build.log".</div><div><br></div><div><b>Setup command</b></div><div>A setup command to set default configurations "abcd setup" such as default android debug keystore config, android home path, cordova path, etc.<br></div><div><br></div><div><b>Build config file</b></div><div>An optional hidden yaml/json file ".digger" or ".abcd" that would have some information for the CLI such as the build type and platform ("andoid" and "gradle" for example) in the future this could also specify a different build version or path to use.</div><div><br></div><div><b>Debug flag</b></div><div>Commands that start another process (such as "build' or "sign") could use a flag "--debug" which if set to true would output everything into stdout, otherwise would just print the actual command response (for example the build command would output a list of generated APKs). Default value for debug would be true.</div><div><div><br></div><div>WDYT?</div><span class="m_632358950256319480HOEnZb"><font color="#888888">-- <br><div class="m_632358950256319480m_-8609854409012702406gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Leonardo Rossetti<br></div><div><a href="mailto:lrossett@redhat.com" target="_blank">lrossett@redhat.com</a><br></div><div dir="ltr"><a href="tel:%2B55%2011%2099703%200621" value="+5511997030621" target="_blank">+55 11 99703 0621</a><br></div></div></div></div>
</font></span></div></div>
<br></div></div>______________________________<wbr>_________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailma<wbr>n/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div></div>
</div>