Continuous deployment and intra-project dependencies

["Hendrikse Z. (Zeger)" <ze...@nl.fortis.com>]

Hi,

In our project we have Continuous integration
with Maven 2.0.4 and Continuum 1.0.3 operational.
Currently I'm trying to continuously deploy a WAR
(containing a WebSphere portlet) to an IBM WebSphere
Portal Server. This WAR depends on another (business) 
module, which is included in the WEB-INF/lib during 
the packaging stage. 

The question is: 
Suppose a modification has been checked in for the 
business module, how can we implement an automated
subsequent deployment of the WAR containing this modified
and hence newly built business module (JAR)? 

In the above scenario, Continuum only rebuilds the business
module, leaving the WAR untouched. In Continuum, this looks
as follows:

-- OurProjectMain (with --non-recursive)
 |
 |-- business-module  (included in the WAR)
 |
 |-- web-module       (containing the portlet)
 |
 |-- other-module     (omitted for the sake of simplicity)

where the main project contains the root POM and a copy
of the complete project tree from CVS (by default with
the --non-recursive option in the build goal). Only this
main project is triggered upon a SCM check-in of any of
its submodules, so can be the only candidate to trigger
the deployment. However, the WAR it would deploy this way
would still contain the unmodified business JAR file in 
its WEB-INF/lib dir!

So far, we could not find any resource that addresses this 
issue: we extensively searched the web and read relevant
chapters from the "Better builds with Maven" book. 

Can anybody shed some light on this issue?

Thanks in advance,

Kind regards,

Zeger Hendrikse.

PS: At this moment we don't think that either a hierarchical 
or flat lay-out of the project structure is of any influence,
but for the sake of completeness: we have a hierarchical lay-out.




****************************DISCLAIMER***********************************
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed on to, or made available for use by any person other than the addressee(s). Fortis rules out any and every liability resulting from any electronic transmission. 
******************************************************************************