Since about a week, all HTTP requests to return an empty text/plain response, no feed. This is not the first time it has failed, not the first time without any public notice.

When I tried to find others experiencing the same problem I came along is it down right now which not only confirmed what I saw but also contained a workaround to resurrect your feed list as OPML. It was one of the latest comments further down that page and I've forgotten who had written it - strangely it is no longer there.

path: /en/personal/blogging | # | Writebacks

XMLUnit for Java 1.6 is mostly a bugfix release adressing four issues:

Note the first two changes may be breaking backwards compatibility in rare cases.

Source and binary distributions are available from SourceForge's File Service, the checksums and PGP signatures can be found here


path: /en/oss/XMLUnit | # | Writebacks

Reposting what I just sent to the xmlunit-general list for wider feedback, don't hesitate dropping me a mail if you want to stop me.

Hi all

if you are following the commits, you may have seen I've started to work
on XMLUnit 2.x again, nothing big, but I'm trying to get it done this

Apart from re-thinking the abstractions used in the difference engine
the biggest piece missing for a release - even a beta - is
documentation.  Here I realized more and more that I really do not feel
like writing a big docbook document again, I need someting more
ligthweight with more immediate feedback.  A wiki would be fine, but
we've also always had a PDF version and I'd like to keep it that way.

Also I realized I prefer git over subversion by now, so I'd like to move
2.x to git.  I know I could do so on Sourceforge, but right now I feel
it would be best to move active development over to github.  A quick
search showed several forks over there, so we may be able to reconnect
and make this a community effort rather than mostly a one-man-show.

Here is what I intend to do, please let me know if anything looks
completely wrong:

* create an xmlunit organization at github
* create three repositories (for now)
  * XMLUnit Java 2.x - including the matchers and xmlunit-legacy
  * XMLUnit .NET 2.x - including constraints
  * a pure Wiki repository for the user guide.  github markdown works
    well enough for me and pandoc can create PDF or even epub from it
    (thanks to Stefan Tilkov for pointing me at it)
* start using github's issue tracker
* create a site for XMLUnit 2.x
* keep using Sourceforge for XMLUnit 1.x
  * move XMLUnit 1.x back to svn trunk and keep it at sourceforge
  * keep using sourceforge's issue tracker for 1.x
  * keep the site for 1.x
* keep using the xmlunit-general@lists.sourceforge as primary
  communication medium for all versions
* keep the sourceforge forums even though I never liked them (or any web

path: /en/oss/XMLUnit | # | Writebacks

Last week the company I work for has published a podcast in which a colleague and I talk about the ASF, what it is, how it works and what I do there. German language only.

path: /en/personal/publications | # | Writebacks

In a project at innoQ we're using QMQP to quickly queue mail to an MTA for delivery.

Even though - or maybe because - the protocol looks rather simple, we didn't find any open source library for this. We've decided to open source our own implementation QMQP Java, version 0.1 is available from Maven central (com.innoq.qmqp:qmqp-client:0.1) under the Apache License 2.0.

This initial release is strongly tailored to our project's needs. If you want to use it and find it lacking anything, don't hesitate and use a pull request or open an issue at github.

path: /en/oss/QMQP | # | Writebacks