Hi,
Yes, the workaround method you pointed out is easy.
When the number of imported scripts is relatively small, it's easy to manually create a closure-compiler command line that compiles them all.
When the number is large, it should still be relatively easy to create a script or something to pull the list out of your source code and create the closure-compiler command line.
Adding a feature like this into closure-compiler would require that we clearly define what use-cases we support,
which may be harder than you think, and then define appropriate command line options and determine how the feature will interact with lots of other things, etc.
These would definitely be open-source-only use-cases since we don't have any inside Google.
Past experience tells me that adding more open-source-only use-cases is not a good idea, because we cannot support them well.
They don't serve the open source community well, and they create a drag on our ability to improve support for our primary use-cases.
Sorry & best regards,
Bradford