[
https://issues.apache.org/jira/browse/OFBIZ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892056#comment-13892056
]
Pierre Smits commented on OFBIZ-5464:
-------------------------------------
With a proper configuration of the build.xml and the CI any setup configuration
can be injected/triggered to build for testing
* against accepted jar-version,
* against latest sub release of jar-version,
* against latest release, and
* against latest available
and based on that it can be decided what version to include in nightly and
release builds before creating the zip files.
This would alleviate the need to commit manually the jars and update the
dependent docs, and revert the commits when testing fails. Which, with over
200+ jars is a cumbersome feat. And which is best handled in a CI system. In
the case of generating nightly and release builds you would just change the
version/revision number of the jar in the configuration setting.
> 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)
