You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacopo Cappellato (JIRA)" <ji...@apache.org> on 2014/03/26 09:27:14 UTC

[jira] [Commented] (OFBIZ-5464) Extend Ivy usage for easier external lib management

    [ https://issues.apache.org/jira/browse/OFBIZ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947664#comment-13947664 ] 

Jacopo Cappellato commented on OFBIZ-5464:
------------------------------------------

I don't think it is a good idea to move to Ivy: upgrading the jars with svn commits is not a relevant overhead for committers.
In this way we have full control of what we distribute with our products, we do not require Internet connection at the time the system is built.
Also, we will still have to maintain the same information on LICENSE and NOTICE files.


> 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)