Redesign compose task
See original GitHub issueCompose task should be redesigned.
Too much things are done in configuration phase, like reading vault filter files to populate compose in-memory model used to produce assembly package.
As of inheriting from Gradle Zip task is good / elegant, easy to use … this should remain unchanged. But as of any spec configuration methods (from()
, into()
) must be called in configuration phase and close to such calls there are usually methods configuring in-memory model… all such computation need to be called on execution phase (postponed in consistent manner).
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (11 by maintainers)
Top Results From Across the Web
Todoist adopted Compose for Wear OS and increased its ...
Todoist completely rebuilt and redesigned its Wear OS application with Compose for Wear OS, improving both the user and developer experience ...
Read more >Website Redesign Project Plan: How-To Guide with Steps
At the end of the evaluation stage, you compose a design brief – a document storing the details of your design project. It...
Read more >Gmail.com redesign leaks, looks pretty incredible - Ars Technica
Google Tasks exists today as a panel inside of Gmail and as an absolutely ancient website, but it seems like the neglected service...
Read more >Gmail redesign is rolling out for all users - Mashable
The company says it has used user feedback to make improvements, and the final version will now show for all Gmail users who...
Read more >How Good is Gmail 'Material You' Redesign? - UX Planet
Gmail has received a redesign that is much more simple. ... Google is also rolling out a stylish Material You redesign for Gmail...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
found working and easy workaround - https://github.com/gradle/gradle/issues/7958#issuecomment-604689214
also have it working nicely using software components which will cause that Gradle Metadata will be also included in publication
I have it working for built packages, now working on built bundles
approach with separate component named “aem” has unfortunately a bottleneck #673 which blocks me releasing 12.0.0 . asked Gradle for help on Slack