October 2015 - xwiki-devs@xwiki.org

[xwiki-devs] [proposal] Process to handle Pull Requests
by Ludovic Dubost 10 May '19

10 May '19

Hi devs, I don't think there is currently a process that is in place to handle pull requests and I have the feeling that the way there are handled today is a bit random. There are usually comments sent out on each pull request but sometimes it seems that some pull requests are going in sleep mode and it's not clear who is in charge. I would like to suggest that a process is put in place where it's clear who is responsible for a pull request and a status is given to the contributors that propose that pull request. Something like: Assigned developer: XXXX Status: New -> new pull request, not yet assigned Assigned -> assigned to a developer, he is in charge of reviewing the pull request and ask for modifications or accept it. The developer can auto assign it to himself. If nobody does, we need to decide how they will be taken into account. ModificationsRequired -> for now rejected with comments. Contributor needs to apply comments and then change back to Assigned for further evaluation VoteRequired -> there are no more comments, but a vote is required as the changes to XWiki core are important WaitingFinalAuthorization -> optional step for complex patches where a additional authorization would be required (need to define who would be the persons that give the authorization) WaitingApplication -> there are no more comments and no changes or vote required. The pull request can be applied and is waiting for a developer to apply it Abandoned -> contributors is abandoning the pull request (cannot do the changes, no more time, etc..) Rejected -> pull request is rejected (quality not enough, etc..) Applied -> pull request is applied What do you think ? Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

7 12

[xwiki-devs] [Vote] Assignee for PR: Contributor or Committer?
by Ecaterina Moraru (Valica) 07 May '18

07 May '18

Hi, We have discussed this subject multiple times, but we don't have an official vote and conclusion on the topic. Problem: In JIRA who is the Assignee of an issue fixed by a Pull Request? 1: Contributor - he provided the solution - giving the attributions, the contributor might feel encouraged to contribute more - we could do some JIRA statistics on external contributions, but this use case can be covered by GitHub statistics 2: Committer - he does the merging on his account and he becomes responsible for the committed code. - in case there are problems, the committer needs to find solution, since we can't rely on contributors availability - in doing the PR review, the committer spends a lot of time analyzing and testing the provided solution We are talking here about complete solutions provided by the PR, since in case of partial solutions, the committer can assign himself on the issue (depends on the quantity of modification he does). Let me know what you think, Caty

9 11

[xwiki-devs] [Proposal] 2 new rules for Application Best Practices
by vincent＠massol.net 03 Oct '16

03 Oct '16

Hi devs, Following our implementation of NS/NP in 7.2 I’d like to propose 2 new best practices for app dev that we would list at http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra… 1) New rule 1: “Code” subspace Current text: * Generally, put all your pages in a single space dedicated for the application you're developing (e.g. Faq, Scheduler, IRC, AppWithinMinutes, etc). The name must be as short as possible while still being understandable of course and without overusing abbreviations. New version: * Generally, put all your pages in a single space dedicated for the application you're developing (e.g. Faq, Scheduler, IRC, AppWithinMinutes, etc). The name must be as short as possible while still being understandable of course and without overusing abbreviations. * Technical pages should be put in a subspace named “Code” Note: this rule can only be applied for new applications for now since the EM doesn’t know how to follow renames currently so for example if I move pages from the FAQCode space to the FAQ.Code space, when EM upgrades the app, it’ll display all pages in FAQCode as deleted (basically it considers all pages in FAQ.Code as new pages and pages in FAQCode as deleted pages). Note: I’ve created http://jira.xwiki.org/browse/XWIKI-12622 for this. 2) New rule 2: * Technical pages without children must be terminal pages. WDYT? Thanks -Vincent

15 52

[xwiki-devs] Deployment issue on jboss (Wildfly)
by Pankraz, Alexander (HP DualStudy) 05 Sep '16

05 Sep '16

Hello dears, i have a issue with deployment of xwiki version 6.1 (actual stable version) on a jboss environment. I get three issues. I was able to fix 2 of them. These two issues are missing classes... I use jboss 8.1 alias Wildfly. I tried deployment over cmd and web-application with a .war file. I also tried this on other devices. Used Java Version last stable 7. The third issue is this one: "{\"JBAS014671: Failed services\" => {\"jboss.deployment.unit.\\\"xwiki.war\\\".WeldStartService\" => \"org.jboss.msc.service.StartException in service jboss.deployment.unit.\\\"xwiki.war\\\".WeldStartService: Failed to start service Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000075: Normal scoped managed bean implementation class has a public field: [EnhancedAnnotatedFieldImpl] public org.restlet.ext.jaxrs.internal.provider.JaxbElementProvider.contextResolver\"}}" I would be very grateful if you could help me with this issue. Here the full deployment log: 2014-08-04 08:05:24,517 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final 2014-08-04 08:05:24,846 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final 2014-08-04 08:05:24,934 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015899: WildFly 8.1.0.Final "Kenny" starting 2014-08-04 08:05:24,944 DEBUG [org.jboss.as.config] (MSC service thread 1-5) Configured system properties: awt.toolkit = sun.awt.windows.WToolkit file.encoding = Cp1252 file.encoding.pkg = sun.io file.separator = \ java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment java.awt.printerjob = sun.awt.windows.WPrinterJob java.class.path = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\jboss-modules.jar java.class.version = 51.0 java.endorsed.dirs = C:\Program Files\Java\jdk1.7.0_45\jre\lib\endorsed java.ext.dirs = C:\Program Files\Java\jdk1.7.0_45\jre\lib\ext;C:\Windows\Sun\Java\lib\ext java.home = C:\Program Files\Java\jdk1.7.0_45\jre java.io.tmpdir = C:\Users\pankraz\AppData\Local\Temp\ java.library.path = C:\Program Files\Java\jdk1.7.0_45\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\RA2HP\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\ActivIdentity\ActivClient\;C:\Program Files (x86)\ActivIdentity\ActivClient\;C:\Program Files (x86)\Hewlett-Packard\HP ProtectTools Security Manager\Bin\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files\Microsoft SQL Server\110\DTS\Binn\;c:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;c:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files\Java\jdk1.7.0_45\bin;C:\Program Files\MiKTeX 2.9\miktex\bin\x64\;C:\Program Files (x86)\MySQL\MySQL Utilities\;C:\Program Files\Java\jdk1.7.0_45\bin;C:\Program Files (x86)\GUI Turbo Assembler\BIN;C:\Program Files\Microsoft Network Monitor 3\;C:\Program Files (x86)\Calibre2\;. java.net.preferIPv4Stack = true java.runtime.name = Java(TM) SE Runtime Environment java.runtime.version = 1.7.0_45-b18 java.specification.name = Java Platform API Specification java.specification.vendor = Oracle Corporation java.specification.version = 1.7 java.util.logging.manager = org.jboss.logmanager.LogManager java.vendor = Oracle Corporation java.vendor.url = http://java.oracle.com/ java.vendor.url.bug = http://bugreport.sun.com/bugreport/ java.version = 1.7.0_45 java.vm.info = mixed mode java.vm.name = Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name = Java Virtual Machine Specification java.vm.specification.vendor = Oracle Corporation java.vm.specification.version = 1.7 java.vm.vendor = Oracle Corporation java.vm.version = 24.45-b08 javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory jboss.home.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final jboss.host.name = pankraz1 jboss.modules.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\modules jboss.modules.system.pkgs = org.jboss.byteman jboss.node.name = pankraz1 jboss.qualified.host.name = pankraz1 jboss.server.base.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone jboss.server.config.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\configuration jboss.server.data.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\data jboss.server.deploy.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\data\content jboss.server.log.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\log jboss.server.name = pankraz1 jboss.server.persist.config = true jboss.server.temp.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\tmp line.separator = logging.configuration = file:C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\configuration/logging.properties module.path = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\modules org.jboss.boot.log.file = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\log\server.log org.jboss.resolver.warning = true org.xml.sax.driver = __redirected.__XMLReaderFactory os.arch = amd64 os.name = Windows 7 os.version = 6.1 path.separator = ; program.name = standalone.bat sun.arch.data.model = 64 sun.boot.class.path = C:\Program Files\Java\jdk1.7.0_45\jre\lib\resources.jar;C:\Program Files\Java\jdk1.7.0_45\jre\lib\rt.jar;C:\Program Files\Java\jdk1.7.0_45\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.7.0_45\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.7.0_45\jre\lib\jce.jar;C:\Program Files\Java\jdk1.7.0_45\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.7.0_45\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.7.0_45\jre\classes sun.boot.library.path = C:\Program Files\Java\jdk1.7.0_45\jre\bin sun.cpu.endian = little sun.cpu.isalist = amd64 sun.desktop = windows sun.io.unicode.encoding = UnicodeLittle sun.java.command = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\jboss-modules.jar -mp C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final sun.java.launcher = SUN_STANDARD sun.jnu.encoding = Cp1252 sun.management.compiler = HotSpot 64-Bit Tiered Compilers sun.os.patch.level = Service Pack 1 user.country = US user.country.format = DE user.dir = C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\bin user.home = C:\Users\pankraz user.language = en user.language.format = de user.name = pankraz user.script = user.timezone = Europe/Paris user.variant = 2014-08-04 08:05:24,946 DEBUG [org.jboss.as.config] (MSC service thread 1-5) VM Arguments: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\log\server.log -Dlogging.configuration=file:C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\configuration/logging.properties 2014-08-04 08:05:26,580 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) 2014-08-04 08:05:26,600 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.2.2.Final 2014-08-04 08:05:26,609 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.2.2.Final 2014-08-04 08:05:26,674 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors 2014-08-04 08:05:26,691 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem 2014-08-04 08:05:26,694 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension 2014-08-04 08:05:26,695 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. 2014-08-04 08:05:26,693 INFO [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem 2014-08-04 08:05:26,712 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem. 2014-08-04 08:05:26,721 INFO [org.jboss.as.security] (MSC service thread 1-8) JBAS013170: Current PicketBox version=4.0.21.Beta1 2014-08-04 08:05:26,752 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main] 2014-08-04 08:05:26,807 INFO [org.jboss.as.connector.logging] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.5.Final) 2014-08-04 08:05:26,819 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 2014-08-04 08:05:26,880 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = h2 2014-08-04 08:05:26,886 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.0.15.Final starting 2014-08-04 08:05:26,918 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017502: Undertow 1.0.15.Final starting 2014-08-04 08:05:26,921 INFO [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service 2014-08-04 08:05:26,922 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default] 2014-08-04 08:05:27,004 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.3.Final 2014-08-04 08:05:27,099 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final/welcome-content 2014-08-04 08:05:27,103 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017525: Started server default-server. 2014-08-04 08:05:27,127 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017531: Host default-host starting 2014-08-04 08:05:27,481 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\pankraz\Downloads\Testdaten01\wildfly-8.1.0.Final\standalone\deployments 2014-08-04 08:05:27,483 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "xwiki.war" (runtime-name: "xwiki.war") 2014-08-04 08:05:46,728 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 2014-08-04 08:05:46,983 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 2014-08-04 08:05:47,269 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final 2014-08-04 08:06:01,341 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xerces-2.5.0.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/batik-rasterizer-1.7.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,342 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xalan-2.6.0.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/batik-rasterizer-1.7.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,343 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xml-apis-1.3.04.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/batik-rasterizer-1.7.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,343 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry fop-0.94.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/batik-rasterizer-1.7.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,344 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry batik-js.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/batik-rasterizer-1.7.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,470 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry emory-util-io.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/emory-util-classloader-2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,472 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry emory-util-security.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/emory-util-classloader-2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,479 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry emory-util-io.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/emory-util-security-2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,486 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry avalon-framework-4.2.0.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,498 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry batik-all-1.7.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,513 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry commons-io-1.3.1.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,529 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry commons-logging-1.0.4.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,533 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry fop-hyph.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,546 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry serializer-2.7.0.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,562 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry servlet-2.2.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,574 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xalan-2.7.0.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xercesImpl-2.7.1.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,592 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xml-apis-1.3.04.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/fop-1.0.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,639 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry commons-io-1.4.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jodconverter-core-3.0-beta-4-xwiki-20110822.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,641 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry commons-cli-1.1.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jodconverter-core-3.0-beta-4-xwiki-20110822.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,646 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry sigar-1.6.5.132.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jodconverter-core-3.0-beta-4-xwiki-20110822.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,650 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry json-20090211.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jodconverter-core-3.0-beta-4-xwiki-20110822.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,655 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry ridl.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/juh-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,663 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jurt.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/juh-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,665 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry ../../lib/ in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/juh-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,671 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry ../bin/ in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/juh-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,680 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry ridl.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jurt-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,684 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry unoloader.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jurt-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,686 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry ../../lib/ in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jurt-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,698 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry ../bin/ in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/jurt-3.2.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,709 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry slf4j-api-1.6.1.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/netcdf-4.2.20.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,711 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry commons-logging-1.0.4.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/netcdf-4.2.20.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,713 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry commons-codec-1.2.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/netcdf-4.2.20.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,732 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jakarta-oro.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/radeox-1.0-b2.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,734 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry commons-logging.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/radeox-1.0-b2.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,744 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry picocontainer.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/radeox-1.0-b2.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,750 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xml-apis.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,761 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry slf4j-api-1.6.1.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/unidataCommon-4.2.20.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,766 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xercesImpl.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,768 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xml-apis.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:01,776 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry serializer.jar in /C:/Users/pankraz/Downloads/Testdaten01/wildfly-8.1.0.Final/bin/content/xwiki.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 2014-08-04 08:06:03,963 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016002: Processing weld deployment xwiki.war 2014-08-04 08:06:04,077 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.1.0.Final 2014-08-04 08:06:04,313 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016005: Starting Services for CDI deployment: xwiki.war 2014-08-04 08:06:05,188 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.1.2 (Final) 2014-08-04 08:06:05,236 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment xwiki.war 2014-08-04 08:06:09,184 WARN [org.jboss.modules] (weld-worker-1) Failed to define class org.apache.hadoop.hdfs.web.resources.UserProvider in Module "deployment.xwiki.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link org/apache/hadoop/hdfs/web/resources/UserProvider (Module "deployment.xwiki.war:main" from Service Module Loader) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final] at org.jboss.as.weld.WeldModuleResourceLoader.classForName(WeldModuleResourceLoader.java:68) [wildfly-weld-8.1.0.Final.jar:8.1.0.Final] at org.jboss.weld.bootstrap.BeanDeployer.loadClass(BeanDeployer.java:106) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:94) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:62) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:60) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] Caused by: java.lang.NoClassDefFoundError: com/sun/jersey/spi/inject/InjectableProvider at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_45] at java.lang.ClassLoader.defineClass(ClassLoader.java:800) [rt.jar:1.7.0_45] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.3.Final] ... 19 more Caused by: java.lang.ClassNotFoundException: com.sun.jersey.spi.inject.InjectableProvider from [Module "deployment.xwiki.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final] ... 23 more 2014-08-04 08:06:09,267 INFO [org.jboss.weld.Bootstrap] (weld-worker-1) WELD-000119: Not generating any bean definitions from org.apache.hadoop.hdfs.web.resources.UserProvider because of underlying class loading error: Type com.sun.jersey.spi.inject.InjectableProvider from [Module "deployment.xwiki.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error. 2014-08-04 08:06:15,400 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."xwiki.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xwiki.war".WeldStartService: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000075: Normal scoped managed bean implementation class has a public field: [EnhancedAnnotatedFieldImpl] public org.restlet.ext.jaxrs.internal.provider.JaxbElementProvider.contextResolver at org.jboss.weld.bean.ManagedBean.checkBeanImplementation(ManagedBean.java:218) at org.jboss.weld.bean.AbstractClassBean.internalInitialize(AbstractClassBean.java:74) at org.jboss.weld.bean.ManagedBean.internalInitialize(ManagedBean.java:96) at org.jboss.weld.bean.RIBean.initialize(RIBean.java:65) at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$5.doWork(ConcurrentBeanDeployer.java:114) at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$5.doWork(ConcurrentBeanDeployer.java:112) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53) at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45] ... 3 more 2014-08-04 08:06:15,468 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "xwiki.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"xwiki.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xwiki.war\".WeldStartService: Failed to start service Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000075: Normal scoped managed bean implementation class has a public field: [EnhancedAnnotatedFieldImpl] public org.restlet.ext.jaxrs.internal.provider.JaxbElementProvider.contextResolver"}} 2014-08-04 08:06:15,556 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "xwiki.war" (runtime-name : "xwiki.war") 2014-08-04 08:06:15,560 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."xwiki.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xwiki.war".WeldStartService: Failed to start service 2014-08-04 08:06:15,603 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 2014-08-04 08:06:15,604 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 2014-08-04 08:06:15,605 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 51415ms - Started 307 of 412 services (51 services failed or missing dependencies, 91 services are lazy, passive or on-demand) 2014-08-04 08:06:15,813 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016009: Stopping weld service for deployment xwiki.war 2014-08-04 08:06:20,720 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment xwiki.war (runtime-name: xwiki.war) in 4916ms 2014-08-04 08:06:20,837 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "xwiki.war" (runtime-name: "xwiki.war") 2014-08-04 08:06:20,856 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.deployment.unit."xwiki.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".WeldInstantiator, JBAS014799: ... and 22 more ] service jboss.deployment.unit."xwiki.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator, service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".WeldInstantiator, service jboss.deployment.unit."xwiki.war".component."org.xwiki.rest.internal.XWikiRestletServlet".WeldInstantiator, JBAS014799: ... and 19 more ] service jboss.deployment.unit."xwiki.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.sun.faces.config.ConfigureListener".START] service jboss.deployment.unit."xwiki.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.sun.faces.config.ConfigureListener".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.gwt.api.server.XWikiServiceImpl".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.gwt.api.server.XWikiServiceImpl".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.gwt.api.server.XWikiServiceImpl".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.gwt.api.server.XWikiServiceImpl".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.gwt.api.server.XWikiServiceImpl".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavFilter".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavFilter".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavFilter".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavServlet".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavServlet".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.plugin.webdav.XWikiDavServlet".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.ActionFilter".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.ActionFilter".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.ActionFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.ActionFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.ActionFilter".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.HomePageRedirectServlet".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.HomePageRedirectServlet".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.HomePageRedirectServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.HomePageRedirectServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.web.HomePageRedirectServlet".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".START] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".START] service jboss.deployment.unit."xwiki.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."javax.faces.webapp.FacetTag".START] service jboss.deployment.unit."xwiki.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."javax.faces.webapp.FacetTag".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."javax.faces.webapp.FacetTag".START] service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] service jboss.deployment.unit."xwiki.war".component."org.apache.struts.action.ActionServlet".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.apache.struts.action.ActionServlet".START] service jboss.deployment.unit."xwiki.war".component."org.apache.struts.action.ActionServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.apache.struts.action.ActionServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.apache.struts.action.ActionServlet".START] service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".START] service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".START] service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".START] service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.SetThreadNameServletRequestListener".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.SetThreadNameServletRequestListener".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.SetThreadNameServletRequestListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.SetThreadNameServletRequestListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.SetThreadNameServletRequestListener".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.XWikiServletContextListener".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.XWikiServletContextListener".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.XWikiServletContextListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.XWikiServletContextListener".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.rest.internal.XWikiRestletServlet".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.rest.internal.XWikiRestletServlet".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.rest.internal.XWikiRestletServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.xwiki.rest.internal.XWikiRestletServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.rest.internal.XWikiRestletServlet".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.XWikiRemoteServiceServlet".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.XWikiRemoteServiceServlet".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.XWikiRemoteServiceServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.XWikiRemoteServiceServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.XWikiRemoteServiceServlet".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.ConversionFilter".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.ConversionFilter".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.ConversionFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.ConversionFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.ConversionFilter".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.XWikiContextInitializationFilter".CREATE (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.XWikiContextInitializationFilter".START] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.XWikiContextInitializationFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki, service jboss.deployment.unit."xwiki.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.XWikiContextInitializationFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."org.xwiki.wysiwyg.server.filter.XWikiContextInitializationFilter".START] service jboss.deployment.unit."xwiki.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] service jboss.deployment.unit."xwiki.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."xwiki.war".component."com.sun.faces.config.ConfigureListener".START, service jboss.deployment.unit."xwiki.war".component."org.xwiki.container.servlet.SetThreadNameServletRequestListener".START, service jboss.deployment.unit."xwiki.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".START, service jboss.deployment.unit."xwiki.war".component."com.xpn.xwiki.xmlrpc.XWikiXmlRpcServlet".START, JBAS014799: ... and 18 more ] service jboss.undertow.deployment.default-server.default-host./xwiki (missing) dependents: [service jboss.deployment.unit."xwiki.war".deploymentCompleteService] service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki] service jboss.undertow.deployment.default-server.default-host./xwiki.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./xwiki.UndertowDeploymentInfoService] JBAS014777: Services which failed to start: service jboss.deployment.unit."xwiki.war".WeldStartService best regards Alexander Pankraz Student HP DualStudy Wirtschaftsinformatik - Software Engineering Hewlett-Packard GmbH alexander.pankraz(a)hp.com<mailto:[email protected]> Hewlett-Packard-Strasse 1 | 61352 Bad Homburg | http://www.hp.com/de/dualstudy [http://intranet.hp.com/country/germany/live/PublishingImages/NeuesLogoSmall…] Geschäftsführer: Heiko Meyer (Vorsitzender), Thomas Bässler, Volkhard Bregulla, Michael Eberhardt, Jochen Erlach, Angelika Gifford, Ernst Reichart Vorsitzender des Aufsichtsrats: Jörg Menno Harms Sitz der Gesellschaft: Böblingen, Amtsgericht Stuttgart HRB 244081 WEEE-Reg.-Nr. DE 30409072 Follow us on [http://intranet.hp.com/country/germany/live/PublishingImages/facebook.gif] <http://www.facebook.com/HPDeutschland> [http://intranet.hp.com/country/germany/live/PublishingImages/twitter.gif] <https://twitter.com/HP_Deutschland> [http://intranet.hp.com/country/germany/live/PublishingImages/linkedin.gif] <http://www.linkedin.com/company/hewlett-packard?trk=tabs_biz_home> [http://intranet.hp.com/country/germany/live/PublishingImages/youtube.gif] <http://www.youtube.com/user/HPDeutschland>

3 2

[xwiki-devs] Convention for class property hints ?
by Jerome Velociter 18 Jul '16

18 Jul '16

Hello, Right now class property hints are not supported right in the core of XWiki (though it's been mentioned as a possible future item of the roadmap for AWM, see http://markmail.org/message/ltuphlj7bnnso2yb ). Once this will be implemented, it will rely on i18n message keys so that hints are localizables (same strategy as for class property pretty names) I'd like to start the discussion and see if we can agree on a convention that would be used in the future when this module is implemented. The reason for this is I'm starting to work on a LDAP admin UI, and I find that their field pretty names are not self-explanatory. It's not a matter of expression, it's just the fact that what they describe needs more explanation than what the pretty name can offer). In this light, I'm planning on displaying such longer hints in this admin section. Right now the format for a pretty name is : Space.Class_property=Pretty name The format for a hint could be something like : Space.Class_property.xHint=Hint This would need escaping rules I think, since I believe "property.xHint" is a valid property name Note that I use "xHint" and not "hint" to be consistent with the form standards class names. This can be discussed though. WDYT ? Do you have other ideas ? Jerome. -- Jérôme Velociter Winesquare http://www.winesquare.net/

5 7

[xwiki-devs] Integration of ratings in xwiki-platform
by Victor Rachieru 29 Jun '16

29 Jun '16

Hei devs, I intend to integrate the ratings application which is now on xwiki-contrib into the xwiki-platform. This in mainly due to 3 points: ----- 1/ give the ability to use ratings in a wiki 2/ using it to provide ratings for the Extension Repository Application (XWIKI-7780) 3/ display ratings within Extension Manager (XWIKI-11509) The first point can be accomplished by using the ratings app as is but the other two imply that the ratings app should be a module that is maintained by XWiki. It makes sense that if the Extension Repository App and Extension Manager which are maintained by XWiki depend on the Ratings App, that this itself is maintained by XWiki as well. The steps needed for this is as follows: ----- 1/ create a new module in the xwiki-platform core for the ratings - xwiki-platform-core -- xwiki-platform-ratings --- xwiki-platform-ratings-api --- xwiki-platform-ratings-ui 2/ change the artifact id from "application-ratings" to "xwiki-platform-ratings" 3/ change the package from "org.xwiki.contrib.ratings" to "org.xwiki.platform.ratings" Implications ----- 1/ clone of the existing code is now in xwiki-platform under a different artifact id (having duplicate code, this takes us to #2) 2/ the code from xwiki-contrib would probably have to be deemed as "retired" 3/ the applications with a dependency to the xwiki-contrib ratings would have to be upgraded to depend on the module from xwiki-platform 4/ the script service would remain unchanged (changing the artifact id and package name does not affect the service) 5/ if by any chance someone has code that uses the classes from the ratings app on contrib, by upgrading, that code will cease to function Please state you position on this matter. Links ----- http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+API http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+Application https://github.com/xwiki-contrib/application-ratings Thank you, Victor

7 8

[xwiki-devs] [Proposal] Releasing a contrib project - Guidelines
by vincent＠massol.net 03 Mar '16

03 Mar '16

Hi devs, I’d like to propose to add some guidelines to contrib.xwiki.org when someone wants to release a project, especially when that person is not the project lead. * The person wanting to do the release should contact the project lead, preferable either through IRC or the mailing list to mention its intent to perform a new release. ** This allows anyone who also want to have some issue fixed be able to do so in the same release for example. ** Usually that person will not have the permission to create a version in JIRA for that project and thus he/she’ll need the Project Lead’s help for that WDYT? Thanks -Vincent

4 11

[xwiki-devs] [Idea] Sponsoring issues
by Vincent Massol 04 Feb '16

04 Feb '16

Hi devs, WDYT of doing like Jenkins is doing and adding a "Sponsor this issue" button on JIRA? For example: https://issues.jenkins-ci.org/browse/JENKINS-9030 When you click it redirects to http://www.freedomsponsors.org/core/login/?next=/core/issue/sponsor%3Ftrack… You can check http://www.freedomsponsors.org/ It could be interesting to try it and see how it goes. WDYT? Thanks -Vincent

8 16

[xwiki-devs] [Proposal] XWiki Core
by vincent＠massol.net 21 Jan '16

21 Jan '16

Hi committers (and devs in general), I’m submitting to you this idea, to try to improve the xwiki open source project and to give it a new dynamism. I believe the topics discussed below are made even more important since we’re soon going to develop the notion of flavors in XWiki. Note that this proposal obsoletes the http://markmail.org/message/4hglttljiio5v2km proposal (i.e. the move of some extensions in the xwiki github organization), which itself was obsoleting http://markmail.org/message/ppw2slpgqou2ihai Issues to solve =============== * The scope of the code maintained by the XWiki Dev Team (== the xwiki github organization) is increasing but the team stays relatively small * The more stuff we move into the repos of the xwiki github organization, the less easy it is for non-“XWiki Dev Team” committers to participate and we want more contributions Proposed solution ================= Executive summary: * Reduce the scope of all the code located in the xwiki github organization by only keeping “core” modules * A “core" module is defined by being a generic transversal module (i.e. that can be used in lots of XWiki flavors, if not all). This is opposed to “vertical” modules which are modules specific of a usage of XWiki. ** Examples of “core" modules: logging module, configuration module, distribution wizard, statistics application, annotations, active installs, one base flavor (the “XWiki” flavor), etc ** Example of “vertical” modules: meeting manager application, blog application, FAQ application, flavors (except the base flavor), etc Some consequences: * We need a new location for several modules that would go out of the xwiki github organization repos * It would be good to separate sandbox extensions from 1st class extensions that are maintained and developed following best practices. We need some way to maintain the quality of important extensions Detailed Implementation: * The “xwiki” github organization’s description becomes “XWiki Core” (it’s too complex to rename the org to “xwiki-core” IMO) * “XWiki Dev Team” becomes the “XWiki Core Team” (and committers in there are called “XWiki Core Committers”). * “xwiki-contrib” is split into 2 github organizations (technically we rename it to “xwiki-contrib-sandbox”): ** “xwiki-contrib-sandbox” (or “xwiki-incubator”), where newly proposed extensions or abandoned extensions are located ** “xwiki-contrib-extensions”, where maintained extensions are located. * These 2 organizations are commonly referred to as “XWiki Contrib" * Same as now, anyone requesting a repo in xwiki-contrib-sandbox would be granted one and he/she’d be given write access to all repos in the xwiki-contrib-sandbox organization. * We define some rules for graduating from xwiki-contrib-sandbox to xwiki-contrib-extensions. For example: ** The extension should have been in xwiki-contrib-sandbox at least 6 months (this gives time to see if the extension is maintained during that time and will survive the test of time - most extensions will die in the first months) ** The extension should have had more than 2 releases and be published on extensions.xwiki.org(http://extensions.xwiki.org) with documentation ** The extension should work with the latest LTS version of XWiki + the latest stable version of XWiki (right now that would be 5.4.5 + 6.3). Note that if the extension has to use new API it’s ok that it doesn’t work on the latest LTS. ** Generally follow the practices defined at http://dev.xwiki.org * Each extension in xwiki-extensions has a leader/maintainer. He/she’s the one proposing to move the extension from xwiki-sandbox to xwiki-extensions. He/she’s responsible for ensuring that the extension gets regular releases and is maintained in general. He/she defines initially the list of committers in his email proposal for moving the extension. * We create a PMC (Project Management Committee) for XWiki Contrib, generally in charge of both xwiki-contrib-sandbox and xwiki-contrib-extensions (voting new extensions in xwiki-contrib-extensions, vote new PMC members, etc). To bootstrap it, I would send a mail on devs@ asking who’s interested to be part of this committee. I expect some core committers + some contrib committers to stand up. * Contrib extensions keep using the org.xwiki.contrib package name and groupid as currently defined at http://contrib.xwiki.org Note: The idea is that xwiki core is developed as a team maintaining all code in there, xwiki contrib is developed extension by extension (each extension is an island). This allows anyone to propose extensions in XWiki Contrib without the need for everyone to support them. WDYT? Thanks -Vincent

8 24

[xwiki-devs] [Proposal] Bundle a Dashboard Gadget with Apps as a best practice
by vincent＠massol.net 12 Jan '16

12 Jan '16

Hi devs, On http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra… we list some app dev best practices. I’m proposing to add one more bullet point which is that apps bundle one or several (but at least one) Dashboard Gadget (technically a Macro) so that users can easily add a view of the app on the home page (in their dashboard). For example: * FAQ app already provides a {{faq}} gadget to list all entries for a given FAQ app * Index app already provides a {{document}} gadget to list all documents matching some criteria * Blog app doesn’t currently provide such a gadget (it provides a velocity macro but that’s not a gadget) * Forum app should provide a {{forums}} gadget too to list all forums and a {{forum}} one to list entries from a given forum * etc WDYT? Thanks -Vincent

7 7

[xwiki-devs] [VOTE] Stop bundling the Statistics Application by default in XE
by Vincent Massol 08 Jan '16

08 Jan '16

Hi devs, Since statistics are disabled by default, I'm proposing to not bundle the Statistics application by default. Admins who want to enable stats on their would need to install it through the EM. In addition, the Stats app's quality is not exactly perfect either and performances are not that great so I think it makes sense to not promote it too much either. Last, since 5.3M2 the stats app is now visible in the Applications Panel (for Admins), thus not bundling it by default seems even more needed now IMO. WDYT? Thanks -Vincent

9 14

[xwiki-devs] [Proposal] Remove TinyMCE files from the XWiki WAR
by vincent＠massol.net 14 Dec '15

14 Dec '15

Hi devs, Here’s what I commented on https://github.com/xwiki/xwiki-platform/pull/307 : “ Thanks Pascal. I've just noticed that we still bundle TinyMCE in XWiki's WAR. It was probably left for backward compatibility but since it's been like 6-7 years that we've dropped it, I believe we could vote about dropping it from our sources and if someone really needs it they'll still be able to manually install them in their wikis. I'll follow up on the devs list, thanks. “ WDYT? Are you ok to remove it? Thanks -Vincent

9 17

[xwiki-devs] [Brainstorming] Wiki vs Nested Spaces
by vincent＠massol.net 25 Nov '15

25 Nov '15

Hi devs, With 7.2 the differences between Wiki and Nested Spaces are smaller and we’re probably going to have more and more questions related to when should a user use a Wiki and when should he/she use a Space. Thus I’ve started http://design.xwiki.org/xwiki/bin/view/Proposal/WikivsNestedSpaces It would be great if you could either reply on this thread with differences that you see (and I’ll update the page) or update that page directly (preferred :)). Once the page has good data, I’ll move the content to the documentation proper. Thanks! -Vincent

5 11

[xwiki-devs] [Survey] Feedback about XWiki and future features
by vincent＠massol.net 21 Nov '15

21 Nov '15

Hi, In previous years the xwiki.org project launched surveys about features we’d like to see implemented in XWiki (see http://www.xwiki.org/xwiki/bin/view/Main/Feedback) After some discussions with fellow XWikiers we thought it could be interesting to launch a similar survey in 2015, especially with the 8.x cycle approaching. But this time instead of having a long list of features to vote on, we thought it might be more interesting to have a few open questions that the community could answer. The aim of this short survey is to find out more about how satisfied (or not!) the members of the XWiki community are with the XWiki product. We'd be happy to learn about: * what you like / dislike about the product * the features and improvements you’d like to see in the product in the future and especially for XWiki 8.x The survey will run till November 13 and the results will be synthesised and made available mid-November through a blog post on the community blog ( http://blog.xwiki.org/xwiki/bin/view/Blog/ ) The survey has 6 questions and should only take a few minutes: http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiProduct2015 Thanks a lot for your contributions and for helping improve the product, -Silvia & Vincent

3 6

[xwiki-devs] [Idea] Page Administration
by Ecaterina Moraru (Valica) 19 Nov '15

19 Nov '15

Hi devs, So this proposal appeared in some of my proposals but right now I created a proper Proposal/Idea mail for it. It's about having an 'Administer Page' section in the menus, similar to the 'Administer Wiki' and 'Administer Space' functionality. The 'Administer Page' will be accessible to global admins, page creators and users with (edit?/admin?) rights for the page. >From what we currently have implemented it should contain the 'Rights Editor' (?editor=rights) at page level. In the future we could make 'Presentation', 'Page Elements' or 'Panel Wizard' to be more granular and be set at Page level (have different panels and style for just one page). Some screenshots at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/PageAdministration Thanks, Caty

5 9

[xwiki-devs] Watchlist icons improvements
by Guillaume "Louis-Marie" Delhumeau 04 Nov '15

04 Nov '15

Hi. The other thread about the content menus re-organization has deviated to talk about the watchlist, so I prefer to continue the discussion on this new thread. I have made some mock-ups that you can see there: http://design.xwiki.org/xwiki/bin/view/Proposal/WatchListButtonsonXE73 WDYT? Thanks, -- Guillaume Delhumeau (gdelhumeau(a)xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project

5 26

[xwiki-devs] [Proposal] Improvements to the Create/Delete/Move/Rename UIs
by vincent＠massol.net 02 Nov '15

02 Nov '15

Hi devs, Some users have raised that when you click on the pencil icon in the Create/Delete/Move/Rename UIs, the user has to understand the “dot notation” (ie the reference notation) and that it’s not user-friendly for simple users. Here’s what I propose: 1) Only display the pencil icon (and thus the advanced controls) for Advanced Users. 2) Note that we were doing this initially but it was modified to fix http://jira.xwiki.org/browse/XWIKI-12526. The idea would be to fix XWIKI-12526 differently by modifying how we perform validation on the title field: if the title field is empty, don’t expand the location edit controls and just highlight the title field (for simple users). 3) (suggested by Edy): Introduce controls in the modal document picker (tree) for creating empty documents in place (similar to creating new folders in an operating system's folder picker, where you would create new folders until you achieve the hierarchy you desire). We could even think about using a template (e.g. space homepage) for these "placeholder" documents. E.g. http://i.stack.imgur.com/umdE9.png http://www.mclures.net/java/struts/Together/Struts-screenshots/create_proje… (contextual menu) etc... The advantage of this would be that it would make more sense to simple users and it would also be something they could use. Of course, one downside would be the extra empty/placeholder documents that it would create, but you have the same thing in a filesystem, more or less. WDYT? Thanks -Vincent

6 5

[xwiki-devs] [Brainstorming] Feel like trying Gitter.im?
by vincent＠massol.net 01 Nov '15

01 Nov '15

Hi devs, I feel it would help the XWiki project if we had some chat infrastructure more user-friendly than IRC channel (which is currently mostly used by the xwiki developers and a few power contributors/users). I think it would help spread xwiki more and be more friendly to our community (btw the same should be done for the mailing list by moving the user mailing list to a forum but that’s for another thread). I wonder if you guys would be interested to moving to another tool such as Gitter.im: https://gitter.im/ It seems to be nice for open communities. Nicer than Slack anyway (I’ve tried Slack for another community I’m in and we quickly reached the 10K messages and it’s not nice to have this red reminder message and you loose some messages that you can’t see - See http://blog.freecodecamp.com/2015/06/so-yeah-we-tried-slack-and-we-deeply-r…) Of course another strategy would be to ask a company to host a tool for us, such as http://www.mattermost.org/ but setting it up and maintaining it has a price and we’d need to convince some company like XWiki SAS to do that and I’m not sure it’s worth it. Let me know what you think and if you’re ok to try it, I’ll set up an org on gitter so that we can make an experiment and try it out. Thanks -Vincent

4 9

[xwiki-devs] ShortURLs on 7.2?
by Paul Libbrecht 30 Oct '15

30 Oct '15

Hello XWiki community, I moved to shortURLs. The tutorial has been nicely effective. The home page serves well, the entry page of my wiki and my space all work well. However, almost all the pages that are there now break at view (with or without the action /bin/view/ in the URL). Similarly, /download/ breaks with 404. These are mostly pages in confluence syntax but moving them to xwiki syntax doesn't change anything. They display: A problem occurred while trying to process your request. Please contact the webmaster if this happens again. Their link is obtained in the index or tree views. These pages work fine at /edit/, save, and /preview/. With some debugging I seem to reach the error that: "No row with the given identifier exists" (at XWikiHibernateStore.loadXWikiDoc). Could it be that the ReferenceSerializer is behaving differently with ShortURLs? That seems bad. Why would it be different in /edit/ action? Is it changed on 7.3 candidates? thanks in advance. Paul

4 3

[xwiki-devs] [Contrib] Request for 'livetable-checkbox-column' contrib project
by Raluca Stavro 29 Oct '15

29 Oct '15

I would like to contribute a new extension that adds the option to select the rows of a livetable by inserting a new column with checkboxes in the table. See more details there : http://extensions.xwiki.org/xwiki/bin/view/Extension/Add+Checkbox+Column+To… . Can someone please create the "livetable-checkbox-column" on xwiki-contrib for me ? Thank you, Raluca.

2 2

[xwiki-devs] [ANN] XWiki 7.3 Milestone 2 released
by Thomas Mortagne 29 Oct '15

29 Oct '15

The XWiki development team is proud to announce the availability of XWiki 7.3 Milestone 2. This is the first of the 2 stabilization releases that happen at the end of each yearly Cycles. Lots of polishing has been done, especially for the recently introduced Nested Pages feature and its consequences on the UI redesign (modified menus for example). Some extensions started exploit nested spaces to bring some improvements. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki73M2 The following people have contributed code to this release: Clemens Robbenhaar Eduard Moraru Guillaume Delhumeau Marius Dumitru Florea Sergiu Dumitriu Thomas Mortagne Vincent Massol Thanks for your support -The XWiki dev team -- Thomas Mortagne

1 0

[xwiki-devs] [Proposal] Extract the DocumentTree macro from the Index App
by vincent＠massol.net 27 Oct '15

27 Oct '15

Hi devs, I see that the DocumentTree macro is used more and more in several places (as it should) and I’d like to propose to extract the DocumentTree macro from the Index App. Proposal 1: =========== xwiki-platform-tree |_ xwiki-platform-tree-generic |_ ... |_ xwiki-platform-tree-document |_ ... Proposal 2: =========== xwiki-platform-index |_ xwiki-platform-index-ui |_ xwiki-plarform-index-tree |_ … WDYT? Any other proposal? Personally I prefer proposal 1. Thanks -Vincent

5 9

[xwiki-devs] [Proposal] Register global wiki macro at wiki level when the macro document is in a subwiki
by Denis Gervalle 27 Oct '15

27 Oct '15

Hi devs, It looks like a bug to me, but wiki macro defined for global level in a subwiki, are effectively influencing the whole farm. I would like to change that like this: * global level macro are registered global only if defined in the main wiki * global and wiki level macro defined in a subwiki are registered at wiki level The rationals are: * if the same global macro document is deployed on more than one wiki, which just means the same extension defining that document is installed on multiple wiki, maybe in different version, all those macros will be in conflict, it will not be easy to know which one wins, and even more difficult to detect the problem in the first place. * there is risk (of course limited by the PR), that user of subwiki influence the behaviors of the whole farm, which IMO is quite opposite to the logical structure, and even the physical storage we are used to. * I do not see any benefit of putting a global macro in a subwiki wdyt ? -- Denis Gervalle SOFTEC sa - CEO

5 6

[xwiki-devs] Status about Hidden pages + Future direction
by vincent＠massol.net 27 Oct '15

27 Oct '15

Hi everyone, I wasn’t sure about current rule for hiding pages so I researched it and I’m listing below what I believe is our current status. I’d like to document it on dev.xwiki.org if we’re ok with this status. Current rules: ============== * Technical documents must be hidden * Technical apps must be hidden and not appear in the Document Tree. These are apps that don’t generate content data. For example the following apps (not exhaustive list) have their pages hidden (including WebHome): ** Stats app ** Active Installs app ** AWM app ** Color Themes app (it generates data but not content data) ** Dashboard app ** Scheduler app * Apps that generate content pages (ie pages that should be appear in global search results) must have their WebHome page not hidden (and the generated content pages must also not be hidden). As a consequence these apps will appear in the Document Tree. Future: ======= It would also be nice to discuss if in the future we wish to separate more Apps from Content and hide all Application pages (including Webhome), so that it is less confusing for users who would: * Use the App bar to navigate to applications * Use the Document Tree to navigate to content pages I personally would like this I think but the current problem is that generated content pages won’t be found in global search results. Each app can provide a specialized search ofc but it’s not good enough. Thus we’d need to find a way for the entries to appear in the global search results even though they are hidden. One solution would be to have a way to mark a space as an application space and exclude those from the DocumentTree (for example). Before we dive into the solutions in details, would you agree that it would be good to better separate Apps from Content? Some Links: =========== * Currently documented best practices about hiding technical documents: http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra… * Mail thread: http://xwiki.475771.n2.nabble.com/Brainstorming-Rules-for-hidden-documents-… * JIRA issue: http://jira.xwiki.org/browse/MOCCACAL-85 Thanks -Vincent

5 7

[xwiki-devs] [Brainstorming] Best practices regarding nested XClasses
by Marius Dumitru Florea 23 Oct '15

23 Oct '15

Hi devs, While fixing XWiki.ClassSheet to work with classes defined in nested spaces, I realized that if the class is defined in a non-terminal (WebHome) document then XWiki.ClassSheet creates WebHomeSheet and WebHomeTemplate, which made me wonder: (1) Does it make sense to have a class defined in a non-terminal (WebHome) document? One good thing about it, I guess, is that we could group the sheet, template and any class related pages (e.g. translation page for class properties) under the class document itself. Path.To.DiagramClass |- Sheet |- Template This would be consistent with the old parent-child relationship were we use to set the class as the parent of the sheet and template. (2) What naming convention should we use for classes defined in non-terminal documents? If we keep the sheet and the template as (terminal?) siblings of the class then we should use the current naming convention: Path.To.DiagramClass.WebHome Path.To.DiagramSheet Path.To.DiagramTemplate If we nest the sheet and the template inside the class then we could have: Path.To.DiagramClass.WebHome <-- this is the class Path.To.DiagramClass.Sheet Path.To.DiagramClass.Template We could also group the class, sheet and template like this: Path.To.Diagram.Class Path.To.Diagram.Sheet Path.To.Diagram.Template i.e. when you create a class you create a space with 3 terminal documents. WDYT? Thanks, Marius

2 1