[
https://issues.apache.org/jira/browse/IVY-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene resolved IVY-676.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-beta-2
> Ivy doesn't respect the order of the ivy patterns as defined in the settings
> ----------------------------------------------------------------------------
>
> Key: IVY-676
> URL: https://issues.apache.org/jira/browse/IVY-676
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0-beta-1
> Reporter: Maarten Coene
> Assignee: Maarten Coene
> Fix For: 2.0.0-beta-2
>
>
> I have a resolver which has multiple Ivy patterns:
> {code}
> <filesystem name="tcomp-repository" checkmodified="true"
> changingPattern=".*" local="true">
> <!-- pattern for the dependencies file -->
> <ivy
> pattern="${tcomp.repository}/lcm/[module]/[module]-[revision]/lib/[module]-[revision].ivy"
> />
> <!-- pattern for the 'old-style' dependencies files -->
> <ivy
> pattern="${tcomp.repository}/lcm/[module]/[module]-[revision]/lib/[module]-[revision].dependencies"
> />
> <!-- the artifact locations -->
> <artifact
> pattern="${tcomp.repository}/lcm/[module]/[module]-[revision]/[type]/[artifact]-[revision].[ext]"
> />
> <artifact
> pattern="${tcomp.repository}/lcm/[module]/[module]-[revision]/[type]/[artifact].[ext]"
> />
> <artifact
> pattern="${tcomp.repository}/lcm/[module]/[module]-[revision]/lib/[artifact]-[revision].[ext]"
> />
> <artifact
> pattern="${tcomp.repository}/lcm/[module]/[module]-[revision]/lib/[artifact].[ext]"
> />
> <!-- source artifacts -->
> <artifact
> pattern="${tcomp.repository}/lcm/[module]/[module]-[revision]/[type]/[artifact]-[revision]-src.[ext]"
> />
> </filesystem>
> {code}
> When both files exists (for instance moduleX-1.0.ivy and
> moduleX-1.0.dependencies):
> with Ivy 1.4, the first pattern that matched was chosen. In most cases, this
> was [module]-[revision].ivy
> with Ivy 2.0.0-beta1, it seems that the last matching pattern is chosen:
> [module]-[revision].dependencies
> This can cause problems if both files defines the dependencies differently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
