Hi devs,
Context
======
Clemens fixed a bug at https://jira.xwiki.org/browse/XWIKI-15163 and while doing so inroduced a new system property to override the location of the xwiki.properties file. I commented at https://jira.xwiki.org/browse/XWIKI-15163?focusedCommentId=98075&page=com.a…
Even though it’s not necessary to introduce a new system property just for the need of this test (it’s easy to refactor the code to not need this IMO), it raises the question of what we want to do to make the configuration simpler in XWiki (simpler config, simpler upgrades, etc).
History
======
We discussed this a few times in the past:
* March 2010: http://markmail.org/message/6cvm5hocvtbqtgp6
* June 2012: https://markmail.org/message/3aq2bjrb6a2ip2ri
Note that the June 2012 proposal was agreed.
Globally this is what we implemented since the June 2012 proposal:
* XCOMMONS-187: The Permanent Data directory resolver should support System Property "xwiki.data.dir". More specifically the code is here: https://github.com/xwiki/xwiki-commons/blob/55569d3466dc0ea36f6964474973f7a…
* XWIKI-13867: Search xwiki.cfg in /etc/xwiki/ first. Code is here: https://github.com/xwiki/xwiki-platform/blob/973d4e9c6ad02dbb31d94fe96df9c1…
* XWIKI-13868: Search xwiki.properties in /etc/xwiki/ first. Code is here: https://github.com/xwiki/xwiki-platform/blob/93f02215783ac0f4030fe3062cac4d…
I’d like to note that I don’t remember discussions/proposals for XWIKI-13867/XWIKI-13868 and I commented on http://jira.xwiki.org/browse/XWIKI-13867 and didn’t get any response from my various comments.
Current behavior
=============
So right now the behavior is the following on config files (I’m excluding the recent change of Clements, see below in actions):
* If xwiki.cfg exists under the. "java:comp/env” JNDI key, then it’s used
* If not found, then search for it in /etc/xwiki/xwiki.cfg
* If not found, then default to WEB-INF/xwiki.cfg
* If /etc/xwiki.xwiki.properties exist then it’s used
* if not found, search in WEB-INF/xwiki.properties (as a ServletContext resource)
* If not found, then default to an empty configuration
Discussion/Proposal
================
* I think we should ask Clemens to rollback the introduction of the xwiki.properties.default.dir system property and to just make the test work without introducing any system property. I can help Clemens do that.
* I propose that instead we continue implementing the June 2012 proposal defined at https://markmail.org/message/3aq2bjrb6a2ip2ri and introduce the xwiki.config.dir system property.
* Right now I don’t like the solution introduced by /etc/xwiki/* because they don’t allow supporting several instances of XWiki on the same machine. However, the introduction of xwiki.config.dir system property would fix it.
* We could also introduce the user home dir location as a location where xwiki config files would be looked for.
* We also need to generalize the config files to hibernate.cfg.xml and clustering config files (jgroup files), and logback. See https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Backup#HConfi…
WDYT?
Thanks
-Vincent
PS: Sorry for the long mail, I had to do a lot of archeology to research this… Took me a while ;)
Hello devs,
I've whipped up quickly a couple of changes to the default PDF export of
the XWiki platform, to try to make it look a little nicer.
I created the issue here https://jira.xwiki.org/browse/XWIKI-15761 and the
pull request here https://github.com/xwiki/xwiki-platform/pull/900 .
I would like to merge that into master unless somebody has something
against it, so please speak up now.
Longer story:
I know that "nicer" is a subjective term, and that a lot more can be done
to improve this default PDF export. My idea was that the current defaults
we have (for the font family, for example, or the information we display in
the pdf header/footer and the style associated) are not the result of an
actual studied choice, iirc they are just defaults that were set like that
in the first version of that export and never changed. Thus, I don't see
why we couldn't slightly change these defaults (without changing the
information displayed or risking regressions) to have a slightly better
looking default PDF, while still allowing all customizations just they way
they worked before.
These modifications are not blocking nor replacing in any way the more
serious improvements that can be done on the PDF export, they're just
slightly improving the current defaults.
Best regards,
Anca
Hi xwikiers,
In the contact of bringing new Page concept (OK 7.4 is starting to get
old) to the API and macros too we decided (1) to introduce a "page"
shortcut property (even if we keep the reference/type for other
types).
While it's nicer for wiki syntax, one issue is that on WYSIWYG macros
UI side, which display all properties, it means ending up with
conflicting parameters that needs to be displayed as such.
I don't really have much clue on how best to display this so I'm
searching for ideas :)
Then I will add in the macro descriptor what's required for whatever
UI we want to build (group and sub groups of properties, etc.).
1: http://design.xwiki.org/xwiki/bin/view/Proposal/DeprecatingSpaceAndSpaceRef…
Thanks,
--
Thomas Mortagnes
Hi devs,
We now have https://dev.xwiki.org/xwiki/bin/view/Community/ServletContainerSupportStrat… but it’s not precise enough.
I’m proposing the following:
* Mention the supported version cycle and mention that we support the latest version of the cycle.
* For Tomcat, I propose to say we support Tomcat 8.x (which means Tomcat 8.5.34 as of today, see “latest” tag on https://hub.docker.com/_/tomcat/)
* For Jetty (standalone packaging or standard), I propose to say we support Jetty 9.x (which means Jetty 9.4.12 as of today, see “latest” tag on https://hub.docker.com/_/jetty/)
WDYT?
Thanks
-Vincent
Hi everyone,
I'll work this month on adding the "delete all" functionality in the
recycle bin.
However I'd like to have your opinion on how it should looks like for
the users.
I have at least 4 proposals that I detailed there:
https://design.xwiki.org/xwiki/bin/view/Proposal/Deleteallfromrecyclebin
The 4 proposal are numbered as following:
A. A simple button
B. A simple button with a checkbox to activate it
C. A button and a modal to confirm the action
D. A generic bulk action on the livetable
Thanks in advance for your feedbacks.
Simon
--
Simon Urli
Software Engineer at XWiki SAS
simon.urli(a)xwiki.com
More about us at http://www.xwiki.com
The XWiki development team is proud to announce the availability of XWiki
10.9.
Starting with this release the Activity Stream Application is fully
replaced by the Notifications Application. The list of followed users is
back in the user profile and the Page Index can be sorted by page title.
The Users and Groups administrations sections have been improved and
there's a new Page Picker Velocity macro that can be used by developers.
You can download it here: https://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.9/
Thanks for your support
-The XWiki dev team
Hi,
In the direction of keeping in commons/rendering/platform only modules that are used in the XS distribution, I’m proposing to move Doxia-based syntaxes to contrib (APT, Docbook & TWiki), in a single doxia github repository (doxia-common, doxia-twiki, doxia-docbook, doxia-twiki).
WDYT?
Thanks
-Vincent