commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark R. Diggory" <mdigg...@latte.harvard.edu>
Subject Re: [all] Shared build causes issues in releases
Date Tue, 06 Apr 2004 13:19:16 GMT
I wasn't clear, I'm not adverse to doing that either.

-Mark

Jeffrey D. Brekke wrote:

> Couldn't the source releases just zip up the commons-build directory
> along with the projects.  Maybe sprinkle a special goal in
> commons-build/maven.xml for this?
> 
> 
>>>>>>On Tue, 06 Apr 2004 09:06:20 -0400, "Mark R. Diggory" <mdiggory@latte.harvard.edu>
said:
> 
> 
>>I would argue that, while I consider Maven to be a great developer
>>tool for sites and testing, I do not consider it to be a great
>>"user" tool at this point, its too heavy. I would highly recommend a
>>Maven generated Ant build file for each project and Ant build file
>>that iterates over the common goals of these for the entire project.
> 
> 
>>1.) The issue of common dependencies could be resolved by
>>parameterizing things like the location that dependency jars are
>>downloaded to so that all scripts use the same location.
> 
> 
>>2.) I'm not impressed that anyone would ever want to download the
>>entire commons as a src zip and compile it. Its modularity, and its
>>separate release cycles for each module really make such an effort
>>have no value (IMHO). When I need a commons module, I go and get
>>just that module, thats the whole power of having everything
>>separate. Why would/should I compile that digester when all I wanted
>>was lang? I say keep things well separated, otherwise the user will
>>suffer.
> 
> 
>>-Mark
> 
> 
> 
>>Stephen Colebourne wrote:
>>
>>>Our maven scripts now depend on commons-build, however this is of
>>>course not included in the release zips.  This is a problem and
>>>means that maven cannot be used in releases.  Anyone got any ideas
>>>on how to solve this? I don't like the idea of hacking project xml
>>>for each release.  Stephen
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail:
>>>commons-dev-help@jakarta.apache.org
>>>
> 
> 
>>-- Mark Diggory Software Developer Harvard MIT Data Center
>>http://www.hmdc.harvard.edu
> 
> 
> 
> 
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
> 

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu

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


Mime
View raw message