Continuum check only groupId/artifactId/version and not the packaging. It's the same mechanism that
is used by maven for the build order.
Emmanuel
Urbieta Matias a écrit :
Hi Emmanuel, that feature is not working well for me. Here i'm
attaching an example where Utils artifact depends on DNI_XML artifact.
When i shot the build ( either group build or Utils buld), it doesn't
respect the dependency order :
<?xml version="1.0" encoding="UTF-8"?><project>
<modelVersion>4.0.0</modelVersion>
<groupId>serverlib</groupId>
<artifactId>Utils</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>tjar</packaging>
<dependency>
<groupId>serverlib</groupId>
<artifactId>DNI_XML</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
...
and the oher artifact's pom is:
<?xml version="1.0" encoding="UTF-8"?>
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>serverlib</groupId>
<artifactId>DNI_XML</artifactId>
<version>1.0-SNAPSHOT</version>
<description></description>
<packaging>tjar</packaging>
...
it just have an special thing, i have my own packaging method.
Thanks
On 11/6/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Continuum build projects in the correct order by an analyse of
dependencies like maven do it in
reactor mode.
Sometimes, Continuum can't resolve the correct order. This case
appears only when you have cyckic
dependencies between all your projects in continuum
Emmanuel
Urbieta Matias a écrit :
> Hi, i am faced with a deploy that needs an ordered build of related
> artifacts. So i want to know how to set up that order.
> I don't know why continuum doesn't analyse the dependencies of an
> artifact and try to find it in the pool of continuum proyects.
> Thanks
>
> --
> Lic Matias Urbieta
>
>
>
