Opened 6 years ago
Last modified 3 weeks ago
#337 assigned defect
PROBE-FILE for jar file entries accessed via http fails
| Reported by: | Evenson Not Org | Owned by: | Evenson Not Org |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.6.1 |
| Component: | interpreter | Version: | 1.2.1-dev |
| Keywords: | jar-pathname abcl-test-lisp | Cc: | |
| Parent Tickets: |
Description (last modified by )
(probe-file #P"jar:http://abcl.org/fasl/42/baz-20140105a-fasl-42.jar!/foo"
(probe-file #P"jar:http://abcl-dynamic-install.googlecode.com/files/baz-20130403a.jar!/foo")
Subtickets
Change History (10)
comment:1 Changed 6 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 6 years ago by
Currently believed to be a problem finding a class to load due to improper encapsulation of previous use of pathnames with TYPE "_".
q.v. Load.findLoadableFile()
comment:3 Changed 6 years ago by
| Owner: | set to Evenson Not Org |
|---|---|
| Priority: | major → blocker |
| Status: | new → assigned |
comment:6 Changed 6 years ago by
| Milestone: | 2.0.0 → 1.4.0 |
|---|
comment:9 Changed 4 weeks ago by
Update tests as the listed resources are returning 404.
TODO: signal 404 errors lisp side for PATHNAME operations
Note: See
TracTickets for help on using
tickets.
Not just GOOG: A newly created jar for remote FASL loads at #P"jar:http://abcl.org/fasl/42/baz-20140105a-fasl-42.jar!/" still fails the load.