Maven releases the installation of the project to the use of the unused and JUnit

End Bowl blowing water

MAVEN launches project to:

The so-called release project is to package the project into a jar package and then choose a repository that is uploaded to a single database, and others can download it to your project in the repository "Learn Java and go to the kaige123.com". A brief introduction to some of the warehouses on the Nexus:

If you want to publish a project that requires a user who has permission to publish, a visitor who does not have permission to publish or a regular user can only download or update it. A brief introduction to some of the accounts on the Nexus:

Now try uploading a jar to the database: 1. Select a warehouse and then configure the address of the warehouse to the project Pom file, where I use the snapshot warehouse as an example:

2. After the configuration is complete, package the project that you want to publish into a jar package:

3. Configure the MAVEN settings file to configure the account and password with deployment privileges to this file, I use the deployment account example here:

4. After configuring the file, use the Deploy command to publish the project:

You can also add a new warehouse or create a user: Create a User:

To create a warehouse:

After the new warehouse is created, it needs to be added to the Warehouse group before it can be updated in Maven to get the ZERO01 warehouse package. Because we configure the address of the Warehouse group in the MAVEN. settings file, the update package will only be updated from the warehouse in the Warehouse group, and the warehouse outside the warehouse group does not have to be updated separately for that warehouse, so we need to add the newly created warehouse to the warehouse group to solve this problem:

JUnit downloads are used:

JUnit is a unit test plug-in, unit testing is its own development of the code to test itself, the purpose of testing is not to test the syntax of errors, but to test the results of the code to run the logic of whether there are errors. The previous version of JUNIT4 was not popular, as those versions were less cumbersome to test, and JUNIT4 improved the drawbacks of previous versions, making testing easier and more convenient, so it became popular.

For example: The JUNIT3 version, which needs to inherit the TestCase class when testing, and then the method name that needs to be tested must be test, and if the method name is not at the beginning of the test, it will not be tested and will be run using JUnit test at run time when using JUnit tests:

JUNIT4 version Improved this disadvantage, in the JUNIT4 version only need to add a @test annotation on the method, you need to test the name of the method can be arbitrary, and do not need to "learn Java, to the Gothic academy kaige123.com" Inherit TestCase class, You do not need to write test at the beginning of the method name. So it's easier than the previous version, and the simpler the test, the better, rather than the more hassle:

The JUnit dependencies can be downloaded directly from the MAVEN project, and generic projects can download the jar packages themselves or use the jar packages provided by the development tools, which are generally easier to use with MAVEN engineering:

Typically eclipse comes with junit and can create junit projects directly, but it is not normally used:

General Engineering Import the JUnit jar package into the engineering environment, then you need to create a test source folder:

Maven releases the installation of the project to the use of the unused and JUnit