Epic created: https://issues.jboss.org/browse/AGDIGGER-9

On Tue, Oct 18, 2016 at 8:05 AM, Matthias Wessendorf <matzew@apache.org> wrote:
Great suggestions for us moving forward w/ 'abcd'

@Leo can you file an EPIC on AGDIGGER JIRA instance, where each of the four suggestions is its own issue ?

Thx,
Matthias

On Tue, Oct 18, 2016 at 11:57 AM, Ali Ok <aliok@redhat.com> wrote:
Log files
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".
+1.
Leave it to the user how to save the logs.


Build config file
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.
You mean in projects, right? Like travis.yml file.

Setup command 
A setup command to set default configurations "abcd setup" such as default android debug keystore config, android home path, cordova path, etc.
I think saving these things into ~/digger-config.yml would be great.

+1 on the others too.
 
Awesome suggestions Leonardo!


On Tue, Oct 18, 2016 at 12:04 PM, Leonardo Rossetti <lrossett@redhat.com> wrote:
Hello,

I was thinking on some enhancements around the CLI usage:

Log files
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".

Setup command
A setup command to set default configurations "abcd setup" such as default android debug keystore config, android home path, cordova path, etc.

Build config file
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.

Debug flag
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.

WDYT?
--

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Leonardo Rossetti
lrossett@redhat.com
+55 11 99703 0621