First of all I believe that (packaged) releases are intended for non-developers (end users) and not for developers. That in mind, releases should have everything that is needed to run generic production systems. And nothing more, not test code, not demo data.
When developers want to look at what is underneath for testing and/or modification they can use svn to have access to everything they might need. As is per ASF policy. We do however facilitate the end user with additional code that helps them to run OFBiz against other underlying Db's and systems (amongst other reasons, due to licence-issues) , e.g. the ant targets to download drivers for PostgreSQL and mySQL. I also believe that having source code in place, that downloads every external jar required to run OFBiz as it should, adheres to ASF policies. I also believe that tooling can help building the releases (no matter what must go in there) as per requirements of the ASF. This would lessen the burden on committers. Instead of removing old versions of external jars and uploading new ones manually, doing configuration management (as IVY- and Maven-integration deliver) will ensure that the right (external) components/jars are incorporated. Maybe we should setup discussions with Xavier Hanin<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=xavier> from the IVY project to explain a bit more what it can do for OFBiz, before we jump to conclusions or start heading in wrong directions. I also believe that when applied correct (build, dependency management and CI) tooling will help us in evaluate external jars better to include in releases or not, and let us focus on what is more important. If we decide that the approach is sound, then we should set up a different branch to explore possibilities and not merge back into trunk unless all issues are addressed. Regards, Pierre Op 12 april 2012 17:02 schreef Jacopo Cappellato < jacopo.cappell...@hotwaxmedia.com> het volgende: > > On Apr 12, 2012, at 4:37 PM, Erwan de FERRIERES wrote: > > > ivy would rename the jars the way we want (eg package-version.jar), > > and using ivy, we would then reduce the LICENSE file, as less jars > > would be released with OFBiz. From an extremist POV, we could only > > whip ant + ivy, and one of the first task would be to download > > everything. > > No no, this is not possible: please ready my previous message carefully; > the release package will have to contain required jars (while the svn may > not) and most of all the LICENSE file must contain all jars that are > required to run/test/use the software. > > Jacopo
