-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
Ease new module creation by structuring modules as a tree #1666
Comments
Is the notion of parent sufficient? For example the postgresql module needs:
the oauth2 security module additionally requires spring mvc. Current errors are not very clear when trying to run a module without one of its prerequisites |
It should not be mandatory @antarus Supposing I created a new project, using my personal starter, I'd like to add PostgreSQL, without the requirement to use init, maven, java base. That's why I think building a tree can help but should not be mandatory. Each developer should know what he/she adds to the project when using each feature of JHLite |
@pascalgrimaud I completely agree that it shouldn't be mandatory. To be studied, but I think that with the new module system, we can maintain a list of files that each module adds / update. This could provide solutions to errors related to missing files for example. |
I'm adding a bounty on this as it's important to ease the use of module |
I think this is covered by #3022 |
I also think so. We can close this issue. Don't forget the bounty @DamnClin. |
Most of current modules have a parent -> child relationship (with some modules being root). The idea would be to enforce that with an interface to define a new module, here's a very incomplete idea:
This enforced parent -> child relationship will allow us to define a dependencies tree between modules those allowing:
I think this can be a great facilitator to create new modules!
The text was updated successfully, but these errors were encountered: