xwiki-devs August 2018

xwiki-devs@xwiki.org

17 participants
31 discussions

[xwiki-devs] [VOTE] Update the xar plugin and stop committing XML wiki page date fields

by Eduard Moraru

Hi, devs. We have had 2 previous discussions on this topic: * July 2016 (discussion): https://markmail.org/thread/oodciq7pv6pj7eic * Jan 2018 (proposal): https://markmail.org/thread/ymwsebvr3k7voy3p And we have at least 2 issues on this topic: * Oct 2011: XWIKI-7058 <http://jira.xwiki.org/browse/XWIKI-7058>: Page creation date should be the date of the installation * Feb 2015: XCOMMONS-1447 <https://jira.xwiki.org/browse/XCOMMONS-1447>: XAR plugin should replace the dates with a common number TL;DR: It's causing confusion for our users to install pages that are created in 2005/2009/etc. so we should avoid committing dates on git that users might end up installing. Reminder: Importing a document with empty dates will: * Use the current date if the document is new (i.e. does not exist in the wiki) * Use the existing dates if the document already exists in the wiki, if using backup import * Use the current user and current date for the document update date, if imported using non-backup import of EM extension install Adel and myself have extended the xar:verify and xar:format goals of the xar plugin to check for the existence of date fields in the XML wiki pages and to remove them. The fields are: * date * contentUpdateDate * creationDate * attachment/date See the PR https://github.com/xwiki/xwiki-commons/pull/44/ This check (on both verify and format goals) is skippable entirely with the "xar.dates.skip property" (default to false) or "xar.dates.skip.documentList" for individual documents (list of doc references). I need your vote for accepting the existing PR and for removing the document dates (e.g. https://github.com/xwiki/xwiki-platform/pull/792) and your feedback in case you know of any problems that this might create. Also, please mention if you would prefer for this behavior to be skipped by default (and explicitly enabled on XWiki Standard, so that 3rd party code is not impacted by this change). Here's my +1 (enabled by default and skippable if needed). Thanks, Eduard

6 years

[xwiki-devs] [contrib] UINSCRIPT JIRA rights update

by Stéphane Laurière

Hi all, While contributing to the UINSCRIPT extension recently, I created an issue referenced by some commits. It seems that I'm not allowed to close it though. Thomas has updated my access rights to the project last week and I'm now able to create new releases – thank you – but still I cannot close the following issue which is assigned to me: https://jira.xwiki.org/browse/UINSCRIPT-3 Could anyone with admin rights please check and possibly grant me the appropriate rights or let me know how I should proceed? Cheers Stéphane -- Stéphane Laurière XWiki www.xwiki.com @slauriere

6 years

[xwiki-devs] [ANN] New committer Adel Atallah

by Thomas Mortagne

Hi everyone, I'm please to welcome Adel in the XWiki core committers family ! Congrats, you will now be able to break stuff without having to hide it in big pull requests ;) Don't worry it does not mean you are on your own now, you can still ask for review of a feature branch when you are not sure but you earned the right to be trusted :) Make sure you take a look at http://dev.xwiki.org/xwiki/bin/view/Community/Committership :) You will also have the pleasure to do XWiki releases (if you want) ! Thanks, -- Thomas Mortagne

6 years

[xwiki-devs] [ANN] XWiki 10.7 released

by Vincent Massol

The XWiki development team is proud to announce the availability of XWiki 10.7. One of the main focus of XWiki 10.7 was bug fixing thus this release starts by reducing the bug count by 33, in important areas such as as Notifications, Skin or the core. This version also contains autocomplete of links when using the WYSIWYG editor, Macro content prefill when inserting a Macro from the WYSIWYG editor, and the beginning of replacing the old XWiki Confirmation boxes with Bootstrap modals with a focus on the comments action box to start with. You can download it here: http://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.7/ Thanks for your support -The XWiki dev team

6 years

Re: [xwiki-devs] [xwiki-notifications] [xwiki-contrib/application-xcopy] 5e9148: initial revision

by Vincent Massol

Hi Stephane, Please note that all commits must have a reference to a jira issue, see https://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HJIRABe… :) Thanks! -Vincent > On 27 Aug 2018, at 17:23, GitHub <noreply(a)github.com> wrote: > > Branch: refs/heads/master > Home: https://github.com/xwiki-contrib/application-xcopy > Commit: 5e91487ea3f1bf76ca25fe5fdfcd58ddfd4084d9 > https://github.com/xwiki-contrib/application-xcopy/commit/5e91487ea3f1bf76c… > Author: Stéphane Laurière <slauriere(a)gmail.com> > Date: 2018-08-27 (Mon, 27 Aug 2018) > > Changed paths: > A .gitignore > A application-xcopy-api/pom.xml > A application-xcopy-api/src/main/java/org/xwiki/contrib/xcopy/AbstractXCopyJob.java > A application-xcopy-api/src/main/java/org/xwiki/contrib/xcopy/XCopyConfiguration.java > A application-xcopy-api/src/main/java/org/xwiki/contrib/xcopy/internal/XCopyJob.java > A application-xcopy-api/src/main/resources/META-INF/MANIFEST.MF > A application-xcopy-api/src/main/resources/META-INF/components.txt > A pom.xml > > Log Message: > ----------- > initial revision > > > > **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ > > Functionality will be removed from GitHub.com on January 31st, 2019.

6 years

[xwiki-devs] [Contrib] New application for copying pages from one wiki to another (name suggestions welcome)

by Anca Luca

Hello XWiki devs, slauriere and I have worked on an extension that copies pages from one wiki (based on a HQL query selecting them) to another wiki, allowing to exclude some class properties from objects in those pages, if the objects are present. It's coded as an async job, it can be manually triggered or scheduled with a scheduler job. We used it to implement some publication scenario, where contributors work on a set of documents on a subwiki and then these documents, if validated, get copied (published) to another subwiki periodically. The validation is based on the custom structure of those documents, using the generic feature of this extension that allows to select documents to be published based on a query. Otherwise there's nothing else related to publication in the code of the application itself. We'd like to publish this application on contrib, so can we please have a repo for it? However, we have some trouble choosing its name. The name that we used so far is "publication application" but we think it might be misleading esp. because of the similarity with publication workflow with which it has nothing to do. So, if you have an idea for a name that would correctly illustrate this work (and its future enhancements), please help us choose its name and create the repo. Thanks, Anca

6 years

[xwiki-devs] Improving tests with Descartes

by Vincent Massol

Hi devs, It would be great if you could help improve our unit tests using Descartes. This is needed for the STAMP research project (https://www.stamp-project.eu/view/main/) and will benefit XWiki by having 2 effects: * increasing the test coverage * improving the tests themselves (increasing their mutation score) Since 10.7 is 50% testing and 50% BFD, it would be great if you could spend all or a substantial part of your testing time working on this. I propose the following strategy: * You find a module you want to work on. * In that module you run: mvn clean install -Pquality -Dxwiki.pitest.skip=false * Then you check target/pit-reports/<date>/issues/index.html and verify if there are "pseudo tested" methods listed (when we have finished fixing all of those we can move to “partially tested methods”). * If there are some, then please record the current jacoco threshold and the current mutation score. * You can get the jacoco threshold by running "mvn clean install -Pquality -Dxwiki.pitest.skip=false -Dxwiki.pitest.mutationThreshold=100” (or by checking target/pit-reports/<date>/index.html, I haven’t checked yet if they are the same). * You can get the current mutation score by checking target/pit-reports/<date>/index.html * Then fix the test so that Descartes doesn’t report any pseudo tested or partially tested methods * Update the jacoco threshold and the mutation scores in the pom.xml * Send a PR on https://github.com/STAMP-project/descartes-usecases-output/tree/master/xwiki using the format already defined there. WDYT? Doable? Thanks -Vincent

6 years

[xwiki-devs] [UX][Polishing] Modals Overview

by Ecaterina Moraru (Valica)

Hi devs, I've made an overview of our usage of modals and popovers. You can find it at: https://design.xwiki.org/xwiki/bin/view/Proposal/Polishing10x/PolishingModa… Ideally we should use as few methods as possible of displaying modals/popovers/tooltips, in order to assure a consistent user experience. Also there are some components that could be deprecated / refreshed. I did my best to visually find all the locations, but I'm missing some alerts for extreme compatibility cases. Let me know if something is missing and your thoughts. Thanks, Caty

6 years

[xwiki-devs] [Brainstorming] Servlet Container support strategy

by Vincent Massol

Hi devs, Right now we have: * Supported browsers: https://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy * Supported DBs: https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy But we don’t have a list of supported Servlet Containers. I think the reason is that we considered that XWiki would work on all of them. While this is true, in practice it means testing and finding the right configuration for XWiki to work on the various contrainers. Thus it requires time and testing, thus support. For example right now lots of users have trouble making XWiki work on Wildfly or Glassfish. In the past I had worked on those and documented how to make XWiki work on them but new version have come up and XWiki has changed too and seems work is needed to document. I also added some jboss-reated config files in our distribution to make it easy and work OOB for JBoss. We might need to do that for other containers or udpate those files. So IMO we should list a subset of Servlet Containers that we official support (ie. that we actively tests and update documentation, fix code when needed). Same as for DBs and browsers, the community is welcome to provide support for more ofc. For me the supported list should be for now: * Jetty * Tomcat I’m hesitating with Wildfly and Glassfish since they’re quite popular too. It would be nice to have them but I don’t think we have the manpower ATM so I would leave them to the community for now, as a best effort. WDYT? Thanks -Vincent

6 years

[xwiki-devs] [ANN] XWiki 10.7-rc-1 released

by Alex Cotiugă

The XWiki development team is proud to announce the availability of XWiki 10.7-rc-1. Since the plan for the XWiki 10.7 is to be a bugfixing one, this release starts by reducing the bugs number with 30, in important areas as Notifications, Skin or Old Core. This version also represents the beginning of replacing the old XWiki Confirmation boxes with Bootstrap modals having the comments' actions to benefit at first. You can download it here: http://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.7RC1/ Thanks for your support -The XWiki dev team

6 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs August 2018