-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflicts in ShowkaseMetadata from multiple modules when building the app #198
Comments
Thanks for the report. I will need to repro this on my end and will publish a fix as this is not intended behavior. |
@vinaygaba I would say this issue has the highest priority for our usage. It's preventing using the library in many modules. I don't want to rename our packages only because of Showkase. |
I think I should be able to fix this relatively quickly. Will try reproing it and publish a fix soon. I think I do understand where the problem lies 🤔 |
Great, thanks! |
@vinaygaba Could you please do a release with this change? |
Great, thanks! |
Hi, sorry for so many issues, but using the library in large mature app comes with challenges :)
I have two feature modules - it works when I enable Showkase for either of them. But if I enable it for both, build fails with this error:
I observe that the problem is with generated file
ShowkaseMetadata*
. It takes top-level package and names the file accordingly. This is our package structure:com.jll.jet.qraccess.view
->ShowkaseMetadataView
com.jll.jet.hid.view
->ShowkaseMetadataView
And that creates the conflict. If the package ends with something else (like
com.jll.jet.hid.view2
), it creates a different file (likeShowkaseMetadataView2
) and there is no issue.The text was updated successfully, but these errors were encountered: