You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Eric Anderson (JIRA)" <ji...@apache.org> on 2009/01/08 00:44:44 UTC
[jira] Created: (IVY-996) Remove excessive HEAD requests for URL
repository
Remove excessive HEAD requests for URL repository
-------------------------------------------------
Key: IVY-996
URL: https://issues.apache.org/jira/browse/IVY-996
Project: Ivy
Issue Type: Improvement
Components: Core
Affects Versions: 2.0-RC2
Reporter: Eric Anderson
h3. Fixing useless extra HEAD requests
When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
IE: /org/project/0.9.2/ivy-0.9.2.xml
This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
h3. Are HEAD requests even necessary?
Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-996) Remove excessive HEAD requests for URL
repository
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667992#action_12667992 ]
Xavier Hanin commented on IVY-996:
----------------------------------
Mmm, this is not straightforward to use a nightly in eclipse, mainly because we have a naming convention for nightlies which conflict with eclipse version naming convention. But this is pretty easy to fix, I'll try to find some time to do it and keep you informed.
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
> Fix For: trunk
>
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVY-996) Remove excessive HEAD requests for URL
repository
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin reassigned IVY-996:
--------------------------------
Assignee: Xavier Hanin
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-996) Remove excessive HEAD requests for URL
repository
Posted by "Eric Anderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668076#action_12668076 ]
Eric Anderson commented on IVY-996:
-----------------------------------
Thank you very much for your help. As soon as there is a way for me to run with this in Eclipse, I can get my guys to test it.
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
> Fix For: trunk
>
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-996) Remove excessive HEAD requests for URL
repository
Posted by "Eric Anderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667838#action_12667838 ]
Eric Anderson commented on IVY-996:
-----------------------------------
I'd love to test this from Eclipse (I have a guy in the field), however I don't know how to take a nightly and get it setup with ivyde. Any help would be great
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
> Fix For: trunk
>
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-996) Remove excessive HEAD requests for URL
repository
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-996:
------------------------------
Fix Version/s: (was: trunk)
2.0.1
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
> Fix For: 2.0.1
>
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-996) Remove excessive HEAD requests for URL
repository
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin resolved IVY-996.
------------------------------
Resolution: Fixed
Fix Version/s: trunk
I've made some modifications on trunk which should fix this as you asked: making head requests only for potential matches. I've made some testing in my environment, and it works well. I'd appreciate feedback though to know if it works for you too.
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
> Fix For: trunk
>
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-996) Remove excessive HEAD requests for URL
repository
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669636#action_12669636 ]
Xavier Hanin commented on IVY-996:
----------------------------------
Thanks to Nicolas Lalevée, an update site with trunk versions of both IvyDE and Ivy is now available here:
http://hudson.zones.apache.org/hudson/view/Ant/job/IvyDE-updatesite/lastSuccessfulBuild/artifact/trunk/build/
Please use this to test the trunk Ivy version and tell me if it works as you expect.
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
> Fix For: trunk
>
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for organization "org", Ivy attempts HEAD requests for completely not possible versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if there is an artifact (for choosing latest-release). Now, after one is chosen, if no ivy.xml file exists, I could understand trying the next one, but trying all of them, just to select the latest one anyways seems like a complete waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.