Joshua Gleitze
Joshua Gleitze
Once again: I am sorry that I am currently not able to participate more in atrium’s development in general, and this discussion in specific. --- I think we have come...
Regarding the groups: We could probably find even better names. Maybe the group’s purpose will always be clear from the context, then `InvisibleGroup` would be enough. Or, if not, `InvisibleReportGroup`...
One example of what I think can be improved: The main build file declares certain types of projects: ```Groovy def commonProjects = getCommonProjects() def jsProjects = getJsProjects() def jvmProjects =...
> I also planned to factor out some logic into an own plugin Factoring out logic is always good! Factoring out configuration is bad, from my point of view. >...
Why is `atrium-scala2` not part of the `atrium` build?
Cool thing! If this works well, maybe we can address this issue one step at a time.
This is unfortunate. A big bang redo of the build logic would surely be a big improvement, but is also difficult and involved to pull off.
If we actually do this, can we please also align the information in parentheses? I feel that this would make it easier for me to scan the output.
> changed also for the example I’d expect the `(readme …` parentheses also to be indented like the others are. I think the rationale is that I usually do not...
Would it make sense to right-align the description texts? Like this: ``` expected that subject: "foo bar" ◆ equals: "baz" ``` instead of: ``` expected that subject: "foo bar" ◆ ...