-
Notifications
You must be signed in to change notification settings - Fork 352
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
new builder #223
new builder #223
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.
Sounds really good. Just a note about the Camel version..
pkg/builder/builder_steps.go
Outdated
//TODO: camel version should be retrieved from an external request or provided as static version | ||
GroupID: "org.apache.camel", | ||
ArtifactID: "camel-bom", | ||
Version: "2.22.1", |
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 think we switched to "2.22.2"
return request.Steps[i].Phase() < request.Steps[j].Phase() | ||
}) | ||
|
||
for _, step := range request.Steps { |
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.
So this means that the phases are no more interleaved, so a full build needs to be completed before a new one is started.
It solves also the problem of the initial contexts not being based one on another sometimes (e.g. randomly the Groovy context is not based on the JVM one)
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 see you've added this to the next things to do, but I'm not sure if it helps using the old strategy...
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.
Yes a full build is needed now, it is much simpler and it avoid clashes as you said. About parallel build, yeah, I'm not sure they are needed, so let's keep it simple for the moment.
c1cc947
to
82133ed
Compare
@nicolaferraro fixed, should bre ready to merge |
This PR is aimed to introduce a flexible builder to accommodate different build needs without having to introduces conditional paths in the current build manager.
Next step are: