archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak" <wsm...@gmail.com>
Subject Should Archiva browse differentiate between present-but-empty and non-existent directories?
Date Wed, 21 Jan 2009 00:37:25 GMT
A user at work brought up this question about Archiva browse.  He
noticed that it doesn't differentiate between a directory that's
present but empty, and one that just doesn't exist.  For example, this
displays a browse repository page even though there is no
com/example/does/not/exist/stuff path in any of the managed repos:

http://localhost:8080/archiva/browse/com.example.does.not.exist/stuff/

Similarly, you get the same "Unable to find project model" error from
   http://localhost:8080/archiva/browse/com.example.does.not.exist/stuff/1.0-SNAPSHOT
as you do from
   http://localhost:8080/archiva/browse/com.example/myproject/1.0-SNAPSHOT
(assuming com/example/myproject/1.0-SNAPSHOT *does* exist, but
contains no artifacts.)

Should Archiva display something different if the underlying directory
exists vs. if it doesn't?

-- 
Wendy

Mime
View raw message