You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Ilya (JIRA)" <ji...@apache.org> on 2015/07/06 06:45:04 UTC
[jira] [Updated] (IVY-1527) Artifacts are not updated if project is
used both as parent and dependency
[ https://issues.apache.org/jira/browse/IVY-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya updated IVY-1527:
----------------------
Description:
Consider the following projects:
1. Project A with an artifact attached
2. Project B, that references A through <extends>
3. Project C, that references A through <dependency changing="true"> and B through <extends>
Disclaimer: I agree that this is a weird setup, but I didn't see it prohibited anywhere either. Please correct me if I'm wrong.
If we now try to resolve C for the first time, everything will go fine.
However, if we update A's artifact and resolve C again, then A's artifact will not be re-downloaded.
was:
Consider the following projects:
1. Project A with an artifact attached
2. Project B, that references A through <extends>
3. Project C, that references A through <dependency changing="true"> and B through <extends>
Disclaimer: I agree that this is a weird setup, but I didn't see it prohibited anywhere either. Please correct me if I'm wrong.
If we now try to resolve C for the first, everything will go fine.
However, if we update A's artifact and resolve C again, then artifact will not be re-downloaded.
> Artifacts are not updated if project is used both as parent and dependency
> --------------------------------------------------------------------------
>
> Key: IVY-1527
> URL: https://issues.apache.org/jira/browse/IVY-1527
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.4.0
> Environment: Linux host 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> Reporter: Ilya
>
> Consider the following projects:
> 1. Project A with an artifact attached
> 2. Project B, that references A through <extends>
> 3. Project C, that references A through <dependency changing="true"> and B through <extends>
> Disclaimer: I agree that this is a weird setup, but I didn't see it prohibited anywhere either. Please correct me if I'm wrong.
> If we now try to resolve C for the first time, everything will go fine.
> However, if we update A's artifact and resolve C again, then A's artifact will not be re-downloaded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)