It seems like one way to handle command line parameters could be to do named injection.
So you would annotate with a name something like --foo And then you would just modify your bindings to inject that parameter but get the value from the command line arguments. But that would be very simple command line handling. It wouldn't support complex command line apps. Then there are systems like Airline: https://github.com/airlift/airline ... so it seems maybe a combination of the two would make a great way to build command line applications. You would get dependency injection, and get command line argument handling. How have other people handled this? I'd rather not re-invent the wheel here if there's a "best practice" way of doing this. -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. To view this discussion on the web visit https://groups.google.com/d/msgid/google-guice/4c2fbd69-46d9-4c5b-b253-b19bef882214%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
