-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add jakarta.inject-api / jakarta.annotation-api to isv build #1436
Add jakarta.inject-api / jakarta.annotation-api to isv build #1436
Conversation
/request-license-review |
License review requests: After all reviews have concluded, re-run the license-vetting check from the Github Actions web-interface to update its status. Workflow run (with attached summary files): |
FYI, ignore the license problem. It's unrelated to your change. |
CI is fine so lets go for it... |
This is still not fixed as the the same symbolic name jakarta.annotation-api is used for both versions which confuses the handcrafted script. |
Do you mean Tycho extra requirements or can you reference the script in question? |
@akurtakov another question: Can we somehow see this error in this build here as well? |
@laeubi do you mean logs from https://download.eclipse.org/eclipse/downloads/drops4/I20231012-1800/logs.php#javadoc ? |
I haven't looked enough into how can we make the jenkins build fail if javadoc build fails if this is the question. |
I have now created: |
@mickaelistria I mean what ever fails and needs fixing here :-) |
No description provided.