[
https://issues.apache.org/jira/browse/IVY-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cranford updated IVY-1564:
---------------------------------
Description:
The fix for IVY-920 introduced a behavior where IVY will try to retrieve the
jar corresponding to all POM packaged artifacts. The vast majority of pom
packaged artifacts are parent POMs which have have no jars. This means IVY is
wasting time trying to retrieve jars which don't exist.
Neither Maven nor Gradle have this problem. They are able to distinguish
between a pom referenced as a parent (for which no jar should be retrieved) and
a pom packaged artifact referenced as a dependency (for which a jar should be
retrieved).
In our environment, failed lookup are particularly expensive due to timeouts,
leading to initial builds which take hours.
was:
The fix for IVY-920 introduced a behavior where IVY will try to retrieve the
jar corresponding to all POM packaged artifacts. The vast majority of pom
packaged artifacts are parent POMs which have have no jars. This means IVY is
wasting time trying to retrieve jars which don't exist.
Neither Maven nor Gradle have this problem. They are able to distinguish
between a pom referenced as a parent (for which no jar should be retrieved)
should and a pom packaged artifact referenced as a dependency (for which a jar
should be retrieved).
In our environment, failed lookup are particularly expensive due to timeouts,
leading to initial builds which take hours.
> IVY retrieves jar's for parent POMs
> -----------------------------------
>
> Key: IVY-1564
> URL: https://issues.apache.org/jira/browse/IVY-1564
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.4.0
> Reporter: Daniel Cranford
>
> The fix for IVY-920 introduced a behavior where IVY will try to retrieve the
> jar corresponding to all POM packaged artifacts. The vast majority of pom
> packaged artifacts are parent POMs which have have no jars. This means IVY is
> wasting time trying to retrieve jars which don't exist.
> Neither Maven nor Gradle have this problem. They are able to distinguish
> between a pom referenced as a parent (for which no jar should be retrieved)
> and a pom packaged artifact referenced as a dependency (for which a jar
> should be retrieved).
> In our environment, failed lookup are particularly expensive due to timeouts,
> leading to initial builds which take hours.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
