redhat-developer / redhat-developer/vscode-java
Is there any plan to support maven multiple module project?
Open
Nobody has claimed this yet.
Maven
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Can not auto detect source code in sub module. Even if I add the source folder manually, the dependency packages still can not be found.
Parent pom:
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.2.1.RELEASE</version>
<relativePath />
</parent>
<groupId>net.jaggerwang</groupId>
<artifactId>spring-cloud-in-practice</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>
<name>spring-cloud-in-practice</name>
<description>Spring cloud in practice</description>
<properties>
<java.version>11</java.version>
<graphql-starter.version>6.0.0</graphql-starter.version>
<guava.version>28.1-jre</guava.version>
<scip-library.version>1.0-SNAPSHOT</scip-library.version>
</properties>
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
...
</dependencies>
<modules>
<module>spring-cloud-in-practice-library</module>
<module>spring-cloud-in-practice-user</module>
<module>spring-cloud-in-practice-post</module>
<module>spring-cloud-in-practice-file</module>
<module>spring-cloud-in-practice-stat</module>
<module>spring-cloud-in-practice-metric</module>
</modules>
</project>
One of sub module pom:
<?xml version="1.0" ?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>net.jaggerwang</groupId>
<artifactId>spring-cloud-in-practice</artifactId>
<version>1.0-SNAPSHOT</version>
</parent>
<groupId>net.jaggerwang</groupId>
<artifactId>spring-cloud-in-practice-user</artifactId>
<version>1.0-SNAPSHOT</version>
<name>spring-cloud-in-practice-user</name>
<description>Spring cloud in practice user service</description>
<properties>
<start-class>net.jaggerwang.scip.api.ScipUserApplication</start-class>
</properties>
<dependencies>
<dependency>
<groupId>net.jaggerwang</groupId>
<artifactId>spring-cloud-in-practice-library</artifactId>
<version>${scip-library.version}</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
</plugin>
<plugin>
<groupId>com.mysema.maven</groupId>
<artifactId>apt-maven-plugin</artifactId>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>process</goal>
</goals>
<configuration>
<outputDirectory>target/generated-sources/java</outputDirectory>
<processor>com.querydsl.apt.jpa.JPAAnnotationProcessor</processor>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
Environment
- Operating System: macOS
- JDK version: 11
- Visual Studio Code version: 1.41.0
- Java extension version: 0.8.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Reproduce the issue with the parent pom.xml and submodule pom.xml shown, using the stated macOS, JDK 11, VS Code 1.41.0, and Java extension 0.8.1 environment. Done means sources in Maven submodules are detected automatically and their dependency packages resolve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot, vscode
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100