maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <j...@codehaus.org>
Subject [jira] (MINVOKER-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
Date Wed, 05 Jun 2013 07:48:03 GMT

    [ https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326217#comment-326217
] 

Anders Hammar commented on MINVOKER-147:
----------------------------------------

I've verified that this a bug in v1.8 with a test project.
                
> setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
> -------------------------------------------------------------------------------------
>
>                 Key: MINVOKER-147
>                 URL: https://jira.codehaus.org/browse/MINVOKER-147
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.8
>         Environment: All.
>            Reporter: Karl Heinz Marbaise
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message