Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of dmgloss@mail.ru designates
 94.100.176.90 as permitted sender)
Message-ID: <49FB7405.8040701@mail.ru>
Date: Sat, 02 May 2009 02:13:25 +0400
From: Vadim Dmitriev <dmgloss@mail.ru>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.21) Gecko/20090409 Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.6.0
MIME-Version: 1.0
To: users@maven.apache.org
Subject: Project/module dependencies in separate JEE apps
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi.

Here is a simple project 'Root' structure:
Root
+-A
| +-A1
| +-A2
| +-A3
+-B
  +-B1
  +-B2
  +-B3

Let's say that A is a JEE web application and B is a backing EJB app. 
Different modules in A depend on different modules in B. For the sake of 
simplicity: A1 depends on B1, A2 depends on B2 and so on.
I want to archive the following behavior. If I package A (which is 
configured to include only modules A1 and A2), then I want maven to 
automatically package project B with only those modules on which depends 
active modules from project A. In this case it's modules B1 and B2 (and 
to package A and B into single EAR, if possible)
I found it is very easy to do if A* and B* are essentialy modules of the 
same project. But in the case of different projects... I'm stuck.

Thanks in advance for any advices.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org