You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Pierre Smits (JIRA)" <ji...@apache.org> on 2016/06/25 17:36:37 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=15349736#comment-15349736 ]
Pierre Smits commented on OFBIZ-5464:
-------------------------------------
If we're prohibited to include external jars in our repos and thus source code, how are we going to deal with:
ant-*.jar
ivy*.jar
> 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: Release Branch 13.07, Release Branch 14.12, Release Branch 15.12
> Reporter: Pierre Smits
> Assignee: 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.3.4#6332)