Author: sebb
Date: Thu Aug 13 22:37:06 2009
New Revision: 804051
URL: http://svn.apache.org/viewvc?rev=804051&view=rev
Log:
Now using SVN
No nightly builds
Modified:
jakarta/bsf/trunk/xdocs/problems.xml
Modified: jakarta/bsf/trunk/xdocs/problems.xml
URL:
http://svn.apache.org/viewvc/jakarta/bsf/trunk/xdocs/problems.xml?rev=804051&r1=804050&r2=804051&view=diff
==============================================================================
--- jakarta/bsf/trunk/xdocs/problems.xml (original)
+++ jakarta/bsf/trunk/xdocs/problems.xml Thu Aug 13 22:37:06 2009
@@ -62,6 +62,7 @@
</p>
</subsection>
+<!--
<subsection name="Has It Been Fixed?">
<p>
After examining the debug output, if you still believe that the
@@ -84,21 +85,16 @@
optional task.
</p>
</subsection>
-
+ -->
<subsection name="Has It Been Reported?">
<p>
- If the current nightly build doesn't resolve your problem, it is
+ It is
possible that someone else has reported the issue. It is time to
look at the
-
- <!-- (old: http://issues.apache.org/bugzilla/) -->
-
<a href="http://issues.apache.org/jira/browse/BSF";>
- Apache Bug Database (jira)</a>. This system is easy to use, and
it will
- let you search the <a
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12312131";>
-
- <!-- <a
href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=BSF&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id";>
-->
-
+ Apache Bug Database (JIRA)</a>. This system is easy to use, and
it will
+ let you search the
+ <a
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12312131";>
currently open</a> and resolved bugs to see if your problem has
already been reported. If your problem has been reported, you can
see whether any of the developers have commented, suggesting
@@ -172,10 +168,9 @@
<p>
If you aren't satisfied with just filing a bug report, you can
try to find the cause of the problem and provide a fix yourself.
- The best way to do that is by working with the latest code from
CVS.
+ The best way to do that is by working with the latest code from
SVN.
Alternatively, you can work with the source code available from the
- <a
href="http://jakarta.apache.org/builds/jakarta-bsf/release/v2.4/src/";>
- source distributions</a>. If you
+ source distributions. If you
are going to tackle the problem at this level, you may want to
discuss some details first on the <nobr><code>bsf-dev</code></nobr>
mailing list. Once you have a fix for the problem, you may submit
@@ -197,9 +192,9 @@
<font face="verdana" size="-1">
diff -u Javac.java.orig Javac.java >
javac.diffs<br></br><br></br>
</font>
- or, if you have source from CVS:<br></br><br></br>
+ or, if you have source from SVN:<br></br><br></br>
<font face="verdana" size="-1">
- cvs diff -u Javac.java > javac.diffs<br></br><br></br>
+ svn diff Javac.java > javac.diffs<br></br><br></br>
</font>
Note: You should give your patch files meaningful names.
@@ -212,4 +207,4 @@
</section>
</body>
-</document>
+</document>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscr...@jakarta.apache.org
For additional commands, e-mail: bsf-dev-h...@jakarta.apache.org
