Continuum Dependency Management

["Morgovsky, Alexander (US - Glen Mills)" <am...@deloitte.com>]

In Continuum 1.0.3, how is dependency management handled, in that if
project A needs to be built before project B, how does Continuum handle
this?  Thanks. 


This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message. 


Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]

Re: Continuum Dependency Management

[Emmanuel Venisse <em...@venisse.net>]

In continuum 1.0.3, Continuum find the right order by analysing all dependencies, so if project B depends on project A, project A will be built before project B.
But, if project A doesn't have changes since its last build, it won't be built and if project A is built and project B doesn't have changes since its last built, project B won't be built.

In 1.1, Continuum find the right order by analysing all dependencies. But if project A have some changes, it is built, then even if project B doesn't have changes, it will be built too because it 
depends on project A that have changed.

Emmanuel

Morgovsky, Alexander (US - Glen Mills) a écrit :
> In Continuum 1.0.3, how is dependency management handled, in that if
> project A needs to be built before project B, how does Continuum handle
> this?  Thanks. 
> 
> 
> This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message. 
> 
> 
> Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
> 

Re: Continuum Dependency Management

[tz...@s-und-n.de]

iirc continuum doesn't manage dependencies as in: "one project requires 
another project to be built first". continuum reacts to changes in a 
projects source, tries to build the project that has been changed and only 
tells you whether or not the projects build system managed to build the 
project. in your case if project a is required by project b it is up to 
you to make sure they are built in correct order.

a suggestion at this point.:
if you are using maven2 as your projects build system, merge the two 
projects if possible and create modules for them instead of seperate 
projects. this way you can setup the main project with its subprojects 
(modules) a and b. you can setup the main project in continuum to be built 
recursively and the maven2 reactor will take care of the required build 
order of the modules (formerly project a and b).

hth

Freundliche Grüße / With kind regards
Thomas Zirke

S&N AG
Klingenderstr. 5
D 33100 Paderborn

voice           +49 5251/1581-984
fax             +49 5251/1581-71
eMail           tzirke@s-und-n.de
Web             http://www.s-und-n.de

Vorstand
Klaus Beverungen
Josef Tillmann

Vorsitzender des Aufsichtsrates
Heinz-Dieter Wendorff

Handelsregister
Amtsgericht Paderborn HRB 3270




"Morgovsky, Alexander (US - Glen Mills)" <am...@deloitte.com>
21.04.2007 07:04
Bitte antworten an continuum-users
 
        An:     <co...@maven.apache.org>
        Kopie: 
        Thema:  Continuum Dependency Management


In Continuum 1.0.3, how is dependency management handled, in that if
project A needs to be built before project B, how does Continuum handle
this?  Thanks. 


This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law. 
If you are not the intended recipient, you should delete this message. 


Any disclosure, copying, or distribution of this message, or the taking of 
any action based on it, is strictly prohibited. [v.E.1]