SoFunction
Updated on 2025-04-14

The reason and solution for not targeting in idea packaging

Reasons for the idea package not appearing in target

maven code block

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns:xsi="http:///2001/XMLSchema-instance"
         xmlns="/POM/4.0.0"
         xsi:schemaLocation="/POM/4.0.0 /xsd/maven-4.0.">
    <parent>
        <groupId></groupId>
        <artifactId>camas-java</artifactId>
        <version>1.0.0</version>
    </parent>
    <modelVersion>4.0.0</modelVersion>
 
    <artifactId>camas</artifactId>
    <packaging>jar</packaging>
 
    <name>${}</name>
    <description>
        rear end Server Main project,By introducing the need module-xxx Dependence。
    </description>
    <url>/YunaiV/ruoyi-vue-pro</url>
 
    <dependencies>
        <!-- TODO taro:Multi-module -->
        <dependency>
            <groupId></groupId>
            <artifactId>module-system-impl</artifactId>
            <version>1.0.0</version>
        </dependency>
        <!-- Default import module-bpm-impl-flowable accomplish,Can be replaced by module-bpm-impl-activiti accomplish-->
        <dependency>
            <groupId></groupId>
            <artifactId>module-bpm-impl-flowable</artifactId>
            <version>1.0.0</version>
        </dependency>
 
        <!-- spring boot Dependencies required for configuration -->
        <dependency>
            <groupId></groupId>
            <artifactId>spring-boot-configuration-processor</artifactId>
            <optional>true</optional>
        </dependency>
 
        <!-- Service guarantee related -->
        <dependency>
            <groupId></groupId>
            <artifactId>spring-boot-starter-protection</artifactId>
        </dependency>
 
    </dependencies>
 
    <build>
        <!-- Set up the built jar Package name -->
        <finalName>${}</finalName>
        <plugins>
            <!-- Pack -->
            <plugin>
                <groupId></groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
                <version>2.5.10</version> <!-- if  Version modification,Then we need to modify it here -->
                <configuration>
                    <fork>true</fork>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>repackage</goal> <!-- Will be introduced jar Into it -->
                        </goals>
                    </execution>
                </executions>
            </plugin>
            <plugin>
                <groupId></groupId>
                <artifactId>mybatis-generator-maven-plugin</artifactId>
                <version>1.3.5</version>
                <configuration>
                    <configurationFile>src/main/resources/generator/</configurationFile>
                    <verbose>true</verbose>
                    <overwrite>true</overwrite>
                </configuration>
            </plugin>
        </plugins>
    </build>
 
</project>

Packaging type

Using maven for module division and management, there is generally a parent project. In addition to GAV (groupId, artifactId, version) of the pom file, it must be configured. Another important attribute is the package packaging type. The package of all parent projects is pom. Packaging is the jar type by default. If no configuration is made, maven will make the project into a jar package.

As a parent project, there is another important property, that is, modules, refer to all child projects of the project through the modules tag. When building the parent project, a build order will be sorted out according to the interdependence of the submodules, and then build in turn.

Summarize

The above is personal experience. I hope you can give you a reference and I hope you can support me more.