[
https://issues.apache.org/jira/browse/OFBIZ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947823#comment-13947823 ]
Pierre Smits commented on OFBIZ-5464:
-------------------------------------
Using IVY in our CI processes not only made testing with newer versions easier, but it also reduced (together with other build configurations) our storage footprint of the nightly builds with 87%. Our latest build was 36,4 MB (compared to 278 MB for latest OFBiz nightly build of trunk).
Given that the project has more 100 nightly builds downloadable, and a lot are mirrored on other sites as well, I would say that would mean a significant storage and transport reduction for the ASF (meaning less HW cost and less traffic cost). But it would also make an additional marketing aspect.
As for staying in control, nothing changes. In stead of removing and adding jars in commits (and that has been forgotten at times), it would just mean a change in a/the configuration document.
> Extend Ivy usage for easier external lib management
> ---------------------------------------------------
>
> Key: OFBIZ-5464
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5464> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS, framework
> Affects Versions: SVN trunk
> Reporter: Pierre Smits
> Attachments: jarfiles.txt
>
>
> Currently Apache Ivy is used to facilitate downloads of specific external jar files for Activemq, mySQL, postgreSQL configuration and Sonar and Cobertura functions.
> However, Apache Ivy can also be for easier management of the standard jars OFBiz is dependent on, in
> - various framework areas
> - various base and special purpose applications/components.
> Applying more ivy functionality will decrease the load on commiters regarding maintenance of (and upgrading) external jars used and required licence information.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Locked
