Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

'maven install' error

See original GitHub issue

When I use maven3 to install jMetal, the printed information is as follows:

mvn install                   
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 5 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 5 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] org.uma.jmetal:jmetal                                              [pom]
[INFO] org.uma.jmetal:jmetal-core                                         [jar]
[INFO] org.uma.jmetal:jmetal-problem                                      [jar]
[INFO] org.uma.jmetal:jmetal-algorithm                                    [jar]
[INFO] org.uma.jmetal:jmetal-exec                                         [jar]
[INFO] 
[INFO] -----------------------< org.uma.jmetal:jmetal >------------------------
[INFO] Building org.uma.jmetal:jmetal 5.8-SNAPSHOT                        [1/5]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.7.201606060606:prepare-agent (default) @ jmetal ---
[INFO] argLine set to -javaagent:/home/turner/.m2/repository/org/jacoco/org.jacoco.agent/0.7.7.201606060606/org.jacoco.agent-0.7.7.201606060606-runtime.jar=destfile=/home/turner/GitHub/jMetal/target/jacoco.exec
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.7.201606060606:report (report) @ jmetal ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources) @ jmetal ---
[INFO] 
[INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ jmetal ---
[INFO] Not executing Javadoc as the project is not a Java classpath-capable package
[INFO] 
[INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @ jmetal ---
[INFO] No site descriptor found: nothing to attach.
[INFO] 
[INFO] --- maven-failsafe-plugin:2.18.1:integration-test (integration-test) @ jmetal ---
[INFO] No tests to run.
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent! The file encoding for reports output files should be provided by the POM property ${project.reporting.outputEncoding}.
[INFO] 
[INFO] --- maven-gpg-plugin:1.5:sign (sign-artifacts) @ jmetal ---
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for org.uma.jmetal:jmetal 5.8-SNAPSHOT:
[INFO] 
[INFO] org.uma.jmetal:jmetal .............................. FAILURE [  1.524 s]
[INFO] org.uma.jmetal:jmetal-core ......................... SKIPPED
[INFO] org.uma.jmetal:jmetal-problem ...................... SKIPPED
[INFO] org.uma.jmetal:jmetal-algorithm .................... SKIPPED
[INFO] org.uma.jmetal:jmetal-exec ......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.061 s
[INFO] Finished at: 2019-03-09T15:00:43+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.5:sign (sign-artifacts) on project jmetal: Exit code: 2 -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

The main reason may be that maven3.x performs maven-ant-plugin differently than maven2.x. When pluginManagement is introduced, it works (For all pom.xml files in jMetal repository).

<build>
   <pluginManagement>
   <plugins>
      <plugin></plugin>

      ... ...

       <plugin></plugin>
    </plugins>
</pluginManagement>
</build>