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

[xwiki-devs] [VOTE] Create a XWiki Debug (IntelliJ) Idea project in the XWiki organization page

by Fabio Mancinelli

Hi guys, I spent some time trying to port the great work Thomas did for Eclipse (https://github.com/xwiki/xwiki-debug-eclipse) to IntelliJ Idea. So I have something working to commit. I've already written the documentation: http://localhost:8080/xwiki/bin/view/Community/XWikiDebugIdea This mail is to ask if I can commit it in the main XWiki repository by creating a xwiki-debug-idea project. Here is my +1 -Fabio

12 years, 10 months

6
17
0 0

[xwiki-devs] [Brainstorming] French translation for "Distribution Wizard"

by Silvia Rusu

Hello, I'd like to get your opinion on what French translation we should use for "Distribution Wizard". So far I've received the following suggestions: * Gestionnaire de distributions * Assistant d'installation * Assistant de distribution Do you prefer one of the above suggestions? Do you have other ideas? Please reply to the present thread with your opinion. Thanks, Silvia

12 years, 10 months

9
11
0 0

[xwiki-devs] [Business] Looking for XWiki web developers for XWiki SAS

by Vincent Massol

Hi fellow XWiki developers, The company I work for, XWiki SAS (see http://bit.ly/SEl2yY for details on the relationship between XWiki SAS and the open source project), is currently in the phase of discussing several new development projects for customers. We are expecting some activity growth pretty quickly in 2013 and beyond and therefore we are looking for front-end developers to work for our Client Development Team in priority (but also in the Core Development Team). We're considering both new hires and sub-contractors, so if you feel there can be a match between your interests and the mission we're proposing send us an email at jobs(a)xwiki.com: * http://www.xwiki.com/xwiki/bin/view/Company/DeveloperOpenPosition * http://www.xwiki.com/xwiki/bin/view/Company/CoreWebDeveloperOpenPosition Looking forward to hearing from you on jobs(a)xwiki.com ! -Vincent Massol XWiki SAS CTO

12 years, 10 months

1
0
0 0

[xwiki-devs] [VOTE] Retire old userdirectory plugin

by Vincent Massol

Hi devs, I'd like to propose to remove the old userdirectory plugin (com.xpn.xwiki.plugin.userdirectory.*) from oldcore and move it to xwiki-contrib/retired I've checked and it's not used anywhere in our code and since it's not been touched for a very long time it's probably not even working. Also it has some concept of group invitation but we've implemented that in the invitation module. Here's my +1 Thanks -Vincent

12 years, 10 months

8
7
0 0

[xwiki-devs] [Contrib] I'd like to move xwiki realtime editor to xwiki-contrib

by Caleb James DeLisle

Hi, Since I've got the realtime editor in a working state and it's hosted as an extension, I'd like to move it to xwiki-contrib so we can take advantage of the jira project and not have issues lost in githubland. WDYT? Thanks, Caleb

12 years, 10 months

4
4
0 0

[xwiki-devs] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.3-milestone-1 released.

by Fabio Mancinelli

The XWiki development team is proud to announce the availability of XWiki Enterprise 4.3-milestone-1. This release brings several improvements in Workspaces, Extension Manager, Distribution Wizard and the REST API. It is now possible to activate the multiwiki feature when using the HSQLDB database (i.e., in the standalone version of XWiki Enterprise). Several important fixes for bugs related to importing Office Documents while using filesystem attachments have also been included. 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/ReleaseNotesXWikiEnterpris… Thanks -The XWiki dev team

12 years, 10 months

2
1
0 0

[xwiki-devs] New localization module

by Thomas Mortagne

Hi devs, I started recently to refactor the localization module Sergiu had started. You can look at the current status in the branch https://github.com/xwiki/xwiki-platform/tree/feature-localization. Nothing is working yet but I wrote enough APIs to see a bit more clear on what I'm up to so here it is. This mail is mostly to discuss the general architecture. There will be other more detailed mails for voting class name and things like that. = Get a translation = * here is the main client API: the client ask for a Translation object to LocalizationManager by indicating it's key (String) and locale (java.util.Locale). Then it calls Translation#render() with optional parameters to get a rendering Block as result. This Block is then inserted in the main XDOM using the translation macro or rendered as text by XWikiMessageTools#get() and other APIs like that if there is = Provide new translations = * support "injecting" new translations just by "marking" pages containing translation using an object to not have to list them in XWikiPreferences anymore. This is especially required for extensions. * the same way I think we should be able to provide translation in a jar extension * on idea introduce by Sergiu and that I agree with is the fact that like with ssx/jsx we need to be able to pull a specific translation explicitly without it to be automatically registered for the whole wiki or something like this * LocalizationManager (and more specifically BundleContext) find the right translations bundles to look at by lokuping all the org.xwiki.localization.Bundle components depending of the context (component can be registered for specific wikis/users). = Translation message syntaxes = * translation message syntax: the current syntax of our translations is a MessageTool based syntax depending on the fact that your have custom parameters or not. This syntax is not very good IMO (managing ' char is a mess) but good or not I think we need to have the possibility to introduce new features (like variables, light formating syntax, etc.) whenever we needs it without breaking anything and the way to do it is by having the possibility to have translation resources in different syntaxes and associated parsers. Note that TranslationMessage does not appear anywhere in the Translation API, any Bundle can implement Translation the way it want but we will have a lot of Bundle on our side using this concept of translation message syntax. The main target is wiki translations. Not all that is going to ends up in 4.3 but the goal is to have at least the new architecture support the "old" ApplicationResources resource and XWikiPreferences static translations pages and start introduce dynamically registered wiki translations. Shoot ! -- Thomas Mortagne

12 years, 10 months

3
6
0 0

[xwiki-devs] New Realtime collaborative editing extension.

by Caleb James DeLisle

Hi guys, I just finished repackaging the realtime collaborative editor which was developed as part of wiki/3.0. It is now installable as an extension. It's still a bit rough around the edges but it's pretty safe to play with so everyone is invited to give it a try. * Multiple users can edit the same document at the same time and their changes are merged in real time. * The "RealTime Wiki" editor is an option along side WYSIWYG and Wiki so it won't break existing editors. * Easy installation by copying a .jar file and importing a .xar file, removal is simply deleting 2 XDocuments. http://extensions.xwiki.org/xwiki/bin/view/Extension/RealTime+Wiki+Editor Please feel free to share your experiences in the mailing list, on the extension wiki page and on the github bug tracker. Thanks, Caleb

12 years, 10 months

6
12
0 0

[xwiki-devs] [Proposal] Define XClass property types using components

by Marius Dumitru Florea

Hi devs, Currently, the available XClass property types are hard-coded in MetaClass [1]. So in order to add a new property type you need to recompile the XWiki old core. I'd like to be able to create new property types using components so I created this branch [2] that includes the following important changes: (A) Use the value of the "classType" XML element from the XAR as a property type hint If you look at the XML export of an XClass you'll see that each property has a "classType" element whose content is the full name of the Java class used to implement that property type: <classType>com.xpn.xwiki.objects.classes.DBTreeListClass</classType> I think this is bad because: * it exposes an implementation detail * you cannot change the property type implementation without breaking backwards compatibility So I'm proposing to use the "classType" as a hint for the property type. Well, technically it will be a hint, but semantically it will specify the data type of the property value (e.g. String, Date, Number). For backwards compatibility, the existing property types will have hints that can be extracted from the value of the 'classType' (i.e. the full Java class name): String hint = StringUtils.removeEnd(StringUtils.substringAfterLast(classType, "."), "Class"); So both: <classType>com.xpn.xwiki.objects.classes.DBTreeListClass</classType> <classType>DBTreeList</classType> will point to the property type with hint "DBTreeList". Of course, when exporting an XClass with the new version of the core you'll only see the property type hint. The only issue with this approach is that XClasses exported with the new version will not work on an older version but this is acceptable IMO. (B) Add a PropertyClassProvider [3] role to retrieve an instance of a property class and to access its meta class Currently, in order to define a new property type you need to create two Java classes: * one extending PropertyMetaClass, to define the list of meta properties of the new property type (e.g. displayType, dateFormat, multiSelect, etc.) * one extending ProperyClass, to define setters and getters for the meta properties and maybe some custom display. This is the property type itself. So I added a PropertyClassProvider role that has two methods: one to get the meta class and one to get a new instance of the property type (e.g. when adding a property to an XClass). As a quick implementation I transformed all meta classes into implementations of this role. Finally, I modified MetaClass to lookup property class providers instead of hard-coding the property types. WDYT? Note that I've not added any CLIRR excludes and I tested my changes with the default, unchanged, class editor and it works fine. Thanks, Marius [1] https://github.com/xwiki/xwiki-platform/blob/xwiki-platform-4.2/xwiki-platf… [2] https://github.com/xwiki/xwiki-platform/compare/feature-xclass-property-com… [3] https://github.com/xwiki/xwiki-platform/commit/fb9fcc7313ccb16f38c2d17dd7ed…

12 years, 10 months

4
10
0 0

[xwiki-devs] New fine-grained way to ignore CLIRR violations

by Vincent Massol

Hi guys, I've committed http://jira.xwiki.org/browse/XCOMMONS-283 which allows us to very precisely exclude CLIRR violations. See http://mojo.codehaus.org/clirr-maven-plugin/examples/ignored-differences.ht… for details. For example I've just added an IRCBot exclude using this with: <ignored> <difference> <className>org/xwiki/ircbot/IRCBot</className> <method>void initialize(java.lang.String)</method> <differenceType>7012</differenceType> <justification>IRCBot is still a young API. Added a new initialize() method to support installing the IRC Bot application in a subwiki</justification> </difference> </ignored> Now could every one who's added a clirr exclude please convert to the new way? This allows us to have fine-grained excludes and not exclude the whole file. Thanks -Vincent

12 years, 10 months

2
5
0 0

[xwiki-devs] Where to define new property types? Java vs. Wiki

by Marius Dumitru Florea

Hi devs, I'd like to extend the set of property types available in the AWM class editor (the field palette) and I'm not sure where is the best place to do this: in the Java code (oldcore) or in the wiki. I prefer the wiki. Let me explain. We recently added two new property types in the oldcore: email and page. If you look at these two you'll see that email is just a string property with a default validation regexp and page is just a dblist property. The AWM class editor has a system that lets you define property 'templates' in the wiki. To define the email property type I could do this: * create AppWithinMinutes.Email xclass with a single String property (the 'template') * set the validation regexp to match an email address (but I can set other meta properties as well with *default* values) * add an object of type AppWithinMinutes.FormFieldClass to AppWithinMinutes.Email to specify (among other things) the list of meta properties that should be visible in the class editor. For instance, I'd like to hide the validation regexp. At this point the AWM class editor will detect the email property type and list it in the field palette and you can add it to your class. The only problem is that when editing the class back the editor doesn't have yet a way to determine what was the template used to add the property so it uses the default one, the one for the String property in this case. So my question is: do you think it's good to be able to define new property types from the wiki (e.g. Image, Attachment, Color, etc.) or should they all be written in Java? If the answer is Wiki, then I'll think of a way to store the reference to the property template so that the AWM class editor can edit back using the right template. Note that it crossed my mind to define a property type component that can be implemented both from Java and from the wiki but transforming the oldcore code that handles objects/properties into components is very difficult. Thanks, Marius

12 years, 10 months

5
5
0 0

[xwiki-devs] Build is unstable again....

by Vincent Massol

Devs, We're receiving tons of build failures every day again …. :( Coud all devs please help in fixing the build so that we can again have a passing build and fix flickering tests? Thanks -Vincent

12 years, 10 months

3
2
0 0

[xwiki-devs] [Contrib] xwiki-enterprise-vagrant

by Sorin Burjan

Hi devs, As part of the Hackathon 2012, I started working no a maven module to create VM' provisioned with XWiki.The module is somehow in its early stages, It needs polishing. In order to make the code public for others to see it and help polish it, I would like to have a xwiki-contrib project for this. project name: xwiki-enterprise-vagrant username: sorinello Regards, Sorin B.

12 years, 10 months

2
3
0 0

[xwiki-devs] Quality Profile now enabled in CI for XWiki Commons

by Vincent Massol

Hi devs, As previously agreed (see http://markmail.org/thread/j5yuaxixbyvytfr3), I've now configured all commons module to have proper TPC % values to make the build pass. I've also configured a Jenkins job that'll run once per day at midnight and send us an email if some module fails to pass the TPC check. When this happens it means some dev will have committed during the day code without enough test and he would have globally lowered the quality of the project for the module(s) where he committed. Even if he committed some functional tests to compensate he'll still need to write some more unit tests to make the TPC check pass again. http://ci.xwiki.org/view/Commons/job/xwiki-commons%20Quality%20Checks/ Next step is to do the same for Rendering and the Platform. I'll work on that. Thanks -Vincent

12 years, 10 months

1
1
0 0

[xwiki-devs] [VOTE] REST API Changes not passing CLIRR. Ignore errors

by Ludovic Dubost

As part of rest improvements to display pretty names of users and other improvements, I'm getting CLIRR errors because of API changes of the model and of public class: 1/ Model CLIRR error because the version field has been moved to PageSummary from Page. Page extends PageSummary. I need the version field also in representations sending back only PageSummaries. Unfortunately CLIRR does not realize that the version field is still there when moved to the super class. I believe it's safe to ignore this error. Howerver I've put ignore all errors on the Page class as I don't have a way to ignore this specific error 2/ CLIRR errors because of parameter additions to objects that are used (I think) only internally by the REST server API. Here are the errors: [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.Attachment createAttachment(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, com.xpn.xwiki.api.Attachment, java.lang.String, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.Attachment createAttachmentAtVersion(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, com.xpn.xwiki.api.Attachment, java.lang.String, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.Comment createComment(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, com.xpn.xwiki.api.Document, com.xpn.xwiki.api.Object)' the number of arguments has changed [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.HistorySummary createHistorySummary(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, java.lang.String, java.lang.String, java.lang.String, java.lang.String, org.suigeneris.jrcs.rcs.Version, java.lang.String, java.util.Date)' the number of arguments has changed [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.Object createObject(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, com.xpn.xwiki.XWikiContext, com.xpn.xwiki.api.Document, com.xpn.xwiki.objects.BaseObject, boolean)' the number of arguments has changed [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.ObjectSummary createObjectSummary(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, com.xpn.xwiki.XWikiContext, com.xpn.xwiki.api.Document, com.xpn.xwiki.objects.BaseObject, boolean)' the number of arguments has changed [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.Page createPage(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, java.net.URI, com.xpn.xwiki.api.Document, boolean, com.xpn.xwiki.api.XWiki)' the number of arguments has changed [ERROR] org.xwiki.rest.DomainObjectFactory: In method 'public org.xwiki.rest.model.jaxb.PageSummary createPageSummary(org.xwiki.rest.model.jaxb.ObjectFactory, java.net.URI, com.xpn.xwiki.api.Document, com.xpn.xwiki.api.XWiki)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.BaseAttachmentsResource: In method 'public org.xwiki.rest.model.jaxb.Attachments getAttachments(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.BaseAttachmentsResource: In method 'protected org.xwiki.rest.model.jaxb.Attachments getAttachmentsForDocument(com.xpn.xwiki.api.Document, int, int)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.BaseSearchResult: In method 'protected java.util.List search(java.util.List, java.lang.String, java.lang.String, java.lang.String, boolean, int)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.BaseSearchResult: In method 'protected java.util.List searchObjects(java.lang.String, java.lang.String, java.lang.String, boolean, int)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.BaseSearchResult: In method 'protected java.util.List searchPages(java.util.List, java.lang.String, java.lang.String, java.lang.String, boolean, int)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.BaseSearchResult: In method 'protected java.util.List searchSpaces(java.lang.String, java.lang.String, boolean, int)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.ModificationsResource: In method 'public org.xwiki.rest.model.jaxb.History getModifications(java.lang.String, java.lang.Integer, java.lang.Integer, java.lang.String, java.lang.Long)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.attachments.AttachmentsAtPageVersionResource: In method 'public org.xwiki.rest.model.jaxb.Attachments getAttachmentsAtPageVersion(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.attachments.AttachmentsResource: In method 'public org.xwiki.rest.model.jaxb.Attachments getAttachments(java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.comments.CommentResource: In method 'public org.xwiki.rest.model.jaxb.Comment getComment(java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.comments.CommentVersionResource: In method 'public org.xwiki.rest.model.jaxb.Comment getCommentVersion(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.comments.CommentsResource: In method 'public org.xwiki.rest.model.jaxb.Comments getComments(java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.comments.CommentsVersionResource: In method 'public org.xwiki.rest.model.jaxb.Comments getCommentsVersion(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.AllObjectsForClassNameResource: In method 'public org.xwiki.rest.model.jaxb.Objects getObjects(java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectAtPageVersionResource: In method 'public org.xwiki.rest.model.jaxb.Object getObject(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectPropertiesAtPageVersionResource: In method 'public org.xwiki.rest.model.jaxb.Properties getObjectProperties(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectPropertiesResource: In method 'public org.xwiki.rest.model.jaxb.Properties getObjectProperties(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectPropertyAtPageVersionResource: In method 'public org.xwiki.rest.model.jaxb.Property getObjectProperty(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectPropertyResource: In method 'public org.xwiki.rest.model.jaxb.Property getObjectProperty(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectResource: In method 'public org.xwiki.rest.model.jaxb.Object getObject(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectsAtPageVersionResource: In method 'public org.xwiki.rest.model.jaxb.Objects getObjects(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectsForClassNameResource: In method 'public org.xwiki.rest.model.jaxb.Objects getObjects(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.objects.ObjectsResource: In method 'public org.xwiki.rest.model.jaxb.Objects getObjects(java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PageChildrenResource: In method 'public org.xwiki.rest.model.jaxb.Pages getPageChildren(java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PageHistoryResource: In method 'public org.xwiki.rest.model.jaxb.History getPageHistory(java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PageResource: In method 'public org.xwiki.rest.model.jaxb.Page getPage(java.lang.String, java.lang.String, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PageTranslationHistoryResource: In method 'public org.xwiki.rest.model.jaxb.History getPageTranslationHistory(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PageTranslationResource: In method 'public org.xwiki.rest.model.jaxb.Page getPageTranslation(java.lang.String, java.lang.String, java.lang.String, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PageTranslationVersionResource: In method 'public org.xwiki.rest.model.jaxb.Page getPageTranslationVersion(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PageVersionResource: In method 'public org.xwiki.rest.model.jaxb.Page getPageVersion(java.lang.String, java.lang.String, java.lang.String, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.pages.PagesResource: In method 'public org.xwiki.rest.model.jaxb.Pages getPages(java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer, java.lang.String)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.spaces.SpaceAttachmentsResource: In method 'public org.xwiki.rest.model.jaxb.Attachments getAttachments(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.spaces.SpaceSearchResource: In method 'public org.xwiki.rest.model.jaxb.SearchResults search(java.lang.String, java.lang.String, java.lang.String, java.util.List, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.tags.PagesForTagsResource: In method 'public org.xwiki.rest.model.jaxb.Pages getTags(java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.wikis.WikiAttachmentsResource: In method 'public org.xwiki.rest.model.jaxb.Attachments getAttachments(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer)' the number of arguments has changed [ERROR] org.xwiki.rest.resources.wikis.WikiSearchResource: In method 'public org.xwiki.rest.model.jaxb.SearchResults search(java.lang.String, java.lang.String, java.util.List, java.lang.Integer)' the number of arguments has changed Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 10 months

6
18
0 0

[xwiki-devs] 4.3M1 release is Monday 22nd - please stabilize

by Vincent Massol

To all devs, The 4.3M1 release is for Monday. Could all devs please fix the build so that it passes and so that we can release on Monday? Make sure to not commit anything more for 4.3M1. What's not committed should now go for 4.3M2 unless it's a blocker. All make sure all your issues are closed with proper documentation fields. Thanks -Vincent

12 years, 10 months

1
0
0 0

[xwiki-devs] [PROPOSAL] Execution context property declarations and property metadata attributes

by Andreas Jonsson

Hi everyone, I would like to propose to introduce a possibility to associate properties in the execution context with metadata by declaring them. We introduce the class 'ExecutionContextProperty' that will store the metadata attributes, in addition to the actual property value. /** * Declare a property in the execution context. * * @param key The key that names the property * @param property The property to declare. */ public void declareProperty(String key, ExecutionContextProperty property) The metadata governs how the property should be treated when managing the execution contexts. For instance, these attributes could be supported: * Read-only - The value may not be updated within the the execution context. * Inherited - The property will be inherited from the current context when replacing the execution context within the scope of a request. * Clone - Also clone the value when the execution context is cloned. * Type - The class of the value, for typechecking when replacing the value. * Non-null - The value may not be null So, the arguments for this proposal are at least two: 1. Catch errors early and simplify debugging. 2. Convenience of having properties automatically maintained across execution contexts within the same request cycle. What do you think? I would like to implement and merge this ASAP. Best Regards, /Andreas

12 years, 11 months

3
10
0 0

[xwiki-devs] [Proposal] Improving our handling of Patches/PR (second step)

by Vincent Massol

Hi devs, Now that we've decided about our mini workflow to know which issues having patches have been answered by us or not, that leaves us with this status: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10000#Issue-Statis… Namely: - 28 issues containing patches that we need to review - 16 issues that we've reviewed and for which we're waiting for an answer from the contributor - 1 waiting for a pull request I think that so far we've not been very good at answering quickly contributors who post patches. I know it's difficult. I'm proposing 2 ways to improve this: * Send a weekly email about issues having patches and awaiting committer feedback * Schedule a "patch day" where devs would work primarily on reviewing issues with patches and applying where possible. At the minimum the goal would be to reply to the issues. WDYT? Thanks -Vincent

12 years, 11 months

6
7
0 0

[xwiki-devs] Contribution Translations

by Richard Hierlmeier

Hi guys, I tried to contribute some translations for the repository extension at http://l10n.xwiki.org. However the message keys for the repository extension are unknown. What is the proposed way to contribute translations for extensions? Here are the translations for German language: ## Translations for the livetables column titles extension.repository.emptyvalue= extension.repository.name=Name extension.repository.summary=Zusammenfassung extension.repository.type=Typ extension.repository.authors=Autoren extension.repository.doc.creationDate=Erzeugt am extension.repository.doc.date=Letzte Änderung ## Administration UI admin.repository=Repository mit Erweiterungen</content> Richard

12 years, 11 months

2
1
0 0

[xwiki-devs] Should we have a vm file or a REST URL for getting a page's content?

by Vincent Massol

Hi devs, Just realized that we don't have direct way of getting a page's content (only the content)… The best we can do is: http://playground.xwiki.org/xwiki/bin/view/Sandbox/WebHome?xpage=plain&outp… But that converts the content to XWiki Syntax. Shouldn't we have a vm for just displaying the content? Or even better a REST URL? Thanks -Vincent

12 years, 11 months

5
6
0 0

[xwiki-devs] Issue with maven generation of the javadoc for SRD

by Ludovic Dubost

Hi, I found an issue with the maven project to generate the javadocs for SRD. Apparently all the internal packages are ignored. This is no necessarly a problem unless we want them in the javadocs. Now there is a problem as some APIs are in internal, which does not seem normal. This is the case of: org.xwiki.officeimporter.internal.script.OfficeImporterScriptService org.xwiki.officeimporter.internal.openoffice.script.OpenOfficeManagerScriptService org.xwiki.office.viewer.internal.DefaultOfficeViewerScriptService Until we find a solution i've reverted to the javadocs manually generated (without the maven project). Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 11 months

6
10
0 0

[xwiki-devs] SRD (Scripting Reference Documentation) Annoucement

by Ludovic Dubost

Hi, I'm happy to announce the first release of the Scripting Reference Documentation (SRD). The objective of this documentation is to have a quick access to the relevant javadoc or documentation page to perfom XWiki scripting. The SRD is available at: http://platform.xwiki.org/xwiki/bin/view/SRD/Navigation?xpage=embed It contains: - javadoc links to Velocity and Groovy bindings, including the main API ($xwiki, $doc, $request, $response, $context) as well as XWiki services and plugins, as well as Velocity Tools. - links to the Velocity and Groovy language documentation This documentation is currently available for XWiki 4.1.x an 4.2.x. This is a very good tools for beginners with XWiki scripting. We do still recommend the development tutorials on the XWiki Dev Guide (http://platform.xwiki.org/xwiki/bin/view/DevGuide/WebHome). Please let us know on the dev list for any feedback on this new documentation. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 11 months

2
2
0 0

[xwiki-devs] Mark user as deactivated/spammer

by Felix AtCurriki

Hi all, At Curriki we currently work on a small tool which allows us to search users and apply changes to their "active/inactive" and "email_undeliverable" values easily without the need of editing the user objects manually. That gives us the following combinations for user states which are already in use (e.g. in the registration process): - User state: Active Values: (active:"Active", email_undeliverable:No) - User state: Inactive Values: (active:"Inactive", email_undeliverable:Yes) - The user needs to revalidate his email address Now if we want users to be marked as deactivated/spammers do you think would it be a good way to define an additional user state by expressing it through boolean combinations like this: - User state: Deactivated/Spammer Values: (active:"Inactive", email_undeliverable:*No*) Or do you think it would it be better to add an entry to the choices of the "active" value in the user object which explicitly says "deactivated" or "spammer". Or do you have any other best practice solutions? Thank you in advance!

12 years, 11 months

4
4
0 0

[xwiki-devs] SRD bugs for $services

by Vincent Massol

Hi (Ludovic), Cool that you applied http://platform.xwiki.org/xwiki/bin/view/SRD/Navigation?xpage=embed I've noticed some bugs in the services listing, like $services.class, $services.line, $services.currentmixed, etc. Also note that the Bindings filter is missing the $services binding. Thanks -Vincent

12 years, 11 months

2
10
0 0

[xwiki-devs] Connect to external database

by Peter Waver

Hello I’m very new to xwiki – found it yesterday ;) cause I’m search for a tool to display the content of our stock databases. This means - i only need a (read-only) front end to some databases here. I found the possibility, to add a custom app in xwiki. But - so far i see - the structure is added to the xwiki default DB. Now here is my question. Is it possible to use xwiki as a front-end or set up different data sources to connect to different databases? And how can i put values from the DB into a xwiki form? The devel Docs on the wiki side seams to covers an older xwiki version. I'm appreciated for any hint ... Thanks a lot Peter -- View this message in context: http://xwiki.475771.n2.nabble.com/Connect-to-external-database-tp7581689.ht… Sent from the XWiki- Dev mailing list archive at Nabble.com.

12 years, 11 months

3
3
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