You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/05/01 20:55:12 UTC
[jira] [Commented] (MINVOKER-147) setupIncludes / parallelThreads
does not guarantee execution of setup*/pom.xml first.
[ https://issues.apache.org/jira/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265879#comment-15265879 ]
Hudson commented on MINVOKER-147:
---------------------------------
SUCCESS: Integrated in maven-plugins #5849 (See [https://builds.apache.org/job/maven-plugins/5849/])
[MINVOKER-147] setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
o Refactored code to execute the setup Jobs before any other job.
Furthermore in the first step only executing single thread. (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1741877])
* maven-invoker-plugin/src/main/java/org/apache/maven/plugin/invoker/AbstractInvokerMojo.java
> setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
> -------------------------------------------------------------------------------------
>
> Key: MINVOKER-147
> URL: https://issues.apache.org/jira/browse/MINVOKER-147
> Project: Maven Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.8
> Environment: All.
> Reporter: Karl Heinz Marbaise
> Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> I've setup an integration test for a maven plugin. I have configured the maven-invoker-plugin like the following:
> {code}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-invoker-plugin</artifactId>
> <dependencies>
> <dependency>
> <groupId>org.codehaus.groovy</groupId>
> <artifactId>groovy</artifactId>
> <version>${org.codehaus.groovy-groovy.version}</version>
> </dependency>
> <dependency>
> <groupId>org.codehaus.gmaven.runtime</groupId>
> <artifactId>gmaven-runtime-1.8</artifactId>
> <version>${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}</version>
> </dependency>
> </dependencies>
> <configuration>
> <addTestClassPath>true</addTestClassPath>
> <debug>false</debug>
> <localRepositoryPath>${project.build.directory}/local-repo</localRepositoryPath>
> <cloneProjectsTo>${project.build.directory}/it</cloneProjectsTo>
> <projectsDirectory>src/it</projectsDirectory>
> <showVersion>true</showVersion>
> <pomIncludes>
> <pomInclude>*/pom.xml</pomInclude>
> </pomIncludes>
> <preBuildHookScript>setup</preBuildHookScript>
> <postBuildHookScript>verify</postBuildHookScript>
> <settingsFile>src/it/settings.xml</settingsFile>
> <parallelThreads>1</parallelThreads>
> </configuration>
> <executions>
> <execution>
> <id>integration-tests</id>
> <goals>
> <goal>install</goal>
> <goal>run</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> {code}
> I have a setup-config/pom.xml project which must be installed before any other tests which seemed to be working with the above configuration.
> But I would like to use the parallelThreads with for example 3 or 4 the result is that the build fails, cause the setup-config/pom.xml project is not running before any other integration.
> This gives the hint that it is not guaranteed that the setup-*/pom.xml project will be running before other integration tests.
> In my opinion the setup-*/pom.xml project must be started first with the appropriate threads afterwards the other integration tests must be started within a second step.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)