Hello,

I noticed that the published site of [VFS] has a example developer URL
for SVN which contains the tag. This might be OK for a read only URL,
but at least for the Developer URL I would rather document to check out
trunk. If I understood it correctly thats a common problem with SVN.

I noticed that the new skin in my local build is better, it talks about
trunk. But I suspect this is somewhat dynamic based on the actual
release (so it might have the same problem if generated for a tag?)

The download page has also some checkout instructions, and it talks
about trunk correctly.


== http://commons.apache.org/proper/commons-vfs/source-repository.html
# Developer access
#
# Everyone can access the Subversion repository via HTTP, but Committers must 
checkout the Subversion repository via HTTPS.
#
# $ svn checkout
# 
https://svn.apache.org/repos/asf/commons/proper/vfs/tags/commons-vfs2-project-2.0
 commons-vfs2-project
...

== source-repository.html
# Developer access
# 
# Everyone can access the Subversion repository via HTTP, but Committers
# must checkout the Subversion repository via HTTPS.
# 
# $ svn checkout
# https://svn.apache.org/repos/asf/commons/proper/vfs/trunk commons-vfs2-project


== http://commons.apache.org/proper/commons-vfs/download.html
# Building Commons VFS
#
# To obtain the Commons VFS source, you can either:
#
#    Check the source out of SVN using:
#    HEAD: svn co http://svn.apache.org/repos/asf/commons/proper/vfs/trunk vfs
#    For a certain version please look at 
http://svn.apache.org/repos/asf/commons/proper/vfs/tags


Gruss
Bernd

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to