JBoss' Wiki portlet, why not XWiki?

Sometimes, there are some unlogical choices that are being made: JBoss chooses JSPWiki as a base for their Wiki portlet in JBoss Portal. They choose to fork and trim JSPWiki (rather than contributing to it) to be able to embed a Wiki engine in their portal as a portlet. Fine. But why not choosing XWiki? XWiki:

• is a member of the JBoss Open Source Federation,
• can already be integrated in JBoss Portal,
• and moreover can also be integrated in any portlet container (The proof is that the eXo Platform already embeds XWiki as a portlet).

That’s weird, isn’t it?