Hi Mark, On Feb 2, 2008, at 3:16 AM, Mark Brouwer wrote:
Hi all,I recently mentioned that it might be confusing for people what part ofthe svn tree they have to pick (due to the reorganization). Well that confusing already arose. What shall we do? delete river/trunk or is there another way to make it invisible?
You could make river/trunk contain a README file that explains why the obvious choice isn't the right one.
README:You have checked out the river/trunk module, and probably didn't realize that there's nothing here. The river community has decided to split river into two parts.
At river/jtsk/trunk you can find the part of the river project that deals with ...
Craig
Another thing I bumped into, it appears that I edited the Confluence Wiki to show the right svn location to utilize by people who want to grap the source but again these changes didn't propagate to the River generated website. This is Confluencehttp://cwiki.apache.org/confluence/display/RIVER/Source+Code and this is the River site http://incubator.apache.org/river/RIVER/source- code.htmlSo it looks like changes in some pages propagate, while others don't (I think the Confluence inclusion mechanism is causing this). Is there a solution to this, or a way I can trigger generation of the whole website (I think I need admin rights for that).Thanks, -- Mark
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
