-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fix camunda-spin-bom import in camunda-only-bom #4605 #4628
Conversation
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.
@cachescrubber
On first glance, changes look good. So please apply the same for commons, connect, that will be great.
I triggered our CI with the changes and I see the following error, could you please check what might be wrong?
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project camunda-spin-bom: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter
Command that is executed in root:
mvn clean source:jar deploy source:test-jar -Pdistro,distro-ce,distro-wildfly,distro-webjar,h2-in-memory`
Hi @yanavasileva - I assigned |
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.
👍 Changes look good to me know. Could you please extend the PR to fix commons and connect too?
please review camunda-commons-bom. I think I'll get connect-box done at until tomorrow. |
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 need to do some testing but overall looks good for now. 👍
Testing was successful. I will merge the changes later today. |
Fix camunda-spin-bom import in camunda-only-bom #4605
Fixes #4605
It was necessary to remove the parent from
camunda-spin-bom
, because it would introduce a cyclic import of thecamunda-bom
which would in turn importcamunda-spin-bom
....camunda-spin-bom
currently is without parent. Should it be necessary I would suggest to usecamunda-bpm-release-parent
.