-
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
Move jib sync testdata to integration/examples
#4367
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4367 +/- ##
==========================================
- Coverage 71.78% 71.77% -0.02%
==========================================
Files 325 325
Lines 12594 12594
==========================================
- Hits 9041 9039 -2
- Misses 2978 2979 +1
- Partials 575 576 +1
Continue to review full report at Codecov.
|
} | ||
``` | ||
|
||
- You must include the `spring-boot-devtools` dependency at the `compile/implementation` scope, which is contrary to the configuration outlined in the [official docs](https://docs.spring.io/spring-boot/docs/current/reference/html/using-spring-boot.html#using-boot-devtools). Because jib is unaware of any special spring only configuration in your builds, we recommend using profiles to turn on or off devtools support in your jib container builds. |
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 Jib currently includes spring-boot-devtools
even if <optional>true
. (And we decided to take care of this using an extension.) Should we still advise to set <scope>compile
?
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 leave optional dependencies out. no?
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.
because it's not explicitly resolved to be a runtime dependency.
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.
oh about the scope, <compile>
is default isn't it?
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.
Ah, right, compile
is already the default. Then, the Spring Boot doc only adds <optional>true
, so I think this comment to add it as compile
doesn't apply.
And I think we include spring-boot-devtools
regardless of <optional>true
. (Would be good to double-check.)
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.
yeah you're right. I can say <!-- optional not necessary -->
bcdd9aa
to
731843d
Compare
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.
Mostly looks good to me.
- separate out maven/gradle skaffold files into skaffold-maven.yaml and skaffold-gradle.yaml - add detailed README.md to example - does NOT copy example to in `/examples` yet
849f023
to
8457c1e
Compare
and skaffold-gradle.yaml
/examples
yet