Günther Grill

Yes. This would be really helpful...

Showing the full dependency tree with gradle for the whole multi-module-project is quite simple: https://solidsoft.wordpress.com/2014/11/13/gradle-tricks-display-dependencies-for-all-subprojects-in-multi-project-build/ I usually pipe the output to a file and then do my investigations.

Yesterday I exactly had the same "issue" to find out where a dependency comes from. It would not only be interesting which project, but also in which configurations this dependency...

@jk1 what do you think of this? Would it improve the data model to have the information where a dependency comes from (which project and which configuration)?

Somehow it seems that this change is more fragile as the `read` version: ```bash function foo() { echo '1'; echo '2'; echo '3 | & ;'; echo '4'; } #...

@andyjack As mentioned in the other MR (maybe we move the discussion to here), I'm not convinced that we should abandon the `read` because of a reason we don't understand....

I'm closing this because the behavior issue is not related to this repository but is a bigger one. @andyjack I'm advising you to maybe reach our to stackoverflow or the...

Very interesting. I'd suggest to remove the need for the `read` (or any other variant of it) at all by changing the way how `gitprompt.sh` and `gitstatus.sh` interact. Currently the...

Yeah, while changing the communication I also stumbled across the `read` in the status script. Therefore I decided against sourcing but changed the output format of the status script so...

@benvaljean Could you maybe just change the `command cd ....` version for getting the script directory to what is proposed in the article you referenced and also proposed here https://stackoverflow.com/a/1482133...