From issues-return-82432-apmail-maven-issues-archive=maven.apache.org@maven.apache.org  Thu Dec  6 15:00:41 2012
Return-Path: <issues-return-82432-apmail-maven-issues-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-issues-archive@minotaur.apache.org
Delivered-To: apmail-maven-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 62631E068
	for <apmail-maven-issues-archive@minotaur.apache.org>; Thu,  6 Dec 2012 15:00:41 +0000 (UTC)
Received: (qmail 32300 invoked by uid 500); 6 Dec 2012 15:00:41 -0000
Delivered-To: apmail-maven-issues-archive@maven.apache.org
Received: (qmail 32245 invoked by uid 500); 6 Dec 2012 15:00:40 -0000
Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@maven.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@maven.apache.org>
List-Post: <mailto:issues@maven.apache.org>
List-Id: <issues.maven.apache.org>
Reply-To: dev@maven.apache.org
Delivered-To: mailing list issues@maven.apache.org
Received: (qmail 32227 invoked by uid 99); 6 Dec 2012 15:00:40 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 15:00:40 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [63.246.24.159] (HELO codehaus01.managed.contegix.com) (63.246.24.159)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 15:00:34 +0000
Received: from codehaus01 (localhost.localdomain [127.0.0.1])
	by codehaus01.managed.contegix.com (Postfix) with ESMTP id EEEDCB0692
	for <issues@maven.apache.org>; Thu,  6 Dec 2012 09:00:13 -0600 (CST)
Date: Thu, 6 Dec 2012 09:00:13 -0600 (CST)
From: "Anders Hammar (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: <1857496119.19357.1354806013979.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
In-Reply-To: <673633645.19345.1354805653266.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
Subject: [jira] (MINVOKER-147) setupIncludes / parallelThreads does not
 guarantee execution of setup*/pom.xml first.
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Hammar updated MINVOKER-147:
-----------------------------------

    Priority: Major  (was: Critical)
    
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira