User: user57  
  Date: 02/03/07 16:27:59

  Modified:    src/docs/developers/guide buildsystem-faq.jsp
  Log:
   o more FAQ for your FAQ'ing pleasure...
  
  Revision  Changes    Path
  1.6       +85 -1     newsite/src/docs/developers/guide/buildsystem-faq.jsp
  
  Index: buildsystem-faq.jsp
  ===================================================================
  RCS file: /cvsroot/jboss/newsite/src/docs/developers/guide/buildsystem-faq.jsp,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- buildsystem-faq.jsp       8 Mar 2002 00:04:28 -0000       1.5
  +++ buildsystem-faq.jsp       8 Mar 2002 00:27:59 -0000       1.6
  @@ -3,7 +3,7 @@
      <jsp:param name="SLOGAN" value="BUILD SYSTEM FAQ"/>
   </jsp:include>
   
  -<!-- $Id: buildsystem-faq.jsp,v 1.5 2002/03/08 00:04:28 user57 Exp $ -->
  +<!-- $Id: buildsystem-faq.jsp,v 1.6 2002/03/08 00:27:59 user57 Exp $ -->
   
   <jsp:include page="/common/picateam.jsp" flush="true"/>
   
  @@ -150,6 +150,90 @@
      You may need to build <em>clean</em> before each test to avoid getting
      old results in the report, or simply delete the 
      <tt>./testsuite/output/reports</tt> directory before running the tests.
  +
  +<p>[<a href="#Contents">Contents</a>]
  +
  +<!-- ==================================================================== -->
  +
  +<h2>I can not log into cvs, why?</h2>
  +
  +<p>If you are using anonymous CVS access you might have forgotten to
  +   log in, try this:
  +
  +<pre class="command">
  +cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/jboss login
  +</pre>
  +
  +<p>There is no password, so just press enter (ie. leave it blank).
  +
  +<p>For more information see the JBoss CVS page at 
  +   <a href="http://sourceforge.net/cvs/?group_id=22866";>Source Forge</a>.
  +
  +<p>[<a href="#Contents">Contents</a>]
  +
  +<!-- ==================================================================== -->
  +
  +<h2>I am lazy, just show me how to get the sources from CVS.</h2>
  +
  +<pre class="command">
  +cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/jboss login
  +cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/jboss get jboss-all
  +</pre>
  +
  +<p>There is no password, so just press enter (ie. leave it blank).
  +
  +<p>For more information see the JBoss CVS page at 
  +   <a href="http://sourceforge.net/cvs/?group_id=22866";>Source Forge</a>.
  +
  +<p>[<a href="#Contents">Contents</a>]
  +
  +<!-- ==================================================================== -->
  +
  +<h2>What are the nessicary CVS modules to build JBoss?</h2>
  +
  +<p>All you need to build the latest development version of JBoss is
  +   the <tt>jboss-all</tt> module.  
  +
  +<p>Do not bother with the details of individual modules... it is just 
  +   not worth the trouble.  Grab <tt>jboss-all</tt> and get on with your life.
  +
  +<p>For more information look <a href="/developers/cvs.jsp">here</a>.
  +
  +<p>[<a href="#Contents">Contents</a>]
  +
  +<!-- ==================================================================== -->
  +
  +<h2>I can not find the <tt>jboss-all</tt> module anywhere... why does this 
work?</h2>
  +
  +<p>The <tt>jboss-all</tt> module (and others) are created by definitions in
  +   CVSROOT/modules.  Have a look at the latest version 
  +   <a 
href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/jboss/CVSROOT/modules?rev=HEAD";>here</a>.
  +   
  +<p>The exact details of this file, how it works are beyond the scope of this
  +   simple FAQ... rather beyond my patience to write at the moment.
  +
  +<p>[<a href="#Contents">Contents</a>]
  +
  +<!-- ==================================================================== -->
  +
  +<h2>Why doesn't <tt>cvs update</tt> work?</h2>
  +
  +<p>When the structure of a module created from CVSROOT/modules changes,
  +   <tt>cvs update</tt> will not fully update the module.  This is due
  +   to a difficency in CVS, where update does not consult the CVSROOT/modules
  +   file for changes.  It will only use the information it all ready has
  +   in local CVS directories.
  +
  +<p>For this reason, when the structure of module changes, you will need to
  +   either re-checkout the module, or update the structure by hand.
  +
  +<p>If there were no structure changes, but update still does not get all of
  +   the changes, you might need to use to <tt>-d</tt> switch, to force
  +   update to create new directories:
  +
  +<pre class="command">
  +cvs update -d
  +</pre>
   
   <p>[<a href="#Contents">Contents</a>]
   
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to