Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
To: dev@avalon.apache.org
From: Leo Simons <leosimons@apache.org>
Subject: maven packaging decisions revisited
Date: Sat, 16 Aug 2003 14:25:08 +0200
Lines: 73
Message-ID: <bhl7ra$h7u$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3) Gecko/20030312
Sender: news <news@sea.gmane.org>

Hi gang,

I was wrong :D

${blah}/src/api
${blah}/src/impl

seems like a good idea, but it is not when you use maven. Mainly because 
maven will not be refactored to support it (at one point in time the 
consensus was that it would be; that has changed). The reasoning behind 
not supporting multiple source dirs in a project is that it makes plugin 
development more difficult. A tradeoff: a little less flexibility in 
your sourcetree setup gains you flexibility in tool modification.

Basically, the requirement when working with maven is that you have 
*one* sourcetree that results in *one* generated jar file for *one* 
project.xml file. Your build layout should look like this:


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org