You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Shane Witbeck (JIRA)" <ji...@apache.org> on 2008/05/13 18:51:55 UTC
[jira] Created: (BUILDR-69) Certain artifacts don't download
properly from remote repository
Certain artifacts don't download properly from remote repository
----------------------------------------------------------------
Key: BUILDR-69
URL: https://issues.apache.org/jira/browse/BUILDR-69
Project: Buildr
Issue Type: Bug
Components: Dependency management
Affects Versions: 1.2.10
Environment: Windoze
Reporter: Shane Witbeck
Priority: Minor
Certain dependencies don't download as expected from a remote repository. I notice that the icon for the struts2-core on the repository is different (not a folder like the others) if I use a browser. I suspect it's a symlink/redirect that Buildr doesn't know how to handle?
Downloading org.apache.struts:struts2-core:jar:2.0.11.1
Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar
undefined method `zero?' for nil:NilClass
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-69) Certain artifacts don't download
properly from remote repository
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597031#action_12597031 ]
Assaf Arkin commented on BUILDR-69:
-----------------------------------
Can you pinpoint the file and line number?
I tried and had no problem grabbing it with:
URI('http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar').download 'struts.jar'
I'm also seeing the bomb icon, but I'm not sure what it means. The directories underneath have the right icon, and those are not redirected, but served fro the expected URL.
> Certain artifacts don't download properly from remote repository
> ----------------------------------------------------------------
>
> Key: BUILDR-69
> URL: https://issues.apache.org/jira/browse/BUILDR-69
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.2.10
> Environment: Windoze
> Reporter: Shane Witbeck
> Priority: Minor
>
> Certain dependencies don't download as expected from a remote repository. I notice that the icon for the struts2-core on the repository is different (not a folder like the others) if I use a browser. I suspect it's a symlink/redirect that Buildr doesn't know how to handle?
> Downloading org.apache.struts:struts2-core:jar:2.0.11.1
> Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar
> undefined method `zero?' for nil:NilClass
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-69) Certain artifacts don't download
properly from remote repository
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Assaf Arkin resolved BUILDR-69.
-------------------------------
Resolution: Cannot Reproduce
> Certain artifacts don't download properly from remote repository
> ----------------------------------------------------------------
>
> Key: BUILDR-69
> URL: https://issues.apache.org/jira/browse/BUILDR-69
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.2.10
> Environment: Windoze
> Reporter: Shane Witbeck
> Priority: Minor
>
> Certain dependencies don't download as expected from a remote repository. I notice that the icon for the struts2-core on the repository is different (not a folder like the others) if I use a browser. I suspect it's a symlink/redirect that Buildr doesn't know how to handle?
> Downloading org.apache.struts:struts2-core:jar:2.0.11.1
> Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar
> undefined method `zero?' for nil:NilClass
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-69) Certain artifacts don't download
properly from remote repository
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597676#action_12597676 ]
Assaf Arkin commented on BUILDR-69:
-----------------------------------
I think that happens when the server returns a response without the Content-Length header. I'll add a fix for Buildr to avoid the exception.
However, you're accessing the maven.org repository here, which runs on Apache. Apache always returns the Content-Length header (essentially the file size), so if you're getting a 200 OK response with no Content-Header, check the proxy server. Unfortunately, if the proxy server decides to send back empty responses, you may end up with zero-sized JARs in your local repository.
> Certain artifacts don't download properly from remote repository
> ----------------------------------------------------------------
>
> Key: BUILDR-69
> URL: https://issues.apache.org/jira/browse/BUILDR-69
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.2.10
> Environment: Windoze
> Reporter: Shane Witbeck
> Priority: Minor
>
> Certain dependencies don't download as expected from a remote repository. I notice that the icon for the struts2-core on the repository is different (not a folder like the others) if I use a browser. I suspect it's a symlink/redirect that Buildr doesn't know how to handle?
> Downloading org.apache.struts:struts2-core:jar:2.0.11.1
> Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar
> undefined method `zero?' for nil:NilClass
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-69) Certain artifacts don't download
properly from remote repository
Posted by "Shane Witbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597113#action_12597113 ]
Shane Witbeck commented on BUILDR-69:
-------------------------------------
I forgot to mention that I suspect this might be a firewall issue since it seems to work some of the time.
> Certain artifacts don't download properly from remote repository
> ----------------------------------------------------------------
>
> Key: BUILDR-69
> URL: https://issues.apache.org/jira/browse/BUILDR-69
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.2.10
> Environment: Windoze
> Reporter: Shane Witbeck
> Priority: Minor
>
> Certain dependencies don't download as expected from a remote repository. I notice that the icon for the struts2-core on the repository is different (not a folder like the others) if I use a browser. I suspect it's a symlink/redirect that Buildr doesn't know how to handle?
> Downloading org.apache.struts:struts2-core:jar:2.0.11.1
> Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar
> undefined method `zero?' for nil:NilClass
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-69) Certain artifacts don't download
properly from remote repository
Posted by "Shane Witbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597100#action_12597100 ]
Shane Witbeck commented on BUILDR-69:
-------------------------------------
I found more information on the bomb icon from an old mailing list post:
"If you use Apache to automatically generate a fancy index, it will auto-
matically give you icons for various files and types. If the file ends
with the string "core," apache assumes it is a core file and sends back
the bomb icon be default"
So it seems that just by virtue of struts-core ending in core is why we see the bomb icon instead of the folder icon.
I've also verified the same download from the same repo works on a Mac for both versions of Buildr (1.2.10 and 1.3.0).
Below is a trace of the failure on Windows XP with Buildr version 1.2.10:
Downloading org.apache.struts:struts2-core:jar:2.0.11.1
Downloading org.apache.struts:struts2-core:jar:2.0.11.1
Requesting http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-c
ore-2.0.11.1.jar
Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-
core-2.0.11.1.jar
undefined method `zero?' for nil:NilClass
c:/ruby/lib/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/progressbar.rb:166:in `show_p
rogress'
c:/ruby/lib/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/progressbar.rb:50:in `initial
ize'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:248:in `new'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:248:in `with_progress_
bar'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:330:in `read'
c:/ruby/lib/ruby/1.8/net/http.rb:1062:in `request'
c:/ruby/lib/ruby/1.8/net/http.rb:2145:in `reading_body'
c:/ruby/lib/ruby/1.8/net/http.rb:1061:in `request'
c:/ruby/lib/ruby/1.8/net/http.rb:957:in `request_get'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:317:in `read'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:355:in `[]'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:355:in `read'
c:/ruby/lib/ruby/1.8/net/http.rb:547:in `start'
c:/ruby/lib/ruby/1.8/net/http.rb:440:in `start'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:355:in `read'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:153:in `download'
c:/ruby/lib/ruby/1.8/tempfile.rb:172:in `open'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:151:in `download'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/transports.rb:77:in `download'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/java/artifact.rb:312:in `download'
c:/ruby/lib/ruby/1.8/fileutils.rb:243:in `find'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/java/artifact.rb:309:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/java/artifact.rb:309:in `find'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/java/artifact.rb:309:in `download'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/java/artifact.rb:258:in `initialize'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `call'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `execute'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `execute'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:13:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:6:in `synchronize'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:6:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/java/compile.rb:219:in `invoke_prerequisi
tes'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `send'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/java/compile.rb:219:in `invoke_prerequisi
tes'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:12:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:6:in `synchronize'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:6:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/project.rb:244:in `local_task'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/project.rb:280:in `[]'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/project.rb:280:in `local_projects'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/project.rb:280:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/project.rb:280:in `local_projects'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/project.rb:242:in `local_task'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `call'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `execute'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:27:in `execute'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:13:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:6:in `synchronize'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/rake_ext.rb:6:in `invoke'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `each'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in `standard_exception_handling
'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in `top_level'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/application.rb:54:in `run'
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in `standard_exception_handling
'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/lib/core/application.rb:51:in `run'
c:/ruby/lib/ruby/gems/1.8/gems/buildr-1.2.10/bin/buildr:7
c:/ruby/bin/buildr:19:in `load'
c:/ruby/bin/buildr:19
> Certain artifacts don't download properly from remote repository
> ----------------------------------------------------------------
>
> Key: BUILDR-69
> URL: https://issues.apache.org/jira/browse/BUILDR-69
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.2.10
> Environment: Windoze
> Reporter: Shane Witbeck
> Priority: Minor
>
> Certain dependencies don't download as expected from a remote repository. I notice that the icon for the struts2-core on the repository is different (not a folder like the others) if I use a browser. I suspect it's a symlink/redirect that Buildr doesn't know how to handle?
> Downloading org.apache.struts:struts2-core:jar:2.0.11.1
> Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar
> undefined method `zero?' for nil:NilClass
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-69) Certain artifacts don't download
properly from remote repository
Posted by "Shane Witbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597108#action_12597108 ]
Shane Witbeck commented on BUILDR-69:
-------------------------------------
This is apparently fixed. I just tested on Windows with both versions of Buildr and the struts-core jar now downloads as expected.
> Certain artifacts don't download properly from remote repository
> ----------------------------------------------------------------
>
> Key: BUILDR-69
> URL: https://issues.apache.org/jira/browse/BUILDR-69
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.2.10
> Environment: Windoze
> Reporter: Shane Witbeck
> Priority: Minor
>
> Certain dependencies don't download as expected from a remote repository. I notice that the icon for the struts2-core on the repository is different (not a folder like the others) if I use a browser. I suspect it's a symlink/redirect that Buildr doesn't know how to handle?
> Downloading org.apache.struts:struts2-core:jar:2.0.11.1
> Downloading http://repo1.maven.org/maven2/org/apache/struts/struts2-core/2.0.11.1/struts2-core-2.0.11.1.jar
> undefined method `zero?' for nil:NilClass
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.