Coreexception: cocould not get the value for parameter compilerid for plugin execution default-compile

Source: Internet
Author: User

Coreexception: cocould not get the value for parameter compilerid for plugin execution default-compile: pluginresolutionexception: plugin Org. apache. maven. plugins: Maven-compiler-plugin: 3.1 or one of its Dependencies cocould not be resolved: the following artifacts cocould not be resolved: COM. google. code. findbugs: jsr305: jar: 2.0.1, org. codehaus. plexus: plexus-compiler-API: jar: 2.2: failure to transfer COM. google. code. findbugs: jsr305: jar: 2.0.1 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. original error: cocould not transfer artifact COM. google. code. findbugs: jsr305: jar: 2.0.1 from/to central (http://repo.maven.apache.org/maven2): The operation was canceled.

How can I see detailed error information?

The process is as follows (this problem is not easy to reproduce and should be caused by unexpected network problems ):

Double-click the wrong Pom. xml file to open the overview video. If the location marked by the red box is displayed, the error message is displayed,


The detailed information shown is displayed when you left-click the error message, or the details displayed in the "Problems in the pom" dialog box.


Click the link shown in to locate the position of the POM file.


Some information on the internet says that "<pluginmanagement>" is added between the "<build>" and "<plugins>" labels. It does not work if I add it, but it does not play a negative role.


I only blame myself for being too bad in English, and carefully analyzed and understood the meaning of the error information. It should be that the corresponding JAR file is missing and searched under the configured Maven local "Repo" directory.


Obviously, the"Plexus-compiler-api-2.2.jar"File, download failed due to network reasons.

Return to the upper-level directory and delete the "2.2" folder.

Modify "Pom. xml", add or delete a space in the blank space, save the file, and trigger the update event!


Multiple Packages may fail or are missing due to the same reason. Use the same solution.


If this is not the case, the following link may help you:

Http://ljhzzyx.blog.163.com/blog/static/383803122013440345857/

Http://liwenqiu.me/blog/2012/12/19/maven-lifecycle-mapping-not-converted/

Http://wiki.eclipse.org/M2E_plugin_execution_not_covered


Coreexception: cocould not get the value for parameter compilerid for plugin execution default-compile

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.