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

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

    Fix Version/s: 1.x

could potentially get this by using the maven 2.1.0 lib that honours it now, 
though we have a clone that among other things avoids failing on cyclic deps 
that we need to be able to continue to do (perhaps falling back?)

> 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åhlén
>             Fix For: 1.x
>
>
> We have a system that consists of a client, a server and a 'common' 
> component. The common component contains a protocol definition file, which is 
> used by a Maven plugin to generate source code for the client-server 
> communication. 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 the 
> 'common' project isn't built before the others, meaning that it will more or 
> less randomly fail, even though the source code repository is in a correct 
> state. The workaround we have in place is to give the projects names that are 
> in the build order, but that is clearly unsatisfactory.

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


Reply via email to