redhat-developer / redhat-developer/vscode-java
Is there any plan to support maven multiple module project?
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 2.3k
- Fork
- 546
- Merge medio
- 20h 1m
- PR unite (30g)
- 11
Descrizione
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
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Non vengono indicati file del repository né test. Riproduci il problema con il parent pom.xml e il submodule pom.xml mostrati, utilizzando l’ambiente specificato con macOS, JDK 11, VS Code 1.41.0 e Java extension 0.8.1. Il lavoro è completato quando le origini nei sottomoduli Maven vengono rilevate automaticamente e i relativi pacchetti delle dipendenze vengono risolti.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, spring-boot, vscode
- Ambito
- build-system, tooling
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100