You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #1135 raised a problem that should be avoided:
gradle is not able to handle modules with the same folder name.
e.g. there cannot be two modules like these (this case does not exist, just for example):
And this should be reflected to the artifact id published.
Related to this topic, module names should be coherent with the domain names in the codebase, e.g. a module regarding the AssetIndex should be called asset-index-sql and not assetindex-sql
Which Areas Would Be Affected?
folder structure, CI
Why Is the Feature Desired?
To avoid bugs like #1135, to have a cleaner structure
Solution Proposal
A check on the CI should be added, giving error on leaf module folder conflict
Type of Issue
cleanup
Checklist
assigned appropriate label?
Do NOT select a milestone or an assignee!
The text was updated successfully, but these errors were encountered:
Feature Request
Issue #1135 raised a problem that should be avoided:
gradle is not able to handle modules with the same folder name.
e.g. there cannot be two modules like these (this case does not exist, just for example):
So every "leaf" module folder should have an unique name, like:
And this should be reflected to the artifact id published.
Related to this topic, module names should be coherent with the domain names in the codebase, e.g. a module regarding the
AssetIndex
should be calledasset-index-sql
and notassetindex-sql
Which Areas Would Be Affected?
folder structure, CI
Why Is the Feature Desired?
To avoid bugs like #1135, to have a cleaner structure
Solution Proposal
A check on the CI should be added, giving error on leaf module folder conflict
Type of Issue
cleanup
Checklist
The text was updated successfully, but these errors were encountered: