You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2014/02/05 16:58:10 UTC
[jira] [Comment Edited] (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=13892251#comment-13892251 ]
Jacques Le Roux edited comment on OFBIZ-5464 at 2/5/14 3:56 PM:
----------------------------------------------------------------
By answering here you answered to 2. :)
Actually to be more clear, this how it went:
> I have - in a separate checkout - a complete working setup with IVY for all
> jars. Not just the main libs, but also in the components.
Would it make sense to share it, in relation with the recent Ivy Jira issues you created?
So I guess you will answer it by contributing from your experience. I fear I will have to put this aside for a moment, I already invested much time recently, notably inr elation with vulnerability dependencies (point 1).
was (Author: jacques.le.roux):
By answering here you answered to 2. :)
> 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.1.5#6160)