[
https://issues.apache.org/jira/browse/IVY-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph C updated IVY-1242:
-------------------------
Priority: Major (was: Critical)
Description:
Currently buildlist does not support revisions while filtering leafs and roots.
The leaf and root attribute should handle specifying revisions (and even
organizations) in the form of (org#module#revision,org#module#revision,...) and
should return a list also of the form
(org#module#revision,org#module#revision,...).
This is crucial when new dependencies are introduced in new releases of a
certain project.
A use case for this is in continuous integration scripts, where a change in a
certain org1#module1#revision1 should trigger a recompilation of a dependent
org2#module2#revision2 (All other org2#module2 projects should not need
rebuilding)
was:
Currently buildlist does not support revisions while filtering leafs and roots.
The leaf and root attribute should handle specifying revisions (and even
organizations) in the form of (org#module#revision,org#module#revision,...) and
should return a list also of the form
(org#module#revision,org#module#revision,...).
This is crucial when new dependencies are introduced in new releases of a
certain project.
A use case for this is in continuous integration scripts, where a change in a
certain org1#module1#revision1 should trigger a recompilation of a dependent
org2#module2#revision2 (All other org2#module2 projects should not need
rebuilding)
> Ivy Buildlist Revision Support
> ------------------------------
>
> Key: IVY-1242
> URL: https://issues.apache.org/jira/browse/IVY-1242
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.2.0
> Reporter: Ralph C
>
> Currently buildlist does not support revisions while filtering leafs and
> roots.
> The leaf and root attribute should handle specifying revisions (and even
> organizations) in the form of (org#module#revision,org#module#revision,...)
> and should return a list also of the form
> (org#module#revision,org#module#revision,...).
> This is crucial when new dependencies are introduced in new releases of a
> certain project.
> A use case for this is in continuous integration scripts, where a change in a
> certain org1#module1#revision1 should trigger a recompilation of a dependent
> org2#module2#revision2 (All other org2#module2 projects should not need
> rebuilding)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
