Generate project Metadatafiles at project root

[kraabrsg]

Hi, we had a strange problem with imports of generated classes(not found with import). The project was initially started with eclipse, to solve the problem we had to add classpath in eclipse. Now we have done an extensions which loads this extension and M$ debug extensions, takes care of writing launch settings in the workspace for debugging, providing maven commands and so on....

We now want to check if the ".classpath" file has this two entries, if not add it.

After turning the setting
java.import.generatesMetadataFilesAtProjectRoot

on nothing was generated (or better said how to trigger it) ???
We assumed to find the files ".project" , ".classpath" and so on in the project root.

We are using quarkus and maven (and also java batch for mainframe).

Common project structure:
REPO -> REPO-BUSINESS -> REPO-BUSINESS-SERVICES
-> REPO-BUSINESS-CONSUMEND-CLIENTS

The ".classpath" file is in the *-SERVICES" folder

1.) how to trigger the generation of the metadatafiles at project root (activating the settings does not seem to do anything)
2.) in the classpath file the path is relative, so this is taken into consideration ?

Thank you!

[snjeza]

After turning the setting
java.import.generatesMetadataFilesAtProjectRoot
on nothing was generated (or better said how to trigger it) ???
We assumed to find the files ".project" , ".classpath" and so on in the project root.

@kraabrsg You can try to set

"java.import.generatesMetadataFilesAtProjectRoot": true,

and Clean the workspace directory

[kraabrsg]

Hi @snjeza i had allready set this setting to true
java.import.generatesMetadataFilesAtProjectRoot

additionally cleaning the workspace directory does not help either.

When should the generation be triggered ?

Thanks!

[snjeza]

When should the generation be triggered ?

They should generated during the importing.
Are there pom.xml, build.gradle or build.gradle.kts in your workspace?
Java LS should generate .project and .classpath in a directory that contains pom.xml, build.gradle or build.gradle.kts.
Could you show your server log?

[kraabrsg]

Hi @snjeza

Are there pom.xml, build.gradle or build.gradle.kts in your workspace?

Yes we have several pom.xml in our project (maven quarkus project)

Workspace/REPO structure

Workspace -> several folders -> REPO (main pom.xml)
Workspace -> several folders -> REPO -> REPO-BUSINESS (business pom.xml)
Workspace -> several folders -> REPO -> REPO-BUSINESS -> REPO-BUSINESS-SERVICES (service pom.xml)
Workspace -> several folders -> REPO -> REPO-BUSINESS -> REPO-BUSINESS-CONSUMED-CLIENTS (clients pom.xml)

Java LS should generate .project and .classpath in a directory that contains pom.xml, build.gradle or build.gradle.kts.

When renaming the mentioned files and restart vscode the following happened (files were created if not exists):

• main pom.xml: ".project" file is generated
• business pom.xml: ".project" file is generated
• service pom.xml: ".project" file is generated
• clients pom.xml: ".project" / ".classpath" file is generated

but in the service pom.xml path no ".classpath" is generated...(once this file was missing entries that caused trouble because of imports that were not found, had to add them in eclipse, and checking this .classpath file with our own extension ist the goal) -> after a clean of the language server the files were generated

Could you show your server log?

i am not sure if i am allowed..

Thanks!