Return-Path: 
 <issues-return-606-apmail-continuum-issues-archive=continuum.apache.org@continuum.apache.org>
Delivered-To: apmail-continuum-issues-archive@www.apache.org
Received: (qmail 86789 invoked from network); 2 Apr 2008 10:56:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 2 Apr 2008 10:56:29 -0000
Received: (qmail 71561 invoked by uid 500); 2 Apr 2008 10:56:29 -0000
Delivered-To: apmail-continuum-issues-archive@continuum.apache.org
Received: (qmail 71540 invoked by uid 500); 2 Apr 2008 10:56:29 -0000
Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@continuum.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@continuum.apache.org>
List-Post: <mailto:issues@continuum.apache.org>
List-Id: <issues.continuum.apache.org>
Reply-To: dev@continuum.apache.org
Delivered-To: mailing list issues@continuum.apache.org
Received: (qmail 71527 invoked by uid 99); 2 Apr 2008 10:56:29 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2008 03:56:29 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com)
 (63.246.2.115)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2008 10:55:38 +0000
Received: from codehaus01.managed.contegix.com (localhost.localdomain
 [127.0.0.1])
	by codehaus01.managed.contegix.com (Postfix) with ESMTP id AE3B8162000D
	for <issues@continuum.apache.org>; Wed,  2 Apr 2008 05:55:58 -0500 (CDT)
Message-ID: 
 <1311338.1207133758711.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Wed, 2 Apr 2008 05:55:58 -0500 (CDT)
From: "Brett Porter (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Updated: (CONTINUUM-998) Build order doesn't take plugin
 dependencies into account
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org


     [ http://jira.codehaus.org/browse/CONTINUUM-998?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-998:
-----------------------------------

    Fix Version/s:     (was: Future)
                   1.x

> Build order doesn't take plugin dependencies into account
> ---------------------------------------------------------
>
>                 Key: CONTINUUM-998
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-998
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.0.3
>            Reporter: Petter M=E5hl=E9n
>             Fix For: 1.x
>
>
> We have a system that consists of a client, a server and a 'common' compo=
nent. The common component contains a protocol definition file, which is us=
ed by a Maven plugin to generate source code for the client-server communic=
ation. The common JAR file should not be distributed with the product, and =
must be available on the classpath of the plugin at build time. Hence, the =
configuration in the POM looks as follows:
> <project>
>  ...
>   <build>
>       <plugins>
>         <plugin>
>           <groupId>se.jadestone.whine</groupId>
>           <artifactId>maven-whine-generator</artifactId>
>           <version>3.0</version>
>  ...
>           <dependencies>
>                 <dependency>
>                     <groupId>se.jadestone.esports</groupId>
>                     <artifactId>hc-common</artifactId>
>                     <version>0.0.1</version>
>                 </dependency>
>            </dependencies>
>       </plugin>
>  ...
>    </build>
>  ...
>   <dependencies>
>       ... main project dependencies to be included in the final package .=
..
>   </dependencies>
> </project>
> Continuum doesn't take the plugin dependency into account, meaning that t=
he 'common' project isn't built before the others, meaning that it will mor=
e or less randomly fail, even though the source code repository is in a cor=
rect state. The workaround we have in place is to give the projects names t=
hat are in the build order, but that is clearly unsatisfactory.

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira