¿Hay algún problema con el complemento de lanzamiento de Maven?

Are there any problems with the Maven release plugin?

Maven release plugin is created years before people started realizing that software production has to become smoother and continuous. Main problems with the plugin includes: It is not atomic. If release goal fails for some stupid reason, you have committed and broken poms.

If for some reason the dependencies weren’t imported correctly (IntelliJ IDEA highlights them), try to perform the following actions: You can check your local maven repository in the Maven | Repositories settings and try to update it. You can check the jar file of the local.m2 repository to see if it was downloaded correctly.

This also brings risks when normal-than-usual releases are needed for some reason (urgent fixes etc). When delivery is not fully automated, every delivery is a potential disaster point. Maven release plugin is created years before people started realizing that software production has to become smoother and continuous.

For example, you can edit your POM and configure Maven compiler plugin to compile your Java code. You should set the compiler level explicitly, so it won’t revert to the default settings when you re-import your project. Open your POM in the editor. Change the configuration for the Maven compiler plugin. Click to import your changes.

Execute the maven build lifecycle on the extracted instance of the project. Deploy the versioned artifacts to appropriate local and remote repositories. The following example shows how to run the release:perform goal from the commandline.

The tagged project source code is extracted, compiled, tested, documented and deployed. An instance of the release artifact is deployed to the machine’s local repository. An another instance of the release can be deployed to a remote repository by configuring the distributionManagement element within the pom.xml file.

The final deliverable will then be released into an appropriate maven repository. Extract file revisions versioned under the new tag name. Execute the maven build lifecycle on the extracted instance of the project. Deploy the versioned artifacts to appropriate local and remote repositories.