maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MINVOKER-191) “Artifact is not fully assembled” error with maven-invoker-plugin in parallel build
Date Fri, 25 Sep 2015 09:34:04 GMT


Robert Scholte commented on MINVOKER-191:

I can confirm this issue. Up until now all reactor-project started before the current project
are always installed, even though they are not used. With a single thread this is not a real
issue, but with multiple threads it can happen that the jar is not yet created (so started,
though not yet finished).
I wonder if this was a hack required for Maven2. I would expect that nowadays Maven can perfectly
pick up the artifact from the reactor if it was part of it.
Anyhow, this piece of code is too aggressive.

> “Artifact is not fully assembled” error with maven-invoker-plugin in parallel build
> -----------------------------------------------------------------------------------
>                 Key: MINVOKER-191
>                 URL:
>             Project: Maven Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.10
>            Reporter: Tavian Barnes
> According to the docs (,
maven-invoker-plugin is "thread-safe and supports parallel builds." However, when I build
by multi-module project with -T 1C, I get an error like the following:
> bq. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:1.10:install
(integration-test) on project my-archetype: Failed to install project dependencies: MavenProject:
com.tavianator:my-archetype:1.6-SNAPSHOT @ /home/tavianator/code/Project/my-archetype/pom.xml:
Failed to install project artifacts: MavenProject: com.tavianator:my-project-2:1.6-SNAPSHOT
@ /home/tavianator/code/Project/my-project-2/pom.xml: Failed to install artifact: com.tavianator:my-project-2:jar:1.6-SNAPSHOT:
Artifact is not fully assembled: /home/tavianator/code/Project/my-project-2/target/classes
-> [Help 1]
> The project layout is like this:
> {code}
> Root
> |--Project 1
> |--Project 2
> |--Archetype (depends on Project 1, scope=test)
> {code}
> The archetype integration tests use the maven-invoker-plugin to install the relevant
dependencies (Root and Project 1) to a local repository, then runs the normal archetype integration
tests. In parallel builds, Archetype and Project 2 run at the same time. When the maven-invoker-plugin
runs, it tries to install Project 2 to the local repo, but Project 2 isn't built yet, hence
the error.

This message was sent by Atlassian JIRA

View raw message