-
Notifications
You must be signed in to change notification settings - Fork 566
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
4.x: Introduces Pico Builder #5195
Conversation
pico/types/src/main/java/io/helidon/pico/types/DefaultTypedElementName.java
Outdated
Show resolved
Hide resolved
9122594
to
255832f
Compare
@@ -48,7 +48,7 @@ | |||
<module>api</module> | |||
<!-- <module>spi</module>--> | |||
<module>types</module> | |||
<!-- <module>builder</module>--> | |||
<module>builder</module> | |||
<!-- <module>config</module>--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming all these other modules will come in a future PR, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically, this PR is perfectly sound and clear, and that is why I'm approving it. Architecturally, I have some concerns about adding (mostly independent and potentially "sold" separately) "Pico" modules into the Helidon repo. This is also emphasized by the current naming that uses "Helidon Pico" as opposed to just "Helidon" for naming modules.
It would be nice to get others to review this PR as well.
No description provided.