Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

DRAFT: Serena Java init_language_server_manager fails for custom gradle setup.#835

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
tkruse wants to merge5 commits intooraios:main
base:main
Choose a base branch
Loading
fromtkruse:main

Conversation

@tkruse
Copy link

@tkrusetkruse commentedDec 12, 2025
edited
Loading

In my company's dev setup serena fails to run the taskinit_language_server_manager due to

org.gradle.api.plugins.UnknownPluginException: Plugin [id: '...'] was not found in any of the following sources

The issue is that the sources for our custom plugins are setup in gradlew wrapper.

This PR removes that as a PoC (without consideration of how this breaks for other projects).

The next problem was that in my company, a gradle plugin checks on every gradle run that an approved JRE is being used, while Serena/JDTLS apparently use a fixed JRE. That could be resolved withls_specific_settings inserena_config.yml. The fork for this MR allowed to start serena successfully.

This MR is not intended to be merged as is, but only to demonstrate a minimal mitigation that works only within my company.

Thibault Kruse added5 commitsDecember 12, 2025 12:31
- Check if 'java' key exists in gradle_settings before accessing it- This fixes crash on JDTLS initialization when gradle_java_home is configured- Refs: eclipse_jdtls.py:740
- Document Gradle/JDTLS integration fixes- Show configuration options in ~/.serena/serena_config.yml- Keep note concise and abstract
@opcode81
Copy link
Contributor

opcode81 commentedDec 12, 2025
edited
Loading

Hi Thibault, long time no see!

So is the purpose of this PR to provide a basis for a general mitigation strategy that shall be implemented independently, or do you intend to ultimately propose a PR that could be merged?

Either way, thanks for trying out Serena and for pointing out the issue.

@tkruse
Copy link
Author

tkruse commentedDec 15, 2025
edited
Loading

Hi Dominik (I was surprised when I realized this project is by you),

my first intent was to provide an immediate github fork of Serena that can be installed and used by others in my company, and to get feedback.

In the medium term of course I would like to delete my fork again once we found a way to run the JDTLS by Serena with gradle projects in my company, e.g. by merging changes such as those in this MR (or a better fix).

At the least I think we would need a way to configure the gradlew wrapper and JRE behavior, and this MR could show a way, though I am not sure whether the MR is good/minimal, I did not have time to polish what the AI produced.
But I am unclear on why gradle is called at all, and with what tasks. Potentially there is another mitigation whether the call is not made or made differently.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@tkruse@opcode81

[8]ページ先頭

©2009-2025 Movatter.jp