Skip to content
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

Add a parent pom for IDEs #8

Merged
merged 1 commit into from
Feb 1, 2022
Merged

Conversation

agoncal
Copy link
Collaborator

@agoncal agoncal commented Feb 1, 2022

Fix #7

Copy link
Collaborator

@edeandrea edeandrea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't you have to also include a reference to the parent in each of the child modules? I'm not so much a Maven person so I don't know.

@edeandrea
Copy link
Collaborator

I'll also have to check whether or not this breaks the automation

https://github.com/quarkusio/quarkus-super-heroes/blob/main/scripts/generate-k8s-resources.sh#L45-L67

@edeandrea edeandrea merged commit 88ee48b into quarkusio:main Feb 1, 2022
@edeandrea
Copy link
Collaborator

Looks good. Thanks for the PR!

@agoncal
Copy link
Collaborator Author

agoncal commented Feb 1, 2022

We could include a reference to the parent pom in each child, but that couples the code a little bit. This way we "simulate" that all the projects are totally independent. I think it's better, it kind of says "you see, each microservice is totally independent from the others" ;o)

@edeandrea
Copy link
Collaborator

I like it and agree I didn't want to couple the projects together. I tested it locally before merging so I think we're good. CI is running now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Having a parent pom for IDEs
2 participants