ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-723) Repository 404 breaks chain-resolver
Date Wed, 25 Jun 2008 10:35:45 GMT

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

Xavier Hanin resolved IVY-723.
------------------------------

       Resolution: Invalid
    Fix Version/s:     (was: 2.0)

With no more details I mark this as invalid. Please reopen with more details if required.

> Repository 404 breaks chain-resolver
> ------------------------------------
>
>                 Key: IVY-723
>                 URL: https://issues.apache.org/jira/browse/IVY-723
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core, Maven Compatibility
>    Affects Versions: 2.0.0-beta-1
>         Environment: WinXP, Java 1.6, Ant 1.7.
>            Reporter: Cody Casterline
>
> I attempted to download dependencies for hibernate and hibernate-annotations, which included
javax.transactions/jta-1.0.1B.jar.    Unfortunately, this JAR was missing from the default
maven2 repository, and resulted in a 404 error on the following file:
> http://repo1.maven.org/maven2/javax/transaction/jta/1.0.1B/jta-1.0.1B.jar
> I tried working around the problem with a custom chain resolver like the one found here:

> http://blogs.steeplesoft.com/dependency-management-with-ant-and-ivy/
> After running into another bug relating to cache/settings discrepancies detailed here:
> http://tapestryjava.blogspot.com/2006/01/maven-and-missing-java-transaction-api.html
> (which I assume is already documented elsewhere in Jira)...
> I cleared my cache and tried fetching dependencies again, only to be halted on the very
same error.
> It seems that if a repository claims to have a dependency (via its .pom, I suppose?)
but does not actually contain the JAR, a chain-resolver hangs, instead of doing what I would
expect -- that is, continuing to check the other repositories in the chain to see if the dependency
is available there.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message