Home Forums algoquant-maven-plugin – FAILURE

  • This topic has 4 replies, 2 voices, and was last updated 5 years ago by hessinemaaoui.
Viewing 1 post (of 1 total)
  • Author
    Posts
  • #5300
    hessinemaaoui
    Keymaster

    I have a similar problem to Yu Dongqing’s.
    But still can’t resolve it after reading his treads.
    here is the screen shot of the error:

    Scanning for projects…
    ————————————————————————
    Reactor Build Order:

    algoquant
    algoquant-maven-plugin
    algoquant-core

    ————————————————————————
    Building algoquant 1.1.0
    ————————————————————————

    — build-helper-maven-plugin:1.9.1:add-resource (add-resource) @ algoquant —

    ————————————————————————
    Building algoquant-maven-plugin 1.1.0
    ————————————————————————

    — maven-plugin-plugin:3.2:helpmojo (help-goal) @ algoquant-maven-plugin —
    Using ‘UTF-8’ encoding to read mojo metadata.
    Applying mojo extractor for language: java
    Mojo extractor for language: java found 0 mojo descriptors.
    Applying mojo extractor for language: bsh
    Mojo extractor for language: bsh found 0 mojo descriptors.
    Applying mojo extractor for language: java-annotations
    Mojo extractor for language: java-annotations found 0 mojo descriptors.

    — maven-plugin-plugin:3.2:descriptor (default-descriptor) @ algoquant-maven-plugin —
    Using ‘UTF-8’ encoding to read mojo metadata.
    Applying mojo extractor for language: java
    Mojo extractor for language: java found 0 mojo descriptors.
    Applying mojo extractor for language: bsh
    Mojo extractor for language: bsh found 0 mojo descriptors.
    Applying mojo extractor for language: java-annotations
    Mojo extractor for language: java-annotations found 0 mojo descriptors.

    — build-helper-maven-plugin:1.9.1:add-resource (add-resource) @ algoquant-maven-plugin —

    — maven-resources-plugin:2.5:resources (default-resources) @ algoquant-maven-plugin —
    [debug] execute contextualize
    Using ‘UTF-8’ encoding to copy filtered resources.
    Copying 2 resources
    Copying 2 resources

    — maven-compiler-plugin:3.2:compile (default-compile) @ algoquant-maven-plugin —
    Changes detected – recompiling the module!
    Compiling 8 source files to C:\Users\Vincent\Desktop\algoquant-1.1.0\maven\target\classes

    — maven-plugin-plugin:3.2:descriptor (mojo-descriptor) @ algoquant-maven-plugin —
    Using ‘UTF-8’ encoding to read mojo metadata.
    Applying mojo extractor for language: java
    Mojo extractor for language: java found 0 mojo descriptors.
    Applying mojo extractor for language: bsh
    Mojo extractor for language: bsh found 0 mojo descriptors.
    Applying mojo extractor for language: java-annotations
    Mojo extractor for language: java-annotations found 3 mojo descriptors.
    ————————————————————————
    Reactor Summary:

    algoquant ………………………………….. SUCCESS [1.354s]
    algoquant-maven-plugin ………………………. FAILURE [17.060s]
    algoquant-core ……………………………… SKIPPED
    ————————————————————————
    BUILD FAILURE
    ————————————————————————
    Total time: 18.604s
    Finished at: Mon Sep 21 14:56:29 CST 2015
    Final Memory: 37M/713M
    ————————————————————————
    Failed to execute goal org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor (mojo-descriptor) on project algoquant-maven-plugin: Error extracting plugin descriptor: ‘Goal: help already exists in the plugin descriptor for prefix: algoquant
    Existing implementation is: HelpMojo
    Conflicting implementation is: com.numericalmethod.algoquant.maven.indices.sp500.HelpMojo’
    -> [Help 1]

    To see the full stack trace of the errors, re-run Maven with the -e switch.
    Re-run Maven using the -X switch to enable full debug logging.

    For more information about the errors and possible solutions, please read the following articles:
    [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

    After correcting the problems, you can resume the build with the command
    mvn -rf :algoquant-maven-plugin

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.