- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [Proposal] Future of XAR Import/Export code

by Vincent Massol

Hi devs, We are trying to reduce the size of oldcore (been working on it for years ;)). We currently have code for XAR import and export in several places in oldcore. I’d like to define the strategy that we’d like to follow in the future for moving this code out. Let’s see what we have and what it could become: * An existing ‘filter" module outside of oldcore to import/export XAR. * An action for exporting a XAR: ExportAction. Future: make it a new URL type with components as we’ve done for webjars * An action for importing a XAR: ImportAction. Future: make it a new URL type with components as we’ve done for webjars * A UI at the page level to export a page as a XAR. Future: add an UIXP in export_modal.vm and plugin the XAR option as an UIX * 2 Uis in the admin to import and export XARx. Future: convert those for ConfigurableClass. * A legacy “packaging” plugin with oldcode to import XARs. Future: retire it in xwiki-contrib and rewrite the Import/Export Admin UI to use the new XAR filter from the filter module. * Ancillary classes such as XARImport*/XARExport* events. So the question is where to put those? Proposal: xwiki-platform-xar ===================== I think what would make the most sense would be to continue the XAR module started by Thomas: xwiki-platform-xar. It would go like this: xwiki-platform-xar |_ xwiki-platform-xar-api (what’s currently in xwiki-platform-xar + Java code from oldcore defined above) |_ xwiki-platform-xar-ui (the ui part of the oldcore code above) |_ xwiki-platform-xar-filter (the move from xwiki-platform-filter-stream-xar) WDYT? The other option that I like less would be to group everything under the filter module but it doesn’t seem good. I’d prefer to keep this module generic as much as possible and have “business” modules using it (XAR import/export, Confluence import/export, MediaWiki,import/export, etc). Thanks -Vincent

9 years

3
3
0 0

[xwiki-devs] [ANN] A new extension released on Contrib: Limits Application

by Guillaume Delhumeau

Hello. I just have released the first version of a new application in contrib, the Limits Application. This extension prevents the creation of too many users or wikis in an instance. It can also limits the number of members of any global group you want. The reason behind the creation of this application is the need, for XWiki hosters, to add some restrictions on their instances to save their resources. For example, a virtual machine handling a lot of users needs more memory: it's fair that the client pay more to push back these limits. See: http://extensions.xwiki.org/xwiki/bin/view/Extension/Limits+Application/ Thanks, -- Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project

9 years

1
0
0 0

Re: [xwiki-devs] [Proposal] Move out Chart Macro + Renderer to Contrib

by Eduard Moraru

Hi, Let`s think about active installs. The client module (i.e. the one doing the work and reporting) can be considered core, but the server module (the one receiving and showing a UI of the collected data) is not really core and can be moved to contrib. This will also fix the chart macro issue, since it's the server/ui module depending on it and not the client-api one. Thanks, Eduard On Sun, Sep 11, 2016 at 8:45 PM, Vincent Massol <vincent(a)massol.net> wrote: > > > On 11 Sep 2016, at 19:24, Vincent Massol <vincent(a)massol.net> wrote: > > > > Hi devs, > > > > I’d like to propose: > > * move out the Chart Macro + Renderer to Contrib since it’s not core. > > * still depend on it in the XE distribution for now. However if everyone > feels that it’s not needed to have it by default for users and that it’s > better to let them install it, I’m also fine. But right now I prefer to > have it by default. > > > > WDYT? > > hmm there’s a small problem… Right now the Active Installs module uses the > chart macro… > > And Statistics UI too. I guess this one could be moved to contrib easily > (we don’t bundle it anymore by defaultà. > > However for ActiveInstalls it’s more complex, unless we don’t want to > consider it core but I don’t think we want that… > > So it means either we stop using the chart macro there (which would be a > shame) or we consider the chart macro core… > > Any idea? > > Thanks > -Vincent > > > Thanks > > -Vincent > > > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs >

9 years

4
12
0 0

[xwiki-devs] [Proposal] Move XE as a flavor, rename it and distribute the platform distribution instead

by Vincent Massol

Hi devs, We have a platform distribution that allows users to pick the flavor they wish to use. However we’re currently not advertising it. Instead we’re currently advertising XE on the xwiki.org download pages. I’m proposing that we change that: * Advertise the platform distribution in the download pages of xwiki.org. We would simply call it “XWiki”, e.g. XWiki 8.3. * Move existing xwiki-platform-distribution/xwiki-platform-flavor into xwiki-platform-distribution/xwiki-platform-flavors/xwiki-platform-flavor-base * Create a new flavor in xwiki-platform-distribution/xwiki-platform-flavors/xwiki-platform-flavor-<new name here> * I’m proposing to name this new flavor "Knowledge Base” (and the module xwiki-platform-distribution/xwiki-platform-flavors/xwiki-platform-flavor-kb) since this is what most users use XWiki for. The idea, initially, would simply be to use the same deps as XE and maybe remove the Blog app (or not). * Stop distributing the XE packagings We’re already well into the XWiki 8.3 dev (M2 is planned for tomorrow Monday) so it seems a bit ambitious to do this for 8.3. We could do it for 8.4 though. WDYT? Outstanding questions: * How do we upgrade existing users using XE? WDYT? Thanks -Vincent

9 years

5
6
0 0

[xwiki-devs] [ANN] XWiki 8.3 Milestone 2 released

by Eduard Moraru

The XWiki development team is proud to announce the availability of XWiki 8.3 Milestone 2. This is a minor milestone release that adds new template provider restrictions, improved support for the WildFly application server, default support for Let's Encrypt certificates and 26 additional bugfixes which contribute to stabilizing XWiki. 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/ReleaseNotesXWiki83M2 Thanks for your support -The XWiki dev team

9 years

1
0
0 0

[xwiki-devs] [Brainstomring] Size of XE distribution - What are the next steps?

by Vincent Massol

Hi devs, FYI here’s how the size of our XE distribution has evolved over the years: https://www.evernote.com/l/AHe8M7Mpc8dLYbLXUUR4BNshyArvRhxM2e4 The sad news is that we’re working to reduce the size of the core for some time already but globally over the years the XE size is still growing. We started going in the right direction in XE 6.3 and 6.4: * XE 6.2 = 222MB * XE 6.3 = 212MB * XE 6.4 = 210MB But then starting with XE 7.0 we started to increase the XE size again: * XE 7.0 = 211MB * XE 7.1 = 225MB * XE 7.2 = 226MB * XE 7.3 = 230MB * XE 7.4 = 230MB * XE 8.0 = 229MB * XE 8.1 = 230MB * XE 8.2 = 233MB FTR at some point we had: * XE 2.0 = 79MB * XE 3.0 = 111MB * XE 4.0 = 142MB * XE 5.0 = 181MB * XE 6.0 = 211MB Any idea of what we could do to back to reducing the size of XE? Some idea: * Remove the GWT Editor (close to 10MB) * Introduce a check in the build to fail it when the distribution goes over, say, 0.5% more of a threshold (for 230MB, 1% = 1.15MB) so that when we increase the size we’ll have to look at what is making that size increase and if we think it’s ok then we increase the threshold. The idea would be to make us think about it regularly. WDYT? * <more idea here> FTR I was reminded of this by a comment on a blog post: "En rapport avec XWiki, à l'époque où j'ai connu Greenpepper, il y avait un pack de démo avec XWiki. J'ai voulu refaire ce pack, mais j'ai l'impression que XWiki a pris un certain nombre de méga bytes en quelques années ^_^ . Est ce qu'il y aurait une version light disponible ?” In short the guy said that XWiki seems to have increased size over the years and was asking whether there was a lightweight version somewhere… WDYT? Do we agree that we should try to contain the size and even start decreasing it if we can? Thanks -Vincent

9 years

4
7
0 0

[xwiki-devs] [Proposal] XWiki 8.3 Roadmap

by Vincent Massol

Hi devs, I’m sorry to be so late to send this email. I thought I had sent it before going on holidays but apparently I didn’t. Sorry about that. So here’s the proposal: * Thomas: ** Priority 1: l10n support for nested pages ** Priority 2: Curated extensions feature in EM (curated extensions listed + ability to see others if explicitly asked) ** Priority 3: Fix various existing NS issues (example: office macro on NP) + continue improving tools ** Priority 4: Paying + Trial feature in EM (see that an app is paying + has a trial and show it) * Marius: ** Priority 1: Fix performance issue in Document Tree + fix "Add support for sorting the pages by their title in the document tree" at the same time ** Priority 2: Fix various existing NS issues (example: office macro on NP) + continue improving tools. Includes as priority "Viewing a PPT / ODP with the Office Macro fails when on a nested page” ** Priority 3: Bring back XCS flavors in XE (involves dropping XE and replacing it with a KB flavor and start using the platform distribution instead of XE) * Caty: ** Priority 1: Complete Templates (set of sample templates (partially done already) + templates in each App and in AWM) in XE ** Priority 2: Demo content extension for XE ** Priority 3: Curated extensions feature in EM (curated extensions listed + ability to see others if explicitly asked) ** Priority 4: Mouseflow + Inspectlet analysis for xwiki.org ** Priority 5: Task for Usability (investigation) * Vincent: ** Priority 1: Curation of extensions.xwiki.org ** Priority 2: Playground flavor ** Priority 3: Continue Confluence + MediaWiki comparison pages + present XWiki as the best Confluence alternative ** Priority 4: Improvement to activeinstalls to capture some more information (email hash for unicity, country, number of users) * Guillaume: ** Priority 1: <internal XWiki SAS work - Infra work for XWiki Cloud if you’re curious ;)> ** Priority 2: Fix various existing NS issues (example: office macro on NP) + continue improving tools * Alex: ** Priority 1: <internal XWiki SAS work - prepare one paying app and setup an XWiki SAS store> ** Priority 2: Demo content extension for XE ** Priority 3: Fix various existing NS issues (example: office macro on NP) + continue improving tools * Edy: ** Priority 1: <internal XWiki SAS work - Network work, this is XWiki SAS’s customer portal: issue tracking, subscriptions, etc> ** Priority 2: Complete Templates (set of sample templates (partially done already) + templates in each App and in AWM) in XE ** Priority 3: Fix various existing NS issues (example: office macro on NP) + continue improving tools Top JIRA issues to fix: * Viewing a PPT / ODP with the Office Macro fails when on a nested page - XWIKI-11611 * Cannot delete document with many large attachments - XWIKI-8910 * Extend "Add Application" UIX with an order parameter - XWIKI-13075 * Rename and copy page operations don't update the page title - XWIKI-12776 * Presentation Office documents (.ppt & .pptx) aren't displayed with LibreOffice 4.3.5.2+ - XWIKI-13256 Dates: * 8.3M1: 22 August 2016 (one more week than usual to account for Holidays) * 8.3M2: 12 Sep 2016 * 8.3RC1: 26 Sep 2016 * 8.3final: 10 Oct 2016 Let me know what you think and reply if you’re interested to participate to this roadmap and you wish to implement/contribute some other stuff. Thanks -Vincent

9 years

4
11
0 0

[xwiki-devs] [Proposal] Move out Chart Macro + Renderer to Contrib

by Vincent Massol

Hi devs, I’d like to propose: * move out the Chart Macro + Renderer to Contrib since it’s not core. * still depend on it in the XE distribution for now. However if everyone feels that it’s not needed to have it by default for users and that it’s better to let them install it, I’m also fine. But right now I prefer to have it by default. WDYT? Thanks -Vincent

9 years

1
1
0 0

[xwiki-devs] [XWiki Day] BFD#117

by Alexandru Cotiuga

Hello devs, This Thursday is BFD#117: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status for the 1 year period is 56 bugs behind. See: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=100 00#Created-vs-Resolved-Chart/10470 Here's the BFD#117 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13635 Happy Bug Fixing Day, Alex

9 years

1
1
0 0

[xwiki-devs] [Proposal] New best practice for extensions and especially recommended ones: LATEST branch

by Vincent Massol

Hi devs, Context ======= I’d like to propose a new best practice for extensions and especially recommended ones. We already have the following on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra…: "In your POM always try to depend on the oldest version of commons/rendering/platform dependencies for which your code works. At least, ensure that your Applications works on the latest LTS version of XWiki. This will allow the largest number of users to use your application.” In addition on the definition of a Recommended Extension at http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensi… we say: “Works at least with the latest stable XWiki versions and with the LTS version” This proposal is about ensuring that an extension works with the latest stable XWiki version. Proposal ======== 1) Always create a LATEST branch for recommended extensions 2) On this branch depend on LATEST for parent pom. For example: <parent> <groupId>org.xwiki.commons</groupId> <artifactId>xwiki-commons-pom</artifactId> <version>LATEST</version> </parent> Note 1: For extensions using https://github.com/xwiki-contrib/parent we also need to release latest version of those poms as part of the XWiki commons/rendering/platform/enterprise release process. Note 2: The advantage of using LATEST is that it doesn’t require maintenance from the extensions whenever new versions of XWiki commons/rendering/platform/enterprise are released. It does require to update the contrib parent poms though. 3) On ci.xwiki.org, make sure that the job is defined to build 2 branches. You can also leave the branch name empty and Jenkins will then build all available branches as I’ve done for IRC Bot app: http://ci.xwiki.org/job/Contrib%20-%20IRC%20Bot%20Application/configure (check the “Source Code Management” section). WDYT? Thanks -Vincent

9 years

2
2
0 0

[xwiki-devs] [ANN] Publication Workflow Application v1.7 released

by Clemens Klein-Robbenhaar

Hi all, a new release of the "XWiki Publication Workflow Application" is available right now: http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Publication+Work… This release mainly adds the new feature to support workflows for multi-language pages. Minor improvements are a marginally more efficient handling of large attachments and less deprecations warnings in the logs. See also the release nots for (pointers to) details: http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Publication+Work… You can install or upgrade with the Extension Manager. Thanks, Clemens

9 years

1
0
0 0

[xwiki-devs] Legal notice for xwiki.org

by Vincent Massol

Hi xwiki committers, According to the French law we have to have a legal notice page on xwiki.org, see: https://www.service-public.fr/professionnels-entreprises/vosdroits/F31228 I’ve thus created http://www.xwiki.org/xwiki/bin/view/Main/LegalNotice/ WDYT? Anything to add? Now we need to link it, somewhere in the footer. @Caty: would you have any idea of where would be the best place? Thanks -Vincent

9 years

6
15
0 0

[xwiki-devs] [PROPOSAL] Make {{html}} default behavior be clean=false

by Caleb James DeLisle

Hello all, Recently we discovered that in XWiki 8.2 the {{html}} macro cleaner now removes <video> tag whereas in 7.4 it did not and this has unfortunately caused problems for the {{video}} macro. 1. After some helpful investigation by a few XWiki developers, we have found that in fact the {{html}} macro is cleaning for XHTML and not for HTML5 which is what XWiki uses and the change has seemingly gone unnoticed since the upgrade to 8.0M1. 2. After some conversation with developers, I have observed that it is rare for an application developer to *intend* to have their HTML cleaned. In the XWiki repositories we find that amongst non-one-liner {{html}} macro invocations, 109 out of 292 (37%) of the invocations explicitly request clean=false [1]. 3. Nowhere is clean="true" specified and though one might think it obvious as it is a default, we find that wiki="false" (also default) is indeed specified 28 times [2]. 4. We see also that the HTML macro proves to be quite slow. During an investigation of SOLR performance Thomas found that "about 23% of the request is spend executing html macros" [3]. I suppose it should be obvious that without the cleaner, the {{html}} macro should not cause any significant performance degradation. Given the status of this feature, I would like to propose that we make an intentional change of behavior and change the default to clean=false. This way we application developers will not need to type it all of the time and XWiki will become measurably faster. Here is my +1 for changing the default. Thanks, Caleb [1]: $ grep -nr '{{html' | grep '.xml:' | grep 'clean=['\''"]*false' | grep -v '{{/html}}' | wc -l 109 $ grep -nr '{{html' | grep '.xml:' | grep -v 'clean=['\''"]*false' | grep -v '{{/html}}' | wc -l 183 [2]: $ grep -nr '{{html' | grep '.xml:' | grep 'wiki=['\''"]*false' | wc -l 28 [3]: https://jira.xwiki.org/browse/XWIKI-12043

9 years

4
4
0 0

[xwiki-devs] [contrib][workflow-publication][Proposal] request for a new release on Tuesday (6.9.)

by Clemens Klein-Robbenhaar

Hi Devs, if nobody objects I would like to cut a new release for the Publication Workflow Application at http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Publication+Work… The version number would be 1.7 I would like to make the release on Tuesday (unless Monday is a bank holiday or the like, in case of the release date shifts to Wednesday) The release would fixes the following issues: http://jira.xwiki.org/browse/XAWORKFLOW/fixforversion/16658 The main change would be some basic support for multi-language documents, which I know someone would really appreciate. There are two new translation keys: one is introduced for XAWORKFLOW-27 and is shown in the workflow panel as a hint for the publisher who is publishing a multi-language document, informing about the fact that all language variants are going to be published workflow.panel.publish.hintLanguages and one that showed up as missing while checking XAWORKFLOW-28: PublicationWorkflow.PublicationWorkflowConfigClass_groupedit_hint = Edit Workflow Group Unfortunately the default "Translations" document is in French, and as I did not want to show in translation key for unsupported languages, I just filled in an English text. If someone could replace these "dummy translations" with a proper French text this would be really appreciated. Are there any objections to the release? Does someone want more time to look at the changes? Cheers Clemens P.S. if there are no objections I can handle most parts of the release on my own, but need a bit of help with updating the versions in JIRA.

9 years

3
4
0 0

[xwiki-devs] [Brainstorming] Designing the perfect FS representation of a wiki

by Vincent Massol

Hi devs, There’s been several individual attemps at representing xwiki in a FS (see http://markmail.org/message/vxq2dyfzuvc5gt3a): * Caleb’s nodejs tool: https://github.com/xwiki-contrib/xwiki-tools-node * Fabio’s xwikifs: https://github.com/fmancinelli/xwikifs * Jean’s XFF: https://github.com/xwiki-contrib/api-xff * Paul’s XInclude extension to the XAR plugin: http://jira.xwiki.org/browse/XWIKI-13643 I think a first step is agreeing on the best representation and one we would agree on. I’ve based the proposal below on the format started by xwikifs since it’s for me the closest to the perfect format. a <— nested page |_ b <— nested page |_ c <— nested page |_ content.<any extension, e.g. xwiki21> <— doc content |_ content.<language, e.g. fr>.<any extension, e.g. xwiki21> <— doc content translated |_ meta.yml <— doc metadata |_ meta.<language, e.g. fr>.yml <— doc metadata for translation |_ class.yml <— class definition |_ objects <— xobjects |_ d |_ e |_ f <— location of xclass |_ <object number, e.g 0> |_ <property id1>.yml |_ <property idN>.yml |_ <property idN>.content.<any extension, e.g. xwiki21> <— for externalizing property content, e.g. textarea Notes: * YAML is really the easiest to read and write and the most concise (parsing is easy but there’s also SnakeYaml). Example: JSON: { “title” : “my title”, “syntax” : “xwiki/2.1" } YAML: title: my title syntax: xwiki/2.1 * The extension is free so that we can use a value that represents the syntax of the content so that tools and IDE use the correct editor * For “objects” there could be some collision with a page name. So we would offer a property for the Maven plugin to override that default value with something else in case it’s necessary for a given project (but it’s unlikely that a page will be named “objects” anyway so this property wouldn’t be used often). * For the xclass of the xobject, I’m hesitating but I’ve put a directory hierarchy for the issue of limitation of file name under windows. If we use a single directory named after the reference, it might go beyond 255 chars more easily. We need to decide what we prefer. It could even be possible to support both representation with a maven property for the Maven plugin. * meta.yml for an xobject will also contain the class definition. Note that if we think it’s important, we could separate it and introduce an additional class.yml file but I don’t see the value right now. Differences with xwikifs * Extension names * No reference syntax. I’ve defined fixed name for the various pieces so a reference syntax doesn’t seem required but I’d like to know Fabio’s POV since he may have had some ideas I haven’t understood. * No classinfo (see above, class info is inside meta.yml) Let’s start with this and iterate! WDYT? What have I forgotten? Thanks -Vincent

9 years

5
22
0 0

[xwiki-devs] Deployment issue on jboss (Wildfly)

by Pankraz, Alexander (HP DualStudy)

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:alexander.pankraz@hp.com> 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>

9 years

3
2
0 0

[xwiki-devs] [Brainstorming] Use cases for an alternative filesystem format (alternative to XAR)

by Vincent Massol

Hi, This is a follow-up on the threads: * "Designing the perfect FS representation of a wiki”: http://markmail.org/message/3yghqwetmdt5woez * "XAR source projects should allow source files”: http://markmail.org/message/432o36r4klh7yv24 It’s also a continuation of the work done here: http://design.xwiki.org/xwiki/bin/view/Design/DirectoryStructureforXWikiApp… Once we get convergence on those thread (or even if we don’t), I’ll update design.xwiki.org with the results. The goal is to define the use case for an alternate filesystem to XAR. Issues with the XAR format ====================== * XML is not an easy to edit format and doesn’t allow use a specific editor to edit content * XML also requires content to be XML-encoded and thus is really not easy to make modification (there’s a risk of breaking the XML easily) Can you see more issues? Use cases for an alternative filesystem format =================================== (some UC taken from http://design.xwiki.org/xwiki/bin/view/Design/DirectoryStructureforXWikiApp…) * UC1: the structure should be (as) easy (as possible) to navigate in an IDE style view * UC2: it should be easy to add content (a new script or attachment on an existing structure). It should allow using specific editors for different content types, e.g. if a page content is in markdown, it should be editable with a MD editor, js and css should be editable with web editors, etc. * UC3: It should be possible to build a packaged version of the sources with Maven * UC4: It should be possible to import the packaged version into a running XWiki instance * UC5: It should be possible to export a portion of a running XWiki instance in this format * UC6: This format should be able to fully replace the XAR format . The new format should support at least all features supported by the XAR format (versioned, etc). Note: XE will need to be refactor a bit so that the XAR format can be swapped out by introducing extension points/APIs. The idea would be to deprecate the XAR format and introduce this new format instead, and the 2 formats should be avle to cohabit next to each other in XWiki. * UC7: When importing in a wiki and exporting again (without making any change in the wiki), it should generate an identical structure and content, with no difference. Any more? Thanks -Vincent

9 years

3
9
0 0

[xwiki-devs] Component ReflectionUtils hidden fields

by Marc Sladek

Hi XWiki-devs I noticed that org.xwiki.component.util.ReflectionUtils.getAllFields(Class<?>) <https://github.com/xwiki/xwiki-commons/blob/master/xwiki-commons-core/xwiki…> does not return hidden fields <https://docs.oracle.com/javase/tutorial/java/IandI/hidevariables.html> of superclasses. These are actively filtered out by the implementation with the following comment: *Make sure that if the same field is declared in a class and its superclass only the field used in the class will be returned.* This implementation caused NPE's for us because the ComponentManager did not inject annotated hidden fields. Can somebody provide a good reason for this implementation? Thanks for the feedback and regards Marc

9 years

2
1
0 0

[xwiki-devs] XAR Unit testing Performance analysis + Guidelines

by Vincent Massol

FWIW I’ve done a quick analysis of the speed of executing a XAR unit test (see http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HXARTesting). Globally it takes 3ms for the first test on my machine. With a profiler the time is roughly doubled (6ms) and is spread like this (for stuff that takes the most time): * loadPage(): 1.1s ** TIKA init : 800ms (initialized in XWikiAttachment) * getRenderedContent(): 1.2s ** org.apache.xpath.jaxp.XPathImpl.evaluate(): 260ms ** javax.validation.Validation.buildDefaultValidatorFactory(): 260ms * init stuff: ** org.slf4j.LoggerFactory.getLogger(String): 804ms ** mocking: 288ms ** component registration: 260ms My only ideas for speeding slightly the execution time would be to ensure that TIKA is not initialized for the test until it is required. And maybe check why SLF4J takes so long and find a way to make it run faster (maybe use a noop logger). So those 2 items could win us a max of 1.6s out of 6s, so that’s 800ms out of 3s. Which would lower our exec time for a single test to close to 2 seconds. But I don’t see how to go below that value. Conclusion: ========== - IMO we shouldn’t call those tests unit tests but integration tests (that’s what they are in practice) - we should run them in the integration-tests profile to not slow down the main build too much - they’re still way faster than writing a functional tests (more than 1 minute to package and run - that’s 20 times slower at best), so when possible this should be favored when we want to validate some specific behavior of a wiki page or ensure that a regression won’t happen again WDYT? If we’re ok I’ll make the changes (integration-tests profile + rename to integration tests). Thanks -Vincent

9 years

3
3
0 0

[xwiki-devs] [XWiki Day] BFD#116

by Alexandru Cotiuga

Hello devs, This Thursday is BFD#116: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status for the 1 year period is 67 bugs behind. See: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=100 00#Created-vs-Resolved-Chart/10470 Here's the BFD#116 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13634 Happy Bug Fixing Day, Alex

9 years

2
2
0 0

[xwiki-devs] [ANN] Full Calendar Macro v2.0.3 Released

by Alexandru Cotiuga

Hello all, I just released a new version of Full Calendar Macro. The most important benefit is the upgrade of FullCalendar <https://fullcalendar.io/> jQuery plugin to v2.9.0. This release might be interesting and could be a reason to release other applications that are using Full Calendar Macro, like Meeting Application <http://extensions.xwiki.org/xwiki/bin/view/Extension/Meeting%20Application> or Mocca Calendar. <http://extensions.xwiki.org/xwiki/bin/view/Extension/MoccaCalendar> See the Release Notes: http://extensions.xwiki.org/xwiki/bin/view/Extension/FullCalendar+Applicati… . Thanks, Alex

9 years

2
3
0 0

[xwiki-devs] Crafting method to add a plugin to the CKEditor?

by Paul Libbrecht

Hello fellow developers, is there some hint to add a plugin (with a button) to the CKEditor? I've met /xwiki/bin/edit/CKEditor/EditSheet?editor=object which is probably the place to start with. I tried adding the extraConfigs variable within the configuration but it seems like this cannot load my plugin. It would be cool to have an extension mechanism for that. thanks in advance. Paul

9 years

2
8
0 0

[xwiki-devs] Cannot upgrade the CKEditor extension that is bundled by default

by Marius Dumitru Florea

Hi devs, Thomas raised this issue http://jira.xwiki.org/browse/XE-1570 . One of the reasons we decided to keep the CKEditor Integration extension in contrib, with its own release cycle, was to allow the users to upgrade it without the need to upgrade the entire XWiki distribution. There wouldn't be any problem if the CKEditor Integration extension didn't had any JAR dependencies. But it depends on the CKEditor WebJar which ends up in the XWiki WAR and thus is considered a core extension, and core extensions cannot be upgraded. Here's what happens: * xwiki-enterprise-ui-common depends on ckeditor-ui ( https://github.com/xwiki/xwiki-enterprise/blob/xwiki-enterprise-8.2.1/xwiki… ) * both xwiki-enterprise-ui-mainwiki and xwiki-enterprise-ui-wiki depend on xwiki-enterprise-ui-common * xwiki-enterprise-web depends on both xwiki-enterprise-ui-mainwiki and xwiki-enterprise-ui-wiki ( https://github.com/xwiki/xwiki-enterprise/blob/xwiki-enterprise-8.2.1/xwiki… ) in order to "transitively include all JAR dependencies in the generated WAR" So the ckeditor-webjar ends up in the XE WAR, thus it becomes a core extension. In order to fix this Thomas has proposed two solutions: (1) Build 2 XE WARs: one that bundles the transitive JAR dependencies of the UI (what we have currently) and one that doesn't bundle them. We would offer only the later for download on xwiki.org, knowing that the transitive JAR dependencies will be installed when the UI is installed (with the Distribution Wizard for instance). The first WAR would be used only for building the Jetty+HSQLDB distribution. The downside of this solution is: * we don't fix the problem for the Jetty+HSQLDB distribution * the ui-all XAR would work only with the "all" WAR (the first one that bundles the XAR dependencies) (2) Exclude the JARs we don't want as core extensions from https://github.com/xwiki/xwiki-enterprise/blob/xwiki-enterprise-8.2.1/xwiki… , one by one. This would fix the WAR-based installations but not the Jetty+HSQLDB distribution which uses the Import Mojo ( https://github.com/xwiki/xwiki-enterprise/blob/xwiki-enterprise-8.2.1/xwiki… ) to generate the distribution data folder and thus won't get the ckeditor-webjar. For this we would need to introduce a new Install Mojo and explicitly install the JAR dependecies we want (ckeditor-webjar in this case). The problem with this solution is the maintenance cost. We'll forget for sure to exclude/install the JAR in XE's pom whenever we add a new JAR dependency to one of the contrib extensions that are bundled in XE (CKEditor and Tour for the moment). Do you have any other ideas? Solution (1) seems the best so far. Thanks, Marius

9 years

4
15
0 0

[xwiki-devs] [Proposal][Urgent] Change of behavior for xproperties editor for backward compat reasons

by Vincent Massol

Hi devs, Marius has recently introduced the honoring of text editor for xproperty editing for textarea types. This is great but it’s causing a lot of backward compatibility issues. We’ve fixed several xclass to use “puretext” for code but there are plenty out there still. I’ve just found another one with XWiki.WatchListMessage. The issue is that this is a blocker. I was trying to make a change there so I was editing using the “source” mode of CKEditor. The problem is that when I saved there were a lot of changes made to the content automatically, breaking the code, see for example: https://www.evernote.com/l/AHf4KpfVtfBOK5zqcyf_up1Rty923fZOm-I The main issue is that I’m stuck. There’s nothing I can do in my wiki (without resorting to scripting, using REST, etc). I’m proposing that we do the opposite: * When no editor is specified, use the wiki editor. Apps that want WYSIWYG in xproperties should say so. This is actually more logical to me because the object editor is a technical editor. In any case we need a solution that doesn’t break backward compatiblity. Since this change of behavior (honoring the editor for xproperties in the object editor) was introduced in XWiki 8.2 we need to act fast before it becomes a problem for our users. WDYT? Thanks -Vincent

9 years

4
8
0 0

[xwiki-devs] [Proposal] Curation process for extensions on e.x.o

by Vincent Massol

Hi devs, We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. P2) It’s hard for users to locate good extensions among the rest. We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. Proposal ======= I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. Then we need to decide about the curation process: * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra…. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. WDYT? I’m willing to help do the work and mark extensions as recommended. Thanks -Vincent

9 years

7
28
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs