ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Syer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IVY-1432) Artifacts that have a .pom but no .jar in local Maven cache should be skipped
Date Wed, 21 Aug 2013 14:19:52 GMT

     [ https://issues.apache.org/jira/browse/IVY-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dave Syer updated IVY-1432:
---------------------------

    Description: 
For Maven users the local cache repo can easily contain a .pom for a dependency but no corresponding
.jar.  Ivy treats this as a resolved dependency that does not exist, and hence fails, whereas
it would actually be perfectly sane to skip it (and allow another resolver to have a go).
Groovy and Gradle users experience this a lot (e.g. http://issues.gradle.org/browse/GRADLE-2034).

A simple workaround is to use a custom Repository in the {{localm2}} (in Groovy Grab terms)
resolver which answers false to {{exists()}} for the .pom resource if the corresponding .jar
is not present.

  was:
For Maven users the local cache repo can easily contain a .pom for a dependency but no corresponding
.jar.  Ivy treats this as a resolved dependency that does not exist, and hence fails, whereas
it would actually be perfectly sane to skip it (and allow another resolver to have a go).
Groovy and Gradle users experience this a lot (e.g. http://issues.gradle.org/browse/GRADLE-2034).

A simple workaround is to use a custom Repository in the {{{localm2}}} (in Groovy Grab terms)
resolver which answers false to {{{exists()}}} for the .pom resource if the corresponding
.jar is not present.

    
> Artifacts that have a .pom but no .jar in local Maven cache should be skipped
> -----------------------------------------------------------------------------
>
>                 Key: IVY-1432
>                 URL: https://issues.apache.org/jira/browse/IVY-1432
>             Project: Ivy
>          Issue Type: Bug
>            Reporter: Dave Syer
>
> For Maven users the local cache repo can easily contain a .pom for a dependency but no
corresponding .jar.  Ivy treats this as a resolved dependency that does not exist, and hence
fails, whereas it would actually be perfectly sane to skip it (and allow another resolver
to have a go). Groovy and Gradle users experience this a lot (e.g. http://issues.gradle.org/browse/GRADLE-2034).
> A simple workaround is to use a custom Repository in the {{localm2}} (in Groovy Grab
terms) resolver which answers false to {{exists()}} for the .pom resource if the corresponding
.jar is not present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message