Fixed
Status Update
No update yet.
Comments
ta...@gmail.com
This would be awesome as a first-party support. I experimented and built this plugin to achieve this:
Kind of hacky but works :)
je...@google.com
je...@google.com
sp...@google.com
Re-opening this. I had marked it as a duplicate of namespace DSL, and this bug tracks the work to support libraries without source manifests.
Description
There are cases where a library module does not need anything in its manifest, and yet we force users to create a manifest just for the package name.
We should have an option to set the package name in the DSL and generate that simply manifest if the user chooses to do so. We could also have a more where the package name is based on a fixed prefix + a component based on the sub-project path so that it's always guaranteed to be unique without requiring people to think about it.
I'm flagging this for 4.2 but we should discuss this as part of our DSL/API work as this changes how we handle packageName in the API.