idea-plugin | IDEA Plugin for Kevoree Modeling | Autocomplete library

I'm developing a IDEA-Plugin. But after updating Intellij IDEA, the ide always show the warning that leading to the failure of code completion:

Background

I'm working on a plugin where users can create new files from an existing file template. The goal is to consolidate multiple file templates inside a new sub-menu under the primary file menu. If possible, I would like to create a nested sub-menu based on the template category. For example:

I have created a Maven (Java) project with three Maven subprojects, module1-3. module2 depends on module1, and module3 depends on both module2 and module1.

In the original build, module1 and module2 are common modules shared between multiple projects, and module3 is the end program which incorporates the other two. All the modules are ultimately compiled into an uber-jar to be distributed to the end customer.

From the command line this builds and runs just fine, but after importing to IntelliJ it's not able to properly resolve the local dependencies. It appears that IntelliJ uses the idea:idea goal for its importing, and running idea:idea on my testcase gives the following output, where it clearly has problems resolving despite ultimately giving a build success.

After importing the project into IntelliJ, all of the cross module references show as unresolved symbols.

Complete source code for this testcase is at: https://github.com/hutch31/maven-intellij-plugin-dep

Is there a missing/extra step required to get IntelliJ to figure out these references across Maven subprojects?

I am using Maven 3.6.3, and IntelliJ 2021.1. IntelliJ's integrated Maven is also version 3.6.3.

Edit: I have tried changing the order of the modules in the parent, and adding parent tags to the child modules, which did not affect the operation. I have updated the repository to reflect the state of the original code, in which module3 has a parent tag but module1 and module2 do not (as they are common code).

On the command line, I build and run using 'mvn clean test'. I have also added a Maven 'compile' configuration, which builds correctly despite the reported errors.

It is the first time I am trying to deploy to Maven Central repo and I cannot find an ultimate guide on how to do it.

No matter what I tried I get the same error:

Missing Signature: '/com/github/chameleontartu/amazon-mws-reports-maven/1.2.0-RC12/amazon-mws-reports-maven-1.2.0-RC12-javadoc.jar.asc' does not exist for 'amazon-mws-reports-maven-1.2.0-RC12-javadoc.jar'.

My open-source project with all code: Github repo.

GitHub Actions workflow .github/workflows/deploy.yml

While it was working fine yesterday. Today, I wasn't able to compile my project(spring-boot). I created a demo project to simulate the same issue that happened in my current project.

When I try to run the project using the run button It doesn't want to compile. Note all the errors from the failed compilation. Also, you can see that all dependencies are imported (see External Libraries):

I know I can run the app by typing mvn spring-boot:run in the terminal. But for some reason, I don't want to do that.

As you can see, this demo is a simple spring-boot project:

pom.xml:

I am currently learning about writing plugins for IntelliJ IDEs. I am especially interested in developing plugins for CLion. Therefore I would like to add support for c++ to my plugin project.

I read in the documentation how to develop plugins for c++.However the way it is described does not work for me. IntelliJ cannot resolve the dependency I want to add.

1. This part of the documentation explains that plugins may depend on other plugins, and how to add dependencies.

Plugin dependencies

Your plugin may depend on classes from other plugins. In this case, plugins can be either bundled, third-party or even your own. For instructions on how to express the dependencies, refer to Plugin Dependencies.

Your plugin should specify which product or products it will be compatible with (all IntelliJ-based IDEs, CLion only, or some subset). You can do that by declaring module dependencies with the tag in plugin.xml (see Plugin Compatibility with IntelliJ Products).

2. This part of the documentation explains which functionality is in which plugin. Each specific language seems to be a plugin. So developing a plugin which wants to parse c++, will depend on the c++ plugin.

Modules Specific to Functionality More specialized functionality is also delivered via modules and plugins in IntelliJ Platform-based products. For example, the com.intellij.modules.python module supports the Python language-specific functionality. If a plugin uses functionality from this module, such as Python-specific inspections and refactoring, it must declare a dependency on this module.

...

The following table lists(1) modules or built-in plugins that provide specific functionality, and the products that currently ship with them.

According to the table mentioned above I need to add com.intellij.modules.cidr.lang as dependency for c++. However when I add this line to my plugins.xml file the cidr.lang part is not recognized.

3. In this Stackoverflow question, which is about java plugin development, someone answered that there was recently a change, that one now also has to add the needed plugins to build.gradle. Furthermore there was a change tha java language support is now a buildin plugin.

I guess c++ support is now also a buildin plugin? But how can I add it?

So instead of