March 2013 - xwiki-devs@xwiki.org

[xwiki-devs] Nexus: Staging Completed.
by Nexus Repository Manager 19 Mar '13

19 Mar '13

1 0

[xwiki-devs] Nexus: Promotion Completed.
by Nexus Repository Manager 19 Mar '13

19 Mar '13

1 0

[xwiki-devs] Nexus: Staging Completed.
by Nexus Repository Manager 19 Mar '13

19 Mar '13

1 0

[xwiki-devs] [Discussion] Set virtual=1 by default and deprecate the virtual mode API
by Eduard Moraru 15 Mar '13

15 Mar '13

Hi devs, According to the Roadmap of 5.0 [1][2] we will be deprecating the virtual mode API and moving to a virtual-by-default mode instead. The idea is that the multiwiki environment should be the default and, anyone wanting to use the single-wiki mode (as XE was doing in the past), will simply not create any subwiki. It is just pointless to have 2 products for such a simple fact and it also confuses users that have downloaded and started to use one product and later on realise that they needed the other. Also, when installing the wiki-manager and/or workspace extension(s) (because you might want to create subwikis/workspaces), there will be no need to stop the wiki, enable-virtual mode and restart it; all will be doable in the browser. Therefore, I`m sending this mail to ask your opinion about this topic, in case you might have something to say against it, and also to brainstorm on the required changes and implications on existing code so that the transition is as smooth and invisible as possible. Proposed changes: - Remove "xwiki.virtual" from xwiki.cfg(.vm) -- remove the usage of the "$xwikiCfgVirtual" maven property from xwiki-platform (, xwiki-enteprise and xwiki-manager) - Deprecate boolean com.xpn.xwiki.XWiki.isVirtualMode() (and the api.XWiki version) -- change its code to ((getVirtualWikisDatabaseNames(context).size() == 1) ? true : false) until it is removed by the deprecation process. Possibly needed changes: - Add main wiki default descriptor to xwiki-enterprise-ui (so that getVirtualWikisDatabaseNames includes the main wiki and also to avoid DNS issues (?) caused by how we handle virtual mode) -- or have it generated programmatically at startup if it does not exist (might be safer this way, since people might be using a different UI than xwiki-enterprise-ui) I will start working on this locally and see if I can spot other issues, but please share your thoughts. Thanks, Eduard ---------- [1] http://markmail.org/message/o6adfbscpidnn7zr [2] http://jira.xwiki.org/browse/XWIKI-8822

7 22

[xwiki-devs] [ANN] XWiki 4.5.2 released
by Vincent Massol 15 Mar '13

15 Mar '13

1 0

[xwiki-devs] Nexus: Promotion Completed.
by Nexus Repository Manager 15 Mar '13

15 Mar '13

1 0

[xwiki-devs] Nexus: Staging Completed.
by Nexus Repository Manager 15 Mar '13

15 Mar '13

1 0

[xwiki-devs] [Reminder] BFD#12 tomorrow the 14th
by Vincent Massol 15 Mar '13

15 Mar '13

Filter for tomorrow: http://jira.xwiki.org/issues/?filter=12203 Thanks -Vincent

4 5

Re: [xwiki-devs] [Contrib] Push XSLT Macro to xwiki-contrib
by Arnaud bourree 15 Mar '13

15 Mar '13

Hello, I'd like to push XSLT Macro extension to xwiki-contrib. XSLT Macro extension is already available at http://extensions.xwiki.org/xwiki/bin/view/Extension/XSLT+Macro Extension is actually version 1.0 and I like to push also a new version 1.1 with style-sheet parameters management. My github username is rnoboo Regards, Arnaud.

3 6

[xwiki-devs] [PROPOSAL] Make "create" right distinct so that running CreateAction on an existing document doesn't fail.
by Caleb James DeLisle 15 Mar '13

15 Mar '13

Hi, I would like to fix http://jira.xwiki.org/browse/XWIKI-8892 by making a distinct "create" right. Currently "create" is an alias for "edit" which fails if CreateAction is called on an existing document. CreateAction and the accompanying UI expect to be called on an existing document and for the name of the new document to be passed in a form parameter. I'm proposing adding a create right which aliases to "edit" on the space and wiki level but is not checked on the per-document level. WDYT? Caleb

2 1