ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nascif Abousalh-Neto (JIRA)" <>
Subject [jira] Updated: (IVY-897) Add VPF as a report output format
Date Sat, 06 Sep 2008 03:36:44 GMT


Nascif Abousalh-Neto updated IVY-897:

    Summary: Add VPF as a report output format  (was: Add VPF as a reort output feature)

> Add VPF as a report output format
> ---------------------------------
>                 Key: IVY-897
>                 URL:
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Nascif Abousalh-Neto
>            Priority: Minor
>             Fix For: unspecified
>         Attachments: vpf.xsl
> One of the best practices in the use of Ivy for large organizations is to replace all
the revision values in the ivy.xml files with properties. 
>   <dependency name="my.module" revision="${my.module.revision}" ... />
> This approach allows an administrator to control all revisions values used by all modules
in one single place - a Version Property File (or VPF for short). This way versions can be
controlled in a uniform way, with minimum maintenance and reduced chance of error. For example,
you can upgrade all your modules dependencies from Log4J 3.5 to 4.0 with one single line change
- and be sure that you didn't forget any of them behind.
> Creating and maintaining VPFs is not trival though. One  way to automate the process
is to "harvest" the module names and their latest versions from the repository, using the
repreport task to create a resolution report for the entire repo and then converting it to
a property file format using a XSL spreadsheet (attached).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message