-
Notifications
You must be signed in to change notification settings - Fork 28
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
chore: fix the build problems #201
chore: fix the build problems #201
Conversation
…ate report, made PRs be not checked by sonar, fix AxonFramework#199
By the way - as usual for the PR with the build system, it might be needed some special attention for the steps used during the deployment/release procedure.... You can simulate these steps with sometimes, but in the end it might be tricky to debug and judge everything in advance. |
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.
Bunch of minor comments to cover before I'll approve.
Co-authored-by: Steven van Beelen <[email protected]>
Is there anything I can do here to progress further here? |
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.
LGTM... although I feel like we added a lot to our pom, sounds like this is the best way to fix this and split our tests!
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.
My concerns have been addressed, hence approving.
Thanks for the effort and patience here @zambrovski! Just went ahead and merged the changes after approval. |
Hi Folks,
as promised, my first attempt. I believe this is a good step towards a more stable and comfortable build. I added a new issue #200 to clean-up pom (especially duplicate declarations and places of version declarations) and focus in this PR on the build process only.
Things changed:
itest
)-Pcoverage-aggregate
)I believe if you like this structure, it might be worth to create a Axon-Community Extension Parent POM project - to simplify the setup of the extension and containing explanations of usage and setup. This would ease your handling of extensions, if they are at least having the same parent and you could move some of the POM magic up to it...