-
Notifications
You must be signed in to change notification settings - Fork 3
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
Build action #3
base: main
Are you sure you want to change the base?
Build action #3
Conversation
<repository> | ||
<id>github</id> | ||
<name>GitHub Packages</name> | ||
<url>https://maven.pkg.github.com/tombueng/spring-otel-extended</url> |
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.
Needs to be adjusted!
working-directory: otel-javaagent-spring-extension | ||
steps: | ||
- uses: actions/checkout@v4 | ||
- name: Set up JDK 11 |
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.
Shuoldn't this be called 21?
@tombueng Thank you for your contribution first of all. Unexpected :) edit: added #4 as issue for this. |
SureAm 30.10.2024 13:34 schrieb Dominik Guhr ***@***.***>:
@DGuhr commented on this pull request.
In .github/workflows/maven-publish.yml:
+ release:
+ types: [created]
+
+jobs:
+ build:
+
+ runs-on: ubuntu-latest
+ permissions:
+ contents: read
+ packages: write
+ defaults:
+ run:
+ working-directory: otel-javaagent-spring-extension
+ steps:
+ - uses: ***@***.***
+ - name: Set up JDK 11
Shuoldn't this be called 21?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Not sure, but compiling with 21 for 11 should work. Will elaborate next days.Am 30.10.2024 13:38 schrieb Dominik Guhr ***@***.***>:
@tombueng Thank you for your contribution first of all. Unexpected :)
That said: The build is using jdk 21. This opens up a question: The reason why I did not add a build action in the first place (apart from me being lazy) is, that you have to build it yourself with the java version matching your applications' java version. So, when you run a JDK 11 java app, but build the extension with jdk 21, it won't work - see my notes in the README. So i think if we want to add a build/release step here, we should have at least a matrix build for, say, last three JDK LTE versions + current one, right? So it's not that simple. I'm happy to hear your thoughts about this, not at all against adding it, but if we add it, it should be right not just for one use case, but in general.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Please add a build action so we can download your extensoin from github.