You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Cody Casterline (JIRA)" <ji...@apache.org> on 2008/02/07 00:31:08 UTC

[jira] Created: (IVY-723) Repository 404 breaks chain-resolver

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.


[jira] Commented: (IVY-723) Repository 404 breaks chain-resolver

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573375#action_12573375 ] 

Xavier Hanin commented on IVY-723:
----------------------------------

Any more details on this issue? 

> 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.


[jira] Commented: (IVY-723) Repository 404 breaks chain-resolver

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566719#action_12566719 ] 

Xavier Hanin commented on IVY-723:
----------------------------------

I'm not sure this is a bug, it may be a misunderstanding of how chain work. If you don't set dual="true", a chain assumes the resolver having the metadata (pom or ivy file) also provides the jar file. If it isn't the case, it's normal it fails. Could you confirm this is not your problem, and provide your settings so that we can better investigate the issue?

> 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.


[jira] Resolved: (IVY-723) Repository 404 breaks chain-resolver

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Updated: (IVY-723) Repository 404 breaks chain-resolver

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin updated IVY-723:
-----------------------------

    Fix Version/s: 2.0

> 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
>             Fix For: 2.0
>
>
> 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.