StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Update: Bingo!!</strong> </p> <p>Here's the Radeox <a href="http://svn.codehaus.org/radeox/" rel="nofollow noreferrer">Subversion repository</a>. Navigate down to <a href="http://svn.codehaus.org/radeox/main/trunk/src/java/org/radeox/" rel="nofollow noreferrer">http://svn.codehaus.org/radeox/main/trunk/src/java/org/radeox/</a> for the source code. </p> <p><strong>Earlier ...</strong></p> <p>Looks like Stephan Schmidt, the author, is currently running a blog at <a href="http://www.codemonkeyism.com" rel="nofollow noreferrer">http://www.codemonkeyism.com</a>. His contact information, including email is <a href="http://www.codemonkeyism.com/about/" rel="nofollow noreferrer">here</a>, and an entry from <a href="http://www.codemonkeyism.com/archives/2007/08/20/forking-radeox-a-new-wiki-render-engine/" rel="nofollow noreferrer">August 2007</a> talked about forking the project over to Reposita.org (which doesn't seem to be up yet). His <a href="http://www.codemonkeyism.com/my-presentations/" rel="nofollow noreferrer">presentations</a> put him at ImobilienScout24 last year.</p> <p>I'm sure you're attuned to the dangers of depending on a dead, unmaintained project. We just purged our software of several such dependencies and are sleeping much better. They included Axis 1.4 for SOAP web services (abandoned with serious threading bugs in 2005), replaced by vanilla Java logic; the kxml parser (also abandoned in 2005), replaced by JAXP; and a no-name HTTP client (so abandoned we couldn't find even the old source), replaced by Apache HTTP Client. Radeox sounds like a more difficult case though.</p> <p>Get legal advice, and make a strenuous effort to find the source and/or Stephan, documenting everything you do. That might be enough due dilligence to enable you to distribute binaries while you work on a replacement strategy.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload