Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-Id: <37D59D9E-2F80-4C7B-9C53-464A282A44DB@reverycodes.com>
From: Vadim Gritsenko <vadim@reverycodes.com>
To: dev@cocoon.apache.org
In-Reply-To: <47DAC4FD.5050500@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: "Normal" release artifacts
Date: Fri, 14 Mar 2008 15:14:09 -0400
References: <47CFFEB2.6050104@apache.org> <47DAC4FD.5050500@apache.org>

On Mar 14, 2008, at 2:33 PM, Reinhard Poetz wrote:

> Reinhard Poetz wrote:
>> I have started to write some Ant scripts to produce non-Maven  
>> release artifacts. This will of course help everybody who doesn't  
>> want to use Maven or Ivy for dependency management but will also  
>> bundle all the information that belongs together (src, binaries,  
>> docs, javadocs, licensing information).
>> Most of the work has been finished but now I got stuck with the  
>> question if we should ship third-party libs or not. E.g. for the  
>> Spring configurator this would be everything listed at http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/1.0/dependencies.html 
>> . The advantages are that the user gets everything that she needs  
>> but the disadvantages are that we would have to add all license  
>> files of all 3rd-party libs (AFAIK there is no automatic mechanism  
>> for that) and the download size would increase. And I think that in  
>> 2008 you shouldn't manage your library dependency graph manually  
>> anymore in your projects (Maven, Ivy, the Maven Ant tasks are of  
>> great help and at least the last one is very easy to use.)
>> Finally, if we decide to ship 3rd party libs, one technical question:
>> Am I right that there is no automatic mechanism for Ant or Maven  
>> that pulls together all license information of all 3rd-party libs?
>> And, if we decide to not ship 3rd party libs, am I right that we  
>> don't have to add license files of them? (Otherwise all artifacts  
>> on the central Maven repository would be legally broken ...)
>> Any comments?
>
> Anyone?
>
> If I don't hear anything I will *not* include any third-party stuff  
> (the only exception will be the getting-started stuff).
>
> Users will have to download all libraries themselves.

IMHO what's good a downloadable release if 'cocoon.sh run' does not  
work? One of the points of such release is to make it one stop shop,  
to get everything up and running in one quick download. May be it's  
just me. Shrug.

Vadim