abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Constabaris <a...@clownsinmycoffee.net>
Subject Re: [jira] Created: (ABDERA-56) Spring Integration
Date Sat, 11 Aug 2007 15:07:10 GMT
Brian Moseley wrote:
> On 8/10/07, James M Snell <jasnell@gmail.com> wrote:
>   
>> Well, my concern regarding distribution is mainly with the ant build.
>> We use the ant build to build the release.  The maven build is provided
>> primarily as a convenience for developers who prefer to work with that
>> tool.  I'm sure the folks who actually use maven can speak up for
>> themselves, but I would not see any problem with spring not being
>> optional in the maven pom so long as it's not included in the release
>> zip created by the ant build.
>>     
>
> i'm not familiar enough with maven2 to understnad what an optional
> dependency is, but it certainly would remove some of the benefit of
> using maven to have to bring spring into the build manually. i assume
> that whatever spring jars the build would depend on are marked as
> build-only dependencies though?
>   
Maven2's "optional" dependencies are provided precisely for this use 
case: some of the functionality in your project depends on X, but you 
recognize that some users won't need that functionality.  So what it 
means that, for those who are pulling in Abdera from the maven 
repositories and their project uses Spring, they'll have to explicitly 
declare Spring as a dependency.  Everybody else will be able to ignore it.

http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

AC

Mime
View raw message