Re: downloading from CVS
Dan <[email protected]> Thu, 28 Sep 2006 04:00:24 -0700 (PDT)
| Newsgroups | gmane.comp.java.sisc.user |
|---|---|
| Message-ID | <[email protected]> |
Regarding CVS -- is there a stable SISC branch and an unstable one? I believe I asked about this in another post, just before the one you answered. If so, then posting the branch names on the web page would save a lot of trouble. That's what I meant by CVS instructions. Even for a standard CVS download (i.e. no branches), a cut-and-paste-able command line helps users. The Sourceforge CVS instructions are (i) long-winded (ii) unclear and (iii) on a slow-loading page. Yes, in the end it was the docbook stylesheet path issue. The final error is rather cryptic. Ironically, I have been bitten by this before, and forgot about it! That's because I was unsure I downloaded from the right CVS branch. -- Dan ----- Original Message ---- From: Matthias Radestock <[email protected]> To: Dan <[email protected]> Cc: [email protected] Sent: Thursday, September 28, 2006 7:40:53 AM Subject: Re: [Sisc-users] downloading from CVS Dan <[email protected]> writes: > Hi, I eventually downloaded what must be mainline SISC > using > > cvs -z3 > -d:pserver:[email protected]:/cvsroot/sisc > co -P sisc > > then tried to compile with "ant dist"; after a long > process, I ended up with > > BUILD FAILED > /usr/local/src/sisc/build.xml:513: > /usr/local/src/sisc/doc/generated/sss not found. I tried the same and it worked, completing in 1 minute 56 seconds. I suspect the problem in your case is that it cannot find the docbook stylesheets (you should have seen a message saying that) and hence fails to generate the documentation which the 'dist' target wants to include in the distribution bundle. That really only matters if either you want the docs or are building a distribution. To just do a build (w/o building a distribution) run 'ant all'. That will still complain about docbook, but you can ignore that. > There is no BUILD INSTALL or build.properties file, > and no README paragraph or anything on the website to > document the process. Please add CVS download/build > instructions somewhere. It's a standard ant build. The major ant targets are documented (you can see the docs by running the standard 'ant -projecthelp' command), though a few are missing ('dist' being one of them). We should also make the build slightly more robust so that it deals with the missing docbook stylesheets more gracefully and prominently. A short README won't hurt either. Please open bugs for these. Even better, contribute the solutions. I see no need to document the CVS download instructions since sourceforge already does that. Matthias ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV