Summary of Maven, 2021 Ali Java advanced interview questions

        <!-- The role of project contributors in the project. The role element describes various roles -->
        <roles>
            <role> Project Manager </role>
            <role> Architect </role>
        </roles>

        <!-- The time zone of the project contributor, -11 An integer in the range from to 12. -->
        <timezone></timezone>

        <!-- Project contributor attributes, such as how to handle instant messages, etc -->
        <properties>
            <dept> No </dept>
        </properties>
    </contributor>
</contributors>

<!-- This element describes all of the project License List. You should list only for this item license List, do not list dependent items license List.
     If more than one is listed license,Users can choose one of them instead of accepting all of them license.  -->
<licenses>
    <!-- Describes the of the project license,Used to build the project web Site license Page, some other reports and validation This element is also used. -->
    <license>
        <!-- license Used as a legal name -->
        <name> Apache 2 </name>

        <!-- Official license Text page URL -->
        <url> http://www.baidu.com/banseon/LICENSE-2.0.txt </url>

        <!-- Main methods of project distribution:
                repo,Can from Maven Library Download
                manual, Users must manually download and install dependencies -->
        <distribution> repo </distribution>

        <!-- about license Supplementary information for -->
        <comments> A business-friendly OSS license </comments>
    </license>
</licenses>

<!-- SCM(Source Control Management)Tags allow you to configure your code base for Maven web Site and other plug-ins. -->
<scm>
    <!-- SCM of URL,Should URL Describes the version library and how to connect to it. For details, please see SCMs Provided URL Format and list. The connection is read-only. -->
    <connection>
        scm:svn:http://svn.baidu.com/banseon/maven/banseon/banseon-maven2-trunk(dao-trunk)
    </connection>

    <!-- For developers, similar connection Element. That is, the connection is not only read-only -->
    <developerConnection>
        scm:svn:http://svn.baidu.com/banseon/maven/banseon/dao-trunk
    </developerConnection>

    <!-- The label of the current code, which defaults to in the development phase HEAD -->
    <tag></tag>

    <!-- Browsable to the item SCM Library (e.g ViewVC perhaps Fisheye)of URL.  -->
    <url> http://svn.baidu.com/banseon </url>
</scm>

<!-- Describes various attributes of the organization to which the project belongs. Maven Generated documents -->
<organization>
    <!-- Full name of the organization -->
    <name> demo </name>

    <!-- Organization home page URL -->
    <url> http://www.baidu.com/banseon </url>
</organization>

<!-- Information needed to build the project -->
<build>
    <!-- This element sets the project source code directory. When building a project, the construction system will compile the source code in the directory. This path is relative
         to pom.xml The relative path of the. -->
    <sourceDirectory></sourceDirectory>

    <!-- This element sets the project script source directory, which is different from the source directory: in most cases, the contents of this directory will be changed
         Is copied to the output directory(Because scripts are interpreted, not compiled).  -->
    <scriptSourceDirectory></scriptSourceDirectory>

    <!-- This element sets the source code directory used by the project unit test. When testing the project, the build system will compile the source code in the directory.
         The path is relative to pom.xml The relative path of the. -->
    <testSourceDirectory></testSourceDirectory>

    <!-- Compiled application class Directory where files are stored. -->
    <outputDirectory></outputDirectory>

    <!-- Compiled tests class Directory where files are stored. -->
    <testOutputDirectory></testOutputDirectory>

    <!-- Use a series of build extensions from the project -->
    <extensions>
        <!-- Describes the build extension used. -->
        <extension>
            <!-- Build extended groupId -->
            <groupId></groupId>

            <!-- Build extended artifactId -->
            <artifactId></artifactId>

            <!-- Build extended version -->
            <version></version>
        </extension>
    </extensions>

    <!-- When the project has no specified objectives( Maven2 Default value when called phase) -->
    <defaultGoal></defaultGoal>

    <!-- This element describes the path list of all resources related to the project, such as the property file related to the project. These resources are included in
         In the final package file. -->
    <resources>
        <!-- This element describes all resource paths related to the project or test -->
        <resource>
            <!-- Describes the target path of the resource. The path is relative target/classes Directory (e.g ${project.build.outputDirectory}). 
                 For example, if you want resources in a specific package(org.apache.maven.messages),You must set the element to
                org/apache/maven/messages. However, if you just want to put resources into the source directory structure, you don't need this configuration. -->
            <targetPath></targetPath>

            <!-- Whether to use parameter value instead of parameter name. Parameter value is taken from properties Element or attribute configured in the file filters element
                 Listed in. -->
            <filtering></filtering>

            <!-- Describes the directory where resources are stored. The path is relative POM route -->
            <directory></directory>

            <!-- Contains a list of modes, such as**/*.xml. -->
            <includes>
                <include></include>
            </includes>

            <!-- List of excluded modes, for example**/*.xml -->
            <excludes>
                <exclude></exclude>
            </excludes>
        </resource>
    </resources>

    <!-- This element describes all the resource paths related to the unit test, such as the property files related to the unit test. -->
    <testResources>
        <!-- This element describes all resource paths related to the test. See build/resources/resource Description of the element -->
        <testResource>
            <!-- Describes the target path of test related resources. The path is relative target/classes Directory (e.g ${project.build.outputDirectory}). 
                 For example, if you want resources in a specific package(org.apache.maven.messages),You must set the element to
                org/apache/maven/messages. However, if you just want to put resources into the source directory structure, you don't need this configuration. -->
            <targetPath></targetPath>

            <!-- Whether to use parameter value instead of parameter name. Parameter value is taken from properties Element or attribute configured in the file filters element
                 Listed in. -->
            <filtering></filtering>

            <!-- Describes the directory where test related resources are stored. This path is relative POM route -->
            <directory></directory>

            <!-- Contains a list of modes, such as**/*.xml. -->
            <includes>
                <include></include>
            </includes>

            <!-- List of excluded modes, for example**/*.xml -->
            <excludes>
                <exclude></exclude>
            </excludes>
        </testResource>
    </testResources>

    <!-- The directory where all files generated by the build are stored -->
    <directory></directory>

    <!-- The file name of the generated component. The default value is ${artifactId}-${version}.  -->
    <finalName></finalName>

    <!-- When filtering List of filter property files used when the switch is on -->
    <filters></filters>

    <!-- Default plug-in information that can be referenced by subprojects. The plug-in configuration item will not be resolved or bound to the life cycle until it is referenced. Any native of a given plug-in
         The local configuration will overwrite the configuration here -->
    <pluginManagement>
        <!-- List of plug-ins used. -->
        <plugins>
            <!-- plugin The element contains the information needed to describe the plug-in. -->
            <plugin>
                <!-- The plug-in is in the warehouse group ID -->
                <groupId></groupId>

                <!-- The plug-in is in the warehouse artifact ID -->
                <artifactId></artifactId>

                <!-- The version (or version range) of the plug-in being used -->
                <version></version>

                <!-- Download from this plugin Maven Extensions (such as packaging and type processors) can only be downloaded if they really need to be downloaded for performance reasons
                     Element is set to enabled.  -->
                <extensions>true/false</extensions>

                <!-- The configuration of a set of goals is performed during the build lifecycle. Each goal may have a different configuration. -->
                <executions>
                    <!-- execution Element contains the information required for plug-in execution -->
                    <execution>
                        <!-- The identifier of the execution target, which is used to identify the target in the construction process or match the execution target to be merged in the inheritance process -->
                        <id></id>

                        <!-- The construction lifecycle phase of the target is bound. If omitted, the target will be bound to the default phase configured in the source data -->
                        <phase></phase>

                        <!-- Configured execution target -->
                        <goals></goals>

                        <!-- Is the configuration propagated to the child POM -->
                        <inherited>true/false</inherited>

                        <!-- As DOM Object configuration -->
                        <configuration></configuration>
                    </execution>
                </executions>

                <!-- Additional dependencies required for the project to introduce plug-ins -->
                <dependencies>
                    <!-- See dependencies/dependency element -->
                    <dependency>
                    </dependency>
                </dependencies>

                <!-- Is any configuration propagated to subprojects -->
                <inherited>true/false</inherited>

                <!-- As DOM Object configuration -->
                <configuration></configuration>
            </plugin>
        </plugins>
    </pluginManagement>

    <!-- List of plug-ins used by the project. -->
    <plugins>
        <!-- plugin The element contains the information needed to describe the plug-in. -->
        <plugin>
            <!-- The plug-in is in the warehouse group ID -->
            <groupId></groupId>

            <!-- The plug-in is in the warehouse artifact ID -->
            <artifactId></artifactId>

            <!-- The version (or version range) of the plug-in being used -->
            <version></version>

            <!-- Download from this plugin Maven Extensions (such as packaging and type processors) can only be downloaded if they really need to be downloaded for performance reasons
                 Element is set to enabled.  -->
            <extensions>true/false</extensions>

            <!-- The configuration of a set of goals is performed during the build lifecycle. Each goal may have a different configuration. -->
            <executions>
                <!-- execution Element contains the information required for plug-in execution -->
                <execution>
                    <!-- The identifier of the execution target, which is used to identify the target in the construction process or match the execution target to be merged in the inheritance process -->
                    <id></id>

                    <!-- The construction lifecycle phase of the target is bound. If omitted, the target will be bound to the default phase configured in the source data -->
                    <phase></phase>

                    <!-- Configured execution target -->
                    <goals></goals>

                    <!-- Is the configuration propagated to the child POM -->
                    <inherited>true/false</inherited>

                    <!-- As DOM Object configuration -->
                    <configuration></configuration>
                </execution>
            </executions>

            <!-- Additional dependencies required for the project to introduce plug-ins -->
            <dependencies>
                <!-- See dependencies/dependency element -->
                <dependency>
                </dependency>
            </dependencies>

            <!-- Is any configuration propagated to subprojects -->
            <inherited>true/false</inherited>

            <!-- As DOM Object configuration -->
            <configuration></configuration>
        </plugin>
    </plugins>
</build>

<!-- Project build in column profile,If activated, the build process is modified -->
<profiles>
    <!-- Activate a build process based on environment parameters or command line parameters -->
    <profile>
        <!-- Unique identifier of the build configuration. Used both for command line activation and for merging objects with the same identifier on inheritance profile.  -->
        <id></id>

        <!-- Automatic trigger profile Conditional logic. Activation yes profile Open the key. profile Its power comes from its ability to
             Automatically use certain values in certain environments; these environments pass activation Element. activation element
             Biotin is not activated profile The only way. -->
        <activation>
            <!-- profile Flag of whether to activate by default -->
            <activeByDefault>true/false</activeByDefault>

            <!-- When matched jdk Detected, profile Activated. For example, 1.4 activation JDK1.4,1.4.0_2,and!1.4 Activate all versions
                 Not with 1.4 initial  JDK.  -->
            <jdk>jdk Version, e.g:1.7</jdk>

            <!-- When a matching operating system attribute is detected, profile Activated. os Element can define some operating system related attributes. -->
            <os>
                <!-- activation profile The name of the operating system -->
                <name> Windows XP </name>

                <!-- activation profile Family of operating systems(as 'windows') -->
                <family> Windows </family>

                <!-- activation profile Operating system architecture -->
                <arch> x86 </arch>

                <!-- activation profile Operating system version of -->
                <version> 5.1.2600 </version>
            </os>

            <!-- If Maven A property has been detected whose value can be POM Passed in ${name}Reference), which has the corresponding name and value, Profile
                 Will be activated. If the value field is empty, the existing attribute name field is activated profile,Otherwise, the match is case sensitive
                 Attribute value field -->
            <property>
                <!-- activation profile The name of the property -->
                <name> mavenVersion </name>

                <!-- activation profile The value of the property -->
                <value> 2.0.3 </value>
            </property>

            <!-- Provide a file name to activate by detecting the presence or absence of the file profile. missing Check whether the file exists, and activate if it does not exist
                 profile. on the other hand, exists The file is checked for existence and activated if it exists profile.  -->
            <file>
                <!-- Activate if the specified file exists profile.  -->
                <exists> /usr/local/hudson/hudson-home/jobs/maven-guide-zh-to-production/workspace/ </exists>

                <!-- Activate if the specified file does not exist profile.  -->
                <missing> /usr/local/hudson/hudson-home/jobs/maven-guide-zh-to-production/workspace/ </missing>
            </file>
        </activation>

        <!-- Information needed to build the project. See build element -->
        <build>
            <defaultGoal />
            <resources>
                <resource>
                    <targetPath></targetPath>
                    <filtering></filtering>
                    <directory></directory>
                    <includes>
                        <include></include>
                    </includes>
                    <excludes>
                        <exclude></exclude>
                    </excludes>
                </resource>
            </resources>
            <testResources>
                <testResource>
                    <targetPath></targetPath>
                    <filtering></filtering>
                    <directory></directory>
                    <includes>
                        <include></include>
                    </includes>
                    <excludes>
                        <exclude></exclude>
                    </excludes>
                </testResource>
            </testResources>
            <directory></directory>
            <finalName></finalName>
            <filters></filters>
            <pluginManagement>
                <plugins>
                    <!-- See build/pluginManagement/plugins/plugin element -->
                    <plugin>
                        <groupId></groupId>
                        <artifactId></artifactId>
                        <version></version>
                        <extensions>true/false</extensions>
                        <executions>
                            <execution>
                                <id></id>
                                <phase></phase>
                                <goals></goals>
                                <inherited>true/false</inherited>
                                <configuration></configuration>
                            </execution>
                        </executions>
                        <dependencies>
                            <!-- See dependencies/dependency element -->
                            <dependency>
                            </dependency>
                        </dependencies>
                        <goals></goals>
                        <inherited>true/false</inherited>
                        <configuration></configuration>
                    </plugin>
                </plugins>
            </pluginManagement>
            <plugins>
                <!-- See build/pluginManagement/plugins/plugin element -->
                <plugin>
                    <groupId></groupId>
                    <artifactId></artifactId>
                    <version></version>
                    <extensions>true/false</extensions>
                    <executions>
                        <execution>
                            <id></id>
                            <phase></phase>
                            <goals></goals>
                            <inherited>true/false</inherited>
                            <configuration></configuration>
                        </execution>
                    </executions>
                    <dependencies>
                        <!-- See dependencies/dependency element -->
                        <dependency>
                        </dependency>
                    </dependencies>
                    <goals></goals>
                    <inherited>true/false</inherited>
                    <configuration></configuration>
                </plugin>
            </plugins>
        </build>

        <!-- Modules (sometimes called subprojects) are built as part of the project. Each module element listed points to the directory of the module
             Relative path -->
        <modules>
            <!--Subproject relative path-->
            <module></module>
        </modules>

        <!-- Discover the list of dependent and extended remote warehouses. -->
        <repositories>
            <!-- See repositories/repository element -->
            <repository>
                <releases>
                    <enabled><enabled>
                    <updatePolicy></updatePolicy>
                    <checksumPolicy></checksumPolicy>
                </releases>
                <snapshots>
                    <enabled><enabled>
                    <updatePolicy></updatePolicy>
                    <checksumPolicy></checksumPolicy>
                </snapshots>
                <id></id>
                <name></name>
                <url></url>
                <layout></layout>
            </repository>
        </repositories>

        <!-- Discover a list of remote repositories for plug-ins that are used to build and report -->
        <pluginRepositories>
            <!-- Contains information about the need to connect to the remote plug-in repository.See repositories/repository element -->
            <pluginRepository>
                <releases>
                    <enabled><enabled>
                    <updatePolicy></updatePolicy>
                    <checksumPolicy></checksumPolicy>
                </releases>
                <snapshots>
                    <enabled><enabled>
                    <updatePolicy></updatePolicy>
                    <checksumPolicy></checksumPolicy>
                </snapshots>
                <id></id>
                <name></name>
                <url></url>
                <layout></layout>
            </pluginRepository>
        </pluginRepositories>

        <!-- This element describes all dependencies related to the project. These dependencies constitute each link in the project construction process. They are automatically defined from the project
             Download from the warehouse. For more information, see project dependency mechanism. -->
        <dependencies>
            <!-- See dependencies/dependency element -->
            <dependency>
            </dependency>
        </dependencies>

        <!-- Disapprove of using. Now? Maven Ignore this element. -->
        <reports></reports>

        <!-- This element includes specifications for generating reports using the report plug-in. When the user executes“ mvn site",These reports will run. You can see them in the page navigation bar
             Links to all reports. See reporting element -->
        <reporting></reporting>

        <!-- See dependencyManagement element -->
        <dependencyManagement>
            <dependencies>
                <!-- See dependencies/dependency element -->
                <dependency>
                </dependency>
            </dependencies>
        </dependencyManagement>

        <!-- See distributionManagement element -->
        <distributionManagement>
        </distributionManagement>

        <!-- See properties element -->
        <properties />
    </profile>
</profiles>

<!-- Modules (sometimes referred to as subprojects) are built as part of the project. Each module element listed is a relative path to the directory of the module -->
<modules>
    <!--Subproject relative path-->
    <module></module>
</modules>

<!-- Discover the list of dependent and extended remote warehouses. -->
<repositories>
    <!-- Contains information that needs to be connected to the remote warehouse -->
    <repository>
        <!-- How to handle the download of release version in remote warehouse -->
        <releases>
            <!-- true perhaps false Indicates whether the warehouse is enabled for downloading certain types of components (release version, snapshot version). -->
            <enabled><enabled>

            <!-- This element specifies how often updates occur. Maven Will compare local POM And remote POM Time stamp of. The options here are: always(All the time),
                 daily(Default, daily), interval: X(here X Is the time interval in minutes), or never(Never). -->
            <updatePolicy></updatePolicy>

            <!-- When Maven What to do when verifying the component verification file fails: ignore(Ignore), fail(Failed), or warn(Warning). -->
            <checksumPolicy></checksumPolicy>
        </releases>

        <!-- How to handle the download of snapshot version in remote warehouse. Yes releases and snapshots These two sets of configurations, POM In each separate warehouse,
             Adopt different strategies for each type of component. For example, someone may decide to turn on support for snapshot version download only for development purposes. See repositories/repository/releases element -->
        <snapshots>
            <enabled><enabled>
            <updatePolicy></updatePolicy>
            <checksumPolicy></checksumPolicy>
        </snapshots>

        <!-- Unique identifier of the remote warehouse. Can be used to match settings.xml Remote warehouse configured in file -->
        <id> banseon-repository-proxy </id>

        <!-- Remote warehouse name -->
        <name> banseon-repository-proxy </name>

        <!-- Remote warehouse URL,Press protocol://hostname/path form -- >
        <url> http://192.168.1.169:9999/repository/ </url>

        <!-- Warehouse layout type used to locate and sort components-Can be default(Default) or legacy(Legacy). Maven 2 Provides a default for its warehouse
             The layout of; however, Maven 1.x There is a different layout. We can use this element to specify whether the layout is default(Default) or legacy(Legacy). -->
        <layout> default </layout>
    </repository>
</repositories>

<!-- Discover a list of remote repositories for plug-ins that are used to build and report -->
<pluginRepositories>
    <!-- Contains information about the need to connect to the remote plug-in repository.See repositories/repository element -->
    <pluginRepository>
    </pluginRepository>
</pluginRepositories>

<!-- This element describes all dependencies related to the project. These dependencies form a part of the project construction process. They are automatically downloaded from the warehouse of the project definition.
     For more information, see project dependency mechanism. -->
<dependencies>
    <dependency>
        <!-- Dependent group ID -->
        <groupId> org.apache.maven </groupId>

        <!-- Dependent artifact ID -->
        <artifactId> maven-artifact </artifactId>

        <!-- Dependent version number Maven 2 in, It can also be configured as a range of version numbers. -->
        <version> 3.8.1 </version>

        <!-- Dependency type. The default type is jar. It usually represents the extension of the dependent file, but there are exceptions. One type can be mapped to another extension
             Name or classifier. Types often correspond to the packaging method used, although there are exceptions. Examples of some types: jar,war,ejb-client and test-jar. 
             If set extensions by true,Can be in plugin Define a new type in. Therefore, the previous example of type is incomplete. -->
        <type> jar </type>

        <!-- Dependent classifiers. Classifiers can distinguish those belonging to the same POM,However, components with different construction methods. The classifier name is appended to the version number of the file name. For example,
             If you want to build two separate components JAR,One use Java 1.4 Compiler, another uses Java 6 Compiler, you can use the classifier to generate
             Into two separate JAR Components. -->
        <classifier></classifier>

        <!-- Dependency scope. It helps to determine which components are included in the project release process. For details, please refer to dependency mechanism.
            - compile : Default range for compilation
            - provided: Similar to compiling, but support what you expect jdk Or a container, similar to classpath
            - runtime: Required for execution
            - test: be used for test Use when task
            - system: Corresponding elements need to be provided externally systemPath To get
            - systemPath: Only for use in the range system. Provide the corresponding path
            - optional: When the project itself is dependent, mark whether the dependency is passed. Used for continuous dependency -->
        <scope> test </scope>

        <!-- Only system Scope use. Note that this element is not encouraged and may be overwritten in the new version. This element specifies the file for dependencies
             Path on the system. An absolute path is required instead of a relative path. It is recommended to match absolute paths with properties, such as ${java.home}.  -->
        <systemPath></systemPath>

        <!-- When calculating the transfer dependency, list the excluded dependent component set from the dependent component list maven You only depend on the specified project, not the project
             Dependency. This element is mainly used to resolve version conflicts -->
        <exclusions>
            <exclusion>
                <artifactId> spring-core </artifactId>
                <groupId> org.springframework </groupId>
            </exclusion>
        </exclusions>

        <!-- Optional dependencies if you are in the project B Middle handle C If the dependency declaration is optional, you need to B Project (e.g. project) A)Explicit reference pairs in C Dependence on.
             Optional dependencies block the transitivity of dependencies. -->
        <optional> true </optional>
    </dependency>
</dependencies>

<!-- Disapprove of using. Now? Maven Ignore this element. -->
<reports></reports>

last

**[CodeChina open source project: [analysis of Java interview questions of first-line large manufacturers + core summary learning notes + latest explanation Video]](

)**

ActiveMQ message middleware interview topic

  • What is ActiveMQ?
  • What if the ActiveMQ server goes down?
  • What about losing the message?
  • What if persistent messages are very slow?
  • What about the uneven consumption of news?
  • What about the dead letter queue?
  • Is the message retransmission interval and number of times in ActiveMQ?

Analysis and expansion of ActiveMQ message middleware interview topic:

redis interview topics and answers

  • What are the clients that support consistent hashing?
  • How is Redis different from other key value stores?
  • What is the memory usage of Redis?
  • What are the ways to reduce Redis's memory usage?
  • What commands are used to view Redis usage and status information?
  • What happens when Redis runs out of memory?
  • Redis is single threaded. How to improve the utilization of multi-core CPU?

Spring interview topics and answers

  • Talk about your understanding of Spring
  • What are the advantages of Spring?
  • Design patterns in Spring
  • How to open annotation assembly and common annotations
  • Briefly introduce the life cycle of spring beans

Analysis and expansion of Spring interview answers

Highly concurrent multithreaded interview topics

  • There are now threads T1, T2, and T3. How do you ensure that T2 threads execute after T1 and T3 threads execute after T2?
  • What are the advantages of the new Lock interface in Java over synchronized block s? If you implement a high-performance cache that supports concurrent reads and single writes, how do you ensure data integrity.
  • What is the difference between wait and sleep methods in Java?
  • How to implement a blocking queue in Java?
  • How to write code in Java to solve producer consumer problems?
  • Write a deadlock code. How do you solve deadlock in Java?

Analysis and expansion of highly concurrent multithreaded interview

jvm interview topics and analysis

  • What are the components of a JVM?
  • JVM memory partitioning?
  • Java's memory model?
  • Classification of references?
  • When does GC start?

JVM interview topic analysis and expansion!

This article has been CodeChina open source project: [analysis of Java interview questions of front-line large manufacturers + core summary learning notes + real project practice + latest explanation Video] Collection, self-study programming route and series of technical articles are constantly updated

1631252934046)]

Highly concurrent multithreaded interview topics

  • There are now threads T1, T2, and T3. How do you ensure that T2 threads execute after T1 and T3 threads execute after T2?
  • What are the advantages of the new Lock interface in Java over synchronized block s? If you implement a high-performance cache that supports concurrent reads and single writes, how do you ensure data integrity.
  • What is the difference between wait and sleep methods in Java?
  • How to implement a blocking queue in Java?
  • How to write code in Java to solve producer consumer problems?
  • Write a deadlock code. How do you solve deadlock in Java?

Analysis and expansion of highly concurrent multithreaded interview

[external chain picture transferring... (img-kf8ELoRP-1631252934048)]

jvm interview topics and analysis

  • What are the components of a JVM?
  • JVM memory partitioning?
  • Java's memory model?
  • Classification of references?
  • When does GC start?

JVM interview topic analysis and expansion!

[external chain picture transferring... (img-uSwxXQP3-1631252934050)]

This article has been CodeChina open source project: [analysis of Java interview questions of front-line large manufacturers + core summary learning notes + real project practice + latest explanation Video] Collection, self-study programming route and series of technical articles are constantly updated

Tags: Java Maven svn Back-end Programmer

Posted on Sat, 20 Nov 2021 19:48:47 -0500 by dtyson2000